Message Reference

SQL30000 - SQL30099

SQL30000N Execution failed because of a Distributed Protocol Error that will not affect the successful execution of subsequent commands or SQL statements: Reason Code "<reason-code(subcode)>".

Explanation: A system error occurred that prevented successful processing of the current environment command or SQL statement. This message (SQLCODE) is produced at statement compilation or execution time.

The command or statement cannot be processed. The current transaction is not rolled back and the application remains connected to the remote database.

User Response: Record the message number and the reason code. Record all error information from the SQLCA, if possible. Attempt to rerun the application.

If sufficient memory resources exist and the problem continues, invoke the Independent Trace Facility at the operating system command prompt. Refer to the Independent Trace Facility in the Troubleshooting Guide for information on how to use this facility.

Required information:

Problem description
SQLCODE and reason code
SQLCA contents if possible
Trace file if possible.

sqlcode: -30000

sqlstate: 58008

SQL30002N The SQL statement cannot be executed due to a prior condition in a chain of statements.

Explanation: An SQL statement was chained to PREPARE, but the PREPARE statement has received a warning SQLCODE that requires the program or end user to either re-issue the chained statement or issue a different SQL request. This error can occur only in a client/server environment.

A distributed client using DRDA has chained an OPEN statement to a PREPARE, but the PREPARE statement received SQLCODE +1140.

The statement cannot be executed as chained.

User Response: The statement must be sent again as a separate request.

sqlcode: -30002

sqlstate: 57057

SQL30020N Execution failed because of a Distributed Protocol Error that will affect the successful execution of subsequent commands and SQL statements: Reason Code "<reason-code>".

Explanation: A system error occurred that prevented successful execution of the current environment command or SQL statement, as well as any subsequent commands or SQL statements.

The command or statement cannot be processed. The current transaction is rolled back and the application is disconnected from the remote database.

User Response: Record the message number (SQLCODE) and the reason code. Record all error information from the SQLCA, if possible. Attempt to connect the remote database and rerun the application.

Required information:

Problem description
SQLCODE and reason code
SQLCA contents if possible
Trace file if possible.

Some possible reason codes include:

121C: Indicates that the user is not authorized to perform the requested command.
1232: The command could not be completed because of a permanent error. In most cases, the server will be in the process of an abend.
220A: The target server has received an invalid data description. If a user SQLDA is specified, ensure that the fields are initialized correctly. Also, ensure that the length does not exceed the maximum allowed length for the data type being used.
If you are using the DB2 Connect product in a gateway server environment with downlevel clients, this error may occur if your application's host variables and the queried table's column descriptions do not match.

sqlcode: -30020

sqlstate: 58009

SQL30021N Execution failed because of a Distributed Protocol Error that will affect the successful execution of subsequent commands and SQL statements: Manager "<manager>" at Level "<level>" not supported.

Explanation: A system error occurred that prevented successful connection of the application to the remote database. This message (SQLCODE) is produced for SQL CONNECT statement. "<manager>" and "<level>" are numeric values that identify the incompatibility between the client and the server.

The command cannot be processed.

User Response: Record the message number, the "<manager>", and "<level>" values. Record all error information from the SQLCA, if possible. Attempt to connect to the remote database again.

If the problem persists, invoke the Independent Trace Facility at the operating system command prompt. Refer to the Independent Trace Facility in the Troubleshooting Guide for information on how to use this facility. Then, contact your service representative with the following information:

Problem description
SQLCODE and reason code
SQLCA contents if possible
Trace file if possible.

sqlcode: -30021

sqlstate: 58010

SQL30040N Execution failed because of unavailable resources that will not affect the successful execution of subsequent commands and SQL statements: Reason "<reason>". Type of Resource "<resource-type>". Resource name "<resource-name>". Product ID "<product-ID>".

Explanation: The application cannot process the command or SQL statement because the specified resource has run out. The current transaction is not rolled back and the application remains connected to the remote database.

The command cannot be processed.

User Response: Increase the size of the specified resource and resubmit the command.

sqlcode: -30040

sqlstate: 57012

SQL30041N Execution failed because of unavailable resources that will affect the successful execution of subsequent commands and SQL statements: Reason "<reason>". Type of Resource "<resource-type>". Resource name "<resource-name>". Product ID "<product-ID>".

Explanation: The application cannot process the command or SQL statement because resources are not available at the remote database. This SQLCODE is produced at statement compilation or processing time.

Federated system users: this situation can also be detected by the data source.

If the "<resource name>" is "Encrypt" or "Decrypt", the user exits for password encryption or decryption are unavailable or had an error.

The command or statement cannot be processed.

User Response: Investigate the remote database system environment.

Federated system users:

If the password encryption or decryption user exit failed, "<reason>" is the integer value that the federated server received when invoking the user exit. Ensure that no errors occurred when the encryption and decryption user exits were link-edited with the federated server.
If using a user-supplied user exit, please check the user exit source code to determine why the "<reason>" was returned. If the error is found in the user exit source code, fix the error, link-edit the object code with the federated server, and reissue the failing command or statement.
For all other cases, isolate the problem to the data source failing the request (refer to the problem determination guide to determine which data source is failing in processing an SQL statement), correct the problem at the data source, and reissue the failing command or statement.

sqlcode: -30041

sqlstate: 57013

SQL30050N "<number>" command or SQL statement invalid while bind is in progress.

Explanation: An application attempted to issue a command or SQL statement that is not valid while a precompile/bind operation is in progress. <number> is a numeric value that identifies the erroneous command or SQL statement.

The command or statement is not processed.

User Response: If the application is not the database manager precompiler/binder, verify that bind is not active before issuing the command or SQL statement.

If the application is the database manager precompiler/binder, record the message number (SQLCODE) and the <number> value. Record all error information from the SQLCA, if possible. Attempt to perform the bind operation again.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and reason code
SQLCA contents if possible
Trace file if possible.

sqlcode: -30050

sqlstate: 58011

SQL30051N Bind process with the specified package name and consistency token not active.

Explanation: An attempt has been made to issue a precompile/bind operation when precompile/bind is not active or an attempt was made to use an invalid package name and/or consistency token during an active precompile/bind operation.

The command or statement cannot be processed.

User Response: If the application is not the database manager. precompiler/binder, verify that precompile/bind is active before issuing the bind operation and that correct information is being passed on the bind operation.

If the application is the database manager precompiler/binder, record the message number (SQLCODE) and all error information from the SQLCA, if possible. Attempt to perform the operation again.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and reason code
SQLCA contents if possible
Trace file if possible.

sqlcode: -30051

sqlstate: 58012

SQL30052N Program preparation assumptions are incorrect.

Explanation: The SQL statement being compiled is not recognized by the precompiler and cannot be processed by the database.

The statement cannot be processed.

User Response: Ensure that the statement is correct and attempt to perform the operation again. If the problem continues, remove the statement from the program.

sqlcode: -30052

sqlstate: 42932

SQL30053N The value for OWNER failed the authorization check at the remote database.

Explanation: The value specified for the OWNER option on the precompile/bind failed the authorization check at the remote database. This SQLCODE is produced during precompile/bind. It is not produced by the database manager precompiler/binder.

The precompile/bind operation cannot be processed.

User Response: Ensure that you are authorized to use the ID specified for the OWNER option, or do not use the OWNER option.

sqlcode: -30053

sqlstate: 42506

SQL30060N "<authorization-ID>" does not have the privilege to perform operation "<operation>".

Explanation: Authorization ID <authorization-ID> attempted to perform the specified <operation> without having been granted the proper authorization to do so. This SQLCODE is produced at statement compilation or processing time.

The statement cannot be processed.

User Response: Ensure that the <authorization-ID> has been granted the authorization necessary to perform the desired operation.

sqlcode: -30060

sqlstate: 08004

SQL30061N The database alias or database name "<name>" was not found at the remote node.

Explanation: The database name is not an existing database at the remote database node.

The statement cannot be processed.

User Response: Resubmit the command with the correct database name or alias.

Federated system users: check to ensure that the entry in SYSCAT.SERVERS correctly specifies the database name of the data source.

sqlcode: -30061

sqlstate: 08004

SQL30070N "<command-identifier>" Command is not supported.

Explanation: The remote database received a command that it does not recognize. The current environment command or SQL statement cannot be processed successfully, nor can any subsequent commands or SQL statements.

The current transaction is rolled back and the application is disconnected from the remote database. The statement cannot be processed.

User Response: Record the message number (SQLCODE) and the command identifier. Record all error information from the SQLCA, if possible. Attempt to connect to the remote database and rerun the application.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and command identifier
SQLCA contents if possible
Trace file if possible.

sqlcode: -30070

sqlstate: 58014

SQL30071N "<object-identifier>" Object is not supported.

Explanation: The remote database received data it does not recognize. The current environment command or SQL statement cannot be processed successfully, nor can any subsequent commands or SQL statements.

The current transaction is rolled back and the application is disconnected from the remote database. The command cannot be processed.

User Response: Record the message number (SQLCODE) and the object identifier. Record all error information from the SQLCA, if possible. Attempt to connect to the remote database and rerun the application.

If sufficient memory resources exist and the problem continues,

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Refer to the Independent Trace Facility in the Troubleshooting Guide for information on how to use this facility.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and object identifier
SQLCA contents if possible
Trace file if possible.

sqlcode: -30071

sqlstate: 58015

SQL30072N "<parameter-identifier>" Parameter is not supported.

The command cannot be processed.. The current transaction is rolled back and the application is disconnected from the remote database.

User Response: Record the message number (SQLCODE) and the parameter identifier. Record all error information from the SQLCA, if possible. Attempt to connect to the remote database and rerun the application.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and parameter identifier
SQLCA contents if possible
Trace file if possible.

sqlcode: -30072

sqlstate: 58016

SQL30073N "<parameter-identifier>" Parameter value "<value>" is not supported.

The current transaction is rolled back and the application is disconnected from the remote database. The command cannot be processed.

If sufficient memory resources exist and the problem continues,

Required information:

Problem description
SQLCODE, parameter identifier, and value
SQLCA contents if possible
Trace file if possible.

Some possible parameter identifiers include:

002F

The target server does not support the data type requested by the application requester. For example, when DB2 Connect is used to connect to DB2 2.3, this error will be returned unless the proper PTF is applied to DB2 2.3. Ensure that the level of the server is supported by the requester.

119C, 119D, 119E

The target server does not support the CCSID requested by the application requester. Ensure the CCSID used by the requester is supported by the server.

119C - Verify the single-byte CCSID.
119D - Verify the double-byte CCSID.
119E - Verify the mixed-byte CCSID.

sqlcode: -30073

sqlstate: 58017

SQL30074N "<reply-identifier>" Reply is not supported.

Explanation: The client received a reply it does not recognize. The current environment command or SQL statement cannot be processed successfully, nor can any subsequent commands or SQL statements.

The current transaction is rolled back and the application is disconnected from the remote database. The statement cannot be processed.

User Response: Record the message number (SQLCODE) and the reply identifier. Record all error information from the SQLCA, if possible. Attempt to connect to the remote database and rerun the application.

Contact your technical service representative with the following information:

Required information:

Problem description
SQLCODE and reply identifier
SQLCA contents if possible
Trace file if possible.

sqlcode: -30074

sqlstate: 58018

SQL30080N A communication error "<reason-code>" occurred sending or receiving data from the remote database.

Explanation: The "<reason-code>" contains the original error codes reported by Communications Manager.

For APPC error codes, the format is pppp-ssssssss-dddddddd where pppp is the primary return code, ssssssss is the secondary return code and dddddddd is the sense data. Each of these error code values is represented in hexadecimal notation. Possible primary and secondary error codes include 0003-00000004 and 0003-00000005, which indicate that a conversation with the Database Server could not be allocated. Sense data will only be displayed for an APPC ALLOCATE error.

The command cannot be processed. The connection attempted to the database is unsuccessful or the current transaction to the connected database is rolled back and the application is disconnected from the remote database.

Refer to the document IBM Communications Manager 1.0 APPC Programming Guide and Reference (SC31-6160) for explanation of the APPC primary and secondary return codes. For details of APPC sense data, refer to the IBM Communications Manager 1.0 Problem Determination Guide (SC31-6156).

User Response: Ensure that both the database manager and Communications Manager are started at the Database Server and that all Communications Manager configuration parameters are correct. Also, consult the Communications Manager/2 APPC Programming Guide & Reference for further information.
Note: If the reason code embedded in your message is 0003-084C0001 one possible cause for this message is that you are trying to make a remote connection to a workstation that is not a server. Verify that the remote workstation is a server. If it is not a server, install the database manager as a server.
sqlcode: -30080

sqlstate: 08001

SQL30081N A communication error has been detected. Communication protocol being used: <protocol>. Communication API being used: <interface>. Location where the error was detected: <location>. Communication function detecting the error: <function>. Protocol specific error code(s): <rc1>, <rc2>, <rc3>.

Explanation: An error has been detected by the communication subsystem.

If the connection has already been established, possible causes include the following:

A communication subsystem error at the client node or server node has caused the connection to go down.
A communication subsystem error at the SOCKS server, if one is being used, has caused the connection to go down.
A network error has caused the connection to go down.
The database agent at the server was forced off by the system administrator.
The database agent at the server was terminated due to an abnormal termination of a key database manager process.

If you are trying to establish a new connection, possible causes include the following:

The remote database server has not been cataloged correctly at the client.
The database manager configuration file at the server has not been configured with the proper communication parameters.
The communication subsystem at the client node or server node has not been configured correctly, or has not been started successfully.
The communication subsystem at the SOCKS server, if one is being used, has not been configured correctly, or has not been started successfully.
The DB2COMM environment variable at the server doesn't specify the communication protocol used by the client.
The database manager at the server has not been started, or has not been started successfully. One or more of the communication protocols specified by DB2COMM may not have been successfully started.

Refer to the token values for details. Depending on the protocol being used and the communication function invoked, some tokens may not be applicable. The following is the explanation of the token values:

<protocol>

The actual communication protocol being used. Valid token values are:

TCP/IP
APPC
NETBIOS
IPX/SPX

<interface>

The application programming interface used to invoke the above communication protocol services. Valid token values are:

SOCKETS
SOCKS
CPI-C
DLR or DD
TLI or Connection/Bindery

<location>

This is a protocol specific ID which uniquely identifies the node that detected the error. If the protocol being used is:

TCP/IP
The format of the ID is the Internet address in dot notation.
APPC
The format of the ID is the fully qualified LU name (networkID.LUname).
NETBIOS
The format of the ID is the Workstation name (nname).
IPX/SPX
The format of the ID is the network address and node address in hexadecimal notation (network.node).

If the location information is not available at the time that the error occurred, this token is not filled in.

<function>

The name of the communication subsystem function that returned the error code(s).

<rc1>, <rc2>, <rc3>

The list of the available error codes and subcodes that are specific to each protocol being used. Tokens that are not applicable contain "*".

If the protocol being used is:

TCP/IP

If present, <rc1> contains the global errno value from the TCP/IP sockets function call. When using Windows Sockets, if present, <rc1> contains the error from the TCP/IP sockets function call returned by WSAGetLastError().
If present, <rc2> contains the global h_errno value from the TCP/IP database function call. When using Windows Sockets, if present, <rc2> contains the error from the TCP/IP database function call returned by WSAGetLastError().
If <rc3> is present and contains "0", it means that the TCP/IP connection has been closed. This could be caused by one of the following:
- The database agent at the server was forced off by the system administrator.
- A database agent could not be started at the server because the maxagents database manager configuration parameter has been exceeded. Check the First Failure Service Log (DB2DIAG.LOG) at the server to see if an error message has been logged.
- The database agent at the server was terminated due to an abnormal termination of a key database manager process.

Note:

When using Windows Sockets, if the <function> is WSAStartup, and <rc1> is 0, then <rc2> contains the Windows Sockets Specification version level requested by DB2, and <rc3> contains the Windows Sockets Specification version level supported by the Windows Sockets DLL.

APPC
<rc1> contains the return code from the CPI-C function. If present, <rc2> contains the global errno value from the CPI-C function call. <rc3> is not applicable.
NETBIOS
<rc1> contains the return code from the call to NetBIOS. <rc2> and <rc3> are not applicable.
IPX/SPX
<rc1> contains the global t_errno value from the call to TLI Services, or the return code from the call to NetWare Connection or Bindery Services. If the <rc1> t_errno is TLOOK, <rc2> contains the TLI event that has occurred. If the <rc2> event is T_DISCONNECT, <rc3> contains the disconnect reason code. On AIX, if the <rc1> t_errno is TSYSERR, <rc3> contains the system errno (defined in sys/errno.h). If <rc1> contains the error return code from a call to AIX NetWare Connection or Bindery Services, <rc2> contains the error generator.

See the Communications Errors appendix of the Messages Reference for more information on specific communication error codes.

User Response:

If the connection has already been established, check if:

The database agent at the server has been forced off.
The database manager at the server has abnormally terminated.
A communication subsystem or network error has occurred. See the Messages Reference for more information on specific communication error codes.

If you are trying to establish a new connection, check if:

The remote database server is cataloged properly on the client node.
The database manager configuration file at the server is configured with the proper communication related parameters. If the database manager configuration parameters have been updated at the server, ensure that you stop and then re-start the database manager, for the changes to take effect.
The communication subsystems on both client and server nodes are configured and started up properly.
The DB2COMM environment variable at the server specifies the communication protocol used by the client.
The database manager at the server is successfully started. Start database manager processing at the server should have returned SQL1063, and not SQL5043. If SQL5043 is returned, check the First Failure Service Log (DB2DIAG.LOG) for more information.
A communication subsystem or network error has occurred.

If the problem persists, consult with your network administrator and/or communication expert to determine the cause of the problem using the set of tokens provided.

sqlcode: -30081

sqlstate: 08001

SQL30082N Attempt to establish connection failed with security reason "<reason-code>" ("<reason-string>").

Explanation: The attempt to connect to the remote database server was rejected due to invalid or incorrect security information. The cause of the security error is described by the <reason-code> and corresponding <reason-string> value.

The following is a list of reason codes and corresponding reason strings:

0 (NOT SPECIFIED)

The specific security error is not specified.

1 (PASSWORD EXPIRED)

The password specified in the request has expired.

2 (PASSWORD INVALID)

The password specified in the request is not valid.

3 (PASSWORD MISSING)

The request did not include a password.

4 (PROTOCOL VIOLATION)

The request violated security protocols.

5 (USERID MISSING)

The request did not include a userid.

6 (USERID INVALID)

The userid specified in the request is not valid.

7 (USERID REVOKED)

The userid specified in the request has been revoked.

8 (GROUP INVALID)

The group specified in the request is not valid.

9 (USERID REVOKED IN GROUP)

The userid specified in the request has been revoked in the group.

10 (USERID NOT IN GROUP)

The userid specified in the request is not in the group.

11 (USERID NOT AUTHORIZED AT REMOTE LU)

The userid specified in the request is not authorized at the remote Logical Unit.

12 (USERID NOT AUTHORIZED FROM LOCAL LU)

The userid specified in the request is not authorized at the remote Logical Unit when coming from the local Logical Unit.

13 (USERID NOT AUTHORIZED TO TP)

The userid specified in the request is not authorized to access the Transaction Program.

14 (INSTALLATION EXIT FAILED)

The installation exit failed.

15 (PROCESSING FAILURE)

Security processing at the server failed.

16 (NEW PASSWORD INVALID)

the password specified on a change password request did not meet the server's requirements.

17 (UNSUPPORTED FUNCTION)

the security mechanism specified by the client is invalid for this server. Some typical examples:

The client sent a new password value to a server that does not support the DRDA change password function.
The client sent DCE authentication information to a server that does not support DCE.
The client sent SERVER_ENCRYPT or DCS_ENCRYPT authentication information to a server that does not support password encryption.

18 (NAMED PIPE ACCESS DENIED)

The named pipe is inaccessible due to a security violation.

19 (USERID DISABLED or RESTRICTED)

The userid has been disabled, or the userid has been restricted from accessing the operating environment at this time.

20 (MUTUAL AUTHENTICATION FAILED)

The server being contacted failed to pass a mutual authentication check. The server is either an imposter, or the ticket sent back was damaged.

User Response: Ensure that the proper userid and/or password is supplied. For reason code 20, make sure the authentication mechanism for the server is started, and retry.

The userid may be disabled, the userid may be restricted to accessing specific workstations, or the userid may be restricted to certain hours of operation.

For reason code 17, retry the command with a supported authentication type.

sqlcode: -30082

sqlstate: 08001

SQL30083N Attempt to change password for user id "<uid>" failed with security reason "<reason-code>" ("<reason-string>").

Explanation: The attempt to change password was rejected due to invalid or incorrect security information. The cause of the security error is described by the "<reason-code>" and corresponding "<reason-string>" values.

The following is a list of reason codes and corresponding reason strings:

0 (NOT SPECIFIED): The specific security error is not specified.
1 (CURRENT PASSWORD INVALID): The old password specified in the request is not vaild.
2 (NEW PASSWORD INVALID): The password specified in the request is not valid under the password rules imposed by the system where password was to be changed.
3 (CURRENT PASSWORD MISSING): The request did not include an old password.
4 (NEW PASSWORD MISSING): The request did not include a new password.
5 (USERID MISSING): The request did not include a userid.
6 (USERID INVALID): The userid specified in the request is not valid.
7 (USERID REVOKED): The userid specified in the request has been revoked. Passwords can not be changed for revoked userids.
14 (INSTALLATION EXIT FAILED): The installation security exit failed.
15 (PROCESSING FAILURE): Security processing at the server failed.
17 (UNSUPPORTED FUNCTION): Change password funcion is not supported by the system.
19 (USERID DISABLED or RESTRICTED): The userid has been disabled, or the userid has been restricted from accessing the operating environment at this time.
24 (USERNAME AND/OR PASSWORD INVALID): The username specified, password specified, or both, are invalid.

User Response: Ensure that the proper userid, current and new passwords are supplied. For reason code 14, check the file db2pem.log in the instance subdirectory (typicaly "db2") for a detailed description of the problem encountered.

The userid may be disabled, the userid may be restricted to accessing specific workstations, or the userid may be restricted to certain hours of operation.

sqlcode: -30083

sqlstate: 08001

SQL30090N Operation invalid for application execution environment. Reason code = "<reason-code>"

Explanation: The operation is invalid for the application execution environment. For example, an operation might be invalid for applications that have special restrictions on statements or APIs - applications such as those that operate in an XA Distributed Transaction Processing environment, such as CICS; those that operate with CONNECT type 2 connection settings; or those that use federated system functionality to update multiple heterogeneous data sources. The operation was rejected.

Possible reason codes are:

01 - an SQL request that changes data (such as an INSERT or a CREATE) was issued against a read-only database; or, a stored procedure was invoked against a read-only database. Read-only databases include the following types:
- Databases accessed using DRDA when operating in a unit of work which has connection setting SYNCPOINT TWOPHASE and executing in a non-XA/DTP environment when either a Synchpoint Manager is not being used or the remote DRDA database does not support level 2 DRDA protocol.
- Databases accessed by DRDA in an XA/DTP environment when either a Synchpoint Manager gateway is unavailable or the remote DRDA database does not support level 2 DRDA protocol.
- Databases which were not the first database updated when the SYNCPOINT ONEPHASE connection setting is in effect for the unit of work.
02 - an API such as Precompile, Bind, or Reorganize Table which causes internal commits was issued in an application which has the setting CONNECT type 2 or is operating in an XA/DTP environment.
03 - an SQL OPEN for a held cursor was issued while in an XA/DTP environment when using an ENCINA or TUXEDO transaction processing monitor.
04 - a DISCONNECT statement was issued while in an XA/DTP environment.
05 - A compound SQL statement which contains a COMMIT statement was issued in a CONNECT type 2 or XA/DTP environment.
06 - The SET CLIENT API was issued in an XA/DTP environment.
07 - A second database is being accessed within a unit of work for which two-phase commit coordination is not being supplied by the transaction manager. To ensure data integrity, the operation has been disallowed.
08 - An attempt was made to access a database for use of commit coordination from a source different from a concurrently connected database. The two types of coordination cannot be mixed, and operations against the current database are rejected.
09 - An attempt was made to execute an XA/DTP local transaction against a database accessed under Synchpoint Manager coordination.
10 - An SQL OPEN for a held cursor was issued in either of these cases:
- XA/DTP environment, or
- federated server accessing a nickname defined on a two phase commit datasource
Cursor hold is not supported in these environments.
11 - An operation is not supported for pass-through.
12 - The insert/update/delete operation requires the existence of a timestamp column and a unique index due to the restriction on the data source.
For an update/delete operation accessing data sources:
- Fujitsu RDB2 requires the existence of a unique index.
13 - A positioned UPDATE or DELETE operation requires the existence of a column in the SELECT list of the cursor, but that column does not exist in the SELECT list of the cursor.
14 - An illegal combination of updatable cursors, cursor hold, and isolation level of Repeatable Read exists. Invalid combinations are:
- Isolation level Repeatable Read and a WITH HOLD cursor
- A WITH HOLD cursor with FOR UPDATE
15 - Reserved for future use
16 - Illegal type column and protocol column value combination in SYSCAT.SERVERS.
17 - The REORG utility cannot be issued against a nickname.
18 - An update request (or, a DDL operation that results in the update of a system catalog table) has been issued that would result in multiple data sources being updated when one or more of the data sources in the unit of work only supports one-phase commit. Possible causes are:
- An attempt was made to update a data source that only supports one-phase commit, but a different data source has already been updated in the same unit of work.
- An attempt was made to update a data source that supports two-phase commit, but a different data source that only supports one-phase commit has already been updated in the same unit of work.
- An attempt was made to update a local federated server table, but a data source that only supports one-phase commit has already been updated in the same unit of work.
- An attempt was made to update a data source that only supports one-phase commit when the application is operating with a CONNECT type 2 connection setting.
19 - The application host variable data type is not supported by the data source in a pass-through session.
20 - SET CLIENT INFORMATION was issued while a Unit of Work is in progress.

User Response:

Correct the problem by doing one of the following steps:

For reasons 01, 02, 03, 04, 06, or 19, remove the statement or API which is not supported.
Alternately, for reasons 01, 02, 03, 04, or 06, execute the application in a different environment which supports the failing statement or API.
For reason 05 move the COMMIT request outside of the compound statement.
For reason 07, ensure that only one database is accessed within a unit of work for which EXEC SQL COMMIT or EXEC SQL ROLLBACK will be issued in place of syncpoint requests to an external transaction manager. If multiple databases must be accessed within the unit of work, utilize the commitment control interface provided by the external transaction manager product.
For reason 08, ensure that all databases being accessed within a unit of work are under the commitment control of the same type of request: external transaction processing monitor (such as CICS SYNCPOINT) or local COMMIT and ROLLBACK EXEC SQL.
For reason 09, do one of the following steps:
- Execute the transaction as an XA/DTP global transaction.
- Access the database in a non-XA/DTP environment.
- Do not use the services of the Synchpoint Manager for the database connection if the transaction is read-only.
For reasons 10 through 17 (federated server users), isolate the problem to the data source failing the request (see the problem determination guide) and examine the restrictions for that data source.
For reason 18, do one of the following steps:
- Submit a COMMIT or ROLLBACK before issuing an update to a different data source.
- If multiple data sources need to be updated within a unit of work, make sure the two_phase_commit server option has been set to 'Y' for all the data sources that need to be updated. See the SQL Reference for information on setting the value used for the two_phase_commit setting.
- If the data source to be updated supports only one-phase commit and the application is operating with a CONNECT type 2 connection setting, change the application to operate with a CONNECT type 1 connection setting.
For reason 20, submit a Commit or Rollback before invoking the API.

sqlcode: -30090

sqlstate: 25000

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]