db2 sql error messages
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
Db2 Sql Codes ListSQLCA block. SQLCODE is no longer part of the SQL-standard. The SQL-standard oracle sql error codes replaced SQLCODE by the more detailed SQLSTATE. Contents 1 SQLCA 2 SQLCODE 2.1 Zero (Successful) 2.2 Negative values (Errors) 2.3 sybase sql error codes Positive Values (Warnings) 3 References SQLCA The SQL communications area (SQLCA) structure is used within the DB2 program to return error information to the application program. This information in the SQLCA http://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/codes/src/tpc/db2z_n.html and the SQLCODE field is updated after every API call for the SQL statement... SQLCA contains ERROR HANDLING data SQLCODE The SQLCODE field contains the SQL return code. The code can be zero (0), negative or positive. 0 means successful execution. Negative means unsuccessful with an error. An example is -911 which means a timeout has occurred with a rollback. Positive means successful execution https://en.wikipedia.org/wiki/DB2_SQL_return_codes with a warning. An example is +100 which means no rows found or end of table Here is a more comprehensive list of the SQLCODEs for DB2: Zero (Successful) 0 Successful Negative values (Errors) -007 The specified 'character' is not a valid character in SQL statements. -010 THE string constant beginning with string is not terminated properly. -029 INTO Clause required. -060 INVALID type SPECIFICATION: spec -084 Unacceptable SQL statement. -101 The statement is too long or too complex. -102 String constant is too long. -104 Illegal symbol encountered in the SQL statement. -117 The number of values in the INSERT does not match the number of columns. -122 Column or Expression in the Select List is not valid -180 Bad data in Date/Time/Timestamp. -181 Bad data in Date/Time/Timestamp. -188 The host variable in a DESCRIBE statement is not a valid string representation of a name. -199 Illegal use of the specified keyword. -204 Object not defined to DB2. -205 Column name not in table. -206 Column does not exist in any table of the SELECT. -208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN column-name IS NOT PART OF
Programmers For Administrators For DBA Managers PRODUCTS Products Overview TestBase TestBase Slice Batch Healthcare - Attach Facility Batch Healthcare - Attach Facility's MRF Feature Batch Healthcare - Batch Analyzer Batch Healthcare - Checkpoint Facility Batch Healthcare - Deadlock Advisor SoftDate RESOURCES Resources Overview https://www.softbase.com/error_codes.php DB2 SQL Error Codes White Papers Case Studies Educational Videos PARTNERS Partners Overview Partner List Becoming a Partner Register a Prospect NEWS News Releases SUPPORT Support Overview Support Login Product Compatibility BLOG Baseline Posts Baseline Videos https://confluence.atlassian.com/confkb/how-to-interpret-db2-error-codes-182931.html ABOUT US About SoftBase People Careers Legal Privacy Area Info Contact Info Contact Us Home Resources DB2 SQL Error Codes DB2 SQL Error Codes SQL return codes provided by DB2 UDB for OS/390 and z/OS can be sql error confusing and often reference manuals are not available or close at hand when you really need them. This reference will review SQL return code processing and common SQL error condition codes you may encounter in DB2. SQL Error Code Lookup Retrieving SQL Return Code Information & Messages COBOL programs executing SQL statements communicate with DB2 via a Working Storage area called the SQL Communications Area (SQLCA). When DB2 executes SQL statements, it returns sql error codes the results of the operation into the SQLCODE and SQLSTATE fields in the SQLCA. SQLCODE provides key information about the success or failure of SQL statement execution. If the SQLWARNO field in the SQLCA contains 'W', DB2 has set at least one of the SQL warning flags (SQLWARN1 through SQLWARNA). These flags provide additional info about execution of specific types of SQL. Prior to DB2 V8, COBOL programs could call a subroutine called DSNTIAR that would convert a SQLCODE in the SQLCA into more a detailed text message with diagnostics about the return code. New with DB2 V8, COBOL programs can now execute a GET DIAGNOSTICS statement that will return all previous SQLCA values and provide additional information about new DB2 V8 extended object names and new SQL functions. The new GET DIAGNOSTICS function replaces existing SQLCA processing now found in most DB2 COBOL programs. GET DIAGNOSTICS also passes a text message about SQLCODE directly to programs. SQLCODE Overview If SQLCODE = 0, execution was successful. If SQLCODE > 0, execution was successful with a warning. If SQLCODE < 0, execution was not successful. If SQLCODE = 100, "no data" was found. For example, a FETCH statement returned no data because the cursor was positioned after the last row of the result table. New with DB2 V8, when DB2
the error code from the db2 command prompt with "? sqlxxxx" where xxxx is the SQLCODE from the error message: [db2inst1@matilda db2inst1]$ db2 ? sql-803 SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "