Explanation | A database error occurred for which the SQL state and the Error code are listed. |
Action | Use the information associated with the error code to fix the problem in the database. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | An error occurred in the WebSphere code. |
Action | Collect all trace and system logs, along with a description of the operation that you were attempting. Visit the IBM support Web site for information on problem determination. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | The database backend generated an exception that was caught by the Data Store Adapter. |
Action | Refer to the error text reported by the database software for possible sources of the error. |
Explanation | The operation resulted in an exception. |
Action | Examine the operation, the exception, and the database log files. |
Explanation | An internal error has occurred. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | The Application Server has detected that the database started a transaction. The Application Server will attempt to resolve the transaction as configured in the custom properties for the data source. |
Action | There is no user action required. |
Explanation | The Application Server has detected that the database started a transaction. The Application Server will attempt to resolve the transaction as configured in the custom properties for the data source. An error occurred that prevented the transaction from being resolved. |
Action | Gather the FFDC log files and any server log files. If the error is not related to a database outage, visit the IBM support Web site for problem determination. |
Explanation | The database has started a transaction on the connection. The Application Server will rollback the transaction before returning the connection to the pool. |
Action | Evaluate the application code to determine what might be causing the implicit transaction. The application code might be able to prevent further implicit transactions explicity, or you could configure an explicit action to take for the data source. |
Explanation | An exception was detected cleaning up the ManagedConnection for a destroy operation. |
Action | Refer to the error reported by the database software to help determine the cause of the error. |
Explanation | The operation that was requested is not allowed during a transaction. |
Action | Perform the operation before starting the transaction or after completing the transaction. |
Explanation | A request was initiated by the user to purge the pool. This request makes existing connections in the pool no longer valid. |
Action | Exit the transaction, and the method boundary, and attempt the logic again with a new connection. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A two phase operation on the database resulted in an exception. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A two-phase operation on the database resulted in an exception. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Application Server attempted to perform an XAResource operation with an Xid other than the Xid that is used for XAResource.start. |
Action | Obtain a new connection and attempt the transaction again. |
Explanation | The data source custom property, oracleRACXARecoveryDelay, causes the application server to delay xa.commit and xa.rollback operations for the duration of the retry interval. |
Action | Wait for the transaction manager to retry the operation. You must configure heuristic retries on the transaction manager in order for oracleRACXARecoveryDelay to work properly. |
Explanation | The database or the jdbc provider specified by datasource does not support the tight branch coupling option. Tight branch coupling is only supported with a DB2 for z/OS database accessed by the DB2 Universal JCC driver. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The database specified by the datasource does not support the tight branch coupling option. Tight branch coupling is only supported with type 4 connections to DB2 for z/OS V8 (+ APAR PK47713) or DB2 for Linux, UNIX, Windows V8 and later versions. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The jdbc provider specified by datasource does not support the tight branch coupling option. Tight branch coupling is only supported with minimum levels of DB2 Universal JCC driver version 3.51 or 3.6, as bundled with DB2 9.5 or 9 service levels, or the JCC4 driver version 4.1. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The connection will not be reset for connection pooling because the application failed to explicitly close all handles. |
Action | Modify the application to always close all connection handles. |
Explanation | The feature that was requested is not available. |
Action | Avoid using the feature, or switch to a driver version that supports the feature if possible. |
Explanation | A valid JDBC driver implementation class was not found. |
Action | Update the configuration so that either the library contains a path to a recognized JDBC driver or the implementation class is specified on the data source. |
Explanation | A valid JDBC driver implementation class was not found. |
Action | Update the configuration so that either the nested library contains a path to a recognized JDBC driver or the implementation class is specified on the data source. |
Explanation | A valid jdbcDriver element could not be found the specified dataSource. |
Action | Update the configuration to include either a valid nested jdbcDriver element or a top-level jdbcDriver element with the same name as the jdbcDriverRef attribute on the dataSource. |
Explanation | An error occurred while attempting to execute the specified SQL command. |
Action | Refer to the exception message to help determine the cause of the problem. |
Explanation | The trace file that you specified on the data source does not exist. |
Action | Use an existing file for the trace file. |
Explanation | The DB2 Universal JDBC driver has been switched to run in an RRS environment on DB2 for z/OS. |
Action | This is the informational message for the environment of the JDBC driver that is running. |
Explanation | The driverType custom property for the data source was set to the value of 2 on the DB2XADatasource. This configuration is not supported by DB2 for z/OS. |
Action | Use the DB2ConnectionPoolDatasource or switch to the DB2 Universal JDBC driver type 4 if it is available for your configuration. |
Explanation | An IOException occurred when the Application Server was trying to open the trace file that was specified. |
Action | Examine the exception, fix the IO problem, and start the Application Server again. |
Explanation | An exception occurred when the Application Server was trying to get or access the metadata object for the database. |
Action | Verify that the metadata is enabled on the backend database. |
Explanation | The Application Server could not find a setter method on the data source to set the property that is requested. |
Action | Verify that the property name that is specified is correct. |
Explanation | The Application Server was not able to locate the data source property that was specified. The possible reasons are: 1) The data source property is not spelled or capitalized correctly, 2) The property that is specified does not apply to the data source that is being configured, or 3) the Application Server contains the default configuration for a different version of the JDBC driver that was specified, and this caused a mismatch of data source properties. |
Action | Verify that the property that is specified is correct for the data source. Correct any errors with spellings or capitalization. Delete the property if it does not apply (or no longer applies) to the JDBC driver that is used. |
Explanation | An exception occurred setting the specified property on the data source. |
Action | Verify that the value that is specified is valid for the property. |
Explanation | See the linkedException for more information. |
Action | See the linkedException for more information. |
Explanation | The 'enable2Phase' property can only be set to false if the data source class implements the ConnectionPoolDatasource interface. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | The 'enable2Phase' property can only be set to true if the data source class implements XADatasource interface. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | This message displays the product name for the Database. |
Action | The Database name that is listed above is now being used by applications. |
Explanation | This message displays the product version for the Database. |
Action | The Database version that is listed above is now being used by applications. |
Explanation | This message displays the name of the Java Database Connectivity (JDBC) driver. |
Action | The name of the JDBC driver that is listed above is now being used by applications. |
Explanation | The version of the Java Database Connectivity (JDBC) driver. |
Action | The version that is listed above for the JDBC driver is now being used by applications. |
Explanation | Oracle databases do not implement the setReadOnly method. A setReadOnly(true) method will not make the connection as readonly connection. The setReadOnly(false) is also not implemented, and a transaction is implicitly started by an Oracle database. The Application Server will not invoke the setReadOnly(false) method on an Oracle database to prevent an unnecessary transaction from being started. |
Action | Inspect your application to verify that your application does not depend on a transaction after the setReadOnly(false) method is called. |
Explanation | The application is using a JDBC provider that is no longer supported by the Application Server. |
Action | Use the JDBC provider that is provided in the error text. |
Explanation | An attempt is made to pool a connection that has an AutoCommit value of False. The application server cannot determine if a transaction is active because the data source is configured as nontransactional. The application server will not attempt to resolve the transaction because the data source is not configured to automatically commit or roll back during connection cleanup. |
Action | Configure the data source to automatically commit or roll back on connection cleanup, or always reset the AutoCommit value to True. |
Explanation | An error occurred closing the JDBC object that is specified. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The application attempted to access a connection or the connection's corresponding Statements, ResultSets, or metadata from a different thread. This behavior is a violation of the programming model for the application server. Closing the objects that the application attempted to access in a finalize() method is also considered a programming model violation, because the finalize() method is run by the JVM in another thread. |
Action | Adjust the application to avoid multithreaded access. |
Explanation | The method being invoked is part of the Java Database Connectivty (JDBC) specification V3.0, and the method does not exist on the provider. |
Action | Ensure that your JDBC provider supports the JDBC specification V3.0, or do not use this method. |
Explanation | The connection handle is now associated with a pooled connection that is different and that does not implement the interface that is requested for the wrapper. |
Action | Wrappers for the interface that is specified should not be used when the Wrapper.isWrapperFor method indicates that the connection is not a wrapper of the interface. |
Explanation | The data source custom property allows you to choose which connection sharing behavior you want. |
Action | Verify that the data source custom property is configured for the behavior you want. |
Explanation | The method that is specified is not supported by the implementation of the Application Server. |
Action | Do not use the method. |
Explanation | This method is provided only for internal use by the Application Server. |
Action | Do not call this method. |
Explanation | Attempted to perform an operation on an object that is closed. |
Action | Retrieve a new instance of the object on which to perform the operation. |
Explanation | The wrapper that is specified does not contain the wrapped object type that is specified. |
Action | Verify that the wrapper and the parameters for the wrapped object are specified correctly. |
Explanation | The Application Server does not permit the operation that was requested. |
Action | Do not use the operation that is specified. |
Explanation | The Application Server does not allow calls to the setTypeMap, setReadOnly or setCatalog methods on Shareable Connections while a global transaction is active. |
Action | Do not call setTypeMap, setReadOnly or setCatalog on Shareable Connections in a global transaction, or switch to Unshareable Connections. |
Explanation | The Application Server does not allow calls to the commit, rollback, setSavepoint or releaseSavepoint methods on the Connection while a global transaction is active. |
Action | Do not call the commit, rollback, setSavepoint or releaseSavepoint methods on the connection when it is in a global transaction. If a non-transactional data source (for example, non-jta-data-source for Java Persistence API) is being used, then configure non-jta-data-source in persistence.xml and also configure the nonTransactionalDataSource custom property on the data source. |
Explanation | You cannot perform operations when the application is in the current transaction state. |
Action | Get a new Connection on which to perform the operation. |
Explanation | The current Connection handle could not be reassociated. |
Action | Try obtaining a new Connection. |
Explanation | Connection handles can only be reassociated from the INACTIVE state. |
Action | Close your current Connection handle, and obtain a new one. |
Explanation | Connection handles can only be reassociated if all the child objects are closed. |
Action | Close your current Connection handle, and obtain a new one. |
Explanation | An operation is currently being performed on the Connection handle. It cannot be dissociated during the operation. |
Action | Wait until all the operations on the handle have finished, then dissociate the handle. |
Explanation | The fetch size can only be set to a value that is not negative. |
Action | Choose a value for the fetch size that is not negative. |
Explanation | The Application Server does not support Kerberos authentication on the database that is used. User name and password will not be used when getting a connection. |
Action | Disable Kerberos, or use a DB2 backend with the DB2 universal JDBC driver. |