DB2 SQL return codes


SQL Return Codes are used on a day-to-day basis for the diagnosis of programming failures as a result of SQL calls by DB2 computer programs. An important feature of DB2 programs is the error processing. The error diagnostic containing the SQL Return Code is held in the field SQLCODE within the DB2 SLCA block.
SQLCODE is no longer part of the SQL-standard. The SQL-standard replaced SQLCODE by the more detailed SQLSTATE.

SQLCA

The SQL communications area structure is used within the DB2 program to return a feedback to the application program.

SQLCODE

The SQLCODE field contains the SQL return code. The code can be zero, negative or positive:
An example is -911, which means that a timeout has occurred with a rollback.
An example is +100, which means that no matching rows were found or that the cursor has reached the end of the table.
Here is a more comprehensive list of the SQLCODEs for DB2. Note that this list is not exhaustive. Also note that some SQLCODEs may only occur in specific DB2 products; e.g., only on DB2 z/OS, only on DB2 LUW, or only on DB2 iSeries.

Zero (Successful)

0 Successful

Negative values (Errors)

-007The specified 'character' is not a valid character in SQL statements.
-010THE string constant beginning with string is not terminated properly.
-029INTO Clause required.
-060INVALID type SPECIFICATION : spec
-084Unacceptable SQL statement.
-101The statement is too long or too complex.
-102String constant is too long.
-103String constant is too long. Max is 128 characters.
-104Illegal symbol encountered in the SQL statement.
-105String constant is too long.
-117The number of values in the INSERT does not match the number of columns.
-122Column or Expression in the Select List is not valid
-156Invalid syntax near keyword.
-180Bad data in Date/Time/Timestamp.
-181Bad data in Date/Time/Timestamp.
-188The host variable in a DESCRIBE statement is not a valid string representation of a name.
-199Illegal use of the specified keyword.
-203A REFERENCE TO COLUMN column-name IS AMBIGUOUS
-204Object not defined to DB2.
-205Column name not in table.
-206Column does not exist in any table of the SELECT.
-207Invalid column name.
-208THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN column-name IS NOT PART OF THE RESULT TABLE
-209Ambiguous column name
-216Not the same number of expressions on both sides of the comparison in a SELECT.
-224FETCH cannot make an INSENSITIVE cursor SENSITIVE.
-229The locale specified in a SET LOCALE statement was not found.
-257Implicit conversion in datatype is not allowed.
-302THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER position-number IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE
-303A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position-number BECAUSE THE DATA TYPES ARE NOT COMPARABLE
-305Null indicator needed.
-311Varchar, insert or update. -LEN field with the right data length not set.
-313The number of host variables specified is not equal to the number of parameter markers.
-401The data types of the operands of an operation are not compatible.
-404The Sql Statement specified contains a String that is too long.
-407AN UPDATE, INSERT, OR SET VALUE IS NULL, BUT THE OBJECT COLUMN column-name CANNOT CONTAIN NULL VALUES
-408A value is not compatible with the data type of its assignment target. Target name is "".
-418Use of parameter marker not valid.
-420The value of a string argument was not acceptable to the 'function-name' function
-438Application raised error with diagnostic text: text
-440Routine &1 in &2 not found with specified parameters.A function or procedure with the specified name and compatible arguments was not found.
-482The procedure returned no locators.
-501Cursor not open on FETCH.
-502Opening cursor that is already open.
-503Updating column needs to be specified.
-504Cursor name not declared.
-510The Table designated by the cursor of the Update or Delete statement cannot be modified.
-530Referential integrity preventing the INSERT/UPDATE
-532Referential integrity preventing the DELETE.
-536Referential integrity preventing the DELETE.
-545Check constraint preventing the INSERT/UPDATE.
-551Authorization failure.
-554An authorization ID or a role cannot GRANT a privilege to itself.
-601You tried to create an object that already exists
-602Too many columns specified in a create index.
-603a unique index cannot be created because the table contains rows which are duplicates with respect to the values of the identified columns and periods
-604a data type definition specifies an invalid length, precision, or scale attribute
-607operation or option operation is not defined for this object
-610warning: a create/alter on object has placed object in pending
-611only lockmax 0 can be specified when the lock size of the tablespace is tablespace or table
-612identifier is a duplicate name
-613the primary key or a hash key or a unique constraint is too long or has too many columns and periods
-614the index cannot be created or altered, or the length of a column cannot be changed because the sum of the internal lengths of the columns for the index is greater than the allowable maximum
-615operation-type is not allowed on a package in use
-616obj-type1 obj-name1 cannot be dropped because it is referenced by obj-type2 obj-name2
-617a type 1 index is not valid for table
-618operation operation is not allowed on system databases
-619operation disallowed because the database is not stopped
-620keyword keyword in stmt-type statement is not permitted for a space-type space in the database-type database
-621duplicate dbid dbid was detected and previously assigned to database-name
-622for mixed data is invalid because the mixed data install option is no
-623cluster is not valid for table-name
-624table table-name already has a primary key or unique constraint with specified columns and periods
-625table table-name does not have an index to enforce the uniqueness of the primary or unique key
-625warning: the definition of table has been changed to incomplete
-626the alter statement is not executable because the page set is not stopped
-627the alter statement is invalid because the table space or index has user-managed data sets
-628the clauses are mutually exclusive
-629set null cannot be specified because foreign key name cannot contain null values
-630error: the WHERE NOT NULL specification is invalid for type 1 indexes
-631foreign key name is too long or has too many columns
-632the table cannot be defined as a dependent of table-name because of DELETE rule restrictions
-633the DELETE rule must be DELETE-rule
-634the DELETE rule must not be cascade
-635the DELETE rules cannot be different or cannot be set null
-636ranges specified for partition part-num are not valid
-637duplicate keyword-name keyword or clause
-638table table-name cannot be created because column definition is missing
-639a nullable column of a foreign key with a DELETE rule of set null cannot be a column of the key of a partitioned index
-640locksize row cannot be specified because table in this tablespace has type 1 index
-642too many columns in unique constraints
-643a check constraint or the value of an expression for a column of an index exceeds the maximum allowable length key expression
-644invalid value specified for keyword or clause keyword-or-clause in statement stmt-type
-645WHERE NOT NULL is ignored because the index key cannot contain null values
-646table table-name cannot be created in specified table space table-space-name because it already contains a table
-647bufferpool bp-name for implicit or explicit tablespace or indexspace name has not been activated
-650the alter statement cannot be executed, reason reason-code copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited
-651table description exceeds maximum size of object descriptor.
-652violation of installation defined edit or validation procedure proc-name
-653table table-name in partitioned table space tspace-name is not available because its partitioned index has not been created
-655the create or alter stogroup is invalid because the storage group would have both specific and non-specific volume ids
-658a object-type cannot be dropped using the statement statement
-660index index-name cannot be created or altered on partitioned table space tspace-name because key limits are not specified
-661object-type object-name cannot be created on partitioned table space tspace-name because the number of partition specifications is not equal to the number of partitions of the table space
-662a partitioned index cannot be created on a table space, or a table space cannot be index-controlled. table space tspace-name, reason reason-code
-663the number of key limit values is either zero, or greater than the number of columns in the key of index index-name
-664the internal length of the limit-key fields for the partitioned index exceeds the length imposed by the index manager
-665the partition clause of an alter statement is omitted or invalid
-666stmt-verb object cannot be executed because function is in progress
-667the clustering index for a partitioned table space cannot be explicitly dropped
-668the column cannot be added to the table because the table has an edit procedure defined with row attribute sensitivity
-669the object cannot be explicitly dropped. reason reason-code
-670the record length of the table exceeds the page size limit
-671the bufferpool attribute of the table space cannot be altered as specified because it would change the page size of the table space
-672operation drop not allowed on table table_name
-676the physical characteristics of the index are incompatible with respect to the specified statement. the statement has failed. reason reason-code
-677insufficient virtual storage for bufferpool expansion
-678the constant specified for the index limit key must conform to the data type data-type of the corresponding column column-name
-679the object name cannot be created because a drop is pending on the object
-680too many columns specified for a table, view or table function
-681column column-name in violation of installation defined field procedure. rt: return-code, rs: reason-code, msg: message-token
-682field procedure procedure-name could not be loaded
-683the specification for column, distinct type, function, or procedure data-item contains incompatible clauses
-684the length of constant list beginning string is too long
-685invalid field type, column-name
-686column defined with a field procedure can not compare with another column with different field procedure
-687field types incomparable
-688incorrect data returned from field procedure, column-name, msgno
-689too many columns defined for a dependent table
-690the statement is rejected by data definition control support. reason reason-code
-691the required registration table table-name does not exist
-692the required unique index index-name for ddl registration table table-name does not exist
-693the column column-name in ddl registration table or index name is not defined properly
-694the schema statement cannot be executed because a drop is pending on the ddl registration table table-name
-694the ddl statement cannot be executed because a drop is pending on the ddl registration table
-695invalid value seclabel specified for security label column of table table-name
-696the definition of trigger trigger-name includes an invalid use of correlation name or transition table name name. reason code=reason-code
-697old or new correlation names are not allowed in a trigger defined with the for each statement clause. old_table or new_table names are not allowed in a trigger with the before clause.
-747The table is not available.
-803Duplicate key on insert or update.
-804Error in input parameters for the SQL statement.
-805DBRM or package not found in plan.
-811More than one row retrieved in SELECT INTO.
-818Plan and program: timestamp mismatch.
-904Unavailable resource. Someone else is locking your data.
-911Deadlock or timeout. Rollback has been done.
-913Deadlock or timeout. No rollback.
-922Authorization needed.
-924DB2 Connection internal error.
-927The language interface was called but no connection had been made.
-964The transaction log space is depleted or temporary increase in the number of active transactions.
-998Error occurred during transaction or heuristic processing.
-7008The object that is specified is not valid for the requested operation.
-10330Permission denied to change database. Contact system administrator.
-30090Remote operation invalid for application execution environment.

Positive Values (Warnings)

+98A dynamic SQL statement ends with a semicolon
+100Row not found or end of cursor.
+222Trying to fetch a row within a DELETE statement.
+223Trying to fetch a row within an UPDATE statement.
+231FETCH after a BEFORE or AFTER but not on a valid row.
+304A value with data type cannot be assigned to a host variable because the value is not within the range of the host variable in position with data type
+354A rowset fetch statement may have returned one or more rows of data. however, one or more warning conditions were also encountered. use the get diagnostics statement for more information regarding the conditions that were encountered
+562A grant of a privilege was ignored because the grantee already has the privilege from the grantor.
+802The null indicator was set to -2 as an arithmetic.