Resource Adapters For WAS messages

DSRA0010E: SQL State = {0}, Error Code = {1}
Explanation: A database error occurred for which the SQL state and the Error code are listed.
User Response: Use the information associated with the error code to fix the problem in the database.

DSRA0011E: Exception: {0}
Explanation: A stack is provided. This stack is related to the problem reported above.
User Response: Use the information associated with the stack to fix the problem.

DSRA0020E: {0} could not be found: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0022E: The DataSource implementation class is null.
Explanation: A valid, non-null DataSource implementation class name is required when creating a JDBC provider.
User Response: Enter a valid DataSource implementation class name and retry.

DSRA0023E: The DataSource implementation class "{0}" could not be found.
Explanation: Unable to locate the DataSource implementation class specified.
User Response: Verify the DataSource class name you provided is correct and is in your classpath.

DSRA0024E: The DataSource could not be created from implementation class "{0}". The exception is: {1}.
Explanation: An error occurred instantiating the DataSource.
User Response: Verify the DataSource class has a public constructor taking no parameters.

DSRA0025E: Class {0} does not implement {1}.
Explanation: Object cannot be cast to the specified interface because it does not implement it.
User Response: Verify that the correct implementation class is provided.

DSRA0030E: Data Store Adapter internal error occurred. Please contact WebSphere support with the following data: {0} {1} {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0035W: DataStore Adapter internal error occurred. Please contact WebSphere support with the following information: {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0040E: WebSphere internal error occurred. Please contact WebSphere support with the following data: {0} {1} {2}
Explanation: An error occurred in the WebSphere code.
User Response: Please collect all trace and system logs, along with a description of what you were attempting to do. Then contact WebSphere support.

DSRA0050W: Data Store Adapter internal warning occurred. Please contact WebSphere support with the following data: {0} {1} {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0060W: WebSphere internal warning occurred. Please contact WebSphere support with the following data: {0} {1} {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0070E: {0} is closed. Unable to perform: {1}
Explanation: Attempted to perform an operation on an object which is closed.
User Response: Retrieve a new instance of the object and retry the operation.

DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: {0}.
Explanation: The database back end generated an exception which was caught by the Data Store Adapter and reported to you.
User Response: Try to fix the primary problem reported by the database software.

DSRA0081E: Unable to perform Optimistic Update; row has been changed by another transaction.
Explanation: Another transaction has updated the data in the row. Because of the conflict the Optimistic Update cannot be completed.
User Response: Application may roll back the transaction and retry at this point, if desired.

DSRA0082E: The Batch update count is null.
Explanation: possible reasons: 1)database returned null, 2) WebSphere internal error.
User Response: for reason 1 batch update should not be used, or switch to a database that supports batch update, and/or contact your database support. for reason 2, contact IBM support with the following trace (RRA=all=enabled and PMGR=all=enabled) and the FFDC files.

DSRA0083E: one of the batched updates failed which caused the database to return -3 in the batch update count.
Explanation: one of the batched updates failed which caused the database to return -3 in the batch update count. -3 is returned if the database continues to execute the batched updates after one fails
User Response: examine your database logs

DSRA0084E: The operation was successful, however, the number of rows updated is not known. The database returned -2 in the batch update count.
Explanation: The operation was successful, however, the number of rows updated is not known. The database returned -2 in the batch update count. This exception is thrown to avoid any possible data integrity issues
User Response: repeat operation

DSRA0085E: The operation was successful, however, the number of rows updated was 0.
Explanation: some or all of the rows were not updated because of a collision usually caused by the use of the optimistic-concurrency-control AccessIntent.
User Response: repeat operation or change AccessIntent if error persists.

DSRA0086E: An operation resulted in an Exception. Operation is: {0}. Exception is: {1}. Possible cause {2}
Explanation: the operation indicated resulted an exception indicated.
User Response: examine the operation, exception and database logs, the exception is ignored in this case.

DSRA0087E: {0} operation was not successful because {1}
Explanation: Batch operation specified above had a problem, see reason above.
User Response: examine your database logs and contact WebSphere support if no obvious reason was found.

DSRA0090W: Subject was valid and not null, but no valid credentials were found.
Explanation: No container-managed authentication alias found.
User Response: Add a container-managed authentication alias on the datasource via the admin console.

DSRA0100E: SQLJ support may not be available for the DataSource class specified. Error message is: {0}
Explanation: The enableSQLJ DataSource property should only be set for JDBC providers for which WebSphere supports SQLJ.
User Response: If you wish to use SQLJ, switch to a JDBC provider for which WebSphere supports SQLJ. Otherwise, set the enableSQLJ DataSource property to false.

DSRA0174W: Warning: GenericDataStoreHelper is being used.
Explanation: GenericDataStoreHelper has been initialized
User Response: None if this was the intention

DSRA0180W: Exception detected during ManagedConnection.destroy(). The exception is: {0}.
Explanation: An exception was detected while cleaning up the ManagedConnection for destroy.
User Response: Try to fix the primary problem reported by the database software.

DSRA0230E: Attempt to perform operation {0} is not allowed because transaction state is {1}.
Explanation: The operation requested is not allowed during a transaction.
User Response: Perform the operation before beginning or after completing the transaction.

DSRA0240E: Invalid Connection. Connection Pool is being purged.
Explanation: A request was initiated by the user to purge the pool, which invalidates existing connections in the pool.
User Response: Exit transaction and or method boundary and retry logic with a new connection.

DSRA0280W: Attempted to add duplicate "ConnectionEventListener" to "ManagedConnection": {0}
Explanation: Warning message.
User Response: No user action is required.

DSRA0302E: XAException occurred. Error code is: {0}. Exception is: {1}
Explanation: A two phase operation on the database resulted in an exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0304E: XAException occurred. XAException contents and details are: {0}.
Explanation: A two phase operation on the database resulted in an exception, more details of the exception are displayed.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA0310E: Xids do not match. XAResource.start: {0} XAResource.{1}: {2}
Explanation: Attempted to perform an XAResource operation with an Xid other than the Xid used for XAResource.start.
User Response: Obtain a new connection and retry the transaction.

DSRA1000E: The WebSphere Relational Resource Adapter does not support message inflow.
Explanation: The ResourceAdapter.endpointActivation method should not be used on the WebSphere Relational Resource Adapter because it does not support message inflow.
User Response: Do not use the ResourceAdapter.endpointActivation method on the WebSphere Relational Resource Adapter.

DSRA1100W: An error occurred while resetting a connection to its default state. The connection will be destroyed. {0}
Explanation: The default connection manager received an error while resetting a ManagedConnection to its default state.
User Response: Take action to return the database to a useable state, if necessary.

DSRA1101W: An error occurred while destroying a connection. {0}
Explanation: The default connection manager received an error while destroying a ManagedConnection.
User Response: Take action to return the database to a useable state, if necessary.

DSRA1102W: An error occurred while validating connections after detection of a fatal connection error. All connections will be destroyed. {0}
Explanation: The default connection manager received an error when requesting validation of pooled ManagedConnections.
User Response: Take action to return the database to a useable state, if necessary.

DSRA1110E: Unable to establish a connection. The maximum number of connections for the connection pool, {0}, is already open.
Explanation: The connection pool has reached its maximum limit for open connections. Further connections cannot be established until some of the open connections are closed.
User Response: Adjust the application to require fewer connections open at the same time.

DSRA1120E: Application did not explicitly close all handles to this Connection. Connection cannot be pooled.
Explanation: The connection will not be reset for connection pooling because the application failed to explicitly close all handles.
User Response: Modify the application to always close all connection handles.

DSRA1130E: A fatal connection error occurred on another connection while this connection was active. This connection cannot be reset to a usable state.
Explanation: The connection cannot be reset for connection pooling because a fatal connection error occurred while it was active.
User Response: Take action to return the database to a usable state, if necessary.

DSRA1200E: The iteration does not contain any more elements. Element {0} does not exist.
Explanation: The 'next' operation was invoked on an iterator that does not contain any more elements.
User Response: Invoke 'hasNext' on the iteration before invoking 'next' to determine whether the iteration contains additional elements.

DSRA1210E: The iterator is not positioned on any element. There is nothing to remove.
Explanation: The 'remove' operation was invoked with the iterator not positioned on any element.
User Response: Position the iterator to a valid element before invoking the 'remove' operation.

DSRA7000W: Mapped Exception could not be instantiated, reason: {0}
Explanation: Could not map the exception, see the exception that occurred during the mapping.
User Response: Verify exception mapping in the DataStoreHelper error map table and the exception constructor.

DSRA7001E: This method must be called from DataDirect DataStoreHelper.
Explanation: MSSQLhelper methods can only be called from DataDirect helpers.
User Response: Use DataDirectDataStoreHelper.class in your setup.

DSRA7002W: Invalid intent combination, can not use NoCollision and Exclusive together, Exclusive alone will be used
Explanation: Can not use NoCollision and Exclusive together.
User Response: Examine your intent and make sure to select Exclusive or NoCollision but not both

DSRA7003E: A java.util.Properties object must be specified which includes all of the necessary connection information.
Explanation: Part or all of the necessary connection information is missing.
User Response: See the Java documentation for the DataStoreHelper.showLockInfo() method for a description of the connection information which is required.

DSRA7004E: showLockInfo method does not support {0} platform.
Explanation: The showLockInfo method does not support the specified Operating System
User Response: Use the correct Operating System

DSRA7005E: showLockInfo(): could not execute db2 command {0}, reason: {1}
Explanation: An exception occurred when an operation was attempted on the database to collect lock information.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA7006I: Lock information should be available in file: {0}
Explanation: DB2 wrote lock information into the filename listed.
User Response: Open the file listed. It contains information on locks in your database. This information may be helpful in resolving deadlocks in the application.

DSRA7007W: Oracle does not support Serializable isolation level when using XA protocol, if XA is being used, an error will be thrown by Oracle. To correct the problem, do not use PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE since it cause a Serializable isolation level to be returned.
Explanation: Oracle does not support Serializable isolation level when using XA protocol.
User Response: Do not use PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE since it cause a Serializable isolation level to be used.

DSRA7008I: Oracle JDBC logging is enabled, Oracle may require the use of a debug version of the oracle jar/zip file.
Explanation: Oracle may require the use of a debug version of jar/zip file if oracle logging is enabled.
User Response: use a debug version of oracle jar/zip file if oracle logging is enabled.

DSRA7009I: DB2 JDBC logging is enabled, DB2 Universal driver is required to display any traces.
Explanation: DB2 requires the use of DB2 Universal driver
User Response: use the above DB2 driver

DSRA7010E: trace file specified {0} does not exist, an exception will be thrown from the database if problem is not corrected.
Explanation: the trace file you specified on the datasource doesn't exist
User Response: make sure to use an existing file

DSRA7011W: A Oracle JDBC provider property (TransactionBranchesLooselyCoupled) has been set.
Explanation: user set an a custom property when creating the oracle JDBC provider, the property requires Oracle patch 2511780
User Response: if patch is installed, no action is required, otherwise, user must contact oracle support to obtain patch.

DSRA7012W: Cloudscape NetworkServer only supports a value of 4 for the driverType datasource custom Property. The driverType value is changed to 4 to continue operation successfully
Explanation: The user sets the driverType datasource custom property to 2 which is not supported on Cloudscape. WebSphere will change the value to 4 at runtime.
User Response: To avoid future warnings, the user must change the driverType value to 4 in the admin console and/or the jacl scripts or omit setting it completely in which WAS will make it default to 4.

DSRA7013E: Wrong configuration : JDBC driver does not support setDriverType
Explanation: The user sets the driverType datasource custom property which is not supported by the JDBC driver.
User Response: Remove the driverType from the datasource custom property.

DSRA7014I: The DB2 Universal JDBC driver runs in a RRS environment
Explanation: The DB2 Universal JDBC driver has been switched to run in a RRS environment on DB2 for zOS.
User Response: This is the information for the JDBC driver running environment.

DSRA7015E: DB2 does not support driver type 2 with DB2XADataSource under DB2 for z/OS
Explanation: The user sets the driverType datasource custom property to 2 on the DB2XADataSource. This configuration is not supported by DB2 for z/OS
User Response: either use DB2ConnectionPoolDataSource or switch to DB2 Universal JDBC driver type 4 if available.

DSRA7016I: The JDBC driver does not support getPooledConnection(GSSCredential)
Explanation: The JDBC driver version used does not support the getPooledConnection(GSSCredential) method.
User Response: Use a JDBC driver that supports the getPooledConnection(GSSCredential) method.

DSRA7017I: Logging to file {0} cannot occur because of IOException {1}
Explanation: An IOException occurred when trying to open the specified trace file.
User Response: Examine the exception, fix the IO problem, and start the WebSphere Application Server again.

DSRA7020E: There is no locking information available from the GenericDataStoreHelper
Explanation: GenericDataStoreHelper does not know how to collect lock information.
User Response: Write or use your database specific DataStoreHelper.

DSRA7030I: Cloudscape Lock information for {0} The Locks.xid is :{1} The Locks.Type is:{2} The TableName is :{3} The Mode is :{4} The Lockname is :{5} The State is :{6} The SQLString is:{7} Lock number :{8}
Explanation: This is the lock information reported by the Cloudscape database for your application.
User Response: This is information on locks in your database. You might want to use the information to resolve deadlocks in your application.

DSRA8000E: No jar or zip files found in {0}
Explanation: Unable to locate any jar or zip files in the JDBC provider library path specified.
User Response: Verify that the path specified is correct and the necessary jars and zips are there.

DSRA8001E: Unable to read JDBC provider jar or zip file: {0}
Explanation: MalformedURLException occurred attempting to read a JDBC provider jar or zip file.
User Response: Verify that the path specified is correct and the necessary jars and zips are valid.

DSRA8010W: Unable to read setter methods from DataSource class. Encountered {0}.
Explanation: An IntrospectionException occurred attempting to retrieve setter methods from the DataSource.
User Response: DataSource properties will not show up in the GUI. You will need to enter them manually.

DSRA8011E: No setter method for property ''{0}''.
Explanation: Could not find a setter on the DataSource to set the requested property.
User Response: Verify the property name specified is correct.

DSRA8020E: Warning: The property ''{1}'' does not exist on the DataSource class {0}.
Explanation: Unable to locate the specified DataSource property. Possible reasons: 1) The DataSource property is spelled or capitalized incorrectly. 2) The specified property does not apply to the DataSource being configured. 3) WebSphere contains the default configuration for a different version of the specified JDBC driver, causing a mismatch of DataSource properties.
User Response: Verify that the property specified is correct for the DataSource. Fix any misspellings or capitalization errors. Delete the property if it does not apply (or no longer applies) to the JDBC driver used.

DSRA8021W: Warning: error setting ''{0}''{1}: {2}
Explanation: An exception occurred setting the specified property on the DataSource.
User Response: Verify that the value specified for the property is valid.

DSRA8025I: Successfully connected to DataSource.
Explanation: Test of DataSource connection was successful.
User Response: The DataSource can now be used by applications.

DSRA8030I: Successfully connected to DataSource, with {0} warnings.
Explanation: Test of DataSource connection was successful, but warnings were issued.
User Response: Review the DataSource configuration to fix the errors indicated by the warnings.

DSRA8040I: Failed to connect to the DataSource. Encountered {0}: {1}.
Explanation: Test of DataSource connection failed.
User Response: Review the DataSource configuration to fix the error that is occurring.

DSRA8041I: Failed to connect to the DataSource. Encountered SQLException with SQL State = {0}, Error Code = {1} : {2}.
Explanation: Test of DataSource connection failed.
User Response: Review the DataSource configuration to fix the error that is occurring.

DSRA8042I: The DataSource was not found. Be sure that the DataSource has been saved before attempting the Test Connection operation
Explanation: The DataSource being tested is not found in the master repository.
User Response: Save the configuration changes before attempting to test the connection

DSRA8050W: Unable to find the DataStoreHelper class specified: {0}
Explanation: Possible causes are the following: 1) The wrong DataStoreHelper class was specified. 2) The DataStoreHelper class name or package name was specified incorrectly. 3) The DataStoreHelper class is not included in the classpath. 4) The JDBC Provider used may not be supported in the WebSphere release being used.
User Response: Based on the corresponding cause, perform one of the following actions: 1) Switch to the appropriate DataStoreHelper class. 2) Correct the DataStoreHelper class or package name. 3) Correct the classpath. 4) Use a different JDBC Provider or different level of WebSphere.

DSRA8051W: Unable to instantiate DataStoreHelper: {0}
Explanation: DataStoreHelper implementation class cannot be an interface or abstract class.
User Response: Provide a class which fully implements the DataStoreHelper interface.

DSRA8052W: Unable to find constructor for DataStoreHelper: {0}
Explanation: DataStoreHelper class cannot be instantiated because it does not have a public constructor taking a Properties object as the parameter.
User Response: Create a public constructor for your DataStoreHelper taking a Properties object as its parameter.

DSRA8053W: Unable to access the constructor for DataStoreHelper: {0}
Explanation: WebSphere cannot access your DataStoreHelper constructor because it is not public.
User Response: Make your DataStoreHelper constructor a public method.

DSRA8054W: DataStoreHelper, ''{0}'', constructor issued following exception: {1}.
Explanation: The DataStoreHelper constructor issued an exception.
User Response: Verify that the Properties passed to the constructor are correct, and that the DataStoreHelper constructor is implemented correctly.

DSRA8055W: The class specified does not implement the DataStoreHelper interface: {0}
Explanation: Custom DataStoreHelper class does not implement DataStoreHelper.
User Response: Update the custom DataStoreHelper class to implement the DataStoreHelper interface.

DSRA8060W: No DataStoreHelper class was specified. The WebSphere GenericDataStoreHelper will be used.
Explanation: Since no DataStoreHelper class was specified, the GenericDataStoreHelper will be used.
User Response: Specify a DataStoreHelper class on the GUI if you do not want the GenericDataStoreHelper.

DSRA8065W: An error occurred executing the DataStoreHelper method {0}: {1}
Explanation: Unable to execute the specified DataStoreHelper method.
User Response: If using a custom DataStoreHelper, ensure that the code in the specified DataStoreHelper method is correct. Otherwise, check your DataSource configuration properties.

DSRA8100E: Unable to get a {0} from the DataSource.
Explanation: See the linkedException for more information.
User Response: See the linkedException for more information.

DSRA8101E: DataSource class cannot be used as one-phase: ClassCastException: {0}
Explanation: The 'enable2Phase' property may only be set to false if the DataSource class implements ConnectionPoolDataSource.
User Response: Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource.

DSRA8102E: DataSource class cannot be used as two-phase: ClassCastException: {0}
Explanation: The 'enable2Phase' property may only be set to true if the DataSource class implements XADataSource.
User Response: Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource.

DSRA8200W: DataSource Configuration: {0}
Explanation: This is a warning message that is displayed during DataSource configuration.
User Response: Read the warning message and take appropriate action to fix the problem, if necessary.

DSRA8201W: DataSource Configuration: {0} {1}
Explanation: This is a warning message that is displayed during DataSource configuration.
User Response: Read the warning message and take appropriate action to fix the problem, if necessary.

DSRA8202I: If sqlj option is to be used when deploying application, 'DB2 Universal JDBC Driver Provider' must be used, otherwise, application will not work properly.
Explanation: This is an information message is displayed during DataSource configuration if any of the DB2 providers is used except Universal.
User Response: If user has no intention to deploy code with sqlj option, then users should be ok

DSRA8203I: Database product name : {0}
Explanation: Database product name
User Response: The named Database product is now used by applications.

DSRA8204I: Database product version : {0}
Explanation: Database product version
User Response: The Database product version is now used by applications.

DSRA8205I: JDBC driver name : {0}
Explanation: The JDBC driver name.
User Response: The JDBC driver name is now used by applications.

DSRA8206I: JDBC driver version : {0}
Explanation: The JDBC driver version.
User Response: The JDBC driver version is now used by applications.

DSRA8207I: Method setReadOnly(false) is ignored. No Oracle transaction will be started.
Explanation: Oracle does not honor the setReadOnly method. A method setReadOnly(true) will not make the connection as readonly connection. In addition, setReadOnly(false) is ignored by Oracle and a transaction is implicitly started by Oracle. Therefore, WebSphere will not invoke the setReadOnly(false) method on Oracle in order to prevent unnecessary transaction to be started.
User Response: Inspect your application to make sure that your application does not depend on a transaction after the setReadOnly(false) method is called.

DSRA8208I: JDBC driver type : {0}
Explanation: The JDBC driver type.
User Response: The JDBC driver type is now used by applications.

DSRA8209I: Support for the {0} JDBC driver is deprecated and will be removed in a future WAS release. Please use the {1} JDBC driver instead.
Explanation: The specified JDBC driver will not be supported in a future release of WAS.
User Response: Switch to the recommended JDBC driver.

DSRA8210I: The database product name {0} may not exactly match with the database represented by the backend ID {1}.
Explanation: The database which is represented by the backend ID may not exactly match the data source connected to.
User Response: Inspect the database version between deployment and runtime datasource. If they are not the same, use a backend ID which matches the datasource to deploy the EJB, or change the datasource to match the backend ID.

DSRA8520W: Unable to send ''connectionErrorOccurred'' ConnectionEvent. ConnectionEvent = {0} Event Connection Handle = {1} ManagedConnection = {2} Error = {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA8600W: Error closing {0} {1}
Explanation: An error occurred while closing the specified JDBC object.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA8650W: Error closing a JDBC child wrapper, {0} {1}
Explanation: An error occurred while closing the specified child object.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA8660W: Error closing the ResultSet''s parent Statement, {0} {1}
Explanation: An error occurred while closing the Statement.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

DSRA8680W: Error clearing the SQLWarnings for Connection, {0} {1}
Explanation: Unable to clear the SQLWarnings for the Connection because an error occurred.
User Response: No user action is required. If the Connection is pooled the SQLWarnings may show up again where it is reused.

DSRA8710W: Error returning PreparedStatement to the cache; closing it instead.
Explanation: Unable to cache the PreparedStatement, will attempt to close it instead.
User Response: No user action is required.

DSRA8720W: Detected multithreaded access on {0}. Last used with thread id: {1} Current thread id: {2} Stack trace of current thread:{3}
Explanation: Application attempted to access Connection or its corresponding Statements, ResultSets, or MetaData from a different thread.
User Response: If multithreaded access was intended, configure the WebSphere DataSource property ''enableMultithreadedAccessDetection'' to false. Otherwise, adjust the application to avoid multithreaded access.

DSRA8730W: A DataSource name was not specified. The following identifier will be used instead for the Performance Monitoring Instrumentation, ''{0}''
Explanation: No DataSource name was specified, so a default value will be used.
User Response: Make sure you have filled in a value for the 'dataSourceName' property on your DataSource.

DSRA8750W: The JDBC 3.0 method {0} is not implemented on this JDBC Provider.
Explanation: The method being invoked is part of the JDBC 3.0 specification, and does not exist on the provider.
User Response: Ensure that your JDBC Provider supports the JDBC 3.0 specification, or do not use this method.

DSRA9000E: {0}: {1} Stack trace: {2}
Explanation: An Exception occurred, which will be converted to a SQLException.
User Response: Take appropriate action based on the exception text.

DSRA9001E: DataStoreAdapterException was created to map a SQLException.
Explanation: DataStoreAdapterException was created to map a SQLException.
User Response: None.

DSRA9002E: ResourceException with error code {0}: {1}
Explanation: ResourceException being converted to a SQLException.
User Response: Take appropriate action based on the exception text.

DSRA9010E: ''{0}'' is not supported on the WebSphere {1} implementation.
Explanation: The specified method is not supported by the WebSphere implementation.
User Response: Do not use the method.

DSRA9020E: The method invoked is not a JDBC method. WebSphere code must pass in a valid key to access this method.
Explanation: This method is provided only for internal use by WebSphere.
User Response: Do not call this method.

DSRA9110E: {0} is closed.
Explanation: Attempted to perform an operation on an object which is closed.
User Response: Retrieve a new instance of the object to perform the operation on.

DSRA9115E: Operation cannot be performed. Connection handle is INACTIVE and implicit reactivation is disabled.
Explanation: Attempted to perform an operation on an inactive Connection handle.
User Response: Enable the InactiveConnectionSupport property for the Resource Adapter.

DSRA9120E: WebSphere ''jdbcCall'' method should only be used for proprietary, non-JDBC methods.
Explanation: Attempted to invoke either a JDBC method or a disallowed proprietary method with the 'jdbcCall' method.
User Response: Call the method on the JDBC object directly.

DSRA9121E: Unable invoke method. Object is not a valid WebSphere JDBC Object.
Explanation: Using the WebSphere 'jdbcCall' method on non-JDBC objects is not allowed.
User Response: Use the WebSphere 'jdbcCall' method only with JDBC objects.

DSRA9122E: {0} does not wrap any objects of type {1}.
Explanation: The wrapper specified does not contain the wrapped object type specified.
User Response: Verify the wrapper and wrapped object parameters are specified correctly.

DSRA9123E: Invocation of the {0} method on the {1} class is not permitted via jdbcPass.
Explanation: WebSphere does not permit the specified method to be invoked via jdbcPass.
User Response: If the method does not alter the state of its native JDBC object parameters in any way, the customer may contact WebSphere support to request the method be added to the list of permitted methods for jdbcPass.

DSRA9210E: Dynamically setting the ''loginTimeout'' property on a WebSphere DataSource is not allowed.
Explanation: The loginTimeout may only be set when configuring a DataSource in the GUI.
User Response: Configure the loginTimeout value in the GUI instead of using 'setLoginTimeout'.

DSRA9250E: Operation {0} is not allowed during a global transaction for Shareable Connections.
Explanation: The user is not allowed to call setTypeMap, setReadOnly or setCatalog on Shareable Connections while a global transaction is active.
User Response: Do not call setTypeMap, setReadOnly or setCatalog on Shareable Connections in a global transaction, or switch to Unshareable Connections.

DSRA9300E: Changing the isolation level while in a global transaction is not allowed.
Explanation: Isolation level cannot be changed while in a global transaction.
User Response: Set the isolation level before beginning the global transaction or after it completes.

DSRA9310E: Application attempted to run outside of a transaction when in Containment mode, possibly due to transaction timeout.
Explanation: Application attempted to run outside of a transaction when in Containment mode, possibly due to transaction timeout.
User Response: Increase the transaction timeout or have the application re-run the transaction.

DSRA9312E: Application is not allowed to request begin of a local transaction when resolution control is CONTAINER.
Explanation: Application is not allowed to request begin of a local transaction when in Containment mode.
User Response: Switch the resolution control to APPLICATION if you need to explicitly begin a local transaction.

DSRA9316E: Cannot execute CCI Interactions outside of a transaction.
Explanation: It is an error to execute CCI Interactions when not in a Global or Local Transaction.
User Response: Begin a transaction before executing the Interaction.

DSRA9320E: Cannot explicitly begin a local transaction in JDBC.
Explanation: Explicit local transaction begin is not supported in JDBC.
User Response: Turn autoCommit off, which will cause an implicit local transaction begin when the Connection is used.

DSRA9330E: Cannot call setAutoCommit on a JDBC Connection being used by a CCI Connection.
Explanation: Connection.setAutoCommit is not allowed on any JDBC Connection being used by a CCI Connection.
User Response: Use the commit method on the CCI LocalTransaction whenever a commit is necessary.

DSRA9340E: Operation {0} is not allowed for SPI local transactions.
Explanation: The user is not allowed to call commit or rollback because the local transaction was started by the Container.
User Response: Rely on the Container to commit/rollback, or switch to APPLICATION mode.

DSRA9350E: Operation {0} is not allowed during a global transaction.
Explanation: The user is not allowed to call commit, rollback, setSavepoint or releaseSavepoint on the Connection while a global transaction is active.
User Response: Do not call commit, rollback, setSavepoint or releaseSavepoint on the Connection while in a global transaction.

DSRA9360E: Unable to perform the requested operation from the following transaction state: {0}.
Explanation: Performing operations while in the current transaction state is not allowed.
User Response: Get a new Connection for performing the operation.

DSRA9380E: A transaction is already active: {0}
Explanation: Cannot begin a local transaction because the connection is already enlisted in another transaction.
User Response: Commit or roll back the current transaction before beginning a new one.

DSRA9400E: Fatal error occurred during Connection reassociation: {0}
Explanation: The current Connection handle could not be reassociated.
User Response: Try getting a new Connection.

DSRA9410E: Handle reassociation is allowed only from the INACTIVE state. Current Connection state is {0}.
Explanation: Connection handles may only be reassociated from the INACTIVE state.
User Response: Close your current Connection handle and obtain a new one.

DSRA9420E: Connection cannot be reassociated because child objects are still open.
Explanation: Connection handles may only be reassociated if all child objects are closed.
User Response: Close your current Connection handle and obtain a new one.

DSRA9430E: Connection handle cannot be dissociated because it is currently in use.
Explanation: An operation is currently being performed on the Connection handle; it cannot be dissociated during the operation.
User Response: Wait until all operations on the handle have finished, then dissociate the handle.

DSRA9500E: Negative values are not allowed for fetch size.
Explanation: The fetch size may only be set to a non-negative value.
User Response: Choose a non-negative value for the fetch size.

DSRA9510W: Custom property preTestSQLString should not be empty if the pre-test connection option is selected.
Explanation: The custom property preTestSQLString may not be empty if the pre-test connection option is selected. If users choose to leave the preTestSQLString property unspecified, the performance will be worse.
User Response: Provide a valid SQL statement for preTestSQLString.

DSRA9520E: The passed-in Statement object cannot be set to null.
Explanation: The passed-in Statement object cannot be set to null. Set the Statement object to a non-null object.
User Response: Set the Statement object to a non-null object.

DSRA9530E: The object {0} is not cloneable.
Explanation: The object cannot be cloned.
User Response: Do not call the clone() method.

DSRA9531E: Attempt to perform getConnection is not allowed because Passkey is not valid.
Explanation: Invalid passkey was passed on the getConnection method.
User Response: Please contact WebSphere support.

DSRA9532E: Attempt to perform getConnection is not allowed for JDBC applications when the jmsOnePhaseOptimization datasource checkbox is checked.
Explanation: The getConnection method on this datasource can only be issued by JMS and CMP Applications.
User Response: Define another datasource for JDBC applications or set jmsOnePhaseOptimization property to false.

DSRA9533E: The jmsOnePhaseOptimization datasource checkbox can not be checked when XA-capable datasource is used.
Explanation: The jmsOnePhaseOptimization datasource checkbox can only be checked on non XA-capable datasources.
User Response: Use a non XA-capable datasource or uncheck the jmsOnePhaseOptimization datasource checkbox.

DSRA9534E: JMS failed to get an optimized connection. The jmsOnePhaseOptimization datasource checkbox must be checked.
Explanation: JMS is attempting to get an optimized connection. This action requires the jmsOnePhaseOptimization datasource checkbox to be checked.
User Response: Check the jmsOnePhaseOptimization checkbox on the datasource, or contact IBM technical support

DSRA9540E: The Connection cannot be null.
Explanation: The Connection cannot be null. Users have to pass a valid connection object.
User Response: Pass a valid connection object.