DSRA

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 and is resolved with the {0} operation. This message is logged once for each DataSource. Subsequent implicit transactions are 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 Liberty is found. Attempting to roll back before cleaning up the connection. This message is logged once for each DataSource. Subsequent implicit transactions are 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}
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}
DSRA1301E: A connection error that requires removing the connection from the connection pool was identified by the application.
DSRA4000E: No implementations of {0} are found for {1} with library {2}. The name or location of JDBC driver JAR files might be incorrect or inaccessible. Searched in: {3}. Searched under packages: {4}.
DSRA4001E: No implementations of {0} are found for {1}. Searched in: {2}. The name or location of JDBC driver JAR files might be incorrect or inaccessible. Searched under packages: {3}.
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.
DSRA4005E: The server does not support the loginTimeout property that is specified in the URL or in the properties of the {0} DataSource.
DSRA4006E: DataSource {0} is unable to connect to the database because {1} returned a null connection for the URL beginning with {2}. This indicates the JDBC driver is in violation of the JDBC specification.
DSRA4008E: The JDBC driver does not support an isolation level of TRANSACTION_NONE, which is configured on data source {0}.
DSRA4009E: The data source {0} cannot be configured with an isolation level of TRANSACTION_NONE and transactional=true.
DSRA4010E: Auto commit is required when using an isolation level of TRANSACTION_NONE, which is configured on data source {0}.
DSRA4011E: The JDBC driver does not support switching to an isolation level of TRANSACTION_NONE on data source {0}.
DSRA4012I: When using Oracle UCP the following data source properties are ignored: {0}.
DSRA4013I: The connection manager properties are not valid. When using Oracle UCP, the following connection manager properties are valid: {0}.
DSRA4014E: The type java.sql.Driver was specified for data source {0} but no URL attribute was specified.
DSRA4015E: The {0} data source was configured with the {1} type, which is not supported by Oracle UCP. Instead, use the XADataSource or DataSource type.
DSRA4016E: The JDBC driver does not support setting the {0} value on the {1} datasource property.
DSRA7000W: The {0} class, which is needed for SQLException identification or replacement, cannot be instantiated. Reason: {1}
DSRA7003E: Connection information must be provided in the java.util.Properties parameter of the showLockInfo method.
DSRA7005E: The showLockInfo method could not execute the {0} DB2 command. Reason: {1}
DSRA7006I: Lock information is available in the file: {0}
DSRA7010E: trace file specified {0} does not exist, an exception is thrown from the database if the 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}
DSRA7020E: The GenericDataStoreHelper does not provide lock information.
DSRA7043W: A default value was used for the {0} system property because of the following parsing error: {1}
DSRA7044I: Oracle JDBC driver tracing was enabled by the {0} system property. One or more of the [{1}] system properties that are required to separate Oracle log files are missing.
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}
DSRA8066E: The ''{0}'' invalid value was specified for the ''as'' attribute on the identifyException element. Recommended values are: {1}
DSRA8067E: At least one of the 'errorCode' or 'sqlState' attributes must be specified on the identifyException element.
DSRA8068E: DataSource {0} cannot configure both the sqlState and errorCode attributes on the same identifyException element when the replaceExceptions attribute is configured to the ''true'' value.
DSRA8069E: DataSource {0} is unable to initialize DataStoreHelper implementation {1} due to an error: {2}
DSRA8100E: Unable to get a {0} from the DataSource.
DSRA8101E: DataSource class cannot be used as one-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 is 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.
DSRA8790W: The beginRequest and endRequest methods must only be used by connection managers. The JDBC specification does not account for multiple connection managers that can manage a connection. Usage of beginRequest and endRequest by other connection managers is suppressed when connection management is provided by the application server. The following stack indicates the code path on which the beginRequest or endRequest operation was invoked: {0}.
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.
DSRA9120E: The WSCallHelper.jdbcCall method does not support invocation of the {0} method.
DSRA9121E: Unable invoke method. {0} is not a Liberty JDBC wrapper.
DSRA9122E: {0} does not wrap any objects of type {1}.
DSRA9123E: Invocation of the {0} method on the {1} class is not permitted by the WSCallHelper.jdbcPass method.
DSRA9124E: Cannot unwrap object to {0} because {0} is not an interface class.
DSRA9125W: A native connection that was returned by the WSCallHelper.getNativeConnection method is vulnerable to corruption by the application. This vulnerability impacts all current and future use of the connection pool.
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 are used to get a connection.
DSRA9549E: Using the IBM Java 8 SDK with an Oracle database is not supported. The Oracle JDBC driver only supports Kerberos authentication using the default security APIs available in OpenJDK, OpenJ9, or other similar SDKs.