Micro Focus Enterprise Test Server 2.3 Update 2
>
Data Access
>
Database Access
>
SQL Option for DB2
>
Reference
>
Error Messages
>
L - Link Error Messages
>
L650 - L699
L650 - L699
Lists the Link error messages from L650 through L699.
L650: THE ALTER INDEX CANNOT BE EXECUTED, REASON reason-code
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -650, for information.
L651: TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -651, for information.
L652: Violation of installation-defined edit or validation procedure proc.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -652, for information.
L653: Table name in partitioned tablespace name not available.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -653, for information.
L655: CREATE OR ALTER STOGROUP IS INVALID
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -655, for information.
L658: object-type CANNOT BE DROPPED USING THE statement STATEMENT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -658, for information.
L660: Cannot create index name on partitioned tablespace name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -660, for information.
L661: Cannot create index name on partitioned tablespace name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -661, for information.
L662: Cannot create a partitioned index on a non-partitioned tablespace name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -662, for information.
L663: Number of key limit values is 0, or > number of columns in key of index.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -663, for information.
L664: Internal length of limit-key fields for partitioned index name is too long.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -664, for information.
L665: The PART clause of an ALTER statement is omitted or invalid.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -665, for information.
L666: stmt-verbobject cannot be executed because of something in progress.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -666, for information.
L667: Clustering index for partitioned tablespace cannot be explicitly dropped.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -667, for information.
L668: Cannot add column to the table because the table has an edit procedure.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -668, for information.
L669: A table in a partitioned tablespace cannot be explicitly dropped.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -669, for information.
L670: The record length of the table exceeds the page size limit.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -670, for information.
L671: Cannot alter buffpool attr of tablespace because pg size of tablespace would change.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -671, for information.
L672: OPERATION DROP NOT ALLOWED ON TABLE table-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -672, for information.
L676: A 32K page bufferpool may not be used for an index.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -676, for information.
L677: Insufficient virtual storage for bufferpool expansion.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -677, for information.
L678: literal specified for index limit key must conform to data type type.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -678, for information.
L679: Object name cannot be created. A drop is pending on the object.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -679, for information.
L680: Too many columns specified for a table.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -680, for information.
L681: Column name in violation of installation-defined field procedure name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -681, for information.
L682: Field procedure proc could not be loaded.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -682, for information.
L683: Invalid column type for fieldproc or bit data option, column.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -683, for information.
L684: The length of literal list beginning string is too long.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -684, for information.
L685: Invalid field type column.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -685, for information.
L686: Cannot compare column defined by one field procedure to one defined by another.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -686, for information.
L687: Field types incomparable.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -687, for information.
L688: Incorrect data returned from field procedure, column, msgno.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -688, for information.
L689: Too many columns defined for a dependent table.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -689, for information.
L690: Statement is rejected by data def ctrl support, reason reason.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -690, for information.
L691: The required registrations table table does not exist.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -691, for information.
L692: Unique index index-name in table table-name does not exist.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -692, for information.
L693: Column column is not defined properly.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -693, for information.
L694: DDL STMT CANNOT EXECUTE; DROP PENDING ON DDL REGISTRATION TABLE table-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -694, for information.
L696: TRIGGER trigger-name CONTAINS INVALID USE OF NAME name, REASON reason-code
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -696, for information.
L697: CORR. NAMES NOT ALLOWED IN TRIGGER WITH "FOR EACH STATEMENT" OR "BEFORE"
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -697, for information.
Parent topic:
L - Link Error Messages
