Explanation

Java exception exception-string was thrown.

Explanation

The Query Controller may not be running or the communication has timed out.

Explanation

An error was encountered during job sequence number generation.

Explanation

The query has been rejected. The reason codes are as follows:

1. DB2 does not allow the query to generate result set, or the query contains host variables, parameter markers, special registers, created temporary tables, declared temporary tables, session variables, IDENTITY_VAL_LOCAL function, NEXT VALUE expression, and/or PREVIOUS VALUE expression. Therefore the query cannot be put on hold or run in the background, as the state might not be valid at the time the query is actually executed.
2. The query would update a DB2 table, therefore it cannot be put on hold or run in background, as the state might no longer be valid at the time the query is actually executed.
3. The query cannot be queued because it contains nested routines.
4. The query cannot be put on hold or run in the background because it contains nested routines.
5. DB2 does not allow this query to be queued. This may occur when the query contains array inserts.
6. DB2 does not allow a query to be queued when the concentrator is turned on.
7. DB2 does not allow a query to be queued when the REOPT ALWAYS option is enabled for the query.

Explanation

The user has cancelled the query submission. No query was submitted.

Explanation

The user has chosen to run the query in the background.

Explanation

The query has been put in held state by Query Patroller.

Explanation

Explanation

An error was encountered while trying to cancel a job. The reason code maps to an SQL or DB2 message.

Explanation

The user has cancelled the query.

Explanation

An error has occurred during internal processing.

Explanation

The user user-ID is suspended from submitting a query to the database.

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.

Explanation

The statement cannot be executed as chained.

Explanation

The current SQL statement failed because the SQL statement was routed to a server that does not support the requested function. The error was such that it will not preclude the successful execution of further SQL statements.

The statement cannot be executed. The SQLCA is formatted.

Explanation

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

Some possible reason codes include:

121C

Indicates that the user is not authorized to perform the requested command.

124C

The DRDA data stream for the request contains a syntax error.

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.

1254

A command sent from the client has resulted in an unarchitected and implementation specific condition on the remote server for which there is no architected message to return to the client.

If the remote server is DB2 UDB for OS/390,zOS then check the console log for information about this error.

If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error.

If the remote server is DB2 Database for Linux, UNIX, and Windows, then check the remote database server's administration notification log for information regarding this error.

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.

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.

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.

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.

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.

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.

Explanation

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

The statement cannot be processed.

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.

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.

Explanation

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

The statement cannot be processed.

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.

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.

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 command cannot be processed.. The current transaction is rolled back and the application is disconnected from the remote database.

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.

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.

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).

Explanation

An error has been detected by the communication subsystem.

The following is a description of the token values:

protocol, location

Communication protocol used and information that uniquely identifies the node that detected the error. If the location information is not available at the time that the error occurred, then the location token is not filled in. Valid token values are:

• protocol TCP/IP; location is the IPv4 or IPv6 address.
• protocol APPC; location is the fully qualified LU name (networkID.LUname).
• protocol MQ; location is the MQ queue name.
• protocol SOAP, SSL, SOCKS, HTTP; location is the Internet address in dot notation.

interface

The application programming interface used to invoke the protocol services in the previous list item. Valid token values are: SOCKETS, SOCKS, CPI-C, MQI-CLIENT, GSKit, HTTP.

function

The name of the communication subsystem function that returned the error code or codes.

If protocol is TCP/IP, here are descriptions of some common scenarios:

• Reason codes rc1, rc2, rc3 represent:
  • If present, rc1 contains the errno returned by the TCP/IP function. On Windows, this is a WSA errno.
  • If present, rc2 contains the h_errno value returned by a TCP/IP name resolution function. On Windows, this is a WSA error number.
  • If rc3 is present and contains "0", the remote side has terminated the connection. If the error was received on the client, then the remote side could be a server or gateway. If the error was received on the gateway, the remote side could be the client or server.

• If protocol = TCP/IP, rc1=*, rc2=*, and rc3=0, possible causes include:
  • The database agent at the server was forced off by the system administrator.
  • A database agent could not be started at the server because a memory limitation was reached on the system.
  • The connection might have been closed by the remote server at the TCP/IP level.
  • The database agent at the server was terminated due to an abnormal termination of a key database manager process.

• On Windows, if protocol = TCP/IP, function = WSAStartup, and rc1 = 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. Cause: There was a version level mismatch.

• If protocol = TCP/IP, function = connect, rc1 = ECONNREFUSED/WSAECONNREFUSED, AIX (79), Windows (10061), linux (111), SUN (146), HP (239), the attempt to connect was rejected. Possible causes:
  • The remote database server has not been cataloged correctly at the client. In a client-gateway-server scenario, ensure the host entries are cataloged correctly on the gateway.
  • The database manager configuration file at the server has not been configured properly with the proper communication parameters. Check that the SVCENAME database manager configuration parameter has been configured properly with the TCP/IP service name or port number and that the port number is unique. If database manager configuration parameters have been updated at the server, the database manager must be stopped and re-started for the changes to take effect. There might be a mismatch between the TCP/IP service name or port number specified on the server and on the client. Ensure the service name maps to the correct port number by checking the services file. You can check this by reading the services file or checking the output from running the command "netstat -a".
  • A firewall at the remote database server has prevented the connection from being established. Verify that the firewall is properly configured to accept connection requests from the client.
  • The DB2COMM environment variable at the server does not specify the communication protocol used by the client. Check that TCPIP has been specified. Issue db2set to see what has already been set. Run the command "db2set DB2COMM=TCPIP" to set the value.
  • The database manager at the server has not been started, or has not been started successfully, or has gone down. The server should have returned SQL1063N, and not SQL5043N. If you set the database manager configuration parameter DIAGLEVEL to 4 using the command "db2 update dbm cfg using diaglevel 4" prior to issuing the "db2start" command, then the administration notification log will provide detailed information on which protocols were started successfully. Check the administration notification log.
  • The server might be too busy to handle the volume of incoming connections at this time.
  • Network failure, contact your network administrator. You can try a test using the protocol tester, pctt, to verify this is not a DB2 problem.

• If protocol = TCP/IP, function = connect, rc1 = ETIMEDOUT/WSAETIMEDOUT, AIX (78), Windows (10060), linux (110), SUN (145), HP (238), attempt to connect timed out before a connection was made. Possible causes:
  • An incorrect host name or IP address was cataloged in the hostname field of the node directory on the client and/or gateway.
  • The network is slow, or the server might be too busy to respond to the connect request within a reasonable amount of time, you might need to adjust your system TCP connect timeout value and/or the DB2TCP_CLIENT_CONTIMEOUT value.

• If protocol = TCP/IP, function = recv, rc1 = ECONNRESET/WSAECONNRESET, AIX (73), Windows (10054), linux (104), SUN (131), HP (232), the connection was reset by the remote side executing a "hard" or "abortive" close. Possible causes:
  • The connection might have been closed by the remote gateway or server at the TCP/IP level (eg. firewall problem, power failure, network failure).
  • Client side connection pooling is enabled and is not handling connection failures. Code the application to retry a connection if a failure is received when connecting to the database and connection pooling is enabled.
  • Might have been caused by a thread timeout on the host machine. Check the system log on the host for the presence of the IDTHTOIN message. Adjust the setting if applicable. If this cannot be adjusted, either disable connection pooling on the gateway, or ensure all objects are properly closed (eg. cursors with hold when the application completes its operation).
  • The database agent at the server was forced off by the database administrator.
  • The database agent at the server was terminated due to an abnormal termination of a key database manager process.

• If protocol = TCP/IP, function = recv, rc1 = ETIMEDOUT/WSAETIMEDOUT, AIX (78), Windows (10060), linux (110), SUN (145), HP (238), the connection was dropped because the remote system failed to respond. Possible causes:
  • SQLCancel() was called from a CLI application because the application set the Query Timeout value or there was an explicit cancel request. Adjust the Query Timeout value set by the application. If this is not possible, adjust the QueryTimeoutInterval setting in the db2cli.ini file. Use QueryTimeoutInterval=0 (no timeout) in the db2cli.ini file to test whether QueryTimeout is the cause of your application's failure. The failure of an existing connection is expected in this scenario.
  • The network is slow, or the server might be too busy to respond to the recv request within a reasonable amount of time, you might need to adjust your system TCP recv timeout value.

• If protocol = TCP/IP, function = selectForConnectTimeout, rc1 = EINPROGRESS/0, AIX (55), Windows (0), linux (115), SUN (150), HP (245), the connect request timed out before it could complete successfully. Possible causes:
  • Either the system connect timeout or the timeout value set by DB2TCP_CLIENT_CONTIMEOUT caused the timeout. Try adjusting these values.

• If protocol = TCP/IP, function = selectForRecvTimeout, rc1 is irrelevant, the recv request timed out before it could complete successfully. Possible causes:
  • Either the system recv timeout or the timeout value set by DB2TCP_CLIENT_RCVTIMEOUT caused the timeout. Try adjusting these values.

If protocol is 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.

If protocol is MQ

• rc1 contains the function completion code, 1 for a warning and 2 for an error.
• rc2 contains the MQ-specific error code.
• rc3 is not used for MQ.

If protocol is SOAP, rc1 contains the return code from the SOAP communication function.

If protocol is SSL, rc1 contains the return code from the Secure Sockets Layer (GSKit).

If protocol is SOCKS

• rc1 contains the return code from the SOCKS proxy server.
• rc2 contains the version (4 or 5) of the protocol.
• rc3 contains the authentication method used (SOCKS v5.)

If protocol is HTTP, rc1 contains the HTTP return code from the remote HTTP server.

Explanation

An error occurred during security processing. 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 change password function.
• The client sent SERVER_ENCRYPT authentication information to a server that does not support password encryption. Authentication type catalog information must be the same at the server and the client.
• The client sent a userid (but no password) to a server that does not support authentication by userid only.
• The client has not specified an authentication type, and the server has not responded with a supported type. This might include the server returning multiple types from which the client is unable to choose.
• The CLIENT AUTHENTICATION type is not supported by "IBM Data Server Driver for ODBC and CLI" and "IBM Data Server Driver package"

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.

21 (RESOURCE TEMPORARILY UNAVAILABLE)

Security processing at the server was terminated because a resource was temporarily unavailable. For example, on AIX, no user licenses may have been available.

24 (USERNAME AND/OR PASSWORD INVALID)

The username specified, password specified, or both, are invalid. Some specific causes are:

1. If you have recently changed permissions on DB2 critical files such as db2ckpw or moved to a new Fixpak, the db2iupdt command which updates the instance might not have been run.
2. The username being used might be in an invalid format. For example, on UNIX and Linux platforms, usernames must be all be lowercase.
3. An error might have been made in specifying the catalog information. For example, the correct authentication type might not have been specified or, if applicable, the remote server might not have been cataloged on the local system.

25 (CONNECTION DISALLOWED)

The security plugin has disallowed the connection.

26 (UNEXPECTED SERVER ERROR)

The server security plugin encountered an unexpected error. The administration notification log file on the server contains more specific problem information. The following are examples of issues that can cause problems:

• The security service was not started.
• The userid starting the DB2 service did not have admin privileges.

27 (INVALID SERVER CREDENTIAL)

The server security plugin encountered an invalid server credential.

28 (EXPIRED SERVER CREDENTIAL)

The server security plugin encountered an expired server credential.

29 (INVALID CLIENT SECURITY TOKEN)

The server security plugin encountered an invalid security token sent by the client.

30 (CLIENT PLUGIN MISSING API)

The client security plugin is missing a required API.

31 (WRONG CLIENT PLUGIN TYPE)

The client security plugin is of the wrong plugin type.

32 (UNKNOWN CLIENT GSS-API PLUGIN)

The client security plugin does not have a matching GSS-API security plugin available for connection to the database.

33 (UNABLE TO LOAD CLIENT PLUGIN)

The client security plugin cannot be loaded.

34 (INVALID CLIENT PLUGIN NAME)

The client security plugin name is invalid.

35 (INCOMPATIBLE CLIENT PLUGIN API VERSION)

The client security plugin reports an API version that is incompatible with DB2.

36 (UNEXPECTED CLIENT ERROR)

The client security plugin encountered an unexpected error.

37 (INVALID SERVER PRINCIPAL NAME)

The server security plugin encountered an invalid principal name.

38 (INVALID CLIENT CREDENTIAL)

The client security plugin encountered an invalid client credential.

39 (EXPIRED CLIENT CREDENTIAL)

The client security plugin encountered an expired client credential.

40 (INVALID SERVER SECURITY TOKEN)

The client security plugin encountered an invalid security token sent by the server.

41 (SWITCH USER INVALID)

The client is configured to request a trusted connection and switch user in the trusted connection. A trusted connection was not established and so the switch user request is invalid.

42 (ROOT CAPABILITY REQUIRED)

Authentication using local client or server passwords is not currently enabled.

43 (NON-DB2 QUERY MANAGER PRODUCT DISALLOWED CONNECTION)

A non-DB2 query manager product has disallowed the connection.

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.

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 thedata 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.

21

The operation that you want performed at the specified data sources is not supported by the wrapper by which DB2 accesses the data sources. Consult the documentation to find out what operations this wrapper supports.

22

A federated insert, update, or delete operation, or a call to federated procedure with an SQL data access indication of MODIFIES SQL DATA is invalid in a function, a data-change-table-reference, a dynamic compound statement, a trigger, and an application execution environment where a

• SAVEPOINT is in effect
• scrollable cursor is used
• target view contains multiple tables or nicknames

23

The API, data structure, or setting is not supported.

24

Data type mappings are not supported by the specified wrapper.

25

Function mappings are not supported by the specified wrapper.

26

In a trusted connection the application can switch the trusted userid only after the commit/rollback has been processed.

27

Use of multiple 2-phase commit servers of the same wrapper library in the same connection where the client library restricts such usage

28

Mix of 1-phase commit server and 2-phase commit server of the same wrapper library in the same connection where the client library restricts such usage

29

An application attempted to issue a switch user request from within a stored procedure.

31

The CREATE WRAPPER statement failed because the DB2LIBPATH environment variable does not contain the path of the client library, and the database manager failed to automatically add that client library path to the DB2LIBPATH environment variable.

Explanation

Bind options were specified on the REBIND request however the database server does not support respecification of any bind options. The bind options specified will be ignored and the options from the original BIND request will be used.

Explanation

While processing the BIND or PRECOMPILE parameters, either the BIND or PRECOMPILE option or the value is not acceptable, or the option and value pair is not appropriate.

The statement cannot be processed.

Explanation

An error was detected with the input data for one row of a multiple row INSERT operation. No further rows will be inserted. For an atomic operation, all inserted rows are rolled back. For a non-atomic operation, rows inserted successfully before the row containing the invalid input data was encountered are not rolled back.

Explanation

You can enable database applications to continue to process transactions with minimal interruption from connection failures by using the automatic client reroute feature. This message is returned when automatic client reroute has detected a connection failure.

reason-code

The value of the token reason-code indicates which special registers would be applied to the new connection:

• 1 or 3: All special register settings up to the point of failure would be returned.
• 2 or 4: All special register settings (and for DB2 for z/OS Version 10.1.5 and later: session global variables) up to the previous commit point would be replayed on the new connection.

The value of the token reason-code also indicates whether connection would be re-established within the current group or in a new group:

• 1 or 2: The connection would be re-established in the current group.
• 3 or 4: The connection would be re-established in an alternate group.

host-name and service-name

The value of the tokens host-name and service-name depend on the token reason-code:

• When reason-code is 1 or 3, the value of the tokens host-name and service-name refer to the new connection.
• When reason-code is 2 or 4, the value of the tokens host-name and service-name depend on whether or not workload balancing is enabled:
  • When workload balancing is enabled, the host name given in the token host-name and the IP address given in service-name refer to the connection that failed.
  • When workload balancing is not enabled, the host name given in the token host-name and the IP address given in service-name refer to the new connection.

connection-failure-code

The value of the token connection-failure-code indicates the nature of the connection failure:

1. Communication failure. For example: connection timeout or query timeout was configured, but before the time out occurred, a member failed over.
2. Database server action. For example: the DB2 member was shut down, or the database was quiesced.
3. An SQL error occurred.
4. Interrupt on client. For example: a query timed out or SQLCancel was called.

underlying-error

The value of the token underlying-error depends on the value of the token connection-failure-code:

• When connection-failure-code is 1 or 2, underlying-error contains the platform-specific error number. Example 1: when the SQLCODE that caused the connection to fail is -30081 and connection-failure-code is 1 or 2, underlying-error might contain the value of the runtime token rc1 of message SQL30081N. Example 2: for Java applications, this value is a communication exception message token that is received from the Java sockets API.
• When connection-failure-code is 3, underlying-error contains the SQLCODE that caused the connection to fail.
• When connection-failure-code is 4, underlying-error contains one of the following numerical values:
  • 1 - The client canceled the execution because a query timed out.
  • 2 - The driver received an interrupt request or a cancel request.
  • 3 - The client canceled the execution because the execution time exceeded the value of the queryTimeout property.

When the database server does not provide a value for the underlying-error, a value of "*" will be returned for underlying-error.

Explanation

There was an attempt to re-establish the connection on a different database server from within the current group of servers or on a database server in an alternate group. The reason code indicates which of these applies.

1

A connection to the database server failed and a connection could not be re-established to an alternate server in the group as none of the available servers in the group had a release level compatible with the initial connection. The release level of the alternate server in the group to which the last connect attempt was made is not compatible with the release level of the original connection.

2

A connection to the database server failed and a connection could not be re-established to a server in an alternate group of servers as none of the available servers in the alternate group had a release level compatible with the initial connection. The release level of the server in the alternate group to which the last connect attempt was made is not compatible with the release level of the original server in the original group.

Explanation

A software product that interacts with the database manager, but is not part of the database product, is returning information about a warning or informational situation in token-list.

Explanation

A software product that interacts with the database manager, but is not part of the database product, is returning information about an error situation in token-list.