Data Provider Error Codes
The Data Provider returns errors in the form of SQLSTATE, SQLCODE, Reason Code, and Error Text, formatted as part of the OLE DB IErrorInfo interface. The Data Provider connects to the DB2 database server using the Distributed Relational Database Architecture (DRDA) protocol and formats. The Data Provider returns DRDA protocol issues in SQLSTATE HY000 or 08S01, with associated SQLCODE errors and text. The following table list DRDA errors. For additional information on DRDA protocol issues, you can refer to the DRDA protocol documentation published by The Open Group (http://www.opengroup.org). You can download DRDA V5 Vol. 3: Distributed Data Management Architecture, publication number C114, from the Open Group bookstore (https://go.microsoft.com/fwlink/?LinkID=219127&clcid=0x409).
DRDA Protocol Errors
The following table lists DRDA protocol error constants, values, SqlState, SqlCode and a description of the error. An asterisk (*) indicates not in use.
| SQLSTATE | SQLCODE | Description |
|---|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| HY000 | -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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 HIS 2010 packages are defined for execution by current user ID or PUBLIC. For more information, see topic on Package Collection. |
| 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 HIS 2010 packages are defined for execution by current user identifier or PUBLIC. Manually create HIS 2010 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 HIS 2010 packages (CREATE, BIND and EXECUTE privileges). For more information, see topic on Package Collection. |
| 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. |
TCPIP Network Errors
The following table lists TCPIP Network Client error constants, values, SqlState, SqlCode and a description of the error.
| SQLSTATE | SQLCODE | Description |
|---|---|---|
| 08S01 | -602 | Message: Could not resolve the specified host name. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. For more information, see topics on Network Address and Network Port. |
| 08S01 | -603 | Message: Could not connect to specified host. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value, or the server is unavailable. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. Contact the network administrator or server administrator. For more information, see topics on Network Address and Network Port. |
| 08S01 | -604 | Message: Socket allocation failed. Reason: The client failed to connect to the DB2 server via a TCP/IP network, when all of the local client socket resources were in use. Action: Close unused client connections. Utilize client connection pooling. For more information, see topic on Connection Pooling. |
| 08S01 | -605 | Message: The network connection was terminated because the host failed to send any data. Reason: The client could not connect to the DB2 server due to an unforeseen problem with the client or server. Action: Contact the client administrator, network administrator, or server administrator. |
| 08S01 | -606 | Message: Enterprise single sign-on failure: Could not contact the SSO server <server-name>. Check that SSO is configured and that the SSO service is running on hat server. Reason: The Enterprise Single Sign-On server is not configured or running. Action: Verify connection information to ensure the ESSO Affiliate Application name matches the value for the server and current user defined by the Enterprise Single Sign-On administrator. Check with your Enterprise Single Sign-On Administrator. Configure an alternative authentication method. For more information, see topic on Security Method. |
| 08S01 | 10014 | Message: A TCPIP socket error has occurred (10014): The sockaddr structure pointed to by the name contains incorrect address format for the associated address family or the namelen parameter is too small. This error is also returned if the sockaddr structure pointed to by the name parameter with a length specified in the namelen parameter is not in a valid part of the user address space. Reason: The client is attempting to connect to the DB2 server using an improperly-formatted IPv6 Network Address. Action: Verify connection information to ensure the Network Address specified matches the server and requirements for either an IPv4 or IPv6 network. For more information, see topic on Network Address. |
| 08S01 | 10022 | Message: A TCPIP socket error has occurred (10022): An invalid argument was supplied. Reason: The client is attempting to connect to the DB2 server using an improperly-formatted IPv4 or IPv6 Network Address. Action: Verify connection information to ensure the Network Address specified matches the server and requirements for either an IPv4 or IPv6 network. For more information, see topic on Network Address. |
| 08S01 | 10024 | Message: A TCPIP socket error has occurred (10024): No more socket descriptors are available. Reason: The client failed to connect to the DB2 server via a TCP/IP network, when all of the local client socket connections were in use. Action: Close unused client connections. Utilize client connection pooling. For more information, see topic on Connection Pooling. |
| 08S01 | 10040 | Message: A TCPIP socket error has occurred (10040): The message was too large to fit into the specified buffer and was truncated. Reason: The client failed to execute a command as requested by the program. Action: Verify that the command syntax and parameter data values are within the limits supported by the DB2 server platform and version. For more information on command and data type limits, see topic on Data Type Mappings. |
| 08S01 | 10043 | Message: A TCPIP socket error has occurred (10043): The specified protocol is not supported. Reason: The client is attempting to connect to the DB2 server using an access method that is not supported by the DB2 server, such as Secure Sockets Layer or Transport Layer Security. Action: Verify connection information to ensure the DB2 server support SSL or TLS. Configure a TCP/IP network without specifying SSL or TLS. Contact the network administrator or server administrator. For more information on TCP/IP Network Connection, see topic on TCP/IP Network Connection. |
| 08S01 | 10047 | Message: A TCPIP socket error has occurred (10047): Addresses in the specified family cannot be used with this socket. Reason: The client is attempting to connect to the DB2 server using an improperly-formatted IPv4 or IPv6 Network Address. Action: Verify connection information to ensure the Network Address specified matches the server and requirements for either an IPv4 or IPv6 network. For more information, see topic on Network Address. |
| 08S01 | 10049 | Message: A TCPIP socket error has occurred (10049): The remote address is not a valid address (such as INADDR_ANY or in6addr_any). Reason: The client is attempting to connect to the DB2 server using an improperly-formatted IPv6 Network Address. Action: Verify connection information to ensure the Network Address specified matches the server and requirements for either an IPv4 or IPv6 network. For more information, see topic on Network Address. |
| 08S01 | 10050 | Message: A TCPIP socket error has occurred (10050): A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value, or the server is unavailable. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. Contact the server administrator. For more information, see topics on Network Address and Network Port. |
| 08S01 | 10051 | Message: A TCPIP socket error has occurred (10053): The network cannot be reached from this host at this time. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value, or the server is unavailable. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. Contact the server administrator. For more information, see topics on Network Address and Network Port. |
| 08S01 | 10052 | Message: A TCPIP socket error has occurred (10053): For a connection-oriented socket, this error indicates that the connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. For a datagram socket, this error indicates that the time to live has expired. Reason: The server closed the client connection. Action: Contact the network administrator or server administrator. |
| 08S01 | 10052 | Message: A TCPIP socket error has occurred (10052): The connection has been broken due to the keep-alive activity detecting a failure while the operation was in progress. Reason: The server closed the client connection. Action: Contact the network administrator or server administrator. |
| 08S01 | 10053 | Message: A TCPIP socket error has occurred (10053): An established connection was aborted by the software in your host machine. Reason: The server closed the client connection. Action: Contact the network administrator or server administrator. |
| 08S01 | 10054 | Message: A TCPIP socket error has occurred (10054): The virtual circuit was reset by the remote side executing a hard or abortive close. The application should close the socket as it is no longer usable. On a UPD-datagram socket this error would indicate that a previous send operation resulted in an ICMP "Port Unreachable" message. Reason: The server closed the client connection. Action: Contact the network administrator or server administrator. |
| 08S01 | 10055 | Message: A TCPIP socket error has occurred (10055): No buffer space is available. Reason: The client failed to connect to the DB2 server via a TCP/IP network, when all of the local client socket resources were in use. Action: Close unused client connections. Utilize client connection pooling. For more information, see topic on Connection Pooling. |
| 08S01 | 10057 | Message: A TCPIP socket error has occurred (10057): A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. For more information, see topics on Network Address and Network Port. |
| 08S01 | 10060 | Message: A TCPIP socket error has occurred (10060): The connection has been dropped because of a network failure or because the peer system failed to respond. Reason: The server closed the client connection. Action: Contact the network administrator or server administrator. |
| 08S01 | 10061 | Message: A TCPIP socket error has occurred (10061): The attempt to connect was forcefully rejected. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. For more information, see topics on Network Address and Network Port. |
| 08S01 | 10065 | Message: A TCPIP socket error has occurred (10065): A socket operation was attempted to an unreachable host. Reason: The client could not connect to the DB2 server with an incorrect user-specified Network Address or Network Port value, or the server is unavailable. Action: Verify connection information to ensure the Network Address and Network Port specified matches the server. Contact the server administrator. For more information, see topics on Network Address and Network Port. |
| 08S01 | 10093 | Message: A TCPIP socket error has occurred (10093): A successful WSAStartup call must occur before using this function. For more information, see https://msdn.microsoft.com/library/ms742213(VS.85).aspx. Reason: The client failed to connect to the DB2 server via a TCP/IP network, when all of the local client socket connections were in use. Action: Close unused client connections. Utilize client connection pooling. For more information, see topic on Connection Pooling. |
Common Errors
The following table describes DB2 server errors that may occur along with the actions you must take to correct them.
| SQLSTATE | SQLCODE | Message | Description |
|---|---|---|---|
| 42601 | -104 | Illegal symbol. Token was not valid Unexpected token. An unexpected token <token> was found following <text>. Expected tokens may include: <token-list>. |
Reason: The server cannot execute a SQL statement that contains illegal, invalid, or unexpected symbols or tokens. Action: Verify the SQL syntax using the IBM DB2 SQL Reference for the specific IBM DB2 platform and version. Check if data consumer application is using unsupported delimited object identifiers (e.g. square brackets ([<object-name>]) as opposed to using supported delimiters (double quotes). |
| 42602 | -113 | INVALID CHARACTER FOUND IN: <string>, REASON CODE <reason-code>. A character that is invalid in a name has been detected. <identifier> contains a character that is not allowed or does not contain any characters. |
Reason: The server cannot process a SQL SET CURRENT SQLID statement, when the client connects to the DB2 server. Action: Verify connection information to ensure the Default Qualifier value matches the DB2 collection in which object is cataloged. For more information, see topic on Default Qualifier. |
| 42802 | -117 | THE NUMBER OF VALUES ASSIGNED IS NOT THE SAME AS THE NUMBER OF SPECIFIED OR IMPLIED COLUMNS. Statement contains wrong number of values. The number of values assigned is not the same as the number of specified or implied columns or variables. |
Reason: The server cannot execute a SQL INSERT statement when the number of values specified is not the same as the number of columns in the table(s). Action: Verify that the number of columns match the objects in the SQL statement, by querying the system catalog (e.g. SYSIBM.SYSCOLUMNS) or executing a client schema query (e.g. OLE DB IDBSchemaRowsets::GetSchemas(DBSCHEMA_COLUMNS) or ADO.NET MsDb2Connection.GetSchema(Columns). |
| 22007 | -181 | THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE Value in date, time, or timestamp string not valid. The string representation of a datetime value is out of range. |
Reason: The server cannot execute the SQL statement where a DATETIME value is incorrectly formatted or out-of-range. Action: Verify the DATETIME values are within the supported range for year of 0001-9999, month of 1-12, day of 28/29/30/31 (depending on month and leap year), hour of 0-24 (12 for USA), minutes of 0-59, seconds of 0-59, and microseconds of 0-999999. Check connection information to ensure the DateTime As Date option is specified True to instruct the client to delete the time portion of Windows DateTime data values mapped to DB2 Timestamp data values, allowing the DB2 database to read these values as DB2 Date data values. For more information, see topic on DateTime As Date. |
| 42704 | -204 | <schema>.<object> is an unidentified name. An undefined object or constraint name was detected. <name> is an undefined name. |
Reason: The server cannot execute a SQL statement that references an invalid <schema>.<object> name. Action: Verify the object name specified in the SQL statement. Check connection information to ensure the Default Qualifier value matches the DB2 collection in which object is cataloged. For more information, see topic on Default Qualifier. |
| 42703 | -206 | <name> IS NOT VALID IN THE CONTEXT WHERE IT IS USED Column <name> not in specified tables. <name> is not valid in the context where it is used. |
Reason: The server cannot execute a SQL statement where a specified column name is not a column of the source or target table or view referenced I the statement. Action: Verify the column references match the objects in the SQL statement, by querying the system catalog (e.g. SYSIBM.SYSCOLUMNS) or executing a client schema query (e.g. OLE DB IDBSchemaRowsets::GetSchemas(DBSCHEMA_COLUMNS) or ADO.NET MsDb2Connection.GetSchema(Columns). |
| 08S01 | -360 | The host resource could not be found. Check that the Initial Catalog value matches the host resource name. | Reason: The server could not connect the client to the requested DRDA RDBNAM (Relational Database Name). Action: Verify the 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. For more information, see topic on Initial Catalog. |
| 42884 | -440 | NO <routine-type> BY THE NAME <routine-name> HAVING COMPATIBLE ARGUMENTS WAS FOUND IN THE CURRENT PATH No routine was found with the specified name and compatible arguments. No authorized routine named <routine-name> of type <routine-type> having compatible arguments was found. |
Reason: The server cannot execute a SQL CALL statement that contains the wrong number of arguments, or invalid parameter data types, or references an invalid <schema>.<object> name. Action: Verify the number of arguments. Check the parameter data types. Verify the object name specified in the SQL statement. Check the connection information to ensure the Default Qualifier value matches the DB2 collection in which object is cataloged. For more information, see topic on Default Qualifier. |
| 24501 | -501 | THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN. Cursor <cursor name> not open. The cursor specified in a FETCH statement or CLOSE statement is not open or a cursor variable in a cursor scalar function reference is not open. |
Reason: The server cannot execute a SQL SELECT or CALL statement that requires a FETCH or CLOSE against a CURSOR that is not in an open state. Action: Verify the application to see if it issuing a COMMIT or ROLLBACK, which might close the cursor. Check for previously-received return message that might indicate the server automatically closed the cursor based on a system event (e.g. SQLCODE -404, -652, -679, -802, -901, -904, -909, -910, -911, -913, or -952). Verify connection information to ensure the AutoCommit option is specified True when working with some generic consumers, including SQL Server Integration Services and Distributed Query Processor, when using remote unit of work transactions. For more information, see topic on AutoCommit. |
| 42501 | -551 | Not authorized to object. Not authorized to object <object-name> in <resource-name> type <resource-type>. <authorization-ID> does not have the required authorization or privilege to perform operation <operation> on object <object-name>. |
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 HIS 2010 packages are defined for execution by current user identifier or PUBLIC. Manually create HIS 2010 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 HIS 2010 packages (CREATE, BIND and EXECUTE privileges). For more information, see topic on Package Collection. |
| 42501 42602 |
-567 -567 |
<bind-type> AUTHORIZATION ERROR USING <auth-id> AUTHORITY PACKAGE = <package-name> PRIVILEGE = <privilege>. Authorization name &1 is not allowed. <authorization-ID> is not a valid authorization ID. |
Reason: The server cannot execute a SQL SELECT statement when the user account does not have permission to create or execute the required DB2 packages. Action: Verify connection information to ensure the Package Collection value matches DB2 collection in which HIS 2010 packages are defined for execution by current user identifier or PUBLIC. Manually create HIS 2010 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 HIS 2010 packages (CREATE, BIND and EXECUTE privileges). For more information, see topic on Package Collection. |
| 42710 | -601 | THE NAME (VERSION OR VOLUME SERIAL NUMBER) OF THE OBJECTTO BE DEFINED OR THE TARGET OF A RENAME STATEMENT IS IDENTICAL TO THE EXISTING NAME (VERSION OR VOLUME SERIAL NUMBER) <object-name> OF THE OBJECT TYPE <object-type>. <name> in <schema> type <type> already exists. The name of the object to be created is identical to the existing name <name> of type <type>. |
Reason: The server cannot name an object when that name is already in use for another object of the same type. Action: Name the object uniquely compared to existing database objects. |
| 42721 | -725 | THE SPECIAL REGISTER <register> AT LOCATION <location> WAS SUPPLIED AN INVALID VALUE | Reason: The server cannot process SET CURRENT SQLID statement when it contains an invalid value for user identifier or collection name. Action: Verify connection information to ensure the Default Qualifier value matches the DB2 collection in which object is cataloged. For more information, see topic on Default Qualifier. |
| 23505 | -803 | AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX IN INDEX SPACE <indexspace-name> CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X <row identifier> Duplicate key value specified. One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by <index-id> constrains table <table-name> from having duplicate values for the index key. |
Reason: The server cannot execute an INSERT or UPDATE statement against a table that is constrained by a UNIQUE INDEX where the statement would result in duplicate values. Action: Verify the data values do not violate a constraint, by querying the system catalog (e.g. SYSIBM.SYSINDEXES) or executing a client schema query (e.g. OLE DB IDBSchemaRowsets::GetSchemas(DBSCHEMA_INDEXES) or ADO.NET MsDb2Connection.GetSchema(Indexes). |
| 51002 | -805 | DBRM OR PACKAGE NAME <location-name>.<collection-id>.<dbrmname>.<consistency-token> NOT FOUND IN PLAN <plan-name>. REASON <reason>. SQL package <package-name> in <collection-name> not found at DRDA Server. Package <package-name> was not found. |
Reason: The server could not find the DB2 static SQL package required by the DB2 client to execute a dynamic SQL SELECT statement. Action: Verify connection information to ensure the Package Collection value matches DB2 collection in which HIS 2010 packages are defined for execution by current user ID or PUBLIC. For more information, see topic on Package Collection. |
| 58004 | -901 | UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS. SQL system error. The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason <reason>.) |
Reason: The server failed to execute the current SQL statement, but subsequent SQL statements may succeed. This error may be caused by a transaction commit fails within a Distributed Unit of Work, or an update fails due to a constraint, or the SQL statement contains an invalid length (0 or beyond maximum length). Action: The user should check the reason code where available to determine if further user or administrator action is required, as well as to determine how to avoid the error by modifying the application, transaction, or command. |
| 57011 | -904 | UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON <reason-code>, TYPE OF RESOURCE <resource-type>, AND RESOURCE NAME <resource-name>. Resource limit exceeded. Unsuccessful execution caused by an unavailable resource. Reason code: <reason-code>, type of resource: <resource-type>, and resource name: <resource-name>. |
Reason: The server cannot execute the SQL statement because the object of the statement is unavailable. Action: Verify that the object and database are available and not in a deadlock, offline, or other unavailable state. |
| 57033 | -913 | UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE <reason-code>, TYPE OF RESOURCE <resource-type>, AND RESOURCE NAME <resource-name>. Row or object <object-name> in <resource-name> type <resource-type> in use. Unsuccessful execution caused by deadlock or timeout. Reason code <reason-code>. |
Reason: The server cannot execute the SQL statement because the object of the statement is unavailable. Action: Verify that the object and database are available and not in a deadlock, offline, or other unavailable state. Commit or rollback previous operation, and then disconnect from the database. Check the server reason code for more information on the state of the object (e.g. DB2 for z/OS reason code 00C90088 indicates a deadlock, whereas 00C9008E indicates a timeout. |