DB2 SQL Errors Codes and Error Messages and Warnings from Error +610 to +650

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+610, SQLSTATE=01566, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
A CREATE/ALTER ON OBJECT
object-name HAS PLACED OBJECT IN
utility-name PENDING
Explanation: As the result of a CREATE or ALTER
action, the specified object has been placed in a
pending status.
object-name
The name of the object.
utility-name
The name of the utility.
The reason for this error depends on the utility-name
value and the object type.
REBUILD pending for an index
v The index is in REBUILD PENDING status
because CREATE INDEX with DEFER was
specified on a populated table.
v The index is in REBUILD PENDING status
because ALTER TABLE ALTER COLUMN
SET DATA TYPE increased a VARCHAR
length column which is part of an index
while in conversion mode.
The index is not generally available until the
index is removed from the REBUILD pending
state.
REORG pending for a table space partition
The table space is in REORG pending because
ALTER INDEX was used to change the limit
key values. The table space partition is not
generally available until the REORG pending
status is removed.
REORG pending for a table space
The table space is in REORG pending because
ALTER TABLE was used to add an identity
column to a populated table. The table space is
not generally available until the REORG
pending status is removed.
System action: The object was placed in the indicated
pending status.
Programmer response: The response for this error
depends on the utility-name value and the object type.
REBUILD pending for an index
Use the REBUILD INDEX utility to rebuild the
index and remove the REBUILD pending
status.
REORG pending for a table space partition
Perform the following steps:
1. Issue a DISPLAY DATABASE command for
the table space to identify which partitions
are in REORG pending.
2. Run the REORG utility on the partitions
that are in REORG pending.
REORG pending for a table space
Run the REORG utility on the table space.
SQLSTATE: 01566

Error: DB2 SQL Error: SQLCODE=+645, SQLSTATE=01528, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
WHERE NOT NULL IS IGNORED
BECAUSE THE INDEX KEY CANNOT
CONTAIN NULL VALUES OR THE
INDEX IS AN XML INDEX
Explanation: The WHERE NOT NULL clause is
ignored on the CREATE INDEX statement because the
index key is defined on columns that cannot contain
null values, or, the index is an XML index.
System action: The option is ignored; processing
continues.
Programmer response: Remove the WHERE NOT
NULL clause to get rid of the warning.
SQLSTATE: 01528

Error: DB2 SQL Error: SQLCODE=+650, SQLSTATE=01538, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE TABLE BEING CREATED OR
ALTERED CANNOT BECOME A
DEPENDENT TABLE
Explanation: This table is defined with the maximum
number of columns. It cannot be altered to be a
dependent table later.
System action: The table is created. Check to see if the
table will become a dependent table at a later time. If
yes, drop and recreate the table with fewer than 750
columns.
SQLSTATE: 01538

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