Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following table lists DRDA protocol error constants, values, SqlState, SqlCode and a description of the error. An asterisk (*) indicates not in use.
| Value | SqlState | SqlCode | Description |
|---|---|---|---|
| -259 | 08S01 | -256 | Message: Abnormal unit of work. Reason: The abnormal unit of work reply message indicates that the server encountered an issue on the server, causing the server to end the unit of work abnormally. Action: Determine whether a deadlock, operator intervention, or other issue caused the server to roll back the unit of work. Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -260 | 08S01 | -260 | Message: Access RDB command is processed. Reason: The access relational database reply message indicates that the server could not complete a database connection request. Action: Verify the connection parameters and re-attempt the connection request. Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -261 | 08S01 | -261 | Message: A permanent error condition has been detected on the target system. Contact your server administrator. Reason: The permanent agent error reply message indicates that the server encountered an issue on the server, causing the server to not complete the requested command. Action: Review a client network trace to determine if the server returned an optional reason code or other optional diagnostic information. |
| -263 | 08S01 | -263 | Message: Package binding process could not be initiated. Reason: The begin bind error reply message indicates that the server encountered an issue on the server, preventing the server from initiating the requested package binding process. Action: Verify the package bind options and re-attempt the package bind process request. Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -269 | 08S01 | -269 | Message: The user is not authorized to perform the requested command on the target system. Reason: The server cannot authenticate the user with the credentials presented at connection. Action: Verify connection information to ensure the User Name (User Identifier), Password and Security Method specified (Interactive sign-on security, Single sign-on, or Kerberos) match the server requirements defined for the current user. For more information, see topics on User Name, Password and Security Method. |
| -270 | 08S01 | -270 | Message: An internal network library error has occurred. The requested command encountered an implementation-specific error condition on the target system. Reason: The command check reply message indicates that the server received a command from the client that the server determined to be un-architected within Distributed Data Management or Distributed Relational Database Architecture. Action: Review a client network trace to determine if the server returned additional optional error messages that might indicate the cause of the problem and actions to resolve the problem. |
| -272 | 08S01 | -272 | Message: An internal network library error has occurred. The requested command is not recognized or is not supported by the target system. Reason: The command not supported reply message indicates that the server received a command from the client that the server does not recognize or that the server does not support. Action: Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -273 | 08S01 | -273 | Message: Command violated processing capability of the conversation. Reason: The command violation reply message indicates that the server received a command from the client that the server determined to be in violation of the processing scope of the current conversation. Action: Verify the connection parameters (e.g. Distributed Unit of Work) and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -274 | 08S01 | -274 | Message: Commitment request. Reason: The commitment request reply message indicates that the server received a commit or rollback request from the client that the server determined to be invalid in the current context. Action: Verify the connection parameters (e.g. Distributed Unit of Work) and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -290 | 08S01 | -290 | Message: Invalid description. Reason: The invalid description reply message indicates that the server could not read one or more data values, causing the command to fail, when the client sent an invalid DRDA Formatted Data Object Content Architecture (FD:OCA) descriptor of the data. Action: Verify the data parameter values and data types, and then re-attempt the command request. Review a client network trace to determine if the server returned an optional severity code, the invalid parameter number, or other optional diagnostic information. |
| -291 | 08S01 | -291 | Message: Host cannot insert, modify, or retrieve a record due to data mapping error. Reason: The data mapping error reply message indicates that the server could not map one or more data values from source to destination, causing the command to fail, when the client sent invalid data. Action: Verify the data parameter values and data types, and then re-attempt the command request. Review a client network trace to determine if the server returned an optional severity code, the invalid parameter number, or other optional diagnostic information. |
| -303 | 08S01 | -303 | Message: End of query. Reason: The end of query reply message indicates the server could not continue process the query result, due to a problem on the server, the network, or the client. Action: Verify the status of the server and the network, and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -304 | 08S01 | -304 | Message: End of unit-of-work. Reason: The end unit of work condition reply message indicates that the server has ended the unit of work, based on the last command that it received from the client. Action: Verify the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, and Static SQL Package Bind Options) and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -331 | 08S01 | -331 | Message: An internal network library error has occurred. A request has been made that requires an internal manager dependency that was not met. Reason: The manager dependency error reply message indicates that the server received a command from the client that the server does not support in the context of the request, based on the server-specified manager levels. Action: Verify the connection parameters and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional reason code or other optional diagnostic information. |
| -332 | 08S01 | -332 | Message: Manager level conflict. Reason: The manager level conflict reply message indicates that the server could not complete a database connection request. Action: Verify the connection parameters and re-attempt the connection request. Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -335 | 08S01 | -335 | Message: An internal network library error has occurred. The requested command sent a data object that is not recognized or is not supported by the target system. Reason: The object not supported reply message indicates that the server received an object from the client that the server does not recognize or that the server does not support. Action: Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -339 | 08S01 | -339 | Message: Open query failed. Reason: The open query failure reply message indicates that the server could not process the client request to open cursor. Action: Verify the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, and Static SQL Package Bind Options) and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -340 | 08S01 | -340 | Message: Open query reply message. Reason: The open query complete reply message indicates that the server could not complete an open query or SQL set statement normally. Action: Verify the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, Static SQL Package Bind Options, or Default Qualifier) and re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -341 | 08S01 | -341 | Message: Package binding process is not active for the specified package. Reason: The relational database package binding not active reply message indicates that the server could not process a bind SQL statement or end bind request, when a preceding begin bind request was not completed. Action: Verify the connection parameters (e.g. Package Collection or Static SQL Package Bind Options) and re-attempt the command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -342 | 08S01 | -342 | Message: The command cannot be processed when the RDB package binding process is active. Reason: The relational database package binding process active reply message indicates that the server could not process a bind SQL statement, when a preceding end bind request was not completed. Action: Verify the connection parameters (e.g. Package Collection or Static SQL Package Bind Options) and re-attempt the command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -343 | HY000 | -343 | Message: An internal network library error has occurred. A network level conversational protocol error has occurred. Reason: The conversation protocol error code string reply message indicates that the server received a protocol command that is out of sequence in the current context. Action: Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -344 | 08S01 | -344 | Message: An internal network library error has occurred. The requested command included a parameter that is not recognized or is not supported by the target system. Reason: The parameter not supported reply message indicates that the server cannot complete the requested command, when the server does not recognize or support the specified command. Action: Verify the connection and command parameters, and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -345 | 08S01 | -345 | Message: Query is not opened. Reason: The query not open reply message indicates that the server could not process a continue query or close query command, when a query is not open. Action: Verify the status of the server, the network, and the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, and Static SQL Package Bind Options), and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -346 | 08S01 | -346 | Message: Query was previously opened. Reason: The query previously opened reply message indicates that the server cannot process an open query request, for a query that is already open. Action: Verify the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, and Static SQL Package Bind Options), and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -356 | 08S01 | -356 | Message: The user already has access to the host resource. Reason: The relational database currently accessed reply message indicates the server cannot complete an access relational database command, when the client is already connected to a relational database. Action: Verify the connection parameters (e.g. Initial Catalog, Connection Pooling, Connection Timeout), and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -357 | 08S01 | -357 | Message: The request for the host resource failed. Reason: The relational database access failed reply message indicates that the server cannot complete a connection request. Action: Verify the status of the server, the network, and the connection parameters (e.g. Initial Catalog, Network Address, Network Port and Connection Timeout), and then re-attempt the connection request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -358 | 08S01 | -358 | Message: The user does not have the authority to access the host resource. Check your authentication credentials or contact your system administrator. Reason: The not authorized to relational database reply message indicates that the server cannot authenticate the user with the credentials presented at connection time. Action: Verify connection information to ensure the User Name (User Identifier), Password and Security Method specified (Interactive sign-on security, Single sign-on, or Kerberos) match the server requirements defined for the current user, and then re-attempt the connection request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. For more information, see topics on User Name, Password and Security Method. |
| -359 | 08S01 | -359 | Message: Access RDB command must be issued prior to any command that requests RDB services. Reason: The relational database not accessed reply message indicates that the server could not complete the command, when the preceding connection request was not completed. Action: Verify connection information and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -360 | 08S01 | -360 | Message: The host resource could not be found. Check that the Initial Catalog value matches the host resource name. Reason: The relational database not found reply message indicates that the server could not connect the client to the requested relational database. Action: Verify connection information to ensure the Initial Catalog value matches DB2 for z/OS location name, DB2 for IBM i relational database directory entry (RDBDIRE), or DB2 for Windows database name. Verify the values for Network Address and Network Port, and then re-attempt the connection request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. For more information, see topic on Initial Catalog. |
| -361 | 08S01 | -361 | Message: RDB update reply message. Reason: The relational database update reply message indicates that the server could not complete a command to update a local or remote relational database. Action: Verify the connection parameters (e.g. Auto Commit, Distributed Unit of Work, Connection Timeout, Command Timeout, FastLoad Optimize, and Static SQL Package Bind Options), and then re-attempt the connection and command request. Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -370 | 08S01 | -370 | Message: There are insufficient resources on the target system to complete the command. Contact your server administrator. Reason: The resource limits reached reply message indicates that the server could not be completed due to insufficient server resources (e.g. memory, lock, buffer). Action: Verify the connection and command parameters, and then re-attempt the connection and command request. Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -372 | 08S01 | -372 | Message: SQL error occurred. Reason: The SQL error condition reply message indicates that the server encountered an error, for which it returned a SQL error. Action: Verify the connection and command parameters, and then re-attempt the connection and command request (e.g. any SQL statement, and any bind SQL statement to static SQL package section process request). Review a client network trace to determine if the server returned a SQL communications area reply data (SQLCARD) with an optional reason code or other optional diagnostic information. |
| -379 | HY000 | -379 | Message: An internal network library error has occurred. A network level syntax error has occurred. Reason: The data stream syntax error reply message indicates that the server could not process a protocol command that the server determined did not conform to the requirements of the Distributed Data Management architecture. Action: Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -381 | 08S01 | -381 | Message: An internal network library error has occurred. The requested command sent a data object extension that is not recognized or is not supported by the target system. Reason: The target not supported reply message indicates that the server received a parameter on an object from the client that the server does not recognize or that the server does not support. Action: Review a client network trace to determine if the server returned an optional severity code or other optional diagnostic information. |
| -385 | 08S01 | -385 | Message: An internal network library error has occurred. The requested command included a parameter value that is not recognized or is not supported by the target system. Reason: The parameter value not supported reply message indicates that the server received a parameter value (e.g. invalid Host CCSID) on an object from the client that the server does not recognize or that the server does not support. The client specified an incorrect user-specified value when connecting or when executing a command. Action: Review a client network trace to view the parameter whose value is not recognized or not supported, and to determine if the server returned an optional severity code or other optional diagnostic information. |
| -1500 | HY000 | -1500 | Message: The maximum number of statements (128) has been reached for the current connection. Reason: The client relies on pre-defined SQL statements in sections within DB2 Static SQL packages to support execution of concurrent SQL SELECT statements. By default, the client defines 128 package sections, allowing the client to execute 128 concurrent SQL SELECT statements per client connection. When the maximum number of outstanding concurrent SQL SELECT statements exceeds the number of pre-defined sections, then the client cannot execute a new SQL SELECT statement. Action: Verify connection information to ensure the Package Collection value matches DB2 collection in which Host Integration Server packages are defined for execution by current user ID or PUBLIC. For more information, see topic on Package Collection. |
| -1501 | HY000 | -1501 | Message: User has no authority to create (execute) package. Reason: The server cannot execute a SQL SELECT or CALL statement that requires a CURSOR statement stored in a static SQL package to which the current user is not authorized. The client relies on pre-defined SQL statements in sections within DB2 Static SQL packages to support execution of SQL SELECT statements. By default, the client defines a package automatically, if the runtime user has package BIND, EXECUTE, and GRANT authority over the DB2 collection specified in the Package Collection connection property. Action: Verify connection information to ensure the Package Collection value matches DB2 collection in which Host Integration Server packages are defined for execution by current user identifier or PUBLIC. Manually create Host Integration Server packages for execution by current user ID or PUBLIC, using Data Access Tool, Data Source Wizard, Data Links, or Data Access Library. Connect to DB2 using an authorization ID that is privileged to automatically create Host Integration Server packages (CREATE, BIND and EXECUTE privileges). For more information, see topic on Package Collection. |
| -7049 | HY000 | -7049 | Message: Failed to get connection from pool. Application reaches the limit of connections from connection pooling. Max number defined in “MAX POOL SIZE” property. Reason: Client cannot connect to server when the available connections in the client connection pool have been exhausted. Action: Configure a larger max pool size and set a timeout on the pooled connections. For more information, see topic on Max Pool Size. |