com.ibm.ws.rsadapter.resources.IBMDataStoreAdapterNLS

DSRA0010E: SQL State = {0}, Error Code = {1}
DSRA0030E: Data Store Adapter internal error occurred. Please contact WebSphere support with the following data: {0} {1} {2}
DSRA0040E: WebSphere internal error occurred. Please contact WebSphere support with the following data: {0} {1} {2}
DSRA0050W: Data Store Adapter internal warning occurred. Please contact WebSphere support with the following data: {0} {1} {2}
DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: {0}.
DSRA0086E: An operation resulted in an Exception. Operation is: {0}. Exception is: {1}. Possible cause {2}
DSRA0091I: Method {0} is not supported for this backend database
DSRA0092I: An implicit database transaction was detected. WebSphere will {0} the transaction. This message will be logged once for each DataSource. Subsequent implicit transactions will be resolved automatically.
DSRA0093I: An implicit database transaction was detected . WebSphere tried to {0} the transaction but an error occurred {1}.
DSRA0095I: A database transaction that is not tracked by WebSphere is found, attemping to rollback before cleaning connection. This message will be logged once for each DataSource. Subsequent implicit transactions will be resolved automatically.
DSRA0180W: Exception detected during ManagedConnection.destroy(). The exception is: {0}.
DSRA0230E: Attempt to perform operation {0} is not allowed because transaction state is {1}.
DSRA0240E: Invalid Connection. Connection Pool is being purged.
DSRA0250E: An exception was received by the Data Store Adapter. See original exception message: {0}.
DSRA0302E: XAException occurred. Error code is: {0}. Exception is: {1}
DSRA0304E: XAException occurred. XAException contents and details are: {0}.
DSRA0310E: Xids do not match. XAResource.start: {0} XAResource.{1}: {2}
DSRA0330E: The application server is delaying the {0} request, because the amount of time from the last stale connection, {1} milliseconds, is within the oracleRACXARecoveryDelay value, which is {2} milliseconds.
DSRA0400W: Datasource {0}: does not support tight branch coupling
DSRA0402W: Datasource {0}: the database version does not support tight branch coupling
DSRA0403W: Datasource {0}: does not support tight branch coupling as the DB2 JCC driver is at an incorrect level
DSRA1120E: Application did not explicitly close all handles to this Connection. Connection cannot be pooled.
DSRA1300E: Feature is not implemented: {0}
DSRA4000E: A valid JDBC driver implementation class was not found for the jdbcDriver {0} using the library {1}.
DSRA4001E: A valid JDBC driver implementation class was not found in the nested library used by jdbcDriver {0}.
DSRA4003E: A valid jdbcDriver element could not be found for the dataSource {0}.
DSRA4004E: Unable to execute onConnect SQL command "{0}" on connection obtained from dataSource {1}. Refer to the cause exception for more information.
DSRA7010E: trace file specified {0} does not exist, an exception will be thrown from the database if problem is not corrected.
DSRA7014I: The DB2 Universal JDBC driver runs in a RRS environment
DSRA7015E: DB2 does not support driver type 2 with DB2XADataSource under DB2 for z/OS
DSRA7017I: Logging to file {0} cannot occur because of IOException {1}
DSRA7018I: Database metadata access caused a non-stale connection exception. Normal execution is resumed. Exception is: {0}
DSRA8011E: No setter method for property ''{0}''.
DSRA8020E: Warning: The property ''{1}'' does not exist on the DataSource class {0}.
DSRA8021W: Warning: error setting ''{0}''{1}: {2}
DSRA8100E: Unable to get a {0} from the DataSource.
DSRA8101E: DataSource class cannot be used as one-phase: ClassCastException: {0}
DSRA8102E: DataSource class cannot be used as two-phase: ClassCastException: {0}
DSRA8203I: Database product name : {0}
DSRA8204I: Database product version : {0}
DSRA8205I: JDBC driver name : {0}
DSRA8206I: JDBC driver version : {0}
DSRA8207I: Method setReadOnly(false) is ignored. No Oracle transaction will be started.
DSRA8213W: JDBC provider, {0}, is no longer supported by WebSphere Application Server. Applications should use {1}.
DSRA8230W: The application server is unable to determine if a transaction should be resolved because data source custom property {0} is configured but data source custom property {1} is not configured.
DSRA8600W: Error closing {0} {1}
DSRA8720W: Detected multithreaded access on {0}. Last used with thread id: {1} Current thread id: {2} Stack trace of current thread:{3}
DSRA8750W: The JDBC 3.0 method {0} is not implemented on this JDBC Provider.
DSRA8760W: Unable to locate the implementation for vendor interface {0} after switching to another pooled connection. The unwrapped connection handle is no longer usable as that interface. The new connection implementation class is: {1}
DSRA8770I: By default, the connection property, {0}, is matched for shareable connections based on the original connection request rather than the current state of the connection. You may use the data source custom property, {1}, to configure this behavior.
DSRA9010E: ''{0}'' is not supported on the WebSphere {1} implementation.
DSRA9020E: The method invoked is not a JDBC method. WebSphere code must pass in a valid key to access this method.
DSRA9110E: {0} is closed.
DSRA9122E: {0} does not wrap any objects of type {1}.
DSRA9130E: Operation is not permitted by the application server: {0}
DSRA9250E: Operation {0} is not allowed during a global transaction for Shareable Connections.
DSRA9350E: Operation {0} is not allowed during a global transaction.
DSRA9360E: Unable to perform the requested operation from the following transaction state: {0}.
DSRA9400E: Fatal error occurred during Connection reassociation: {0}
DSRA9410E: Handle reassociation is allowed only from the INACTIVE state. Current Connection state is {0}.
DSRA9420E: Connection cannot be reassociated because child objects are still open.
DSRA9430E: Connection handle cannot be dissociated because it is currently in use.
DSRA9500E: Negative values are not allowed for fetch size.
DSRA9543W: The Application Server does not support Kerberos against the backend database that is being used. No user name and password will be used to get a connection.