DB2 SQL Errors Codes and Error Messages and Warnings from Error -435 to -440

SQLServerF1

Error: DB2 SQL Error: SQLCODE=-435, SQLSTATE=428B3, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
AN INVALID SQLSTATE sqlstate IS
SPECIFIED IN A RAISE_ERROR
FUNCTION, RESIGNAL STATEMENT,
OR SIGNAL STATEMENT
Explanation: The SQLSTATE specified in the
RAISE_ERROR function, RESIGNAL statement, or
SIGNAL statement of a trigger or a routine does not
conform to the rules for a valid SQLSTATE.
System action: The statement cannot be processed.
Programmer response: Change the SQLSTATE
specified in the RAISE_ERROR function, RESIGNAL
statement, or SIGNAL statement so that it conforms to
the rules stated in SQL Reference.
For the RAISE_ERROR function, the SQLSTATE must
be a character string containing exactly five (5)
characters. It must be of type CHAR defined with a
length of five (5), or, a type VARCHAR defined with a
length of five (5) or greater. The SQLSTATE value must
conform to the following rules:
v Each character must be from the set of digits (‘0’
through ‘9’) or non-accented upper case letters (‘A’
through ‘Z’).
v The SQLSTATE class (the first two characters) cannot
be ’00’, ’01’ or ’02’ because these characters do not
indicate error classes.
v If the SQLSTATE class (the first two characters) start
with the character ‘0’ through ‘6’ or ‘A’ through ‘H’,
then the subclass (the last three characters) must start
with a letter in the range ‘I’ through ‘Z’.
v If the SQLSTATE class (the first two characters) start
with the character ‘7’, ‘8’, ‘9’ or ‘I’ through ‘Z’, then
the subclass (the last three characters) must be from
the set of characters ‘0’ through ‘9’ or ‘A’ through ‘Z’.
For the RESIGNAL and SIGNAL statements, the
SQLSTATE value must be exactly five (5) characters
that follow the following rules:
v Each character must be from the set of digits ‘0’
through ‘9’ or non-accented upper case letter ‘A’
through ‘Z’.
v The SQLSTATE class (the first two characters) cannot
be ’00’ because it represents successful completion.
SQLSTATE: 428B3

Error: DB2 SQL Error: SQLCODE=-438, SQLSTATE=Defined by the application, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
APPLICATION RAISED ERROR WITH
DIAGNOSTIC TEXT: text
Explanation:
This error occurred as a result of the RAISE_ERROR
function, a RESIGNAL statement, a SIGNAL SQLSTATE
statement, or it was an unhandled condition when
processing of the trigger or routine completed.
text Diagnostic text provided by the invocation of
the RAISE_ERROR function or the SIGNAL
SQLSTATE statement.
System action: The statement cannot be processed.
Programmer response: Use application-provided
diagnostic text, if provided, to determine the cause of
the error.
SQLSTATE: Defined by the application

Error: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
NO routine-type BY THE NAME
routine-name HAVING COMPATIBLE
ARGUMENTS WAS FOUND IN THE
CURRENT PATH
Explanation: This 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. There are several reasons why
this could occur.
v routine-name was either incorrectly specified or does
not exist in the database.
v A qualified reference was made, and the qualifier
was incorrectly spelled.
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: The statement cannot be executed.
Programmer response: Fix the problem and retry. This
could involve a change to the SQL statement, the
addition of new routines or a change to the user’s SQL
path.
SQLSTATE: 42884

Above are list of DB2 SQL Errors and Warnings from Error -435 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.

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 *