Error: DB2 SQL Error: SQLCODE=+434, SQLSTATE=01608, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
clause IS A DEPRECATED CLAUSE
Explanation: The use of clause is accepted for now, but
continued use of it is not recommended. However, for
native SQL procedures, clause is not supported. See the
SQL Reference for a list of options that are supported
for native SQL procedures. SQLCODE -4705 might be
issued instead if the situation occurs with a BIND
COPY command that is used to deploy a version of a
native SQL procedure that uses a deprecated
option,and a package already exists by that name at the
For indexes, use type 2 indexes rather than type 1
indexes to avoid any incompatibilities.
System action: Processing continues and the clause is
User response: No change is required for the current
release. However, you should change your SQL
statement and remove this clause to prepare for
releases when this clause is no longer accepted.
To prevent the warning, remove the deprecated clause
from the statement.
Error: DB2 SQL Error: SQLCODE=+438, SQLSTATE=Defined by the application, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
APPLICATION RAISED WARNING
WITH DIAGNOSTIC TEXT: text
Explanation: This warning occurred as a result of the
SIGNAL or RESIGNAL statement.
text Diagnostic text provided by the SIGNAL or
System action: The statement was processed, but a
warning was encountered.
Programmer response: Use the application-provided
diagnostic text, if provided, to determine the cause of
SQLSTATE: Defined by the application
Error: DB2 SQL Error: SQLCODE=+440, SQLSTATE=01681, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
NO routine-type BY THE NAME
routine-name HAVING COMPATIBLE
ARGUMENTS WAS FOUND
Explanation: This warning occurs in a reference to
routine (stored procedure or function) routine-name,
when DB2 cannot find a function or stored procedure it
can use to implement the reference. Several reasons are
present for this warning:
v routine-name was either incorrectly specified or does
not exist in the database.
v A qualified reference was made and the qualifier was
v A user’s SQL path does not contain the schema to
which the desired function belongs, and an
unqualified reference was used.
v The wrong number of arguments were included.
v For functions, the data types of one or more of the
arguments is incorrect.
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: Fix the problem and retry.
Change the SQL statement, add new routines, or
change the user’s SQL path.
Above are list of DB2 SQL Errors and Warnings from Error +434 to +440 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.