DB2 SQL Errors Codes and Error Messages and Warnings from Error -430 to -433

SQLServerF1

Error: DB2 SQL Error: SQLCODE=-430, SQLSTATE=38503, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
routine-type routine-name (SPECIFIC
NAME specific-name) HAS
ABNORMALLY TERMINATED
Explanation: An abnormal termination has occurred
while the routine routine-name (stored procedure or
function) was in control.
System action: The statement cannot be executed.
Programmer response: The stored procedure or
function needs to be fixed. Contact the author of the
routine or your database administrator. Until it is fixed,
the routine should not be used.
SQLSTATE: 38503

Error: DB2 SQL Error: SQLCODE=-431, SQLSTATE=38504, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ROUTINE routine-name (SPECIFIC
NAME specific-name) OF TYPE
routine-type HAS BEEN INTERRUPTED
BY THE USER
Explanation: A user has issued TERMINATE during a
debugging session of SQL routine routine-name. The
TERMINATE might have been issued because an
infinite wait or loop was encountered.
System action: The statement cannot be processed.
User response: No recovery is necessary.
SQLSTATE: 38504

Error: DB2 SQL Error: SQLCODE=-433, SQLSTATE=22001, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
VALUE value IS TOO LONG
Explanation: The value value required truncation by a
system (built-in) cast or adjustment function, which
was called to transform the value in some way. The
truncation is not allowed where this value is used. The
value being transformed is one of the following:
v an argument to a user defined function (UDF)
v an input to the SET clause of an UPDATE statement
v a value being INSERTed into a table
v an input to a cast or adjustment function in some
other context.
If value has the ‘for bit data’ subtype, or has a data type
of BINARY or VARBINARY, then the value is printed as
a hexadecimal string in quotes followed by an X.
System action: The statement cannot be executed.
Programmer response: If value is a literal string in the
SQL statement, it is too long for its intended use. If
value is not a literal string, examine the SQL statement
to determine where the transformation is taking place.
Either the input to the transformation is too long, or
the target is too short. Correct the problem and rerun
the statement.
SQLSTATE: 22001

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