DB2 SQL Errors Codes and Error Messages and Warnings from Error +807 to +883

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+807, SQLSTATE=01554, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE RESULT OF DECIMAL
MULTIPLICATION MAY CAUSE
OVERFLOW
Explanation: An arithmetic expression contains a
decimal multiplication that may cause an overflow
condition when the statement is executed. The problem
may be corrected by restructuring the arithmetic
expression so that decimal multiplication precedes
decimal division or by changing the precision and scale
of the operands in the arithmetic expression. Refer to
chapter 2 of SQL Reference for the precision and scale of
the decimal multiplication and division results.
System action: A valid package will be created if no
errors are detected.
SQLSTATE: 01554

Error: DB2 SQL Error: SQLCODE=+863, SQLSTATE=01539, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE CONNECTION WAS
SUCCESSFUL BUT ONLY SBCS WILL
BE SUPPORTED
Explanation: The target AS supports only the DB2
SBCS CCSID. The DB2 Mixed CCSID or GRAPHIC
CCSID or both are not supported by the target AS. DB2
character data sent to the target AS must be restricted
to SBCS.
System action: The CONNECT statement is
successful. The release level of the target AS has been
placed into the SQLERRP field of the SQLCA (see SQL
Reference for the CONNECT statement).
Programmer response: Do not execute any SQL
statements which pass either mixed data or graphic
data as input host variables.
SQLSTATE: 01539

Error: DB2 SQL Error: SQLCODE=+883, SQLSTATE=01640, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ROLLBACK TO SAVEPOINT
OCCURRED WHEN THERE WERE
OPERATIONS THAT CANNOT BE
UNDONE, OR AN OPERATION THAT
CANNOT BE UNDONE OCCURRED
WHEN THERE WAS A SAVEPOINT
OUTSTANDING
Explanation: The operations that are referred to are
updates (inserts into or deletes from) a created global
temporary table. If this SQL warning code is received
as the result of a ROLLBACK TO SAVEPOINT
statement, the rollback is performed; however, the
changes that were made to the temporary table are not
undone. If this SQL warning code is received as the
result of an operation to a created global temporary
table, the operation is performed; however, be advised
that a savepoint is outstanding, and the update will not
be backed out if a rollback to the savepoint is
performed.
System action: The SQL statement is processed.
Programmer response: Verify that this is what you
meant.
SQLSTATE: 01640

Above are list of DB2 SQL Errors and Warnings from Error +807 to +883 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.

Thanks,
SQLServerF1 Team
Information about DB2 SQL Error Codes and Error Messages on Windows, Linux and Z/OS Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *