DB2 SQL Errors Codes and Error Messages and Warnings from Error -491 to -495
Error: DB2 SQL Error: SQLCODE=-491, SQLSTATE=42601, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
CREATE STATEMENT FOR
function-name MUST HAVE A RETURNS
CLAUSE AND: THE EXTERNAL
CLAUSE WITH OTHER REQUIRED
KEYWORDS; THE RETURN
STATEMENT AND PARAMETER
NAMES; OR THE SOURCE CLAUSE
Error: DB2 SQL Error: SQLCODE=-492, SQLSTATE=42879, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE CREATE FUNCTION FOR
function-name HAS A PROBLEM WITH
PARAMETER NUMBER number. IT
MAY INVOLVE A MISMATCH WITH
A SOURCE FUNCTION
Error: DB2 SQL Error: SQLCODE=-495, SQLSTATE=57051, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ESTIMATED PROCESSOR COST OF
SECONDS (estimate-amount2 SERVICE
UNITS) IN COST CATEGORY
cost-category EXCEEDS A RESOURCE
LIMIT ERROR THRESHOLD OF limitamount
Above are list of DB2 SQL Errors and Warnings from Error -491 to -495 received while performing certain operation against DB2 Database or related products.
SQLCODE – Regardless of whether the application program provides an SQLCA or a stand-alone variable, SQLCODE is set by DB2 after each SQL statement is
executed. DB2 conforms to the ISO/ANSI SQL standard as follows:
If SQLCODE = 0, execution was successful.
If SQLCODE > 0, execution was successful with a warning.
If SQLCODE < 0, execution was not successful.
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.
SQLSTATE – SQLSTATE is also set by DB2 after the execution of each SQL statement. Thus, application programs can check the execution of SQL statements by testing SQLSTATE instead of SQLCODE.
Hope this was helpful.
Information about DB2 SQL Error Codes and Error Messages on Windows, Linux and Z/OS Operating Systems.