DB2 SQL Errors Codes and Error Messages and Warnings from Error +653 to +658
Error: DB2 SQL Error: SQLCODE=+653, SQLSTATE=01551, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
TABLE table-name IN PARTITIONED
TABLESPACE tspace-name IS NOT
AVAILABLE BECAUSE ITS
PARTITIONED INDEX HAS NOT
Explanation: An attempt has been made to insert or
manipulate data in or create a view on a partitioned
table (that is, a table residing in a partitioned table
space) before the partitioned index for that table has
A table residing in a partitioned table space cannot be
referenced in any SQL manipulative statement or a
CREATE VIEW statement before the partitioned index
for that table has been created.
System action: A valid plan or package will be
created if no errors are detected. The statement is
bound dynamically on each execution of the statement.
Programmer response: For better performance, rebind
the plan or package after correcting the statement. To
correct the statement, verify that the correct table was
specified in the statement. If so, ensure that the
partitioned index for the table has been created
successfully before attempting to execute any SQL
manipulative statements that reference that table.
Error: DB2 SQL Error: SQLCODE=+655, SQLSTATE=01597, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
STOGROUP stogroup_name HAS BOTH
SPECIFIC AND NON-SPECIFIC
VOLUME IDS. IT WILL NOT BE
ALLOWED IN FUTURE RELEASES
Explanation: The CREATE or ALTER STOGROUP
statement has caused the STOGROUP with
stogroup_name to have both specific and non-specific
(‘*’) volume Ids. This warning code is used to specify
that the mixing of different types of volume Ids will
not be allowed in future releases.
System action: DB2 continues processing.
Programmer response: Plan to use either specific or
non-specific volume ids to avoid future release
migration impact. ALTER STOGROUP may be used to
drop all specific volume ids or all non-specific volume
Error: DB2 SQL Error: SQLCODE=+658, SQLSTATE=01600, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE SUBPAGES VALUE IS IGNORED
FOR THE CATALOG INDEX index-name
Explanation: Only SUBPAGES 1 is allowed for this
System action: The index was altered successfully
using SUBPAGES 1. If you are also altering the TYPE
option to a new value, the index is placed in recovery
Above are list of DB2 SQL Errors and Warnings from Error +653 to +658 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.
Information about DB2 SQL Error Codes and Error Messages on Windows, Linux and Z/OS Operating Systems.