DB2 SQL Errors Codes and Error Messages and Warnings from Error -455 to -457

SQLServerF1

Error: DB2 SQL Error: SQLCODE=-455, SQLSTATE=42882, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
IN CREATE FUNCTION FOR
function-name, THE SCHEMA NAME
schema-name1 PROVIDED FOR THE
SPECIFIC NAME DOES NOT MATCH
THE SCHEMA NAME schema-name2 OF
THE FUNCTION
Explanation: If the SPECIFIC name is specified as a
two part name, the schema-name1 portion must be the
same as the schema-name2 portion of the function-name.
Note that the schema-name2 portion of function-name
may have been specified directly or it may have
defaulted to the authorization ID of the statement.
System action: The statement cannot be executed.
Programmer response: Correct the statement.
SQLSTATE: 42882

Error: DB2 SQL Error: SQLCODE=-456, SQLSTATE=42710, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
IN CREATE FUNCTION FOR
function-name, THE SPECIFIC NAME
specific-name ALREADY EXISTS IN THE
SCHEMA
Explanation: A SPECIFIC name has been explicitly
specified as specific-name in the CREATE FUNCTION
statement for function-name, but this name already
exists as the SPECIFIC name for another function
within the schema.
System action: The statement cannot be executed.
Programmer response: Choose a new SPECIFIC name.
SQLSTATE: 42710

Error: DB2 SQL Error: SQLCODE=-457, SQLSTATE=42939, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
A FUNCTION OR DISTINCT TYPE
CANNOT BE CALLED name SINCE IT
IS RESERVED FOR SYSTEM USE
Explanation: The user-defined function or distinct
type cannot be created or referenced because the name
selected is reserved for use by the system.
A number of names used as keywords are reserved for
system use. These names may not be used as
user-defined functions or distinct-type-names, even if
they are delimited identifiers. These names are:
= < > >= <=
< > ¬= ¬> ¬>
ALL AND ANY BETWEEN DISTINCT
EXCEPT EXISTS FALSE FOR FROM
IN IS LIKE MATCH NOT
NULL ONLY OR OVERLAPS SIMILAR
SOME TABLE TRUE TYPE UNIQUE
UNKNOWN
The names of built-in data types cannot be used as the
name of a distinct type (for example, CHAR).
Restriction: You cannot use an asterisk (*) as a specific
name for a user-defined or procedure name.
System action: The statement is not executed.
Programmer response: Select a name for the function
or distinct type that is not reserved for system use.
SQLSTATE: 42939

Above are list of DB2 SQL Errors and Warnings from Error -455 to -457 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 &gt; 0, execution was successful with a warning.
If SQLCODE &lt; 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 *