DB2 SQL Errors Codes and Error Messages and Warnings from Error +562 to +599

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+562, SQLSTATE=01560, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
A GRANT OF A PRIVILEGE WAS
IGNORED BECAUSE THE GRANTEE
ALREADY HAS THE PRIVILEGE
FROM THE GRANTOR
Explanation: At least one of the privileges in the
GRANT statement was ignored because the privilege
was already granted to the grantee by the grantor.
System action: The privileges previously granted are
ignored; all others are granted.
SQLSTATE: 01560

Error: DB2 SQL Error: SQLCODE=+585, SQLSTATE=01625, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE COLLECTION collection-id
APPEARS MORE THAN ONCE WHEN
SETTING THE special-register SPECIAL
REGISTER
Explanation: The SET statement for special register
special-register includes collection-id more than once.
System action: Duplicates are removed from the list,
and the first occurrence of collection-id is used. The
statement is executed.
Programmer response: Verify the list that contains the
duplicate. If the error is only in entering a collection-id
incorrectly that happens to duplicate another entry,
enter the collection-id correctly and reissue the
statement. If the entry is intended to be a duplicate, no
action is required.
SQLSTATE: 01625

Error: DB2 SQL Error: SQLCODE=+599, SQLSTATE=01596, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
COMPARISON FUNCTIONS ARE NOT
CREATED FOR A DISTINCT TYPE
BASED ON A LONG STRING DATA
TYPE
Explanation: Comparison functions are not created for
a distinct type based on a long string data type (BLOB,
CLOB, DBCLOB) since the corresponding function are
not available for these built-in data types.
System action: The statement is processed
successfully.
Programmer response: No action is required.
SQLSTATE: 01596

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