List of pureQuery Runtime default SQL error codes that are used with logging

For Java™ applications, you can write log records that are stored in memory to a log file when an SQL error occurs. pureQuery Runtime has a default list of SQL errors codes you can specify with the keyword default. You specify the keyword default with the pureQuery Runtime properties dumpLogsOnSqlCodes and dumpLogsExcludedSqlCodes.
The following table lists the SQL errors codes used by pureQuery Runtime when logging errors. For error codes that apply to both DB2® for z/OS® databases and DB2 for Linux, UNIX and Windows databases, The SQL error code is the same between the two platforms, however the message might differ between the two platforms.
Table 1. pureQuery Runtime default SQL error codes
Platform (see notes) SQL error code Message
L -171 The data type, length, or value of argument nn of function-name is invalid
Z -184 An arithmetic expression with a datetime value contains a parameter marker
L, Z -301 The value of input host variable or parameter number position-number cannot be used as specified because of its data type
L, Z -302 The value of input variable or parameter number position-number is invalid or too large for the target column or the target value
Z -303 A value cannot be assigned to output host variable number position-number because the data types are not comparable
Z -304 A value with data type data-type1 cannot be assigned to a host variable because the value is not within the range of the host variable in position position-number with data type data-type2
Z -305 The null value cannot be assigned to output host variable number position-number because no indicator variable is specified
Z -310 Decimal host variable or parameter number contains non-decimal data
Z -311 The length of input host variable number position-number is negative or greater than the maximum
L, Z -313 The number of host variables specified is not equal to the number of parameter marker
Z -314 The statement contains an ambiguous host variable reference
Z -330 A string cannot be used because it cannot be processed. Reason reason-code, character code-point, host variable position-number
Z -331 Character conversion cannot be performed because a string, position position-number, cannot be converted from source-ccsid to target-ccsid, reason reason-code
Z -332 Character conversion between CCSID from-ccsid to to-ccsid requested by reason-code is not supported
Z -333 The subtype of a string variable is not the same as the subtype known at bind time and the difference cannot be resolved by character conversion
Z -336 The scale of the decimal number must be zero
L, Z -351 An unsupported SQLTYPE was encountered in position position-number of the select-list
L, Z -352 An unsupported SQLTYPE was encountered in position position-number of the input-list
Z -363 The extended indicator variable value for parameter number is out of range
L -365 The value of the extended indicator variable in position position is not valid
Z -392 SQLDA provided for cursor cursor has been changed from the previous fetch
Z -398 A locator was requested for host variable number position-number but the variable is not a LOB
Z -401 The operands of an arithmetic or comparison operation are not comparable
Z -402 An arithmetic function or operator arith-fop is applied to character or datetime data
Z -404 The SQL statement specifies a string that is too long
Z -405 The numeric constant constant cannot be used as specified because it is out of range
Z -406 A calculated or derived numeric value is not within the range of its object column
Z -407 An UPDATE, INSERT, or SET value is null, but the object column column-name cannot contain null values
L, Z -408 The value is not compatible with the data type of its target. Target name is name
Z -410 A numeric value value is too long, or it has a value that is not within the range of its data type
Z -413 Overflow occurred during numeric data type conversion
L, Z -417 A statement string to be prepared includes parameter markers as the operands of the same operator
L, Z -418 A statement string to be prepared contains an invalid use of parameter markers
Z -433 Value value is too long
L -469 SQL call statement must specify an output host variable for parameter number
Z -502 The cursor identified in an OPEN statement is already open
Z -507 The cursor identified in the UPDATE or DELETE statement is not open
Z -517 Cursor cursor-name cannot be used because its statement name does not identify a prepared select statement
Z -518 The EXECUTE statement does not identify a valid prepared statement
Z -525 The SQL statement cannot be executed because it was in error at bind time for section = sectno package = pkgname consistency token = contoken
Z -533 Invalid multiple-row insert
L -670 The record length of the table exceeds the page size limit
L -678 The constant constant specified for the index limit key must conform to the data type data-type of the corresponding column column-name
L -713 The replacement value for special-register is invalid
L -727 An error occurred during implicit system action type action-type. Information returned for the error includes SQLCODE sqlcode, SQLSTATE sqlstate and message tokens Token-list.
L -789 The data type for parameter or variable name is not supported in the SQL routine.
L, Z -804 An error was found in the application program input parameters for the SQL statement, reason reason
L, Z -805 DBRM or package name location-name.collection-id.dbrm-name.consistency-token not found in plan plan-name. Reason reason
L -811 The result of an embedded select statement or a subselect in the set clause of an update statement is a table of more than one row, or the result of a subquery of a basic predicate is more than one value
L -818 The precompiler-generated timestamp x in the load module is different from the bind timestamp y built from the dbrm
L, Z -822 The SQLDA contains an invalid data address or indicator variable address
L -874 The encoding scheme specified for the object-type must be the same as the containing table space or other parameters
L -880 Savepoint savepoint-name does not exist or is invalid in this context
L -905 Unsuccessful execution due to resource limit being exceeded, resource name = resource-name limit = limit-amount1 CPU seconds (limit-amount2 service units) derived from limit-source
L -908 Bind-type error using auth-id authority. BIND, REBIND or AUTO-REBIND operation is not allowed
L, Z -911 The current unit of work has been rolled back due to deadlock or timeout. Reason reason-code, type of resource resource-type, and resource name resource-name
L -912 The maximum number of lock requests has been reached for the database
L, Z -913 Unsuccessful execution caused by deadlock or timeout. Reason code reason-code, type of resource resource-type, and resource name resource-name
L, Z -917 Bind package failed
Z -918 The SQL statement cannot be executed because a connection has been lost
Z -924 DB2 connection internal error, function-code, return-code, reason-code
L -1023 The communications conversation failed
L -1164 The SQLDA or host variables, of type type, used in the SQL statement are not valid. Reason code reason-code, host variable/SQLVAR number var-number
L -1352 Trusted Connection cannot be reused during a transaction
L -1358 A duplicate cursor cannot be opened
L -1426 A default instance cannot be determined
Z -20107 Host variable or parameter number position-numbercannot be used as specified because reason Reason
L -20191 For an INOUT parameter in a dynamically prepared CALL statement, the same host variable must be used in both the USING and INTO clauses
Z -30000 Execution failed due to a distribution protocol error that will not affect the successful execution of subsequent commands or SQL statements: reason reason-code (sub-code)
Z -30002 The SQL statement cannot be executed due to a prior condition in a chain of statements
L, Z -30020 Execution failed due to a distribution protocol error that caused deallocation of the conversation: reason reason-code (sub-code)
Z -30021 Execution failed due to a distribution protocol error that will affect the successful execution of subsequent commands or SQL statements: manager manager at level level not supported error
L -30073 parameter-subcode Parameter value value not supported error
Note:

Z - The error code applies to DB2 for z/OS databases.

L - The error code applies to DB2 for Linux, UNIX and Windows databases.

Feedback