DB2 SQL Errors Codes and Error Messages and Warnings from Error -511 to -513

SQLServerF1

Error: DB2 SQL Error: SQLCODE=-511, SQLSTATE=42829, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE FOR UPDATE CLAUSE CANNOT
BE SPECIFIED BECAUSE THE RESULT
TABLE DESIGNATED BY THE SELECT
STATEMENT CANNOT BE MODIFIED
SQLSTATE: 42829

Error: DB2 SQL Error: SQLCODE=-512, SQLSTATE=56023, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
STATEMENT REFERENCE TO
REMOTE OBJECT IS INVALID
SQLSTATE: 56023

Error: DB2 SQL Error: SQLCODE=-513, SQLSTATE=42924, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE ALIAS alias-name MUST NOT BE
DEFINED ON ANOTHER LOCAL OR
REMOTE ALIAS
SQLSTATE: 42924

Above are list of DB2 SQL Errors and Warnings from Error -511 to -513 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 *