DB2 SQL Errors Codes and Error Messages and Warnings from Error +20378 to +20459

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+20378, SQLSTATE=01683, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
A NON-ATOMIC statement
STATEMENT SUCCESSFULLY
COMPLETED FOR SOME OF THE
REQUESTED ROWS, POSSIBLY WITH
WARNINGS, AND ONE OR MORE
ERRORS, AND THE CURSOR CAN BE
USED
Explanation: A non-atomic statement statement
successfully processed some of the rows of data that
were requested. However, one or more error conditions
occurred, and some warnings might have also
occurred. Use GET DIAGNOSTICS to obtain
information about the error and warning conditions
that occurred. The cursor can be used to retrieve data
for the rows that were successfully processed.
System action: One or more rows were successfully
processed, but one or more errors or warnings also
occurred.
Programmer response: Analyze the error and warning
conditions to determine if the statement should be
rolled back.
SQLSTATE:: 01683

Error: DB2 SQL Error: SQLCODE=+20458, SQLSTATE=01H54, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE PROCEDURE procedure-name HAS
ENCOUNTERED AN INTERNAL
PARAMETER PROCESSING ERROR
IN PARAMETER number1. THE VALUE
FOR PARAMETER number2 CONTAINS
FURTHER INFORMATION ABOUT
THE ERROR.
Explanation: The format or content of the parameter
in ordinal position number1 in the call to the procedure
procedure-name is invalid. The output parameter
specified in ordinal position number2 contains
information on how to respond to the error.
User response: Use the information in the output
parameter specified in ordinal position number2 to
correct the format or content of the parameter value
and call the procedure again.
SQLSTATE: 01H54

Error: DB2 SQL Error: SQLCODE=+20459, SQLSTATE=01H55, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE PROCEDURE procedure-name HAD
ENCOUNTERED AN INTERNAL
PROCESSING ERROR. THE VALUE
FOR PARAMETER number CONTAINS
FURTHER INFORMATION ABOUT
THE ERROR.
Explanation: An error occurred when the procedure
procedure-name was processing a request. The output
parameter specified in ordinal position number contains
information on how to respond to the error.
User response: An error occurred when the procedure
procedure-name was processing a request. The output
parameter specified in ordinal position number
contains information on how to respond to the error.
number to correct the error and call the procedure
again.
SQLSTATE: 01H55

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