|
|
01
You are preprocessing a package using a
-760
Statement cannot be executed in the
previous release of an SQL/DS or DB2 Server
same logical unit of work where a
for VSE application requester against a remote
package is being updated because the
DB2 Server for VSE or SQL/DS application
authority to execute the statement did
server of a newer release. The two releases are
not exist when the package was
incompatible. If you want to store a package
processed again.
in the target application server, preprocess
Explanation: The database manager has processed the
your program on an application requester of
subject package again. When this processing ended, the
the same release, and then you can run the
authority to execute the current statement did not exist.
program from the back release application
The resulting limitation on the user is that the current
requester.
statement might not execute in the same logical unit of
work in which the system is updating the package. A
SQLSTATE Spaces.
previous DROP STATEMENT or Extended PREPARE
System Action: Execution of the statement has ended.
against the subject package in the current logical unit of
work started the update activity.
User Response: See the Explanation for details.
SQLSTATE 56044.
-801
Exception error exception-type occurred
System Action: Processing of the SQL statement ends.
during operation-type operation on
User Response: Drop the current statement. Replace it
data-type data.
after the authority needed to execute the statement has
Explanation: The database manager had to materialize
been granted.
a view. In doing so, an arithmetic operation in the
subselect clause of the view definition has caused the
-761
The language preprocessor being run
program exception identified by the exception-type
cannot replace package package-name.
value.
Explanation: The Assembler, C, PL/I, and COBOL
The explanation for SQLCODE -802 describes the
preprocessors cannot be used to replace a package
exception-type and data-type values possible.
created using the FORTRAN preprocessor or the
SQLSTATEs:
CREATE PACKAGE statement. A package created by
using a CREATE PACKAGE statement can be replaced
22003
Arithmetic overflow or underflow
only by using a CREATE PACKAGE statement with the
22012
Division by zero
REPLACE option. It cannot be replaced by the
language preprocessor now being executed.
22502
Anything else.
System Action: Processing of the SQL statement has
Note: This SQLCODE will also be issued if you
ended.
preprocessed a FORTRAN program in a
Distributed Relational Database Architecture
User Response: The information shown in the
(DRDA) environment and then repreprocess it in
message can be used by the view owner to determine
a non-DRDA environment.
what data used in the view might be causing the
program exception.
To avoid this situation, you must either first
System Programmer Response: The view owner can
drop the package or consistently preprocess the
use the information shown in the message to determine
program in a DRDA or non-DRDA environment.
what data used in the view might cause the program
exception. Running just the subselect clause used in
SQLSTATE Spaces.
defining the view should cause a similar problem,
System Action: Processing of the SQL statement has
except it produces SQLCODE -802. This information
ended.
should help you to determine the problem.
User Response: Either use the appropriate
preprocessor or change the preprocessor parameters
-802
Exception error exception-type occurred
PREPNAME or USERID and then rerun the
during operation-type operation on
preprocessor.
data-type data, position position-number.
psw1 psw2.
-762
Your request is incompatible with the
Explanation: An arithmetic operation in the SQL
target application server. Reason Code =
statement has caused the program exception identified
reason-code.
by the exception-type value. The two 4-byte fields
shown in the message are the contents of the Program
Explanation: The target application server cannot
Status Word (PSW) when the abend occurred.
process your request. The possible reason code is:
310
Messages and Codes
exception-type, data-type, operation-type
v SIGNIFICANCE EXCEPTION can occur when an
position-number and psw1 psw2 may or may not be
error has occurred in floating-point addition or
returned in SQLCA, depending on where the error was
subtraction. The error is that the fraction resulting
detected. The SQLERRD1 field will be -9xx, where xx is
from the arithmetic operation in the SQL statement is
the value of the interruption code.
zero.
Note: SQLERRD1 would not be set if you are using the
The possible data-types are INTEGER, SMALLINT,
Distributed Relational Database Architecture
DECIMAL, and FLOAT. The data type displayed in the
(DRDA) protocol.
message indicates the data type of the temporary
internal copy of the data which may differ from the
The following is a list of exception-type values:
actual column or literal data type due to conversions
by the database manager. The possible operation-types
v
DATA EXCEPTION can occur when incorrect
are ADDITION, SUBTRACTION, MULTIPLICATION,
operand fields have been detected in a machine code
and DIVISION. (Unary minus is treated as a multiply
instruction. One of the following has occurred:
by -1.) If the error was in the select-list of an outer
- The sign or digit codes of operands in Decimal
SELECT statement then position-number will indicate
Instructions or in CONVERT TO BINARY are not
the position of the expression in the select list. If the
correct.
error was not in the select-list, position-number will be
- The multiplicand in MULTIPLY DECIMAL has too
zero.
few high-order zeros.
- In ADD DECIMAL, COMPARE DECIMAL,
SQLSTATEs:
DIVIDE DECIMAL, MULTIPLY DECIMAL, or
22003
Arithmetic overflow or underflow
SUBTRACT DECIMAL the operand fields overlap
such that the rightmost bytes of the operand fields
22012
Division by zero
do not occupy the same place in storage.
22502
Anything else.
- In ZERO AND ADD DECIMAL, the operand
fields overlap, but the rightmost byte of the
System Action: Processing of the SQL statement ends.
second operand is to the right of the rightmost
User Response: Check the arithmetic operation and
byte of the first operand.
the columns within the statement to determine what
v
FIXED POINT OVERFLOW can occur during any
data may be causing the program exception. If you
arithmetic operation on either INTEGER or
cannot determine the cause of the error, contact your
SMALLINT fields.
system programmer.
v
DECIMAL OVERFLOW exception can occur when
one or more non-zero digits are lost because the
Note: If the error occurred in the select-list of an outer
destination field in any decimal operation is too
subselect, indicator variables can be added to
short to contain the result.
each of the expressions to allow you to get
values not in error and retrieve subsequent rows.
v
DIVIDE EXCEPTION can occur on a division by
In that case, the +802 SQLCODE would be
zero operation on any numeric field type (DECIMAL,
issued.
FLOAT, SMALLINT, or INTEGER), on a decimal
division operation when the quotient exceeds the
System Programmer Response: Check the arithmetic
specified data-field size, or on a decimal division
operation and the columns within the statement to
operation when the conversion of the divisor
determine what data may be causing the program
requires more than 15 significant digits to represent
exception. The exception-type and associated PSW
the whole part of the number.
shown in the message should aid in problem
v
MULTIPLY EXCEPTION can occur on a decimal
determination. Also refer to the DB2 Server for VSE &
multiplication operation when the value chosen for
VM Database Administration manual for information on
conversion requires more than 15 significant digits to
arithmetic operations.
represent the whole part of the number. This
exception can only occur when both the multiplier
-803
The statement failed because the
and the multiplicand have precision greater than 15.
INSERT or UPDATE statement causes a
v
EXPONENT OVERFLOW can occur when the result
duplicate value for a column defined in
characteristic of any floating point operation exceeds
either a UNIQUE INDEX, PRIMARY
the maximum value supported by System/370
KEY, or UNIQUE CONSTRAINT. Index
architecture (approximately 7.2E+75).
identifier = index-id Dbspace number =
v
EXPONENT-UNDERFLOW EXCEPTION can occur
dbspace-number Reason code = reason code
if the resulting value of a double-precision
Explanation: A column was defined with a unique
floating-point arithmetic operation was less than the
index, primary key, or unique constraint. An attempt
minimum value supported by System/370
was made to update such a column with a value that
architecture.
311
already exists in that column. This is not allowed.
modify an existing RDIIN, a database manager error
has occurred. Notify your system programmer.
If a column has a type of VARCHAR or
VARGRAPHIC, two column values which differ only
System Programmer Response: Record the error and
by trailing blanks cause duplication.
contact the designated support group for your
installation.
The index name corresponding to index-id can be
found in the SYSINDEXES catalog table as follows:
-805
The package owner.package-name is not in
SELECT A.DBSPACENO,B.II.INAME,B.ICREATOR,A.TNAME
FROM SYSTEM.SYSCATALOG A, SYSTEM.SYSINDEXES B
the SYSTEM.SYSACCESS catalog table.
WHERE A.TNAME = B.TNAME AND A.CREATOR = B.CREATOR
Explanation: When the system tried to run the
AND A.DBSPACENO = dbspace-number
program, it could not find the package in the catalog
AND B.IID = index-id
table SYSTEM.SYSACCESS.
ORDER BY A.DBSPACENO,B.IID
SQLSTATEs:
The reason code provides additional information about
42704
On a GRANT, REVOKE, or DROP statement
the error.
(for example, when directly naming the
0
The statement executed was one of the
package)
following:
51002
On any other statement (for example, when
v An INSERT
indirectly attempting to access a package that
v A positioned UPDATE
is not at the application server).
v A searched UPDATE where at most one row
System Action: Processing of the SQL statement has
can satisfy the search condition.
ended. The application can issue subsequent SQL
1
The statement executed was a searched
statements.
UPDATE on a table in a recoverable storage
User Response: Be sure that the program has been
pool whose search condition could be satisfied
preprocessed with no errors. If not, correct any errors
by more than one row. Uniqueness checking
which caused the preprocess to fail, preprocess the
was deferred until all rows were updated but
program and rerun it.
all duplicates were not resolved by the end of
statement processing.
-806
The package owner.package-name is
2
The statement executed was a searched
unusable.
UPDATE on a table in a nonrecoverable
storage pool whose search condition could be
Explanation: The package is unusable because it
satisfied by more than one row. Uniqueness
depends on some name (table, view, index, etc.) not
checking was not deferred and a duplicate was
now defined, or some authorization is required which
detected before all rows were updated.
is not granted now.
SQLSTATE Spaces.
SQLSTATE 23505.
System Action: Processing of the SQL statement has
System Action: Processing of the SQL statement has
ended. The logical unit of work (if any) is rolled back.
ended.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
User Response: Correct the statement. Try again.
S to signal that a severe error has occurred.
User Response: Determine the name or authorization
-804
Either the structure or the section
that is required and submit necessary statements to
number in the RDIIN control block
correct the error. If a change is made to the program, it
with call type call-type is incorrect.
must be preprocessed.
Explanation: The database manager found an
incorrect call type in the RDIIN structure.
-807
The maximum number of active
packages for an agent is exceeded.
SQLSTATE 07002.
Maximum allowed number is npackage.
System Action: The processing of this call to the
Explanation: The user has link edited more than the
database manager ends.
permissible number of programs together and has
User Response: If your program generates its own
executed an SQL statement from each of them without
RDIIN structure or modifies an RDIIN structure that
an intervening COMMIT or ROLLBACK. This means
DB2 Server for VSE preprocessors generated, ensure
that the user has more than the permissible number of
that a valid call type is in the RDIIN.
packages active at the same time. The maximum
number of active packages allowed is the same as the
If your program does not generate its own RDIIN or
value of the initialization parameter NPACKAGE.
312
Messages and Codes
SQLSTATE 54017.
-811
The use of this statement is invalid
System Action: Processing of the SQL statement ends
against a section created by a PREPARE
and the logical unit of work (if any) is rolled back.
SINGLE ROW statement.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
Explanation: The only statements that can be executed
S to signal that a severe error has occurred.
against a section created by the PREPARE SINGLE
User Response:
ROW form of the EXTENDED PREPARE statement are
Extended EXECUTE statements specified with the
1. Redesign or restructure your programs so that no
OUTPUT DESCRIPTOR clause and Extended
more than the maximum permissible number of
DESCRIBE statements.
packages are involved during execution; or ask your
database administrator to increase the value of the
SQLSTATE 07007.
NPACKAGE parameter on the SQLSTART EXEC.
System Action: Processing of the SQL statement has
If the value of the NPACKAGE parameter changes,
ended.
using the new value, re-run the SQLSTART EXEC.
Programmer response: Correct the statement. Try
2. Issue a COMMIT at an appropriate point during
again.
execution, before the program which causes this
error executes.
-813
You cannot lock a view.
-809
The statement failed because an attempt
Explanation: An attempt was made to lock a view. A
was made to insert a row longer than
user may only lock a DBSPACE or a table.
allowed.
SQLSTATE 42809.
Explanation: The row was longer than allowed for a
table. Only 4080 bytes of data can be placed in a row,
System Action: Processing of the SQL statement has
unless a long string is involved. A long string column
ended.
is either a LONG VARCHAR, LONG VARGRAPHIC,
User Response: Correct the statement. Try again.
VARCHAR(n) where n is greater than 254 but less than
or equal to 32767, or VARGRAPHIC(n) where n is
greater than 127 but less than or equal to 16383.
-814
You cannot lock a system dbspace or
catalog table.
This error is not detected at the time the table is
created. Rather, the error is issued the first time that an
Explanation: A dbspace with owner of SYSTEM or a
attempt is made to insert data into the table.
catalog table cannot be locked.
SQLSTATE 54018.
SQLSTATE 42832.
System Action: Processing of the SQL statement has
System Action: Processing of the SQL statement has
ended.
ended.
User Response: Drop the table. Recreate the table so
User Response: Correct the statement. Try again.
that the total length of a row is reduced. Try again.
-815
CONNECT denied by accounting user
-810
The statement failed because more than
exit routine.
one row was returned for a SELECT
Explanation: An attempt to connect to the application
clause when only one is allowed.
server was rejected by the installation’s accounting user
(Subquery or non-cursor SELECT).
exit routine. Note that this can occur on either an
Explanation: A cursor SELECT is required to return
explicit or implicit (only applies to the on-line
more than one row.
environment) SQL CONNECT.
The contents of any output host variables are
SQLSTATE 42505.
unpredictable.
System Action: The application server denies the
SQLSTATE 21000.
connection and returns to the application. SQLERRD1
contains the return code from the installation’s
System Action: Processing of the SQL statement has
accounting user exit routine.
ended.
User Response: Contact the database administrator to
User Response: Correct the statement. Try again.
verify the authorization name which was rejected.
313
System Action: Processing of the SQL statement has
-816
Error converting a date/time value in the
ended.
local exit routine exit-name.
User Response: Ensure that the SQL statement that is
Explanation: The local date/time exit exit-name
being used by the PREPARE or EXECUTE IMMEDIATE
encountered an error when converting a date/time
statement is a variable length character string with a
value from/to the local format.
length of from 0 to 8 192.
SQLERRD5 contains the function code with the
For a host variable declared as a fixed length character
following values.
string variable in PL/I or in FORTRAN, ensure that the
v
4 - Convert from local format to ISO format.
length is correct.
v
8 - Convert from ISO format to local format.
-823
The statement failed because you are
SQLERRD1 contains the return code set by the local
not permitted to perform this operation
exit.
on a catalog table.
SQLSTATE 58002.
Explanation: This code is issued when you attempt to
do any of the following:
System Action: The statement is not executed.
v Delete rows from certain catalog tables.
User Response: Contact your system administrator
v Update rows in certain catalog tables.
about this problem.
v Insert rows into certain catalog tables.
v Alter any catalog table other than
-818
The preprocessor-generated consistency
SYSTEM.SYSLANGUAGE.
token in the load module is different
v Reference a catalog table other than
from the consistency token in the
SYSTEM.SYSLANGUAGE as the parent table of your
package.
foreign key.
Explanation: At preprocessing time, the database
v Reorganize a system-created index on any catalog
manager creates a consistency token and stores it, for
table other than SYSTEM.SYSLANGUAGE using the
run time use, in the source program (to be stored later
DBS Utility REORGANIZE INDEX command.
in the object program) and in the package. At run time,
the consistency token within the package is compared
Only someone with DBA authority may issue UPDATE,
with the consistency token in the object program being
INSERT and DELETE statements against catalog tables
executed. If the two consistency tokens do not match,
whose columns may be altered. For a list of alterable
the package and the program were not the result of the
catalog tables, see the DB2 Server for VSE & VM SQL
same preprocessing invocation.
Reference manual.
This problem can occur if the owner of an application
changes the program (in other words, adds or deletes
SQLSTATE 42832.
SQL statements), repreprocesses and recompiles the
System Action: Processing of the SQL statement has
application, and someone else tries to run the program
ended.
using the old object code.
User Response: Correct the statement. Try again.
SQLSTATE 51003.
System Action: Processing of the SQL statement ends.
-824
Resource Adapter internal error.
User Response: Preprocess and compile the program
Explanation: This is a DB2 Server for VSE system
again and rerun it, or rerun the program using the
error. An incorrect set/reset request was made, or an
object code that matches the package.
internal error occurred during blocking of a FETCH or
PUT request. SQLERRD1 contains further information
-821
The PREPARE or EXECUTE
about the error. The possible values are:
IMMEDIATE statement failed because
-4
A pointer used to obtain addressability to an
the associated SQL statement has an
internal control block is zero.
incorrect length.
-5
The calltype of the statement passed is not P
Explanation: The SQL statement that was sent over to
(for PUT) or F (for FETCH).
the database manager on a PREPARE or EXECUTE
IMMEDIATE statement at execution time contained an
4
The set exit process found that a cancel exit is
incorrect length. The SQL statement was expected to be
already enabled.
in the form of a variable length character string with
8
The set or reset exit process found the RMAR
length of from 0 to 8 192 bytes.
pointer is zero.
SQLSTATE 22501.
314
Messages and Codes
12
The Online Resource Adapter found that the
messages returned to the user and the operator, and
pointer to the cancel exit in the RMAR is zero.
take the appropriate corrective action.
16
The reset exit process found that a cancel exit
is not enabled.
-826
The statement identifier statement-id in
package owner.package-name is not valid
SQLSTATE 58004.
because: reason-code.
System Action: Processing of the SQL statement has
Explanation: The statement-id of an Extended
ended.
DESCRIBE, DECLARE cursor, or EXECUTE is not valid
for one of the following reasons:
If the value of SQLERRD1 is less than zero, a severe
1. statement-id does not exist in the package named.
error has occurred. The logical unit of work (if any) is
rolled back. SQLWARN0 and SQLWARN6 of the
2. statement-id is not executable because it was
SQLCA are set to S to signal that a severe error has
deleted with a DROP STATEMENT.
occurred.
3. statement-id is not a SELECT, but a query operation
is implied by the current statement. (The current
User Response: Notify your system programmer.
statement is an extended DESCRIBE or DECLARE
After a severe error has occurred, only a CONNECT
CURSOR).
statement will be accepted.
4. statement-id is a SELECT, but a query operation is
System Programmer Response: Make a record of
not implied by the current statement. (The current
what went wrong. Ensure that the SQLERRD1 value is
statement is an extended EXECUTE).
included in the information. Contact the designated
5. statement-id is not a SELECT statement, but a
support group for your installation.
SELECT statement is required. (The current
statement is an extended PREPARE SINGLE
-825
An error occurred while processing an
ROW...).
operator command.
6. statement-id is not a SINGLE ROW SELECT
Explanation: An error occurred while processing an
(prepared with a PREPARE SINGLE ROW form of
operator command. SQLERRD1 contains further
PREPARE). (The current statement is an extended
information about the errors. The possible values are:
EXECUTE...USING OUTPUT DESCRIPTOR).
-65
Operator commands are not valid in a LUW.
SQLSTATEs for reason codes 1 and 2:
-120
Operator commands are not valid in SUM.
07003
EXECUTE
+61
Length of operator command or parameter
26501
DECLARE CURSOR, DESCRIBE,
exceeds 8 characters. Refer to message
DROP STATEMENT, PREPARE -
ARI0061E for detailed information.
Filling empty section.
+63
Operator command has not been specified.
SQLSTATEs for other reason codes:
Refer to message ARI0063I for detailed
information.
07005
Reason code 3
+64
Operator command is invalid. Refer to
07003
Reason code 4
message ARI0064E for detailed information.
26507
Reason code 6
+66
Unexpected error such as: invalid parameter
26508
Reason code 5.
or I/O error. Refer to message ARI0066E for
detailed information.
System Action: Execution of the SQL statement has
ended.
+67
Invalid SHOW command. Refer to message
ARI0067E for detailed information.
User Response: Rollback the logical unit of work, then
correct the error. Try again.
+68
Invalid SET command. Refer to message
ARI0068E for detailed information.
-827
Extended dynamic statements are
SQLSTATE 51010.
permitted only for package created by
the CREATE PACKAGE statement.
System Action: database operator command
Package owner.package-name was not
processing ends.
created by CREATE PACKAGE.
User Response: Ensure that the command is correct
Explanation: You can use extended dynamic
and try again. However, if the SQLERRD1 is +66 and
statements only to execute or modify a package that a
the problem persists, notify your system programmer.
CREATE PACKAGE statement has created.
System Programmer Response: Refer to the error
SQLSTATE 42862.
315
System Action: Processing of SQL statement ends.
v If the MODIFY option was specified, rerun the
application locally if the application can be ported to
User Response: Roll back the logical unit of work,
this operating environment.
correct the error, and rerun the program.
-831
A package created by the CREATE
-828
Package owner.package-name was created
PACKAGE statement can be the target
using the NODESCRIBE option of the
of the following Extended Dynamic
CREATE PACKAGE statement.
Statements only: EXECUTE, DECLARE
Therefore, you cannot use the
CURSOR, OPEN, FETCH, PUT, CLOSE,
DESCRIBE statement for it.
DROP STATEMENT, and DESCRIBE.
Explanation: You used the NODESCRIBE option when
Explanation: The only SQL extended dynamic
creating the package with the CREATE PACKAGE
statements that might reference or modify a package
statement.
created using the CREATE PACKAGE statement are:
SQLSTATE Spaces.
v Extended DECLARE CURSOR
v Extended DROP STATEMENT
System Action: Processing of the SQL statement has
v Extended OPEN, FETCH, PUT, and CLOSE
ended.
v Extended EXECUTE
User Response: Roll back the logical unit of work,
v Extended DESCRIBE.
then correct the error. Try again.
Any other SQL statements referencing a CREATE
PACKAGE package are invalid.
-829
You cannot use a CREATE PACKAGE
statement with the REPLACE option to
SQLSTATE Spaces.
replace package owner.package-name
which was created with the MODIFY
System Action: Processing of the SQL statement has
option.
ended.
Explanation: When the package was originally
User Response: Roll back the current logical unit of
created, the MODIFY option was specified. The current
work, correct the problem, and rerun the preprocessor.
CREATE PACKAGE statement is incorrect because it
contains the REPLACE option. A modifiable package
-832
A CREATE PACKAGE statement has
may not be replaced.
been issued in the current logical unit
SQLSTATE 56046.
of work. The database manager cannot
execute the current statement until you
System Action: Processing of SQL statement has
commit or roll back the current logical
ended.
unit of work.
User Response: Rollback the logical unit of work, then
Explanation: After you have issued a CREATE
correct the error. Try again.
PACKAGE, rules apply to the execution of SQL
statements that can follow in the same logical unit of
-830
You cannot use an Extended PREPARE
work. Those rules are:
or DROP STATEMENT to change
v If the CREATE PACKAGE contains the NOMODIFY
package owner.package-name.
option, only Extended PREPARE SQL statements can
follow.
Explanation: You are not allowed to add or delete a
statement from the package either because:
v If the CREATE PACKAGE contains the MODIFY
option, the SQL statements that follow can only
v The package was created with the NOMODIFY
reference the package named in the CREATE
option, or
PACKAGE statement, and must be one or a
v The package was created with the MODIFY option
combination of the following SQL statements:
but you are running the program under the
Extended PREPARE
Distributed protocol, which does not support these
Extended EXECUTE
two statements.
Extended DECLARE Cursor
Extended OPEN
SQLSTATE 42859.
Extended PUT
Extended FETCH
System Action: Processing of the SQL statement ends.
Extended CLOSE
User Response:
Extended DESCRIBE
v If the NOMODIFY option was specified on the
DROP STATEMENT.
CREATE PACKAGE, roll back the logical unit of
work, correct the error, and rerun the program.
316
Messages and Codes
After a COMMIT or ROLLBACK statement is issued,
In the current logical unit of work, this statement does
these rules no longer apply.
not follow a CREATE PACKAGE statement of the form:
CREATE PACKAGE...USING NOMODIFY
SQLSTATE 56042.
Therefore, the database manager does not allow it to be
executed. The database manager enforces an execution
System Action: Processing of the SQL statement has
sequence rule for the NULL form of the Extended
ended.
PREPARE: it must be in the same logical unit of work
User Response: Modify the user program so that the
as CREATE PACKAGE of the form: CREATE
statement in error is executed after the package has
PACKAGE...USING NOMODIFY... ; and it must follow
been committed or rolled back. A package is committed
the CREATE PACKAGE in the execution sequence.
with the COMMIT statement and rolled back with the
SQLSTATE 56047.
ROLLBACK statement.
System Action: Processing of the SQL statement has
ended.
-833
The package or view, name, cannot be
rebound because the character set under
User Response: Arrange the execution sequence of the
which it was preprocessed, charset1, does
NULL form of the Extended PREPARE so that it
not coincide with the character set under
follows, in the same logical unit of work, a CREATE
which the database manager is running,
PACKAGE of the form: CREATE PACKAGE... USING
charset2.
NOMODIFY
Explanation: The database manager is rebinding
package or view name. The package or view was
-835
The database manager cannot rebind the
preprocessed with the character set charset1. The
view owner.view-name because this view
database manager is currently running using character
was created in a previous version of the
set charset2, which is different from the preprocessed
database system.
character set.
Explanation: When the database manager is running
Note that if the value of the column ’VALID’ in
an application for the first time, and the application
SYSTEM.SYSACCESS is manually changed to ’N’ by a
uses a view that was created before the current version
user for a view package, this error will be received on
of the application, the database manager rebinds the
all subsequent invocations of the view.
CREATE VIEW statement of the view.
SQLSTATE 51016.
An unexpected error can occur during the rebinding. In
most instances, this is because the view definition
System Action: Rebinding is terminated and
included a SELECT * and the table on which the view
processing of the SQL statement has ended.
is based had columns added to it since the view was
User Response:
originally created. In this instance, SQLERRD1 is equal
to -110. Otherwise, SQLERRD1 is set to the SQLCODE
1. Preprocess the package again. If it is the DBS Utility
that indicates the error detected during view
package (SQLDBA.ARIDSQL), the database manager
repreprocessing.
provides a job control program to recreate the package.
See the DB2 Server for VSE Program Directory for more
When the application server default CHARNAME
information.
value has been changed and a view has a dependency
on a system table, the view is no longer valid. In this
2. Contact the database administrator. End the
case, SQLERRD1 is set to -833.
application server and restart, supplying a character set
name in the CHARNAME parameter that is identical to
SQLSTATE 56049.
the character set that was used to first preprocess the
System Action: Processing of the SQL statement has
package.
ended.
Packages preprocessed using either the ENGLISH or
User Response: Drop the view and recreate it before
the INTERNATIONAL character set never encounter
rerunning the application. Contact your database
this error. They are always rebound in ENGLISH or
administrator to have this done.
INTERNATIONAL, respectively.
-836
The current statement cannot be
-834
The NULL form of the Extended
executed using the DRDA protocol.
PREPARE statement does not follow a
CREATE PACKAGE...USING
Explanation: The current statement is not defined in
NOMODIFY statement in the current
the DRDA protocol. The following is a list of the
logical unit of work.
statements that are not supported when the DRDA
protocol is used.
Explanation: The user application is executing an
Extended PREPARE statement using the NULL option.
317
v Extended PREPARE SINGLE ROW (In FORTRAN
-844
An Extended PREPARE can only be
this is SELECT INTO.)
executed using the DRDA protocol if it
v Positioned UPDATE or positioned DELETE in
has an input SQLDA.
FORTRAN.
Explanation: You cannot PREPARE an SQL statement
v Extended EXECUTE...USING OUTPUT DESCRIPTOR
with host parameter markers without specifying input
v CONNECT (userid) IDENTIFIED BY (password)
SQLDA when using the DRDA protocol.
v DB2 Server for VSE Operator Commands
SQLSTATE 56041.
v Extended Dynamic statements for modifiable
System Action: Processing of the SQL statement has
packages
ended.
SQLSTATE 42612.
User Response: Execute the program against a local
application server. If you must execute against a remote
System Action: Processing of the SQL statement has
server, the program should be rewritten to include the
ended. The logical unit of work (if any) has been rolled
SQLDA information for the parameter markers
back. SQLWARN0 and SQLWARN6 of the SQLCA are
specified in the PREPARE statement.
set to S to signal that a severe error has occurred.
User Response: Preprocess and execute the program
-860
The SQL statement was not processed
against the database application server and do not use
because the application server
the DRDA protocol. If you must execute against a
server-name is not accepting connections
remote server, a program should be rewritten to avoid
from DRDA-only application requesters.
these statements. For example, if the current statement
is a PREPARE SINGLE ROW, replace it with a Basic
Explanation: A VSE application requester is
PREPARE and use cursor operations to retrieve the
attempting to access a remote server, but the remote
required data.
server does not support the DRDA protocol.
SQLSTATE 56077.
-841
A DBNAME Directory error has
System Action: Processing of this SQL statement has
occurred. Reason Code= X’reason-code’.
ended. The resource adapter returns to the application
Explanation: The database manager detected an error
with SQLCA fields SQLWARN0 and SQLWARN6 both
with the DBNAME Directory when it tried to resolve
set to S, indicating a serious system error.
the server name.
User Response: Change your dbname directory so the
The reason-code value is the 2-byte hexadecimal error
DB2 Server for VM application server is no longer
code. Possible reasons for the error:
defined as a remote database and will be accessed
v X’1007’ - Default DBNAME not found in DBNAME
through guest sharing, or contact your Database
Directory.
Administrator to start the DB2 Server for VM
application server with PROTOCOL(AUTO).
v X’1015’ - SNA communications is requested, but SNA
address information is not available for the
DBNAME.
-861
Cannot access a remote server because
v X'1016' - TCP/IP communications is requested, but
the DRDA facility has not been
TCP/IP address information is not available for the
installed for the application requester.
DBNAME.
Explanation: The application requester is connecting
to a remote application server. However, the DRDA
SQLSTATE:
facility has not been installed for the application
57040
requester.
System Action: Processing of the SQL statement ends
SQLSTATE 56079
and the logical unit of work (if any) is rolled back.
System Action: Processing of the SQL statement ends.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
The resource adapter returns to the application with the
S to signal that a severe error has occurred.
SQLCA fields SQLWARN0 and SQLWARN6 both set to
User Response: After a severe error has occurred,
S, indicating a serious system error.
only a CONNECT statement will be accepted.
User Response: Contact your database administrator
Correct the communications directory problem and try
to install the DRDA facility.
to connect again.
Database Administrator Response:
Determine whether or not you require your application
requester to initiate DRDA conversation. If so, install
the DRDA facility following the steps in the DB2 Server
318
Messages and Codes
for VSE System Administration manual. If not, access to
-902
Serious system error. Discontinue
remote application servers will not be allowed.
further use of the database manager.
Explanation: An unrecoverable error occurred.
-900
The SQL statement cannot be executed
because the previous error has left the
SQLSTATE 58005.
application in an unconnected
System Action: Processing of the SQL statement has
condition.
ended. SQLWARN0 and SQLWARN6 of the SQLCA are
Explanation: A previous failure has placed the
set to S to signal that a severe error has occurred. If a
application process in a connectable and unconnected
severe error has occurred, only a CONNECT statement
state. The only SQL statement that can be executed
will be accepted.
from the connectable and unconnected state is
User Response: Notify your system programmer.
CONNECT.
System Programmer Response: Use SQLERRP and
SQLSTATE 08003.
SQLERRD1 in message ARI0504I to determine more
System Action: Processing of the SQL statement ends
information about the error. Make a record of what
and SQLWARN0 and SQLWARN6 of the SQLCA are set
went wrong and contact the designated support group
to S to signal that a severe error has occurred.
for your installation.
User Response: After a severe error occurs, enter a
CONNECT statement only.
-903
The current logical unit of work has
been rolled back because of a system
failure.
-901
The SQL statement failed because of a
system error. You can continue to use
Explanation: An error has occurred that may be due
the database manager.
to a user error or a real system error. The catalog may
be destroyed. Refer to User Response.
Explanation: An error has occurred which is due to
system error.
SQLSTATE 40003.
SQLSTATE 58004.
System Action: Processing of the SQL statement has
ended. SQLWARN0 and SQLWARN6 of the SQLCA are
System Action: Processing of the SQL statement has
set to S to signal that a severe error has occurred. If a
ended.
severe error has occurred, only a CONNECT statement
User Response: Verify that your SQL statement is
will be accepted.
valid. If you cannot determine the cause of the error,
User Response: Notify your system programmer.
contact your system programmer.
SQLERRD2 in message ARI0504I or in the SQLCA is
SQLERRD2 in message ARI0504I or in the SQLCA is
the DBSS return code which may further define the
the DBSS return code which may further define the
error that occurred. The following SQLERRD2 codes
error that occurred. The following SQLERRD2 codes
are considered to be limit or user errors, not system
are considered to be limit or user errors, not system
errors:
errors:
v
-63 = 'SCHEDULE' (for example, CONNECT)
v
-63 = 'SCHEDULE' (for example, CONNECT)
operation requested from an active LUW
operation requested from an active LUW
v
-64 = Database log space exhausted
v
-64 = Database log space exhausted
v
-65 = Operation not valid in an active LUW
v
-65 = Operation not valid in an active LUW
v
-92 = Checkpoint in progress, try later
v
-92 = Checkpoint in progress, try later
v
137 = Duplicate found during sort of unique index,
v
137 = Duplicate found during sort of unique index,
unique constraint, or primary key
unique constraint, or primary key
For a complete list of possible SQLERRD2 values, see
For a complete list of possible SQLERRD2 values, see
Chapter 17, “DBSS Return Codes,” on page 231.
Chapter 17, “DBSS Return Codes,” on page 231.
System Programmer Response: SQLERRD2 in
System Programmer Response: Use SQLERRP and
message ARI0504I is the DBSS return code if
SQLERRD1 in message ARI0504I to determine more
SQLERRD2 is not zero. For more information about the
information about the error. Verify that the database
error, see Chapter 17, “DBSS Return Codes,” on page
catalog has not been destroyed. If this is a system error:
231. If SQLERRD2 is zero, a database system error has
Make a record of what went wrong and contact the
occurred. In that case, make a record of what went
designated support group for your installation.
wrong and contact the designated support group for
your installation.
319
SQLSTATE 57028.
-906
The current program was cancelled
because of a system error. The program
System Action: Processing has ended for this logical
exception is as follows: exception-type
unit of work and all changes to the database have been
psw1 psw2
rolled back.
Explanation: While the system was executing a
User Response: Resubmit your current job at a later
package, a program exception occurred.
time.
SQLSTATE 58023.
-913
Unsuccessful execution caused by
System Action: Processing has ended.
timeout. Reason code reason-code, type of
User Response: Notify your system programmer.
resource resource-type, and resource name
resource-name.
System Programmer Response: The exception-type
and associated PSW shown in the message should aid
Explanation: A CALL statement has timed out while
in problem determination. If a database system error
waiting for a stored procedure server. The startup
occurred, make a record of what went wrong and
parameter PTIMEOUT determines the maximum time
contact the designated support group for your
the database manager will wait for a stored procedure
installation.
server to be assigned for an SQL CALL statement.
Possible reason codes are:
-911
The current logical unit of work was
rolled back because of a deadlock or
1
An agent has exceeded the allowed time
timeout. It was waiting for a lock-level
to wait for a stored procedure server
lock in dbspace = dbspace-number held by
to become available.
user {job-name|sql-userid}. Reason code =
code.
2
A stored procedure server failed to
start within the allowed time.
Explanation: The current unit of work was involved
in an unresolved contention for use of an object and
SQLSTATE: 57033
had to be rolled back.
System Action: The statement terminates.
The reason codes are as follows:
User Response: Run the application again when the
2
transaction rolled back due to deadlock.
stored procedure servers are less busy. Consider
68
transaction rolled back due to lock timeout.
rebalancing the stored procedure server workload, or
defining additional stored procedure servers.
The value of lock-level can be any one of DBSPACE,
TABLE, INDEX PAGE, PAGE, INDEX KEY, or ROW.
-914
A ROLLBACK of the current logical
unit of work was scheduled because of
SQLSTATE 40001.
a user CANCEL request.
System Action: Processing has ended for this logical
Explanation: A CANCEL request has been issued. The
unit of work and all changes to the database have been
CANCEL could be initiated by the user or by the
rolled back.
system. The CANCEL initiated by the system is a result
User Response: If a deadlock occurred, resubmit your
of reaching the limit on lock request blocks.
current job at a later time.
SQLSTATE 57014.
If a lock timeout occurred, determine if the lock
System Action:
timeout value is too short or resubmit your current job
v The ROLLBACK is scheduled.
at a later time.
v The SQLCODE is returned to the application.
Operator Response: If a lock timeout occurred and it
v For a VSE system online user, the communication
is determined that the lock timeout value is too short,
path to the database manager remains unavailable
the lock timeout value can be increased by using the
until the required rollback is completed.
SET LTIMEOUT new-time command.
User Response: You may continue to use SQL.
-912
The current logical unit of work was
If the user did not issue a CANCEL request, then retry
rolled back because of excessive
at a later time and if the operation is still receiving an
(system-wide) lock requests.
SQLCODE of -914, contact your system programmer
about increasing the NLRBU or the NLRBS parameters
Explanation: The system has encountered too many
when starting the application server.
system lock requests and has ended processing for this
logical unit of work.
320
Messages and Codes
Make a record of what went wrong and contact the
-915
The current logical unit of work was
designated support group for your installation.
rolled back because of excessive locks
held for this logical unit of work.
-923
The index was marked invalid.
Explanation: The user has issued too many lock
requests within the logical unit of work.
Explanation: One of the following may have
happened during ROLLBACK, UNDO or REDO
SQLSTATE 57029.
processing:
System Action: Processing has ended and all changes
v The database manager cannot obtain a logical index
to the data base have been rolled back.
page. The shortage of index pages can result from
the ROLLBACK or UNDO of either a DROP INDEX,
User Response: Issue a COMMIT statement between
a REORGANIZE INDEX, a deletion of a row, or an
lock requests and rerun.
update of a row. It can also result from the REDO of
either a CREATE INDEX, an insertion of a row, or an
-916
The current logical unit of work was
update of a row.
rolled back because of operator action.
v The database manager cannot obtain a physical index
Explanation: The system operator entered the FORCE
page. The shortage of index pages can result from
command to cause ROLLBACK of the current logical
the ROLLBACK or UNDO of either a DROP INDEX,
unit of work.
a REORGANIZE INDEX, a deletion of a row, or an
update of a row. It can also result from the REDO of
SQLSTATE 57027.
either a CREATE INDEX, an insertion of a row, or an
System Action: ROLLBACK logical unit of work.
update of a row.
v Not enough virtual storage or not enough room in a
User Response: You may continue to use SQL.
temporary DBSPACE exists to recreate an index. The
shortage can result from the ROLLBACK or UNDO
-917
The package was not created and the
of either a DROP INDEX or REORGANIZE INDEX,
logical unit of work was rolled back due
or from the REDO of a CREATE INDEX or
to a system error.
REORGANIZE INDEX.
Explanation: During preprocessing or the creation of a
SQLSTATE 51012.
nonmodifiable extended dynamic package that was
processed with the ERROR bind option, an error
System Action: The database manager completed the
occurred that prevents the package from being created.
ROLLBACK, UNDO, or REDO without updating the
The logical unit of work was rolled back (SQLWARN0
index and marked the index invalid. You may now
= W, SQLWARN6 = W). Examples of these types of
have more than one invalid index. If the database
errors are invalid section numbers, internal limitations
manager performed an implicit ROLLBACK, the actual
of the system, or a system error (-9XX).
reason for the ROLLBACK (DBSS Return Code) is in
SQLERRD2.
SQLSTATEs:
User Response: Issue the SHOW INVALID operator
42969
Statement too long or invalid section number
command to find the invalid indexes. You cannot use
58027
Earlier system error
an invalid index until you have dropped and recreated
it. Drop invalid indexes that you own, and inform your
System Action: Processing has ended for this logical
system programmer about any other invalid indexes.
unit of work and all changes to the database have been
rolled back.
System Programmer Response: Contact the owners of
the invalid indexes and have them drop and recreate
User Response: Correct the cause of the problem and
the indexes.
try again.
-928
An error error occurred while accessing
-921
The system catalog table table-name has
the {user | global} SQLGLOB record.
an incorrect column type column-type.
Explanation: An error occurred when the DRDA
Explanation: The catalog table in the message has an
Resource Adapter tried to access the SQLGLOB VSAM
incorrect column type as shown.
file. Possible causes are:
SQLSTATE 58025.
v neither the user nor the global SQLGLOB record
were found in the SQLGLOB file,
System Action: Processing of the SQL statement has
ended.
v the user SQLGLOB record may have been altered by
an unauthorized change to the SQLGLOB file,
User Response: Notify your system programmer.
v the global SQLGLOB record may have been altered
System Programmer Response: This is a system error.
by an unauthorized change to the SQLGLOB file.
321
SQLSTATE: 55028
SQLSTATE 58004.
System Action: Processing of the SQL statement ends.
System Action: Processing of the SQL statement has
SQLWARN0 and SQLWARN6 of the SQLCA are set to
ended. SQLWARN0 and SQLWARN6 of the SQLCA are
S to signal that a severe error has occurred.
set to S to signal that a severe error has occurred. If a
severe error has occurred, only a CONNECT statement
User Response: Use the DSQU transaction or execute
will be accepted.
the job ARISBGUD to update the user SQLGLOB
parameters, or notify your system programmer.
User Response: Notify your system programmer.
Make a record of what went wrong and contact the
System Programmer Response: Use the DSQG
designated support group for your installation.
transaction or execute the job ARISBGUD to update the
global SQLGLOB parameters, or recreate the SQLGLOB
file. Refer to the DB2 Server for VSE & VM Database
-932
An error occurred when the Resource
Administration manual.
Adapter attempted to get or to free
dynamic storage.
-929
The database name has not been
Explanation: The resource adapter encountered an
defined in the DBNAME Directory.
error in either getting or freeing storage needed for
control blocks and work areas. SQLERRM will be set to
Explanation: The application server name has not
GET or GETVIS for a failure when trying to obtain
been defined in the DBNAME Directory.
storage. SQLERRM will be set to FREE, FREEVIS,
SQLSTATE 42705.
MBXFREE, CURSFREE, or SQLDAFRE.
System Action: Preprocessor or statement execution
SQLSTATEs:
ends.
57011
Dynamic storage could not be obtained.
User Response: Correct the statement. Try again.
58004
Dynamic storage could not be released.
System Action: Processing of the SQL statement ends
-930
Sufficient storage is not available to
and the logical unit of work (if any) is rolled back.
process the statement.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
Explanation: The virtual storage necessary to execute
S to signal that a severe error has occurred.
the command is not available now.
User Response: If possible, retry with a larger user
SQLSTATE 57011.
partition GETVIS area. Otherwise, notify your system
programmer.
System Action: Processing of the SQL statement has
ended.
After a severe error has occurred, only a CONNECT
statement will be accepted. If the resource adaptor is
User Response: Resubmit the statement later. If the
initialized, only a CONNECT statement will be
problem persists, notify your system programmer.
accepted. If the resource adaptor is not initialized, any
System Programmer Response: One of the following
subsequent statement will result in termination of the
has occurred:
application.
v All available virtual storage has been used.
System Programmer Response: SQLERRD1 contains
v A hardware error has occurred.
the GETVIS or FREEVIS macro return code. If
SQLERRD1 is 12, it indicates that not enough space
v An internal database error has occurred.
was available to satisfy the request for additional
storage. SQLERRD2 indicates the amount of space
This error is associated with message ARI0001E. Refer
required.
to the explanation of message ARI0001E for more
information.
-933
The communications path to the server is
Reconfigure the system so that you have a larger DB2
disabled. No further access to this path
Server for VSE partition. If the problem persists, make
is possible. Request Code = request-code.
a record of what went wrong and contact the
Explanation: The database manager detected a
designated support group for your installation.
communication error. This usually indicates that the
communication link to the database partition was
-931
Failure while freeing dynamically
disconnected. This disconnection may have resulted
allocated storage.
from:
v The system operator terminating the database
Explanation: While attempting to free storage during
manager
processing, an error occurred. This is a DB2 Server for
VSE or VSE error.
v A serious system or sub-system error
322
Messages and Codes
v The system operator issuing a FORCE command.
message ARI2908I is displayed on the system console,
record the content of this message. Contact the
SQLERRD1 contains the return code which the resource
designated support group for your installation.
adapter received from the DSC component of the
database manager. SQLERRD2 is the reason code which
-934
An error occurred referencing object. The
DSC received from the system communication facility.
action being performed was action.
Refer to "VSE/Advanced Functions Cross-Partition
Communication Codes" (or to Chapter 20, “DB2 Server
Explanation: An error occurred when the Resource
for VSE Reason Codes,” on page 355) for a list of these
Adapter attempted to perform the specified action on
codes and their meanings. If the reason code is not
the specified object.
listed in the above reference, see the System
object is the program or control block on which the
Programmer Response below for a list of these codes
action is performed.
and their meanings.
action is the action performed.
If communication is through TCP/IP, SQLERRD1
contains the return code which the resource adapter
Note: If the application is linked with SQL/DS Version
received from TCP/IP and SQLERRD2 is always 0.
3 Release 3 or earlier code, the action may not be
Refer to the IBM Language Environment for VSE/ESA:
available.
LE/VSE Enhancements manual for the meaning of the
TCP/IP return codes.
SQLSTATE 58021.
System Action: Processing has ended. The following
Request Code=request-code is the communication
fields are set in the SQLCA:
request code.
v SQLWARN0 and SQLWARN6 are set to S to signal
that a severe error has occurred
TCP/IP request codes:
v SQLERRD1 is set to the error code returned by the
1.
002 - Connect
failing action
2.
008 - Close socket
v SQLERRP contains the name of the module reporting
the error.
SQLSTATEs:
User Response:
57027
Operator action.
Notify your system programmer.
57030
Maximum number of connections to
System Programmer Response:
virtual machine exceeded.
This is when all necessary packages should be added to
40003
System error.
your libraries. If no steps were left out and all ran
System Action: The logical unit of work (if any) of the
successfully, you have a database system error. Make a
application is rolled back.
record of what went wrong and contact the designated
support group for your installation.
v The CIRT termination transaction was internally
activated. The transaction displays message
ARI0406E on the system operator console.
-935
The address of an output variable is
v Any further attempt by the application to access the
outside the partition.
database manager will cause CICS to abort the
Explanation: An address pointing to application
transaction with an AEY9 abend code.
output variables was found to be outside the
application partition boundaries.
Processing of the SQL statement has ended.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
SQLSTATE 51004.
S to signal that a severe error has occurred. If a severe
System Action: The resource adapter returns to the
error has occurred, only a CONNECT statement will be
calling program. Some output variables may have been
accepted.
moved to the user area if they contained valid
User Response: Report this problem to your system
addresses. No moving takes place after the incorrect
programmer. Do not reenter the user transaction until
addresses are found. Processing of the SQL statement
the problem in the database manager is corrected and
has ended. SQLWARN0 and SQLWARN6 of the SQLCA
the database on-line support is restored using the CIRB
are set to S to signal that a severe error has occurred. If
or CIRA transaction.
a severe error has occurred, only a CONNECT
statement will be accepted.
System Programmer Response: Take corrective action
based on the Explanation and message ARI0406E. If
In the SQLCA, SQLERRD1 is set to 5, meaning an
SQLERRD2 shows a reason code that is not
addressing error has occurred.
documented in this manual, record this reason code. If
SQLERRD2 is set to the host variable ordinal position
323
number of the address in error, in the host variable list
-938
Multiple task SQL statements were
or SQLDA descriptor.
submitted in single partition mode.
User Response: Notify your system programmer.
Explanation: After one task had issued an SQL
System Programmer Response: Check the RDIIN
statement, in single user mode, a second task issued a
structure and verify that it is the same as after
subsequent SQL statement. Multi-task SQL statements
preprocessing. If the program looks valid, make a
are not allowed in single user mode.
record of what went wrong and contact the designated
SQLSTATE 56063.
support group for your installation.
System Action: Processing of the SQL statement has
ended. SQLWARN0 and SQLWARN6 of the SQLCA are
-936
DB2 Server for VSE Resource Adapter
set to S to signal that a severe error has occurred. If a
internal error.
severe error has occurred, only a CONNECT statement
Explanation: A database system error has occurred.
will be accepted.
The number of logical units of work prepared for
User Response: Restart the job in multiple user mode.
commit or rollback exceeds an internal limitation.
Applications and terminal users should not receive this
SQLCODE.
-939
An error occurred with the CICS/VSE
service service while accessing the [file]
SQLSTATE Spaces.
file.
System Action: When the Resource Adapter receives
Explanation: An error occurred while the Online
this SQLCODE, it generates message ARI0408E and the
DRDA Resource Adapter is accessing file.
CIRA or CIRB transaction ends.
SQLSTATE 58030.
User Response: Notify your system programmer.
System Action: Processing of the SQL statement ends
System Programmer Response: Make a record of
and the logical unit of work (if any) is rolled back.
what went wrong and contact the designated support
SQLWARN0 and SQLWARN6 of the SQLCA are set to
group for your installation.
S to signal that a severe error has occurred.
User Response: Report the problem to your system
-937
The DB2 Server for VSE online support
administrator.
is ending. No further support to the
application server is possible.
System Programmer Response: To correct a PHLOAD
error, refer to SQLERRD1 for the CICS/VSE RESP2
Explanation: The Resource Adapter Termination
value returned from the CICS/VSE LOAD service.
transaction (CIRT) or the Resource Adapter Remove
Connections transaction (CIRR) was activated by either
a terminal operator or the CIRR transaction was
-940
The SQL statement was not processed
activated internally, by the DB2 Server for VSE online
because the application server resource
support. (The CIRR transaction is internally activated
server-name was not ready or was not
when the online support detects a serious error.)
found.
SQLSTATE 57039.
Explanation: An implicit or explicit connect request
failed due to the following possible reasons:
System Action:
v If you issued a CONNECT statement with the TO
v The CIRT or CIRR termination process continues.
server-name option, either no DB2 Server for VSE
v Any further attempt by the application to access the
application servers were started with the application
database manager will cause CICS/VSE to abort the
server resource name you desired, or you specified
transaction with an AEY9 abend code.
an incorrect server name.
v The logical unit of work (if any) of the application is
v Otherwise, it is likely that your application server
rolled back. SQLWARN0 and SQLWARN6 of the
has not been started with the server name you
SQLCA are set to S to signal that a severe error has
specified in the DBNAME directory or on the CIRB
occurred.
or CIRC CICS transactions.
User Response: The user transaction should not be
v SNA sessions between the AVS gateway and the
reentered until the DB2 Server for VSE online support
target LU may not be established when the user
is restarted using the CIRB transaction.
attempts to connect to a remote application server
through VTAM.
v Intermediate communications server, like TSAF, or
AVS may not be active.
324
Messages and Codes
v The COMDIR has been unloaded by the VM system
64
No pointer to Mailbox found in RDIIN for
after the application program or the application
blocked PUT.
server abended.
For error codes 12 and 16 the amount of storage
If the SQLSTATE is 57011, then a communications
required by the message is placed in SQLERRD2.
directory entry was found with the specified
server-name, but the connection to the target application
For error code 44, the ordinal number of the host
server failed.
variable with the unsupported datatype in the SQLDA
is placed in SQLERRD2.
If the SQLSTATE is 42705, no communications directory
entry was found or the directories were not used. The
Either the application program overlaid some of the
attempt to connect to the target application server
input structure, or this is a system error.
failed.
SQLSTATE 58004.
SQLSTATEs:
System Action: Processing of the SQL statement ends
57011
server-name resource not available.
and the logical unit of work (if any) is rolled back.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
42705
server-name resource not available.
S to signal that a severe error has occurred.
System Action: Processing of the SQL statement ends
User Response: Notify your system programmer.
and the logical unit of work (if any) is rolled back.
After a severe error has occurred, only a CONNECT
SQLWARN0 and SQLWARN6 of the SQLCA are set to
statement will be accepted.
S to signal that a severe error has occurred.
System Programmer Response: Verify that the desired
User Response: After a severe error has occurred,
database machine has been started and that the
only a CONNECT statement will be accepted.
application does not mistakenly overlay any of the DB2
Contact your system administrator to start up the
Server for VSE input structures. If neither of these is
desired application server, communications server, or
the case, then this is a DB2 Server for VSE system error.
SNA sessions, and restart your application.
Make a record of what went wrong and contact the
designated support group for your installation.
-941
An error occurred while the database
manager was building a system
-942
Because of insufficient storage, the
communication message.
database manager cannot process the
SQL statement.
Explanation: An error was detected while building a
cross-partition message. The cause of the error is
Explanation: The DB2 Server for VSE partition does
indicated by the return code in SQLERRD1.
not have enough storage to build internal control
blocks necessary for receiving the SQL statement.
The possible return codes are:
SQLERRD1 contains the length of the storage required.
12
Not enough virtual storage for the message.
Note: This code will be reported for DB2 Server for
16
Incorrect storage area being freed.
VSE protocol.
36
CALLTYPE in RDIIN specifies a function
which is not supported.
SQLSTATE 57011.
40
The specified RDICTYPE requires an input
System Action:
length and RDIMBLEN is not specified in
v The SQLCODE is returned to the user.
RDIIN.
v The logical unit of work is not rolled back.
44
SQLTYPE in SQLDA specifies a data type
User Response: Re-enter the SQL statement after the
which is not supported.
DB2 Server for VSE partition is made larger (or when
the partition is less active).
48
RDIMBLEN in RDIIN does not specify a
length which is equal to the total input.
-944
The system dbspace SYS0002 does not
52
Free area pointer is not equal to the start of
exist.
the Mailbox plus our current offset to it.
Explanation: The database manager was attempting to
56
Space used plus space left not equal to 8K for
store a package on dbspace SYS0002 during
blocked output.
preprocessing; however, SYS0002 does not exist. This
60
Address of blocked PUT Mailbox is less than
dbspace should have been created at DB2 Server for
or equal to zero.
VSE installation time during database generation.
325
SQLSTATE 57026.
System Action: Preprocessing or statement execution
ends. If dbspaces became full during the current logical
System Action: Preprocessing will end.
unit of work, the current logical unit of work is rolled
User Response: Contact your system programmer to
back, the entry or entries in the
find out why dbspace SYS0002 was not created or why
SYSTEM.SYSDBSPACES table for the filled dbspaces is
it no longer exists. When SYS0002 becomes available,
updated to reflect the full condition (the FREEPCT
rerun the preprocessor job.
columns are updated), and the entries in the
SYSTEM.SYSACCESS table for the filled dbspaces are
System Programmer Response: A user with DBA
also updated to reflect the full condition (the TNAME
authority may have deleted the SYS0002 entry in the
columns are updated).
SYSTEM.SYSDBSPACES catalog table. Use the INSERT
command on the SYSTEM.SYSDBSPACES catalog table
User Response: Notify your system programmer or
with the following values for the associated column
database administrator.
names:
System Programmer Response: Acquire a public
dbspace named SYSyyyy as follows:
DBSPACENAME - SYS0002
ACQUIRE PUBLIC DBSPACE NAMED SYSyyyy
DBSPACENO - 2
(PAGES = xxx, PCTINDEX = 0, PCTFREE = 1)
OWNER - PUBLIC
DBSPACETYPE - 1
where SYSyyyy is the name of the new package
NTABS - 0
dbspace (yyyy being a value 0003-9999 that has not
NPAGES - (value specified at database
already been used) and xxx is the number of dbspace
generation for the second
pages for the packages in this new dbspace. This size is
PUBLIC DBSPACE)
installation dependent, as determined by the size of the
NRHEADER - 8
programs at your installation. (The recommended size
PCTINDEX - 0
for the initial dbspace is 1024 pages).
FREEPCT - 1
LOCKMODE - P
Refer to the DB2 Server for VSE System Administration
NACTIVE - 1
manual for exact instructions on acquiring dbspaces for
POOL - (value specified at database
packages.
generation for the second
PUBLIC DBSPACE)
-946
There is insufficient space remaining for
If this fails or does not correct the problem, you have a
packages in dbspace number
system error. A database generation may be necessary.
dbspace-number. Someone with DBA
Make a record of what went wrong and contact the
authority may need to acquire another
designated support group for your installation.
dbspace for packages if all existing
package dbspaces are full.
-945
All dbspaces for packages are full.
Explanation: While attempting to insert a row into a
Acquire another dbspace for additional
package table residing in dbspace number
packages.
dbspace-number, the database manager found that the
dbspace was full.
Explanation: Because all dbspaces for packages are
full, another package dbspace must be acquired before
SQLSTATE 57025.
CREATE VIEW, CREATE PACKAGE, RELOAD
System Action: The current logical unit of work is
PACKAGE, or a preprocessor can run successfully. A
rolled back. The entry in the SYSTEM.SYSDBSPACES
dbspace might be full for one of the following reasons:
catalog table for the filled dbspace is updated to reflect
v All the available packages in the dbspace are used.
the full condition. (The FREEPCT column is updated.)
v No more space is available in the dbspace.
The entries in the SYSTEM.SYSACCESS table for the
filled dbspace are also updated to reflect the full
A FREEPCT column value of zero in a row for a
condition. (The TNAME columns are updated.)
package dbspace in SYSTEM.SYSDBSPACES catalog
Preprocessing will end.
table indicates the second condition. Issuing the
following SELECT indicates (by a count of 255) that all
User Response: Notify your system programmer or
packages in a dbspace are used:
database administrator.
SELECT DBSPACENO,COUNT(*)
System Programmer Response: If other package
FROM SYSTEM.SYSACCESS
dbspaces are not yet full, retry the command. If all
WHERE TNAME NOT LIKE ’%AVAILABLE’
package dbspaces are now full, you need to acquire
GROUP BY DBSPACENO
additional package dbspaces. A dbspace might be full
for one of the following reasons:
SQLSTATE 57025.
v All the available packages in the dbspace are used.
326
Messages and Codes
v No more space is available in the dbspace.
Explanation:
You tried to switch to a new CMS work unit while
A FREEPCT column value of zero in a row for a
running in single user mode. Support is only available
package dbspace entry in the SYSTEM.SYSDBSPACES
in multiple user mode.
catalog table indicates the second condition. Issuing the
following SELECT indicates (by a count of 255) that all
SQLSTATE 56038.
packages in a dbspace are used:
System Action: Processing of this SQL statement ends.
SELECT DBSPACENO,COUNT(*)
FROM SYSTEM.SYSACCESS
User Response: If you were operating in single user
WHERE TNAME NOT LIKE ’%AVAILABLE’
mode, rerun the program in multiple user mode.
GROUP BY DBSPACENO
Format 3
Acquire a PUBLIC DBSPACE named SYSyyyy as
If string is DBNAME parameter in preprocessor or
follows:
DBSU, the Explanation, SQLSTATE value, System
ACQUIRE PUBLIC DBSPACE NAMED SYSyyyy
Action and User Response are as follows:
(PAGES = xxx, PCTINDEX = 0, PCTFREE = 1)
Explanation: This environment does not support the
DBNAME parameter in the preprocessor or the DBS
where SYSyyyy is the name of the new package
Utility.
DBSPACE (yyyy being a value 0003-9999 that has not
already been used) and xxx is the number of dbspace
SQLSTATE 56038.
pages for the packages in this new dbspace. This size is
System Action: The statement is not executed.
installation dependent, as determined by the size of the
programs at your installation. (The recommended size
User Response: Correct the error. Try again.
for the initial dbspace is 1024 pages.)
Format 4
Refer to the DB2 Server for VSE System Administration
If string is RESULT SET PROCESSING, the
manual for exact instructions on acquiring dbspaces for
Explanation, SQLSTATE value, System Action and User
packages.
Response are as follows:
Explanation: You tried to process result sets over
-947
This environment does not support
private protocol. The following is a list of statements
string.
that are not supported when private protocol is in use :
v ASSOCIATE LOCATORS
Explanation: See each Format, below:
v ALLOCATE CURSOR
Format 1
v DESCRIBE PROCEDURE
If string is DATABASE SWITCHING, the Explanation,
v DESCRIBE CURSOR
SQLSTATE value, System Action and User Response
are as follows:
SQLSTATE 56038.
This environment does not support database switching.
System Action: Processing of this SQL statement ends.
Environment may be:
User Response: Preprocess and execute the program
v SINGLE USER MODE
against the database application server and do not use
v DBMODE=N
private protocol.
You tried to connect to a database other than the
Format 5
default one while running in single user mode.
If string is AMODE24 ARIUXIT, the Explanation,
Database Switching Support is only available in
SQLSTATE value, System Action and User Response
multiple user mode with DBMODE=L or DBMODE=G.
are as follows:
SQLSTATE 56038.
Explanation: You tried to connect to a remote DRDA
application server, and your accounting exit is
System Action: The statement is not executed.
link-edited in AMODE 24.
User Response: If you were operating in single user
SQLSTATE 56038.
mode, rerun the program in multiple user mode.
System Action: Connect is not executed.
Format 2
User Response: Link-edit the accounting exit with
If string is CMS WORK UNITS, the Explanation,
AMODE ANY, RMODE 24. Try again.
SQLSTATE value, System Action and User Response
are as follows:
327
SQLWARN0 and SQLWARN6 of the SQLCA are set to
-949
A system error has occurred. Reason
S to signal that a severe error has occurred.
Code = reason-code.
User Response: Report this problem to your system
Explanation: The database manager has encountered
programmer.
an Operating System error. SQLERRD1 contains the
return code from the Operating System if one exists.
System Programmer Response: Create the file file.
The possible Reason Codes are:
Refer to the DB2 Server for VSE Program Directory for
the steps to follow.
01
An error occurred while the Resource
Adapter was attempting to EXTRACT
the current work unit id.
-994
The row with charname = charname does
not exist in the file file.
SQLSTATE 58024.
Explanation: The character table for charname cannot
System Action: The statement is not executed.
be loaded by the DRDA Resource Adapter because the
required row does not exist in the file file.
User Response: Notify your system programmer.
SQLSTATE 57045.
System Programmer Response: Make a record of
what went wrong. Ensure that both the Reason Code
System Action: Processing of the SQL statement ends
and the return code are included in this information.
and the logical unit of work (if any) is rolled back.
Contact the designated support group for your
SQLWARN0 and SQLWARN6 of the SQLCA are set to
installation.
S to signal that a severe error has occurred.
User Response: Report this problem to your system
-965
FORMAT 1
programmer.
Stored procedure proc-name
System Programmer Response: Create the file file to
terminated abnormally.
include the required character translation table. Refer to
FORMAT 2
the DB2 Server for VSE Program Directory for the steps
Stored procedure proc-name
to follow.
terminated abnormally for AUTHID
authid.
-8001
Product key validation failed.
Explanation: DB2 received an SQL CALL statement
for a stored procedure. The stored procedure
Explanation: A valid product license key is not found
terminated abnormally while attempting to execute the
or is invalid. A valid key is required to run DB2 Server
statement.
for VSE. SQLERRD1 contains the return code from the
validation. The possible values are:
proc-name
The name of the stored procedure that
8
The key is not found or the key that was
terminated abnormally.
found is invalid.
authid The authorization ID associated with the
20
The key validation routine is not loaded.
stored procedure.
SQLSTATE 42968.
SQLSTATE: 51021
System Action: Processing of the SQL statement ends
System Action: The statement cannot be executed. If
and the logical unit of work (if any) is rolled back.
the procedure has exceeded the maximum abend count,
SQLWARN0 and SQLWARN6 of the SQLCA are set to
which is determined by the startup parameter
S to signal that a severe error has occurred.
PROCMXAB, then the procedure proc-name is stopped
User Response: Report this error to your system
and further requests to call it are rejected.
programmer.
User Response: Correct the errors in the procedure,
System Programmer Response: Obtain and install a
and then issue START PROC command to activate the
valid key for the product. A valid key can be obtained
stored procedure.
by contacting your IBM representative. Instructions for
installing the key are found in the DB2 Server for VSE
-993
The file file cannot be found.
Program Directory.
Explanation: The file file cannot be found by the
DRDA Resource Adapter.
-15000
The object-type object-name must have a
status of status, and not be in use, before
SQLSTATE 57044.
it can be altered or dropped.
System Action: Processing of the SQL statement ends
Explanation: A stored procedure must have been
and the logical unit of work (if any) is rolled back.
stopped with the REJECT option, giving a status of
328
Messages and Codes
STOP-REJ, and not be running in a stored procedure
v X’02’ which indicates that the error was discovered
server, before an ALTER or DROP of that procedure can
at the application server.
be processed. In addition, no agents can be running the
procedure. A stored procedure server must have been
The second byte of the sub-code should be X’00’, unless
stopped with IMPL=NO before an ALTER or DROP of
the reply message has an error code defined. The error
that stored procedure server can be processed.
code value should be placed in the second byte. The
reply messages with error codes defined are listed
Note: If the CREATE PROCEDURE or CREATE
below:
PSERVER statement is not yet committed, the
DSCINVRM
PROCEDURE or PSERVER cannot be stopped
The sub-code value is a 1-byte hexadecimal
since the entry is not put in the cache until the
value that defines the type of descriptor error.
unit of work is committed. However, in this case,
Refer to the DDM term DSCERRCD in the
as ALTER or DROP is allowed if it is issued in
IBM Distributed Data Management (DDM)
the same unit of work as the CREATE statement.
Architecture, Architecture Reference, Level 4
manual for the 1-byte hexadecimal values.
SQLSTATE 55044.
MGRDEPRM
System Action: Processing of the SQL statement ends.
The sub-code value is a 1-byte hexadecimal
User Response: Issue the appropriate STOP operator
value that defines the manager dependency
command. If the ALTER or DROP PROCEDURE is
that was not met. Refer to the DDM term
rejected because an agent is running the procedure, the
DEPERRCD in the IBM Distributed Data
SHOW PROC command can be used to monitor
Management (DDM) Architecture, Architecture
activity and determine when the agent(s) have finished
Reference, Level 4 manual for the 1-byte
running the procedure. Once no agents are running the
hexadecimal values. No FFDC dump.
procedure, issue the ALTER or DROP statement again.
PRCCNVRM
The sub-code value is a 1-byte hexadecimal
-30020
Execution failed because of a DRDA
value that defines the type of conversation
protocol error that caused deallocation
protocol error. Refer to the DDM term
of the conversation. Reason Code =
PRCCNVCD in the IBM Distributed Data
reason-code(sub-code)
Management (DDM) Architecture, Architecture
Reference, Level 4 manual for the 1-byte
Explanation: The reason-code value is the 2-byte
hexadecimal values.
hexadecimal code point for the DDM reply message
that reported the error and is one of the following:
SYNTAXRM
The sub-code value is a 1-byte hexadecimal
v X’1232’ - AGNPRMRM
value that defines the type of syntax error.
v X’1254’ - CMDCHKRM
Refer to the DDM term SYNERRCD in the
v X’220A’ - DSCINVRM
IBM Distributed Data Management (DDM)
v X’220E’ - DTAMCHRM
Architecture, Architecture Reference, Level 4
manual for the 1-byte hexadecimal values.
v X’1218’ - MGRDEPRM
v X’1245’ - PRCCNVRM
SQLSTATE 58009.
v X’2202’ - QRYNOPRM
System Action: Processing of the SQL statement ends
v X’220F’ - QRYPOPRM
and the logical unit of work (if any) is rolled back.
v X’2207’ - RDBACCRM
SQLWARN0 and SQLWARN6 of the SQLCA are set to
v X’2204’ - RDBNACRM
S to signal that a severe error has occurred.
v X’124C’ - SYNTAXRM
User Response: After a severe error has occurred,
only a CONNECT statement will be accepted.
When the error is reported at the application requester,
System Programmer Response: This is a DRDA
the reason-code is the 2-byte hexadecimal code point of
protocol error. Make a record of what went wrong and
the reply message that most closely defines the error
contact the designated support group.
condition.
The sub-code is a 2-byte hexadecimal value represented
-30021
Execution failed because of a DRDA
as a hexadecimal string constant. The first byte of the
protocol error that will affect the
sub-code is defined as:
successful execution of subsequent
DDM commands or SQL statements.
v X’01’ which indicates that the error was discovered
Manager manager at level level is not
at the application requester.
supported.
329
Explanation: The manager value is the 2-byte
-30041
Execution failed because of unavailable
hexadecimal code point for the DDM manager class
resources that affect the successful
identified as not supported in the EXCSATRD that
execution of subsequent commands or
reported the error. Refer to the DDM term MGRLVL in
SQL statements: Application server
the IBM Distributed Data Management (DDM)
server-name, type of resource resource-type,
Architecture, Architecture Reference, Level 4 manual for
reason reason-code (sub-code).
the 2-byte hexadecimal values.
Explanation: The application server has problems
The manager level is the decimal value for the manager
obtaining or freeing resources that are needed to
class identified as not supported in the EXCSATRD that
process the current request before or after the request is
reported the error. Refer to the DDM term MGRLVL in
executed by the target relational database manager. The
the IBM Distributed Data Management (DDM)
server-name identifies the target application server.
Architecture, Architecture Reference, Level 4 manual for
more information.
The resource-type indicates the type of resource
involved, such as storage. If the resource-type is
SQLSTATE 58010.
″Encrypt″ or ″Decrypt″, the user exits for password
System Action: The attempt to connect to the
encryption or decryption are unavailable or had an
database is not successful. The resource adapter returns
error. The reason-code may or may not contain product
to the application with SQLCA fields SQLWARN0 and
specific information, depending on the product-id
SQLWARN6 both set to S, indicating a serious system
involved. The sub-code is a 2-byte hexadecimal value
error.
represented as a hexadecimal string constant. The first
byte of sub-code is defined as:
User Response: Do not continue processing. Notify
v X’01’ indicates that the error was discovered at the
your system programmer.
application requester.
v X’02’ indicates that the error was discovered at the
-30040
Execution failed because of unavailable
application server.
resources that do not affect the
successful execution of subsequent
If the second byte of sub-code is not X’00’ it is defined
commands and SQL statements:
as:
Application server server-name, type of
v X’01’ indicates that the user exit for
resource resource-type, reason
encryption/decryption is not available.
reason-code(sub-code).
v X’02’ indicates that the user exit for
Explanation: The application server has problems
encryption/decryption encountered an error.
obtaining or freeing resources that are needed to
process the current request before or after the request is
SQLSTATE 57013.
executed by the target relational database manager.
System Action: Processing of the SQL statement ends
server-name identifies the target application server.
and the logical unit of work (if any) is rolled back.
resource-type indicates the type of resource involved,
SQLWARN0 and SQLWARN6 of the SQLCA are set to
such as storage; reason-code may or may not contain
S to signal that a severe error has occurred.
product-specific information, depending on the product
User Response: After a severe error has occurred,
ID involved. The sub-code is a 2-byte hexadecimal value
only a CONNECT statement will be accepted. If
represented as a hexadecimal string constant. The first
resource-type is ″Encrypt″ or ″Decrypt″, disable
byte of the sub-code is defined as:
password encryption/decryption by removing the
v X‘01’ indicates that the error was discovered at the
PWDENC tag from the DBNAME directory or setting it
application requester.
to N. Reload the DBNAME directory and try again.
v X’02’ indicates that the error was discovered at the
Notify your system programmer of this error.
application server.
System Programmer Response: If the second byte of
sub-code is X’01’, install the encryption/decryption user
The second byte of the sub-code is X’00.
exit, as described in the DB2 Server for VSE System
Administration manual. If the problem persists, make a
SQLSTATE 57012.
record of what went wrong and contact the designated
System Action: The SQL statement is not processed.
support group.
User Response: Resubmit the statement later. If the
problem persists, notify your system programmer.
-30050
The ddm-command-codepoint command is
invalid while the bind process is in
progress.
Explanation: An attempt was made to execute a
specific DDM command that is invalid while a bind
330
Messages and Codes
process is in progress. BNDSQLSTT, RDBCMM,
v The person who preprocesses the program does not
RDBRLLBCK, and ENDBND are the only legal DDM
have the authority to specify the value pkgownid for
commands that you can issue while a bind process is in
the OWNER parameter.
progress. The ddm-command-codepoint command is a two
v When the target application server is a DB2 Server
byte hexadecimal codepoint.
for VSE server, the value of the OWNER parameter
(of SQLPREP EXEC or CREATE PACKAGE) is not
SQLSTATE 58011.
the same as that of:
System Action: The SQL statement is not processed.
- the COLLECTION-ID portion for the PREPNAME
The resource adapter returns to the application with
parameter
SQLCA fields SQLWARN0 and SQLWARN6 both set to
- the USERID parameter when the
S, indicating a serious system error.
COLLECTION-ID portion for the PREPNAME
parameter is not specified
User Response: Do not continue processing. Notify
- the connected user’s id as it is known to the target
your system programmer of this DRDA protocol error.
application server when the USERID parameter is
not specified and the COLLECTION-ID portion
-30051
The bind process with specified package
for the PREPNAME parameter is not specified
name and consistency token is not
active.
SQLSTATE 42506.
Explanation: An attempt was made to execute a DDM
System Action: The SQL statement is not processed,
BNDSQLSTT or ENDBND command for a bind process
or the preprocessing of the program has ended with no
that was not active.
package created.
SQLSTATE 58012.
-30000
(SQLSTATE 58008)
-30020
(SQLSTATE 58009)
System Action: The preprocessing of the program
ends. No package is created. The resource adapter
-30021
(SQLSTATE 58010)
returns to the application with SQLCA fields
-30040
(SQLSTATE 57012)
SQLWARN0 and SQLWARN6 both set to S, indicating a
-30041
(SQLSTATE 57013)
serious system error.
-30050
(SQLSTATE 58011)
User Response: Do not continue further processing.
-30051
(SQLSTATE 58012)
Notify your system programmer of this DRDA protocol
-30052
(SQLSTATE 42932)
error.
-30053
(SQLSTATE 42506)
-30060
(SQLSTATE 08004)
-30052
Program preparation assumptions are
incorrect.
-30061
(SQLSTATE 08004)
-30070
(SQLSTATE 58014)
Explanation: An SQL statement that is incompletely
understood by the preprocessor is sent to the target
-30071
(SQLSTATE 58015)
application server with the following assumptions:
-30072
(SQLSTATE 58016)
v All host variables are assumed to be input variables.
-30073
(SQLSTATE 58017)
v The statement is assigned a unique section number.
v The section is executed through the DDM
-30074
(SQLSTATE 58018)
EXCSQLSTT command.
-30080
(SQLSTATE 08001)
At least one of these assumptions is incorrect according
-30090
(SQLSTATE 25000)
to the target application server.
-30060
Application Server server-name
SQLSTATE 42932.
authorization failure.
System Action: The preprocessing of the program has
Explanation: The user is not authorized to access the
ended. No package is created.
application server server-name.
User Response: Do not continue processing. Notify
SQLSTATE 08004.
your system programmer and database administrator of
this DRDA protocol error.
System Action: Processing of the SQL statement ends
and the logical unit of work (if any) is rolled back.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
-30053
Owner pkgownid authorization failure.
S to signal that a severe error has occurred.
Explanation: An authorization error occurred
User Response: After a severe error has occurred,
associated with pkgownid when preprocessing a
only a CONNECT statement will be accepted.
program. The following are some possible scenarios
where this error may occur:
331
subsequent DRDA commands and SQL statements
-30061
Application server server-name is not
issued by the application program. The
found.
ddm-command-type command is a two byte hexadecimal
Explanation: The user attempted to connect to an
codepoint.
application server server-name which cannot be found.
SQLSTATE 58016.
SQLSTATE 08004.
System Action: Processing of the SQL statement ends
System Action: Processing of the SQL statement ends
and the logical unit of work (if any) is rolled back.
and the logical unit of work (if any) is rolled back.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
SQLWARN0 and SQLWARN6 of the SQLCA are set to
S to signal that a severe error has occurred.
S to signal that a severe error has occurred.
System Programmer Response: Make a record of
User Response: After a severe error has occurred,
what went wrong and contact the designated support
only a CONNECT statement will be accepted.
group.
Contact your system administrator to start up the
desired application server and restart your application.
-30073
Value not supported for ddm-parameter
parameter.
-30070
ddm-command-codepoint DDM command
Explanation: The target does not support a particular
is not supported.
DDM command parameter value. The error causes
termination of processing, but does not affect the
Explanation: The target does not support a particular
processing of subsequent DDM commands and SQL
DDM command. The error causes the command
statements issued by the application program. The
processing to end, but does not affect the processing of
ddm-command-type command is a two byte hexadecimal
subsequent DDM commands and SQL statements
codepoint.
issued by the application program. The
ddm-command-codepoint command is a two byte
SQLSTATE 58017.
hexadecimal codepoint.
System Action: The SQL statement is not processed.
SQLSTATE 58014.
User Response: Do not continue processing. Notify
System Action: The SQL statement is not processed.
your system programmer and database administrator of
this DRDA protocol error.
User Response: Do not continue processing. Notify
your system programmer and database administrator of
this DRDA protocol error.
-30074
There is no support for the reply
message with a codepoint of
codepoint(svrcod)
-30071
There is no support for the DDM object
ddm-object-type.
Explanation: The application server has returned a
reply message that is not known to the application
Explanation: The application server does not support
requester. DDM architecture defines the valid codepoints
a particular DDM object. The error causes current DDM
and svrcod values for reply messages.
command processing to end, but does not affect the
processing of subsequent DDM commands and SQL
SQLSTATE 58018.
statements issued by the application program. The
System Action: The SQL statement has produced
ddm-command-type command is a two byte hexadecimal
unpredictable results.
codepoint.
User Response: Do not continue processing. Notify
SQLSTATE 58015.
your system programmer and database administrator of
System Action: Processing of the SQL statement ends
this DRDA protocol error.
and the logical unit of work (if any) is rolled back.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
-30080
FORMAT 1
S to signal that a severe error has occurred.
Communication error occurred.
User Response: After a severe error has occurred,
FUNCTION: function
only a CONNECT statement will be accepted.
RETCODE: retcode
CDBCOMPL: {0|1}
CDBSYNC: {0|1}
-30072
There is no support for the DDM
CDBFREE: {0|1}
command parameter ddm-parameter.
CDBRECV: {0|1}
Explanation: The target does not support a particular
CDBSIG: {0|1}
DDM command parameter. The error causes command
CDBCONF: {0|1}
processing to end, but does not affect the processing of
CDBERR: {0|1}
332
Messages and Codes
CDBERRCD: cdberrcd
CDBSYNRB: {0|1}
FORMAT 2
Communication error occurred.
FUNCTION: function
RETCODE: X’TCP/IP retcode’
Explanation: This SQLCODE reports TCP/IP
communications errors that are visible to an application
requester or application server.
One possible reason is that a FORCE command was
issued by the DB2 Server for VSE operator.
System Action: Processing of the SQL statement ends
and the logical unit of work (if any) is rolled back.
SQLWARN0 and SQLWARN6 of the SQLCA are set to
S to signal that a severe error has occurred.
User Response: After a severe error has occurred,
only a CONNECT statement will be accepted.
System Programmer Response: Take corrective action
based on the Explanation and the User Response.
-30090
The remote operation is invalid for this
application execution environment.
Explanation: You are trying to update a read-only
application server, or to dynamically prepare or execute
a COMMIT or ROLLBACK statement against a
read-only application server.
SQLSTATE 25000.
System Action: The SQL statement is not processed.
User Response: Issue other non-update SQL
statements or notify your database administrator.
333
Chapter 19. SQLSTATEs
If you have the Remote unit of work feature, the
25
Invalid Transaction State
SQLSTATE value can provide application
26
Invalid SQL Statement Identifier
programs with common codes for common error
conditions that can occur in any of the DB2
27
Triggered Data Change Violation
family of database systems including DB2 Server
28
Invalid Authorization Specification
for VSE.
2B
Dependent Privilege Descriptors Still Exist
An SQLSTATE field is returned in the SQLCA for
2C
Invalid Character Set Name
all warnings and errors that can be returned from
executing SQL statements. The SQLCA contains
2D
Invalid Transaction Termination
both an SQLCODE and a corresponding
2E
Invalid Connection Name
SQLSTATE value, if applicable. If, however, you
are running an SQL/DS Version 2 Release 2 or
33
Invalid SQL Descriptor Name
earlier database that is connected to a DB2 Server
34
Invalid Cursor Name
for VSE Version 7 Release 1 user machine, the
DB2 Server for VSE system has no control of the
35
Invalid Condition Number
SQLSTATE value returned to you.
37
Syntax Error (Discontinued)
The application programs, when SQLSTATEs are
38
External Function Exception
fully implemented, can test for classes of errors
39
External Function Call Exception
that are common to all products, or for specific
errors that are unique to a product.
3C
Ambiguous Cursor Name
3D
Invalid Catalog Name
SQLSTATE values are comprised of a
two-character class code value, followed by a
3F
Invalid Collection (Schema) Name
three-character subclass code value. Class code
40
Transaction Rollback (Serialization
values represent classes of successful (class codes
Failure)
00 and 01) and unsuccessful (all other class codes)
execution conditions.
42
Syntax Error or Access Rule Violation
425
Access Violation
The SQLSTATE class codes defined by IBM SQL
426
Syntax Error
and ISO/ANSI are:
427
Duplicate or Undefined Name
428
Invalid Operand or Inconsistent
00
Unqualified Successful Completion
Specification
01
Warning
429
Miscellaneous SQL or Product
01H External Function Warning
Restriction
02
No Data
44
WITH CHECK OPTION Violation
07
Dynamic SQL Error
51
Invalid Application State
08
Connection Exception
52
Duplicate or Undefined Name
(Discontinued)
09
Triggered Action Exception
53
Invalid Operand or Inconsistent
0A
Feature Not Supported
Specification (DB2 and SQL/DS only)
0F
Invalid Token
54
SQL or Product Limit Exceeded
21
Cardinality Violation
55
Object Not in Prerequisite State
22
Data Exception
56
Miscellaneous SQL or Product Error
23
Constraint Violation
57
Resource Not Available or Operator
24
Invalid Cursor State
Intervention
335
SQLSTATEs
579
Request Suspended - Intervention
37501
changed to
42601
Required
37502
changed to
42602
37503
changed to
42603
58
System Error
37504
changed to
42604
HY Call Level Interface
37505
changed to
42605
37506
changed to
42606
HZ Remote Database Access
37507
changed to
42607
S1
ODBC Interface
37509
changed to
42609
37510
changed to
42610
Programmers who want to use SQLSTATE as the
37511
changed to
42611
basis of their application’s return codes may
37512
changed to
42612
define SQLCODE numbers above 32767,
37514
changed to
42614
SQLSTATE classes beginning with the characters
37515
changed to
42615
’7’ through ’9’ or ’I’ through ’Z’ and subclasses
37517
changed to
42617
for any class beginning with the characters ’I’
37518
changed to
42618
through ’Z’. These value ranges will not be used
by IBM SQL or ISO/ANSI.
40000
changed to
40001
42507
changed to
08004
The SQLSTATE values have been standardized in
SQL92 the (ISO IS 9075:1992, Database Language
51001
changed to
07002
SQL manual). If the SQLSTATE values of all
51011
changed to
0A001
databases comply with SQL92, customers who are
51018
changed to
08003
writing applications which are either portable
52001
changed to
42701
across SQL implementations or have to connect to
52002
changed to
42702
more than one SQL implementation can thus rely
52003
changed to
42703
on a consistent SQLSTATE being returned to
52004
changed to
42704
report the same diagnostic condition.
52005
changed to
42705
52006
changed to
42706
IBM standardized diagnostic reporting across its
52007
changed to
42707
various databases by complying with the
52008
changed to
34000
SQLSTATE mechanism proposed in the
52009
changed to
42709
ISO/ANSI SQL2 the (DIS 9075:199x(E) Database
52010
changed to
42710
Language SQL2) draft a few years ago. However,
52011
changed to
42711
the SQLSTATE values in the final published
52012
changed to
42712
version of SQL92 deviate in many ways from the
52013
changed to
3C000
scheme that SQL/DS was planning to follow a
52017
changed to
08004
few years ago. As a result, SQL/DS is
52019
changed to
42719
implementing those changes in Version 3 Release
53002
changed to
42802
5 to comply with SQL92.
53003
changed to
42803
53005
changed to
42805
Here is a summary of the changes:
53007
changed to
42807
53008
changed to
42808
01501 changed to 01004
53009
changed to
42809
01502 changed to 01003
53010
changed to
42810
53011
changed to
42811
22509 changed to 42806
53013
changed to
42813
22515 changed to 23515
53015
changed to
42815
22517 changed to 22021
53016
changed to
42816
22518 changed to 22021
53018
changed to
42818
22520 changed to 23520
53019
changed to
42819
23501 changed to 44000
53020
changed to
42820
26503 changed to 07005
53021
changed to
42821
26504 changed to 07003
53023
changed to
42823
26506 changed to 07007
53024
changed to
42824
53025
changed to
42825
53026
changed to
42826
336
Messages and Codes
SQLSTATEs
53027
changed to
42827
-752 on page 309
53028
changed to
42828
0F001
The locator value does not currently
53029
changed to
42829
represent any value.
53031
changed to
42831
53032
changed to
42832
-423 on page 281
53034
changed to
42834
0A501
Security Failure
53042
changed to
42842
53052
changed to
42852
-30080 on page 332
53053
changed to
42853
01003
This SQLSTATE was formerly 01502.
53056
changed to
28000
53059
changed to
42859
Null values were eliminated from the
53062
changed to
42862
argument of a column function.
53067
changed to
42867
0 on page 237 for SQLWARN2=W
54003
changed to
42622
55008
changed to
42888
01004
This SQLSTATE was formerly 01501.
55013
changed to
42889
The value of a string column was
56001
changed to
42901
truncated when assigned to a host
56002
changed to
42902
variable.
56003
changed to
42903
56005
changed to
42905
0 on page 237 for SQLWARN1=W
56006
changed to
42906
01501
This SQLSTATE has been changed to
56007
changed to
42907
01004.
56008
changed to
42908
56009
changed to
42909
01502
This SQLSTATE has been changed to
56011
changed to
42911
01003.
56012
changed to
42912
01503
The number or result columns is larger
56013
changed to
42913
than the number of host variables
56014
changed to
42914
provided.
56015
changed to
42915
56017
changed to
42917
0 on page 237 for SQLWARN3=W
56026
changed to
25000
01504
The UPDATE or DELETE statement does
56032
changed to
42932
not include a WHERE clause.
56037
changed to
42937
56039
changed to
42939
0 on page 237 for SQLWARN4=W
56043
changed to
42943
01506
An adjustment was made to a DATE or
56061
changed to
42961
TIMESTAMP value to correct an invalid
56069
changed to
42969
date resulting from an arithmetic
58019
changed to
08001
operation.
58022
changed to
40003
0 on page 237 for SQLWARN7=W
The SQLSTATEs and their corresponding
01507
One or more non-zero digits were
SQLCODEs are listed below. In some cases, the
eliminated from the fractional part of a
SQLSTATE occurs when a particular situation
number used as the operand of a multiply
caused the SQLCODE, and these situations are
or divide operation.
also listed. For more information about the
corresponding SQLCODEs, a page number is
0 on page 237 for SQLWARN7=Z
provided with each reference.
01508
The statement was disqualified for
SQLSTATE
blocking for reasons other than storage.
Meaning and SQLCODE
0 on page 237 for SQLWARN8=W
00000
0 on page 237 for no warnings
01509
Blocking was cancelled for a cursor,
0A001
This SQLSTATE was formerly 51011.
because there is insufficient storage in the
user virtual machine.
The CONNECT statement is invalid,
because the process is not in the
0 on page 237 for SQLWARN9=W
connectable state.
Chapter 19. SQLSTATEs
337
SQLSTATEs
01510
Blocking was canceled for a cursor,
+206 on page 241
because a blocking factor of at least two
01536
During remote bind where existence
rows could not be maintained.
checking is deferred, the server name
0 on page 237 for SQLWARNA=W
specified does not match the current
server.
01511
Performance may not be optimum
because of the number of predicates
+114 on page 237
specified in the WHERE clause.
01539
Connection is successful, but only SBCS
0 on page 237 for SQLWARN5=W
characters should be used.
01512
The REVOKE operation has no effect on
+863 on page 248
CONNECT privileges.
01541
Operator command processing has
+150 on page 239
completed successfully.
01513
A subsequent commit operation will
+825 on page 248
revoke all EXECUTE privileges on the
01542
Authorization ID does not have the
package except for that of the owner.
privilege to perform the operation as
+200 on page 240
specified.
01515
The null value has been assigned to a
+552 on page 246
host variable, because the non-null value
01543
A duplicate constraint has been ignored.
of the column is not within the range of
the host variable.
+541 on page 245
+304 on page 242
01545
An unqualified column name has been
interpreted as a correlated reference.
01516
An inapplicable WITH GRANT OPTION
has been ignored.
+12 on page 237
+558 on page 246
01548
Authorization ID does not have the
privilege to perform the specified
01517
A character that could not be translated
operation on the identified object.
was replaced with a substitute character.
+551 on page 246
0 on page 237 for SQLWARN8=Z
01555
Mixed data is invalid and has been
01519
The null value has been assigned to a
truncated according to SBCS rules.
host variable, because an arithmetic
exception occurred in computing the
0 on page 237 for SQLWARN1=Z
value of the column.
01570
The bind process detected a character
+802 on page 247
string in an INSERT or UPDATE
statement that is too large for the target
01520
The null value has been assigned to a
column.
host variable, because the characters
cannot be translated.
+404 on page 242
+331 on page 242
01571
The bind process detected a numeric
value that is out of range.
01525
The number of INSERT values is not the
same as the number of columns.
+414 on page 244
+117 on page 238
01572
The bind process detected an invalid
datetime format; that is, an invalid string
01532
An undefined object name was detected.
representation or an invalid value.
+204 on page 241
+180 on page 240
01533
An undefined column name was detected.
01573
The bind process detected a null insert or
+202 on page 240
update value is null for a column that
cannot contain null values.
+205 on page 241
+407 on page 243
338
Messages and Codes
SQLSTATEs
01574
The bind process detected an INSERT,
+668 on page 247
UPDATE, or DELETE that is not
01609
The procedure generated more than the
permitted on this object.
maximum allowed number of result sets.
+149 on page 239
Only the first integer result sets have been
returned to the caller.
01575
The bind process detected a
non-updateable column in an INSERT or
+464 on page 245
UPDATE statement.
01610
One or more ad hoc results sets were
+151 on page 239
returned from the procedure.
01576
The bind process detected a CREATE
+466 on page 245
INDEX statement for a view.
01614
There are fewer locations than the
+154 on page 239
number of result sets.
01577
The bind process detected a CREATE
+494 on page 245
VIEW statement that includes an operator
02000
One of the following exceptions occurred:
or operand that is not valid for views.
v The result of the SELECT INTO
+154 on page 239
statement or the subselect of the
INSERT statement was an empty table.
01578
The bind process detected operands of an
operator that are not compatible.
v The number of rows identified in the
searched UPDATE or DELETE
+401 on page 242
statement was zero.
01579
The bind process detected a numeric
v The position of the cursor referenced in
constant that is either too long or has a
the FETCH statement was after the last
value that is not within the range of its
row of the result table.
data type.
+100 on page 237
+405 on page 243
07001
This SQLSTATE was formerly 53017.
01580
The bind process detected an update or
The number of host variables is not the
insert value that is not compatible with
same as the number of parameter
the column.
markers.
+408 on page 243
-313 on page 271
01581
The bind process detected incompatible
07002
This SQLSTATE was formerly 51001.
operands of a UNION operation.
An invalid call parameter list or control
+415 on page 244
block was detected.
01582
The bind process detected a string that is
-804 on page 312
too long.
07003
This SQLSTATE was formerly 26504.
+134 on page 238
The statement identified in the EXECUTE
+416 on page 244
is a select-statement, or it is not in a
01583
The bind process detected a decimal
prepared state.
divide operation that is invalid because
-160 on page 258 for using EXECUTE
the result would have a negative scale.
-504 on page 285 when statement not
+419 on page 245
prepared
01584
The bind process detected an insert or
-516 on page 287 for EXECUTE
update value of a long string column that
is neither a host variable or NULL.
-826 on page 315 for reason code 4 and
EXECUTE
+135 on page 238
07004
This SQLSTATE was formerly 53017.
01585
The bind process detected a table that
cannot be accessed because it is inactive.
Chapter 19. SQLSTATEs
339
SQLSTATEs
The statement contains parameter
21502
A multiple-row UPDATE of a Primary
markers but the USING clause is not
Key is invalid.
specified.
-534 on page 290
-313 on page 271
21504
A multiple-row DELETE from a
07005
This SQLSTATE was formerly 26503.
self-referencing table with a delete rule of
RESTRICT or SET NULL is invalid.
The statement-name of the cursor
identifies a prepared statement that
22001
Character data, right truncation occurred;
cannot be associated with a cursor.
for example, an update or insert value is
a string that is too long for the column.
-512 on page 287
-302 on page 269 when character or
-826 on page 315 for reason code 3.
graphic string is too long
07006
This SQLSTATE was formerly 22507.
-304 on page 270 when date or time value
An input host variable cannot be used
is too large for host variable
because of its data type.
-404 on page 279.
-301 on page 268
22002
A null value or the absence of an
07007
This SQLSTATE was formerly 26506.
indicator parameter was detected; for
example, the null value cannot be
INTO DESCRIPTOR clause must be
assigned to a host variable, because no
specified on an Extended EXECUTE
indicator variable is specified.
against a statement that was prepared via
an Extended PREPARE - Single Row.
-305 on page 270
-811 on page 313
22003
A numeric value is out of range.
08001
Communication error occurred.
-302 on page 269 for numeric overflow or
underflow
-30080 on page 332
-304 on page 270 for numeric overflow or
08003
This SQLSTATE was formerly 51018.
underflow
An error has left the application in an
-413 on page 280
unconnected state.
-425 on page 281
-900 on page 319
-801 on page 310 for arithmetic overflow
08004
The application server rejected
and underflow
establishment of the connection.
-802 on page 310 for arithmetic overflow
-30060 on page 331
and underflow.
-30061 on page 332
22007
An invalid datetime format was detected;
2D528
A COMMIT WORK statement cannot be
that is, an invalid string representation or
dynamically prepared or executed.
an invalid value was specified.
-515 on page 287
-180 on page 264
2D529
A ROLLBACK WORK statement cannot
-181 on page 264.
be dynamically prepared or executed.
22008
Datetime field overflow occurred; for
-515 on page 287
example, an arithmetic operation on a
date or timestamp has a result that is not
21000
The result of a SELECT INTO is a table of
within the valid range of dates, or a
more than one row, or the result of the
datetime value cannot be assigned to a
subquery of a basic predicate is more than
host variable because it is too small.
one value.
-183 on page 265
-810 on page 313
22011
A substring error occurred; for example,
21501
A multiple-row INSERT into a
an argument of SUBSTR is out of range.
self-referencing table is invalid.
340
Messages and Codes
SQLSTATEs
-171 on page 263 when an argument of
22512
A host variable in a predicate is invalid,
SUBSTR is out of range
because its indicator variable is negative.
22012
Division by zero is invalid.
-309 on page 271
-801 on page 310 for division by zero
22515
This SQLSTATE has been changed to
23515.
-802 on page 310 for division by zero.
22517
This SQLSTATE has been changed to
22019
The LIKE predicate has an invalid escape
22021.
character.
22518
This SQLSTATE has been changed to
-131 on page 255
22021.
22021
This SQLSTATE was formerly 22517 or
22519
The Primary or Foreign Key cannot be
22518.
activated.
Character is not in the coded character
-667 on page 301
set.
22520
This SQLSTATE has been changed to
-330 on page 277
23520.
-331 on page 277
22521
The Foreign Key cannot be defined,
22024
This SQLSTATE was formerly 22510.
because the Primary Key of the parent
table is inactive.
A C NUL-terminated input host variable
with length greater than 1, did not
-670 on page 301 for reason code 1
contain a NUL.
22522
CCSID value is not valid at all, not valid
-302 on page 269
for the data type or subtype, or not valid
for the encoding scheme.
22025
The LIKE predicate string pattern
contains an invalid occurrence of an
-189 on page 265
escape character.
22524
A string conversion resulted in truncation.
-131 on page 255
-334 on page 278
22501
The length control field of a variable
23501
This SQLSTATE has been changed to
length string is negative or greater than
44000.
the maximum.
23502
An insert or update value is null, but the
-311 on page 271
column cannot contain null values.
-821 on page 314.
-407 on page 279
22502
Miscellaneous data exceptions occurred;
23503
The insert or update value of a foreign
for example, a floating-point NAN (not a
key is invalid.
number) or invalid data in a packed
decimal field was detected.
-530 on page 290
-424 on page 281
23504
The operation is prevented by the
RESTRICT update or delete rule.
-801 on page 310 for general errors
-532 on page 290
-802 on page 310 for general errors.
23505
A violation of the constraint imposed by a
22504
Mixed data value is improperly formed.
unique index occurred.
-191 on page 265
-803 on page 311
22507
This SQLSTATE has been changed to
23507
A violation of a constraint imposed by a
07006.
field procedure occurred.
22509
This SQLSTATE has been changed to
-681 on page 302
42806.
23515
This SQLSTATE was formerly 22515.
22510
This SQLSTATE has been changed to
22024.
Chapter 19. SQLSTATEs
341
SQLSTATEs
The unique index could not be created,
DECLARE CURSOR, DESCRIBE, DROP
because the table contains duplicate
STATEMENT, and PREPARE (Filling
values of the specified key.
empty section)
-603 on page 294
26503
This SQLSTATE has been changed to
07005.
23520
This SQLSTATE was formerly 22520.
26504
This SQLSTATE has been changed to
The Foreign Key cannot be defined,
07003.
because all of its values are not equal to
the primary key of the parent table.
26505
An extended EXECUTE, DECLARE
CURSOR, or DESCRIBE has been issued
-670 on page 301 for reason code 2
against an empty section.
24501
The identified cursor is not open.
-504 on page 285 when trying to execute a
-160 on page 258 for using FETCH
NULL section
-501 on page 285
26506
This SQLSTATE has been changed to
07007.
-507 on page 286.
26507
An extended EXECUTE with an OUTPUT
24502
The cursor identified in an OPEN
DESCRIPTOR has been issued against a
statement is already open.
section that is not a Single Row SELECT.
-502 on page 285
-826 on page 315 for reason code 6
24503
The cursor identified in the PUT
26508
The statement identified in an extended
statement is a select cursor, or the cursor
PREPARE Single Row is not a
identified in the FETCH statement is an
select-statement.
insert cursor.
-826 on page 315 for reason code 5
-160 on page 258 for using PUT
28000
This SQLSTATE was formerly 53056.
24504
The cursor identified in the UPDATE or
DELETE statement is not positioned on a
Authorization-name or password on
row.
CONNECT is missing or invalid.
-508 on page 286
-564 on page 293
24505
COMMIT is invalid, because blocking is
3C000
This SQLSTATE was formerly 52013.
in effect and an insert cursor is open.
A duplicate cursor name was detected.
-519 on page 288
-517 on page 287
24506
The statement identified in the PREPARE
34000
This SQLSTATE was formerly 52008.
is the select-statement of an open cursor.
An undefined cursor name was detected.
-519 on page 288
-504 on page 285 when cursor name not
24506
The statement identified in the PREPARE
declared
is the select-statement of an open cursor.
37501
This SQLSTATE has been changed to
24516
A cursor has already been assigned to a
42601.
result set.
37502
This SQLSTATE has been changed to
-499 on page 284
42602.
25000
Operation is invalid for the application
37503
This SQLSTATE has been changed to
execution environment.
42603.
-30090 on page 333
37504
This SQLSTATE has been changed to
26501
The statement identified does not exist.
42604.
-516 on page 287 for DESCRIBE or
37505
This SQLSTATE has been changed to
dynamic cursor operation
42605.
-826 on page 315 for reason code 1 and 2
342
Messages and Codes
SQLSTATEs
37506
This SQLSTATE has been changed to
privilege to perform the specified
42606.
operation on the identified object.
37507
This SQLSTATE has been changed to
-551 on page 291
42607.
-566 on page 294.
37509
This SQLSTATE has been changed to
42502
Authorization ID does not have the
42609.
privilege to perform the operation as
37510
This SQLSTATE has been changed to
specified.
42610.
-552 on page 291
37511
This SQLSTATE has been changed to
-554 on page 292
42611.
-555 on page 292
37514
This SQLSTATE has been changed to
42614.
-556 on page 292
37515
This SQLSTATE has been changed to
-606 on page 295
42615.
-610 on page 296
37517
This SQLSTATE has been changed to
-708 on page 306.
42617.
42504
A specified privilege cannot be revoked
37518
This SQLSTATE has been changed to
from a specified authorization-name.
42618.
-556 on page 292 when revokee does not
38003
The statement is not allowed in a function
have privilege
or procedure.
-558 on page 292.
-751 on page 308
42505
Connection authorization failure occurred.
39002
A null value is not allowed for an IN or
INOUT argument when using the
-560 on page 293
SIMPLE CALL calling convention.
-561 on page 293
-470 on page 283
-815 on page 313.
39501
An output argument value returned from
42506
Owner authorization failure occurred.
a function or a procedure was too long.
-30053 on page 331
-450 on page 282
42601
This SQLSTATE was formerly 37501.
40000
This SQLSTATE has been changed to
40001.
A character, token, or clause is invalid or
missing.
40001
This SQLSTATE was formerly 40000.
-104 on page 249 for general errors
Deadlock or timeout with automatic
rollback occurred.
-105 on page 250
-911 on page 320
-106 on page 250 for general errors
40003
This SQLSTATE was formerly 58022.
-109 on page 251
A system error has caused the unit of
-110 on page 251
work to be rolled back.
-115 on page 252
-903 on page 319
-128 on page 254
-933 on page 322 for a for a system error.
-130 on page 255
40503
PRIVATE dbspace is in use by another
-159 on page 257
process.
-160 on page 258 for using ALL,
-710 on page 307
REFERENCE, STRUCTURE, COST, or
42501
Authorization ID does not have the
PLAN
Chapter 19. SQLSTATEs
343
SQLSTATEs
-162 on page 260 when the name is
An invalid use of parameter markers has
missing
been detected.
-524 on page 289
-184 on page 265
-611 on page 296.
-418 on page 280.
42602
This SQLSTATE was formerly 37502.
42611
This SQLSTATE was formerly 37511.
An invalid character in a name has been
An invalid column definition has been
detected.
detected.
-162 on page 260 when the name is
-604 on page 295
incorrect
42612
The statement string is an SQL statement
-165 on page 261
that is not acceptable in the context in
which it is presented.
-210 on page 268.
-084 on page 248
42603
This SQLSTATE was formerly 37503.
-836 on page 317
An unterminated string constant has been
detected.
42614
This SQLSTATE was formerly 37514.
-106 on page 250 for an unterminated
Invalid duplication of keyword has been
string constant
detected.
42604
This SQLSTATE was formerly 37504.
-630 on page 299
An invalid numeric or string constant has
42615
This SQLSTATE was formerly 37515.
been detected.
Invalid alternative has been detected.
-103 on page 249
-168 on page 262
-164 on page 261
-705 on page 306
-166 on page 261
42617
This SQLSTATE was formerly 37517.
-170 on page 262.
The statement string is blank or empty.
42605
This SQLSTATE was formerly 37505.
-104 on page 249 when statement string is
The number of arguments specified for a
empty or blank
scalar function is invalid.
42618
This SQLSTATE was formerly 37518.
-172 on page 264
Host variable is not allowed.
42606
This SQLSTATE was formerly 37506.
-163 on page 261
An invalid hexadecimal constant has been
-312 on page 271.
detected.
42622
This SQLSTATE was formerly 54003.
-167 on page 262
A name or label is too long.
42607
This SQLSTATE was formerly 37507.
-107 on page 250
An invalid operand of a column function
has been detected.
-108 on page 251
-112 on page 251
-116 on page 252
-409 on page 279.
-162 on page 260 when the name is too
long.
42609
This SQLSTATE was formerly 37509.
42701
This SQLSTATE was formerly 52001.
All operands of an operator or predicate
are parameter markers.
A duplicate column name in INSERT or
UPDATE statement was detected.
-417 on page 280
-121 on page 253
42610
This SQLSTATE was formerly 37510.
344
Messages and Codes
SQLSTATEs
42702
This SQLSTATE was formerly 52002.
-618 on page 297
A column reference is ambiguous because
-644 on page 300.
of duplicate names.
42711
This SQLSTATE was formerly 52011.
-203 on page 266
A duplicate column name in an object
-209 on page 267
definition was detected.
42703
This SQLSTATE was formerly 52003.
-612 on page 296
An undefined column name was detected.
42712
This SQLSTATE was formerly 52012.
-201 on page 266
A duplicate table designator in a FROM
clause was detected.
-202 on page 266
-211 on page 268
-205 on page 267
42719
This SQLSTATE was formerly 52019.
-666 on page 300.
The cursor referenced in the extended
42704
This SQLSTATE was formerly 52004.
OPEN, FETCH, PUT, or CLOSE has not
An undefined object or constraint name
been declared in the current unit of work.
was detected.
-518 on page 287
-204 on page 267 for general errors
42724
Unable to access an external program
-206 on page 267
used for a user-defined function or a
procedure.
-608 on page 295
-444 on page 282
-805 on page 312 for a GRANT, REVOKE
or DROP statement.
42802
This SQLSTATE was formerly 53002.
-649 on page 300 for a missing EXPLAIN
The number of insert values is not the
table.
same as the number of columns.
42705
This SQLSTATE was formerly 52005.
-117 on page 252
An undefined server name was detected.
42803
This SQLSTATE was formerly 53003.
-929 on page 322
A column reference in the SELECT or
HAVING clause is invalid, because it is
42706
This SQLSTATE was formerly 52006.
not a grouping column or a column
Column names in ORDER BY are invalid,
reference in the GROUP BY clause is
because all columns of the result table are
invalid.
unnamed.
-119 on page 252
-207 on page 267
42805
This SQLSTATE was formerly 53005.
42707
This SQLSTATE was formerly 52007.
An integer in the ORDER BY clause does
Column name in ORDER BY does not
not identify a column of the result table.
identify a column of the result table.
-125 on page 253
-208 on page 267
42806
This SQLSTATE was formerly 22509.
42709
This SQLSTATE was formerly 52009.
A value cannot be assigned to a host
A duplicate column name in a PRIMARY
variable, because the data types are not
or FOREIGN KEY clause was detected.
compatible.
-537 on page 290
-303 on page 270
42710
This SQLSTATE was formerly 52010.
42807
This SQLSTATE was formerly 53007.
A duplicate object name was detected.
The INSERT, UPDATE, or DELETE is not
permitted on this object.
-601 on page 294
Chapter 19. SQLSTATEs
345
SQLSTATEs
-149 on page 257
-401 on page 278
42808
This SQLSTATE was formerly 53008.
42819
This SQLSTATE was formerly 53019.
A column identified in the INSERT or
An operand of an arithmetic operation is
UPDATE statement is not updateable.
not a number.
-151 on page 257
-402 on page 278
42809
This SQLSTATE was formerly 53009.
42820
This SQLSTATE was formerly 53020.
The identified object is not the type of
A numeric constant is too long, or it has a
object to which the statement applies.
value that is not within the range of its
data type.
-154 on page 257 for using CREATE
INDEX on a view.
-405 on page 279
-204 on page 267 for DROP VIEW table or
42821
This SQLSTATE was formerly 53021.
DROP TABLE view
An update or insert value is not
-657 on page 300
compatible with the column.
-813 on page 313.
-408 on page 279
42810
This SQLSTATE was formerly 53010.
42823
This SQLSTATE was formerly 53023.
A view is identified in a FOREIGN KEY
The SELECT clause of a subquery
clause.
specifies multiple columns.
-157 on page 257 for general errors
-412 on page 279
42811
This SQLSTATE was formerly 53011.
42824
This SQLSTATE was formerly 53024.
The number of columns specified is not
An operand of LIKE is not a string, or the
the same as the number of columns in the
first operand not a column.
SELECT clause.
-132 on page 255
-158 on page 257
-414 on page 280.
42813
This SQLSTATE was formerly 53013.
42825
This SQLSTATE was formerly 53025.
WITH CHECK OPTION cannot be used
The operands of UNION do not have
for the specified view.
compatible columns.
-140 on page 256
-415 on page 280
42815
This SQLSTATE was formerly 53015.
42826
This SQLSTATE was formerly 53026.
The data type, length, value, or CCSID of
The operands of UNION do not have the
an operand is invalid.
same number of columns.
-171 on page 263 for general errors
-422 on page 281 for different number of
-713 on page 307.
items in select lists
42816
This SQLSTATE was formerly 53016.
42827
This SQLSTATE was formerly 53027.
An invalid use of a datetime value or
The table identified in the UPDATE or
duration in an expression has been
DELETE is not the same table designated
detected.
by the cursor.
-182 on page 264
-509 on page 286
-187 on page 265.
42828
This SQLSTATE was formerly 53028.
42818
This SQLSTATE was formerly 53018.
The table designated by the cursor of the
UPDATE or DELETE statement cannot be
The operands of an operator are not
modified, or the cursor is read-only.
compatible.
-510 on page 286
346
Messages and Codes
SQLSTATEs
-520 on page 288.
42859
This SQLSTATE was formerly 53059.
42829
This SQLSTATE was formerly 53029.
An extended PREPARE or DROP
STATEMENT cannot be used to change a
FOR UPDATE OF is invalid, because the
non-modifiable package.
table designated by the cursor cannot be
modified.
-830 on page 316
-126 on page 253
42862
This SQLSTATE was formerly 53062.
-511 on page 287.
An extended dynamic statement cannot
be executed against a non-extended
42830
This SQLSTATE was formerly 53030.
dynamic package.
The Foreign Key does not conform to the
-827 on page 315
description of the Primary Key.
42867
This SQLSTATE was formerly 53067.
-538 on page 290
Conflicting options have been specified.
42831
This SQLSTATE was formerly 53031.
-160 on page 258 for the inconsistent use
A column of a Primary Key cannot allow
of the NEW, CHECK, or ERROR clauses
null values.
42878
An invalid function or procedure name
-542 on page 291
was used with the EXTERNAL keyword.
42832
This SQLSTATE was formerly 53032.
-449 on page 282
The operation is not allowed on system
42884
No function or procedure was found with
objects.
the specified name and compatible
-609 on page 296
arguments.
-709 on page 306
-440 on page 281
-814 on page 313
42886
The IN, OUT, or INOUT parameter
attributes do not match.
-823 on page 314.
-469 on page 283
42834
This SQLSTATE was formerly 53034.
42888
This SQLSTATE was formerly 55008.
SET NULL cannot be specified, because
the Foreign Key does not allow null
The nominated parent table does not have
values.
a Primary Key.
-629 on page 299
-539 on page 291
42842
This SQLSTATE was formerly 53042.
42889
This SQLSTATE was formerly 55013.
A column definition is invalid, because a
The table already has a primary key.
specified option is inconsistent with the
-656 on page 300
column description.
42893
The object or constraint cannot be
-683 on page 303
dropped, because other objects are
42852
This SQLSTATE was formerly 53052.
dependent on it.
Privileges specified in GRANT or
-478 on page 284
REVOKE are invalid or inconsistent.
42895
For static SQL, an input host variable
-557 on page 292
cannot be used, because its data type is
not compatible with the parameter of a
42853
This SQLSTATE was formerly 53053.
procedure or user-defined function.
Both alternatives of an option were
-302 on page 269
specified, or the same option was
specified more than once.
42901
This SQLSTATE was formerly 56001.
-161 on page 260
A column function does not include a
column name.
Chapter 19. SQLSTATEs
347
SQLSTATEs
-111 on page 251
-503 on page 285
42902
This SQLSTATE was formerly 56002.
42913
This SQLSTATE was formerly 56013.
The object of the INSERT, UPDATE, or
An invalid UPDATE or DELETE WHERE
DELETE is also identified in a FROM
CURRENT OF has been detected.
clause.
-535 on page 290
-118 on page 252
42914
This SQLSTATE was formerly 56014.
42903
This SQLSTATE was formerly 56003.
The DELETE is invalid, because a table
A WHERE clause or SET clause includes
referenced in a subquery can be affected
an invalid reference such as a column
by the operation.
function.
-536 on page 290
-120 on page 253
42915
This SQLSTATE was formerly 56015.
42905
This SQLSTATE was formerly 56005.
One or more invalid referential
DISTINCT is specified more than once in
constraints have been detected.
a subselect.
-632 on page 299
-127 on page 254
-648 on page 300
42906
This SQLSTATE was formerly 56006.
42917
This SQLSTATE was formerly 56017.
A column function in a subquery of a
The object cannot be explicitly dropped.
HAVING clause includes an expression
that applies an operator to a correlated
-669 on page 301
reference.
42932
Program preparation assumptions are
-133 on page 255
incorrect.
42907
This SQLSTATE was formerly 56007.
-30052 on page 331
The string is too long.
42937
This SQLSTATE was formerly 56037.
-134 on page 255
Parameter must not have a subtype of
mixed.
-416 on page 280.
-192 on page 265
42908
This SQLSTATE was formerly 56008.
42939
This SQLSTATE was formerly 56039.
The statement does not include a required
column list.
The object cannot be created, because the
specified qualifier (or an DB2 Server for
-153 on page 257
VSE DBSPACE name that starts with SYS)
42909
This SQLSTATE was formerly 56009.
is reserved for system use.
The CREATE VIEW includes an operator
-550 on page 291
or operand that is not valid for views.
-707 on page 306.
-154 on page 257 for general errors
42943
This SQLSTATE was formerly 56043.
42911
This SQLSTATE was formerly 56011.
The database manager has not committed
A decimal divide operation is invalid,
package package-name because it is a
because the result would have a negative
modifiable package and it contains no
scale.
statements.
-419 on page 281
-759 on page 309
42912
This SQLSTATE was formerly 56012.
42961
This SQLSTATE was formerly 56061.
A column cannot be updated, because it
The server name specified does not match
is not identified in the UPDATE clause of
the current server.
the select-statement of the cursor.
-114 on page 251
348
Messages and Codes
SQLSTATEs
42969
This SQLSTATE was formerly 56069.
was originally bound is different than the
character set under which the database
The package was not created and the unit
manager is running.
of work was rolled back because of either
an invalid section number or internal
-833 on page 317
limitations.
51018
This SQLSTATE has been changed to
-917 on page 321
08003.
44000
This SQLSTATE was formerly 23501.
51021
SQL statements cannot be executed until
the application process executes a rollback
The INSERT or UPDATE is not allowed,
operation.
because a resulting row does not satisfy
the view definition.
-965 on page 328
-141 on page 256
51030
The procedure referenced in a DESCRIBE
PROCEDURE statement or an
51001
This SQLSTATE has been changed to
ALLOCATE CURSOR statement has not
07002.
yet been called within the application
51002
The package corresponding to an SQL
process.
statement execution request was not
-480 on page 284
found.
-482 on page 284
-805 on page 312 for any statement other
than GRANT, REVOKE or DROP
52001
This SQLSTATE has been changed to
42701.
51003
Consistency tokens do not match.
52002
This SQLSTATE has been changed to
-818 on page 314
42702.
51004
An address in the SQLDA is invalid.
52003
This SQLSTATE has been changed to
-935 on page 323
42703.
51007
A CONNECT statement has not been
52004
This SQLSTATE has been changed to
executed.
42704.
-563 on page 293
52005
This SQLSTATE has been changed to
42705.
51010
The programmable interface for operator
commands is not valid when within a
52006
This SQLSTATE has been changed to
unit of work.
42706.
-825 on page 315
52007
This SQLSTATE has been changed to
42707.
51011
This SQLSTATE has been changed to
0A001.
52008
This SQLSTATE has been changed to
34000.
51012
Index has been marked invalid.
52009
This SQLSTATE has been changed to
-923 on page 321
42709.
51013
An attempt has been made to use an
52010
This SQLSTATE has been changed to
index that has been marked as invalid.
42710.
-621 on page 298
52011
This SQLSTATE has been changed to
51015
An attempt was made to execute a section
42711.
that was found to be in error at bind
52012
This SQLSTATE has been changed to
time.
42712.
-525 on page 289
52013
This SQLSTATE has been changed to
51016
A package or view cannot be rebound,
3C000.
because the character set under which it
52017
This SQLSTATE has been changed to
08004.
Chapter 19. SQLSTATEs
349
SQLSTATEs
52019
This SQLSTATE has been changed to
53028
This SQLSTATE has been changed to
42719.
42828.
53002
This SQLSTATE has been changed to
53029
This SQLSTATE has been changed to
42802.
42829.
53003
This SQLSTATE has been changed to
53030
This SQLSTATE has been changed to
42803.
42830.
53005
This SQLSTATE has been changed to
53031
This SQLSTATE has been changed to
42805.
42831.
53007
This SQLSTATE has been changed to
53032
This SQLSTATE has been changed to
42807.
42832.
53008
This SQLSTATE has been changed to
53034
This SQLSTATE has been changed to
42808.
42834.
53009
This SQLSTATE has been changed to
53042
This SQLSTATE has been changed to
42809.
42842.
53010
This SQLSTATE has been changed to
53043
Columns with different field procedures
42810.
cannot be compared.
53011
This SQLSTATE has been changed to
-686 on page 303
42811.
53044
The columns have a field procedure, but
53013
This SQLSTATE has been changed to
the field types are not compatible.
42813.
-687 on page 304
53015
This SQLSTATE has been changed to
53052
This SQLSTATE has been changed to
42815.
42852.
53016
This SQLSTATE has been changed to
53053
This SQLSTATE has been changed to
42816.
42853.
53017
This SQLSTATE has been changed to
53056
This SQLSTATE has been changed to
07001 and 07004.
28000.
53018
This SQLSTATE has been changed to
53059
This SQLSTATE has been changed to
42818.
42859.
53019
This SQLSTATE has been changed to
53060
Public dbspaces must be acquired from a
42819.
recoverable storage pool.
53020
This SQLSTATE has been changed to
-706 on page 306
42820.
53062
This SQLSTATE has been changed to
53021
This SQLSTATE has been changed to
42862.
42821.
53067
This SQLSTATE has been changed to
53023
This SQLSTATE has been changed to
42867.
42823.
54001
The statement is too long or too complex.
53024
This SQLSTATE has been changed to
42824.
-101 on page 248
53025
This SQLSTATE has been changed to
54002
A string constant is too long.
42825.
-102 on page 249
53026
This SQLSTATE has been changed to
54003
This SQLSTATE has been changed to
42826.
42622.
53027
This SQLSTATE has been changed to
54004
The statement has too many table names
42827.
or too many items in a SELECT or
INSERT list.
350
Messages and Codes
|
||
|
|
|