DB2 SQL Errors Codes and Error Messages and Warnings from Error +364 to +394

SQLServerF1

Error: DB2 SQL Error: SQLCODE=+364, SQLSTATE=0168C, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
DECFLOAT EXCEPTION exception-type
HAS OCCURRED DURING
operation-type OPERATION, POSITION
position-number
Explanation: The exception error exception-type
occurred while performing an ADDITION,
SUBTRACTION, MULTIPLICATION, DIVISION,
NEGATION, or BUILT-IN FUNCTION operation on a
field whose data type is DECFLOAT. The error
occurred while processing an arithmetic expression. If
the error occurred in the SELECT list of an outer
SELECT statement, position in the select list is denoted
by position-number. If not, position number is 0. The
possible exception types are UNDERFLOW,
OVERFLOW, INEXACT, INVALID OPERATION,
DIVISION BY ZERO, or SUBNORMAL. The data type
displayed in the message may indicate the data type of
the temporary internal copy of the data, which may
differ from the actual column or literal data type due to
conversions by DB2.
Any of the exceptions or overflows can occur during
the processing of a built-in function. If operation-type is
FUNCTION, then the error occurred while processing
either an input, intermediate, or final value. The cause
could be that the value of a parameter is out of range.
Note: Parts of exception-type, operation-type, and
position-number might or might not be returned in
SQLCA, depending upon when the error was detected.
System action: The resulting data proceeds according
to IEEE 754r rules. Execution of the statement
continues. If the statement is cursor controlled, then the
cursor will remain open.
Programmer response: Examine the expression for
which the warning occurred to see if the likely cause of
the problem can be determined. The problem may be
data-dependent, in which case it will be necessary to
examine the data that was being processed at the time
that the error occurred. See the explanation of
SQLCODE -405 for allowed ranges of numeric data
types.
SQLSTATE: 0168C if INEXACT
0168D if INVALID OPERATION
0168E if UNDERFLOW,OVERFLOW
0168F if DIVISION BY ZERO
0168G if SUBNORMAL

Error: DB2 SQL Error: SQLCODE=+385, SQLSTATE=01643, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ASSIGNMENT TO AN SQLSTATE OR
SQLCODE VARIABLE IN AN SQL
ROUTINE routine-name MAY BE
OVERWRITTEN AND DOES NOT
ACTIVATE ANY HANDLER
Explanation: SQL routine routine-name was created,
but it contains an assignment statement that specifies
the SQLCODE or SQLSTATE variable as the target.
Assignment to an SQLSTATE or SQLCODE variable in
an SQL routine only changes the value in the variable,
and does not activate any handler. The SQLSTATE and
SQLCODE variables are assigned values by processing
of SQL statements in the SQL routine. Therefore, any
value assigned might be over-written as a result of SQL
statement processing.
System action: The routine definition is processed
successfully.
User response: No recovery is necessary. If the intent
was to signal an error or warning, specify the SIGNAL
or RESIGNAL statement instead of the assignment.
To prevent the warning, remove any assignments to the
SQLSTATE or SQLCODE special variables.
SQLSTATE: 01643

Error: DB2 SQL Error: SQLCODE=+394, SQLSTATE=01629, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
ALL USER SPECIFIED OPTIMIZATION
HINTS USED DURING ACCESS PATH
SELECTION
Explanation: All user specified optimization hints that
were found for the statement being optimized are used.
System action: Processing continues normally.
Programmer response: Ensure that the access path is
correct and produces the correct results. Refer to
Administration Guide for more information on
OPTHINT, including a list of what fields are used as
hints to the DB2 Optimizer
SQLSTATE: 01629

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