DB2 SQL Errors Codes and Error Messages and Warnings from Error +20460 to +30100

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+20460, SQLSTATE=01H56, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE PROCEDURE procedure-name
SUPPORTS A HIGHER VERSION,
version1. THAN THE SPECIFIED
VERSION, version2, FOR PARAMETER
number.
Explanation: A higher version, version1, for the
parameter in ordinal position number is supported by
the procedure procedure-name. The specified version,
version2, is supported for the parameter.
User response: Check the documentation for the
procedure to understand the additional features
supported by the newer version of the parameter.
Upgrade to the current version to take advantage of
these additional features.
SQLSTATE: 01H56

Error: DB2 SQL Error: SQLCODE=+20461, SQLSTATE=01H57, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE PROCEDURE procedure-name
RETURNED OUTPUT IN THE
ALTERNATE LOCALE, locale1,
INSTEAD OF THE LOCALE locale2,
SPECIFIED IN PARAMETER number.
Explanation: The locale, locale2, specified in the
parameter in ordinal position number was not available
for the output of the procedure procedure-name. The
output is returned using locale locale1.
User response: Install the message file support on the
server for the specified locale, locale2, or specify a
supported locale.
SQLSTATE: 01H57

Error: DB2 SQL Error: SQLCODE=+20520, SQLSTATE=01694, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ATTEMPT TO USE A DEPRECATED
FEATURE ON OBJECT object-name.
REASON CODE reason-code
Explanation: The statement attempted to use a
deprecated feature.
reason-code
A numeric value that identifies the deprecated
feature:
1 The statement attempted use the XML
schema decomposition feature.
Processing continues and the stored
procedure was invoked. This situation
can occur when the following stored
procedures are called:
v SYSPROC.XSR_COMPLETE with
the issuedfordecomposition flag set
to 1
v SYSPROC.XDBDECOMPXML
v
SYSPROC.XDBDECOMPXML100MB
System action: Processing continues as described in
the explanation.
User response: No change is required at this time.
However, you should update the statement to prepare
for future releases, when an error will be returned for
the same condition.
Programmer response: Change the statement for
future releases. Take the action that corresponds to the
reason-code value:
1 Update your SQL statement to change any
implicit or explicit reference to the XML
schema decomposition feature so that they use
the XMLTABLE function for the decomposition
of an XML document.
SQLSTATE: 01694

Error: DB2 SQL Error: SQLCODE=+30100, SQLSTATE=01558, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
OPERATION COMPLETED
SUCCESSFULLY BUT A
DISTRIBUTION PROTOCOL
VIOLATION HAS BEEN DETECTED.
ORIGINAL SQLCODE=original-sqlcode
AND ORIGINAL SQLSTATE=originalsqlstate
Explanation: The application requested operation
(either COMMIT or ROLLBACK) has completed
successfully but the response from the remote server
and the SQLCODE that was returned from the remote
server are inconsistent. For example, the reply message
from the remote server indicates that a COMMIT
operation completed successfully but the SQLCODE
returned from the AS was negative.
System action: An alert was generated. A DSNL031I
message may have been written to the console. Refer to
the description of this message for further information.
The SQLCODE returned by the remote server is
replaced with +30100 and the SQLSTATE returned by
the remote server is replaced with 01558.
The SQLCODE and SQLSTATE values that were
returned from the AS are stored in the SQLERRM field
in a string of the following format: original-sqlcode ‘FF’X
original-sqlstate
Programmer response: Notify the System Programmer
for assistance in analyzing the trace data that was
generated.
SQLSTATE: 01558

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