L600 - L649
Lists the Link error messages from L600 through L649.
Restriction:
This topic applies to Windows environments only.
L601: Name of the object to be created identical to existing name name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -601, for information.
L602: Too many columns specified in a CREATE INDEX.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -602, for information.
L603: Unique index cannot be created. The table has rows with duplicate columns.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -603, for information.
L604: Column definition specifies an invalid length, precision, or scale attribute.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -604, for information.
L607: Operation operation is not defined for system tables.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -607, for information.
L611: ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN LOCK SIZE IS TABLESPACE OR TABLE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -611, for information.
L612: name is a duplicate column name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -612, for information.
L613: The primary key is too long or has too many columns.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -613, for information.
L614: Cannot create index. Sum of internal lengths of columns > allowable.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -614, for information.
L615: op is not allowed on a package in use.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -615, for information.
L616: obj-typeobj-name CANNOT BE DROPPED; REFERENCED BY obj-typeobj-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -616, for information.
L617: TYPE 1 INDEX IS NOT VALID FOR TABLE table-name
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -617, for information.
L618: Operation operation is not allowed on system databases.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -618, for information.
L619: Operation disallowed because the workfile database is not stopped.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -619, for information.
L620: Keyword keyword not allowed for tablespace in workfile database.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -620, for information.
L621: Duplicate dbid dbid was detected and previously assigned to dbname.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -621, for information.
L622: FOR MIXED DATA is invalid because MIXED DATA inst opt is NO.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -622, for information.
L623: A clustering index already exists on table name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -623, for information.
L624: Table name already has a primary key.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -624, for information.
L625: TABLE table-name DOES NOT HAVE INDEX TO ENFORCE UNIQUENESS OF PARENT KEY
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -625, for information.
L626: ALTER statement is not executable because the pageset is not stopped.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -626, for information.
L627: ALTER statement is invalid because the pageset has user-managed data set.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -627, for information.
L628: THE CLAUSES ARE MUTUALLY EXCLUSIVE
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -628, for information.
L629: No set NULL because foreign key name cannot contain NULL values.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -629, for information.
L630: WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1 INDEXES
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -630, for information.
L631: Foreign key name is too long or has too many columns.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -631, for information.
L632: Cannot define table as dependent of name due to delete rule restriction.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -632, for information.
L633: The delete rule must be delete.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -633, for information.
L634: The delete rule must not be cascade.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -634, for information.
L635: The delete rules cannot be different or cannot be set NULL.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -635, for information.
L636: Partitioning keys not specified in ascending/descending order.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -636, for information.
L637: Duplicate keyword keyword.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -637, for information.
L638: Table name cannot be created. Column definition is missing.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -638, for information.
L639: Column of foreign key with delete rule of set NULL cannot be in partition index.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -639, for information.
L640: LOCKSIZE ROW CANNOT BE SPECIFIED; TABLE HAS TYPE 1 INDEX
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -640, for information.
L642: TOO MANY COLUMNS IN UNIQUE CONSTRAINTS
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -642, for information.
L643: CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -643, for information.
L644: INVALID VALUE SPECIFIED FOR KEYWORD keyword IN statement-type STATEMENT
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -644, for information.
L646: Cannot create table name in partitioned default tablespace name.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -646, for information.
L647: Bufferpool name cannot be specified. It has not been activated.
See the section Error SQLCODES in your IBM Database Messages and Codes manual, message -647, for information.
Parent topic:
L - Link Error Messages