DB2 SQL Errors Codes and Error Messages and Warnings from Error +111 to +204

SQLServerF1_Header_Small

Error: DB2 SQL Error: SQLCODE=+111, SQLSTATE=01590, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE SUBPAGES OPTION IS NOT
SUPPORTED FOR TYPE 2 INDEXES
Explanation: You cannot use the SUBPAGES option
for type 2 indexes.
System action: The option is ignored and processing
continues.
Programmer response: Remove the SUBPAGES option
to get rid of the warning.
SQLSTATE: 01590

Error: DB2 SQL Error: SQLCODE=+117 , SQLSTATE=01525, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE NUMBER OF INSERT VALUES IS
NOT THE SAME AS THE NUMBER OF
OBJECT COLUMNS
Explanation: The number of insert values in the value
list of the insert operation is not the same as the
number of object columns specified.
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, specify one and only one value
for each of the specified object columns.
SQLSTATE: 01525

Error: DB2 SQL Error: SQLCODE=+162 , SQLSTATE=01514, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
TABLESPACE database-name.tablespacename
HAS BEEN PLACED IN CHECK
PENDING
Explanation: The indicated table space is in check
pending status because the ALTER TABLE statement
was used to specify either of the following:
v A referential constraint
v A check constraint, when the CURRENT RULES
special register is set to ‘DB2’
The table space is not generally available until the
check pending status is removed from the table space.
System action: The table space was placed in check
pending status.
Programmer response: Run the CHECK DATA utility.
The enforcement of the referential constraint or the
check constraint is deferred until the CHECK DATA
utility is run.
SQLSTATE: 01514
Error: DB2 SQL Error: SQLCODE=+203 , SQLSTATE=01552, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE QUALIFIED COLUMN NAME
column-name WAS RESOLVED USING A
NON-UNIQUE OR UNEXPOSED
NAME
Explanation: The table designator selected to resolve a
qualified column name is one of the following:
v An unexposed name
v An exposed name that has an exposed duplicate in
the same FROM clause
v An exposed name that has an unexposed duplicate
which appears before the selected name in the
ordered list of names to which the qualifier is
compared
Therefore, the statement does not conform to the
guidelines for using only unique exposed names as
qualifiers or it is possible that the column reference was
not resolved to the intended instance of the table or
view.
System action: DB2 uses the selected name to resolve
the reference.
Programmer response: If DB2’s resolution of the
qualifier was not what you intended, rewrite the SQL
statement and submit it again. The rules used to
resolve column name qualifiers are given in chapter 2
of SQL Reference .
SQLSTATE: 01552

Error: DB2 SQL Error: SQLCODE=+204 , SQLSTATE=01532, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
name IS AN UNDEFINED NAME
Explanation: The object identified by name is not
defined in the DB2 subsystem. This return code can be
generated for any type of DB2 object.
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, determine that the object name
was correctly specified in the SQL statement (including
any required qualifiers). If so, ensure that the object
exists in the system before resubmitting the statement.
SQLSTATE: 01532

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