DB2 SQL Errors Codes and Error Messages and Warnings from Error +20365 to +20371
Error: DB2 SQL Error: SQLCODE=+20365, SQLSTATE=01565, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
A SIGNALING NAN WAS
ENCOUNTERED, OR AN EXCEPTION
OCCURRED IN AN ARITHMETIC
OPERATION OR FUNCTION
INVOLVING A DECFLOAT.
Explanation: A signaling NaN (sNaN) was
encountered in an expression, arithmetic operation, or
function involving a DECFLOAT column, or value
resulted in an exception. In either case, the result is
NAN, and a warning is issued.
System action: Execution of the statement continues.
All non-error columns and expressions of the outer
SELECT list are returned. If the statement is cursor
controlled, then the cursor will remain open.
User response: Examine the expression for which the
warning occurred to see you can determine the cause
of the problem. The problem might be data-dependent,
in which case you must examine the data that was
being processed at the time the error occurred.
Error: DB2 SQL Error: SQLCODE=+20367, SQLSTATE=01680, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
OPTION clause IS NOT SUPPORTED
IN THE CONTEXT IN WHICH IT WAS
Explanation: The clause in the statement is not
supported in the context in which has been specified.
The clause is ignored.
System action: Processing continues normally.
Programmer response: No change is required for the
current release; however, it is recommended that the
statement be modified to conform to valid SQL syntax.
Error: DB2 SQL Error: SQLCODE=+20371, SQLSTATE=01682, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE ABILITY TO USE TRUSTED
CONTEXT context-name WAS
REMOVED FROM SOME, BUT NOT
ALL AUTHORIZATION IDS
SPECIFIED IN THE STATEMENT.
Explanation: An ALTER TRUSTED CONTEXT
statement for context name contained a DROP USE FOR
clause with multiple authorization IDs or PUBLIC, but
one or more authorization IDs were not defined to use
the trusted context.
System action: The statement is processed.
Programmer response: One or more users were
removed from the definition of the trusted context, but
one or more other users were not previously allowed to
use the trusted context.
Above are list of DB2 SQL Errors and Warnings from Error +20365 to +20371 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.