DSRA

DSRA0010E: SQL State = {0}, Error Code = {1}
DSRA0015W: A warning was reported by a JDBC resource. JDBC resource: {0}, SQLState: {1}, Error Code: {2}, Warning: {3}.
DSRA0020E: {0} could not be found: {1}
DSRA0022E: The DataSource implementation class is null.
DSRA0023E: The DataSource implementation class "{0}" could not be found.
DSRA0024E: The DataSource could not be created from implementation class "{0}". The exception is: {1}.
DSRA0025E: Class {0} does not implement {1}.
DSRA0027W: An exception occurred while the application server was determining the class loader isolation for the resource with JNDI name {1}. Exception: {0}.
DSRA0030E: Data Store Adapter internal error occurred. Please contact WebSphere support with the following data: {0} {1} {2}
DSRA0035W: DataStore Adapter internal error occurred. Please contact WebSphere support with the following information: {0} {1}
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}
DSRA0060W: WebSphere internal warning occurred. Please contact WebSphere support with the following data: {0} {1} {2}
DSRA0070E: {0} is closed. Unable to perform: {1}
DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: {0}.
DSRA0082E: The Batch update count is null.
DSRA0083E: one of the batched updates failed which caused the database to return -3 in the batch update count.
DSRA0084E: The operation was successful, however, the number of rows updated is not known. The database returned -2 in the batch update count.
DSRA0085E: The operation was successful, however, the number of rows updated was 0.
DSRA0086E: An operation resulted in an Exception. Operation is: {0}. Exception is: {1}. Possible cause {2}
DSRA0087E: {0} operation was not successful because {1}
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.
DSRA0096I: An unexpected value was specified on DataSource:{0} custom property:{1}. The value specified is {2}. Expected values are {3}.
DSRA0097W: DataSource:{0} has specified custom properties {1} and {2}. {1} is deprecated and is replaced by {2}. The following values will be used {3}={4} {5}={6} {7}={8}.
DSRA0098I: A deprecated custom property has been specified on DataSource:{0}. The property {1} has been replaced by {2}.
DSRA0099E: An illegal attempt was made to load an unknown class {0}.
DSRA0101W: A removed custom property has been specified on DataSource:{0}. The property {1} has been replaced by {2}.
DSRA0110E: {0} is not available in {1}.
DSRA0174W: Warning: GenericDataStoreHelper is being used.
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.
DSRA0244E: The connection did not validate within the designated interval.
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
DSRA0401W: Datasource {0}: does not support tight branch coupling xa_start option
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
DSRA1000E: The WebSphere Relational Resource Adapter does not support message inflow.
DSRA1100W: An error occurred while resetting a connection to its default state. The connection will be destroyed. {0}
DSRA1101W: An error occurred while destroying a connection. {0}
DSRA1102W: An error occurred while validating connections after detection of a fatal connection error. All connections will be destroyed. {0}
DSRA1110E: Unable to establish a connection. The maximum number of connections for the connection pool, {0}, is already open.
DSRA1120E: Application did not explicitly close all handles to this Connection. Connection cannot be pooled.
DSRA1130E: A fatal connection error occurred on another connection while this connection was active. This connection cannot be reset to a usable state.
DSRA1200E: The iteration does not contain any more elements. Element {0} does not exist.
DSRA1210E: The iterator is not positioned on any element. There is nothing to remove.
DSRA1211E: The JNDI name of the delegate datasource mapped from the Base Proxy DataSource JNDI name {0} is null or an empty string.
DSRA1212E: {0} is not configured as a delegate datasource for the Base Proxy DataSource {1}.
DSRA1213E: Failed to look up datasource {0}.
DSRA1300E: Feature is not implemented: {0}
DSRA1301E: The Relational Resource Adapter was notified of a connection error.
DSRA3600E: Validation for command {0} failed for the following reason: {1}.
DSRA3601E: {0} command failed for the following reason: {1}.
DSRA3602E: Invalid {0} parameter value specified: {1}
DSRA3603E: Unable to locate a JDBC provider template for provider name: {0}
DSRA3604E: Unable to locate a datasource template for provider name: {0}
DSRA3605E: The {0} step of the {1} command failed for the following reason: {2}
DSRA3606E: Unable to update {0} resource property name of type {1} with value {2}.
DSRA3607E: The {0} step of the {1} command requires a value for the {2} resource property of type {3}.
DSRA3608E: Invalid parameter value {0} for parameter {1} of type {2} for the {3} step of the {4} command.
DSRA3610E: The target object submitted to command {0} is not a {1}.
DSRA7000W: Mapped Exception could not be instantiated, reason: {0}
DSRA7001E: This method must be called from DataDirect DataStoreHelper.
DSRA7003E: A java.util.Properties object must be specified which includes all of the necessary connection information.
DSRA7004E: showLockInfo method does not support {0} platform.
DSRA7005E: showLockInfo(): could not execute db2 command {0}, reason: {1}
DSRA7006I: Lock information should be available in file: {0}
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.
DSRA7009I: DB2 JDBC logging is enabled, DB2 Universal driver is required to display any traces.
DSRA7010E: trace file specified {0} does not exist, an exception will be thrown from the database if problem is not corrected.
DSRA7011W: A Oracle JDBC provider property (TransactionBranchesLooselyCoupled) has been set.
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
DSRA7013E: Wrong configuration : JDBC driver does not support setDriverType
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}
DSRA7019W: Oracle10gDataStoreHelper or a subclass of it must be used when configuring WebSphere DataSources to run using Oracle10g jdbc driver.
DSRA7020E: There is no locking information available from the GenericDataStoreHelper
DSRA7021I: DB2 Universal XA datasource custom property, retrieveMessagesFromServerOnGetMessage value is changed from true to false.
DSRA7022W: {0} is a deprecated API. Using the API will disable some WebSphere new features.
DSRA7024I: The reauthentication custom property for the data source cannot be enabled if TrustedConnectionMapping login configuration is used.
DSRA7025E: The reauthentication custom property for the data source cannot be enabled when you are using the TrustedConnectionMapping login configuration.
DSRA7026W: Connection Reauthentication cannot be enabled without overwriting the doConnectionSetupPerTransaction DataStoreHelper method to provide actual connection authentication implementation.
DSRA7027W: A failure occurred during a getPooledConnection method that was using Kerberos credentials.
DSRA7028E: You cannot use the TrustedConnectionMapping login configuration when the ThreadIdentity property is enabled.
DSRA7029W: The propagateClientIdentityUsingTrustedContext custom property for the data source is no longer used, value will be ignored.
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}
DSRA7031W: The {0} datasource custom property is not supported when using the {1} DataStoreHelper. Disabling {0} datasource custom property.
DSRA7032W: The {0} datasource property can not be specified in the {1}. The {0} datasource property will be ignored.
DSRA7033E: You cannot enable the useTrustedContextWithAuthentication custom property for the data source without overwriting the getPasswordForUseWithTrustedContextWithAuthentication DataStoreHelper.
DSRA7034I: Enabling the useTrustedContextWithAuthentication custom property for the data source requires that you override the getPasswordForUseWithTrustedContextWithAuthentication DataStoreHelper method to provide the password that is required to switch trusted context identity.
DSRA7035W: The {0} method is not found on the {1} class.
DSRA7036W: The {0} method did not complete successfully. The reason is: {1}.
DSRA7037W: The JDBC Driver that is configured with the data source for the application server does not support Oracle connection pooling.
DSRA7038W: The application server was not able to remove existing Oracle connection cache with name: {0}. Exception: {1}
DSRA7039W: The application server was not able to check for the existence of the Oracle connection cache with the name: {0}. The exception is: {1}
DSRA7040I: The application server has disabled internal connection pooling.
DSRA7041W: You must use the {0} class or a subclass of that data store helper when you configure a data source to use this JDBC driver: {1}
DSRA7042W: Oracle does not support the use of version {0} of their JDBC driver with the version of the Java runtime environment that is used by the application server.
DSRA7600E: Cloudscape migration of database instance {0} to new database instance {1} failed, reason: {2}
DSRA7601W: Cloudscape migration of database instance {0} to new database instance {1} was partially completed. Last step to complete successfully is: {2}. Missing steps are {3}
DSRA7602I: Attempting to delete newly created Derby database {0}
DSRA7603E: Failed to delete newly created Derby database {0}
DSRA7604I: Done deleting newly created Derby database {0}
DSRA7605E: Internal error, providerType not found based on {0}, returning null
DSRA7606I: The name of the new Derby database that will be created is {0}
DSRA8000E: Java archive (JAR) or compressed files do not exist in the path or the required access is not allowed. Path: {0}
DSRA8001E: Unable to read JDBC provider jar or zip file: {0}
DSRA8010W: Unable to read setter methods from DataSource class. Encountered {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}
DSRA8023W: {0} is not a valid option for {1}. {1} will default to {2}.
DSRA8024W: {0}={1} is not compatible with {2}={3}. The {2} attribute will default to {4}.
DSRA8025I: Successfully connected to DataSource.
DSRA8026W: The {0} property of the data source class is incorrect.
DSRA8027W: The {0} property of the data source class is incorrect. Exception: {1}
DSRA8028W: The Application Server was not able to configure DB2 client reroute persistence on the data source when the JDBC driver type 2 is used. The Application Server is ignoring the settings for persistence of DB2 client reroute information.
DSRA8030I: Successfully connected to DataSource, with {0} warnings.
DSRA8032W: The unbind method of JNDI name ''{0}'' failed: Exception: {1}
DSRA8033W: The lookup method of JNDI name ''{0}'' failed: Exception: {1}
DSRA8034W: The bind method of JNDI name ''{0}'' failed: Exception: {1}
DSRA8035W: The creation of a DB2ClientRerouteServerList failed: Exception: {0}
DSRA8040I: Failed to connect to the DataSource. Encountered {0}: {1}.
DSRA8041I: Failed to connect to the DataSource. Encountered SQLException with SQL State = {0}, Error Code = {1} : {2}.
DSRA8043W: The database connection has been rerouted.
DSRA8050W: Unable to find the DataStoreHelper class specified: {0}
DSRA8051W: Unable to instantiate DataStoreHelper: {0}
DSRA8052W: Unable to find constructor for DataStoreHelper: {0}
DSRA8053W: Unable to access the constructor for DataStoreHelper: {0}
DSRA8054W: DataStoreHelper, ''{0}'', constructor issued following exception: {1}.
DSRA8055W: The class specified does not implement the DataStoreHelper interface: {0}
DSRA8065W: An error occurred executing the DataStoreHelper method {0}: {1}
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}
DSRA8150E: The data source custom property {0} contains an exception class that cannot be loaded: {1}
DSRA8160E: The application server is not able to parse data source custom property {0} near {1}. The full property value is {2}. Refer to the chained exception for more information.
DSRA8200W: DataSource Configuration: {0}
DSRA8201W: DataSource Configuration: {0} {1}
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.
DSRA8208I: JDBC driver type : {0}
DSRA8209I: WebSphere Application Server support for the {0} JDBC driver is deprecated. Consequently, it might not be officially certified with future WebSphere Application Server releases. If possible, consider using the {1} JDBC driver instead.
DSRA8210I: The database product name {0} may not exactly match with the database represented by the backend ID {1}.
DSRA8211I: Backend id checking is disabled.
DSRA8212I: DataStoreHelper name is: {0}.
DSRA8213W: JDBC provider, {0}, is no longer supported by WebSphere Application Server. Applications should use {1}.
DSRA8214W: Unable to configure client reroute on the data source class {0}. Exception: {1}.
DSRA8215W: Unable to configure client reroute server list JNDI context on the data source class {0}. Exception: {1}.
DSRA8216W: Unable to configure client reroute server list JNDI name on the data source class {0}. Exception: {1}.
DSRA8217W: Unable to configure client reroute on the data source class {0}. clientRerouteAlternateServerName and clientRerouteAlternatePortNumber data source custom property must be set and must have equal number of entries.
DSRA8218I: JDBC driver specification level : {0}
DSRA8220W: Enablement of {0} requires a JDBC driver compliant with JDBC specification level {1} or higher.
DSRA8221I: Test connection cannot use Kerberos authentication, because some security information is only available to a resource at run time. The application server will use the normal authentication to connect to the data source.
DSRA8222E: The application server was not able to create a trusted connection to the data source.
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}
DSRA8650W: Error closing a JDBC child wrapper, {0} {1}
DSRA8660W: Error closing the ResultSet''s parent Statement, {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.
DSRA8780I: By default, the connection property, {0}, is matched for shareable connections based on the current state of the connection rather than the original connection request. You may use the data source custom property, {1}, to configure this behavior.
DSRA9001E: DataStoreAdapterException was created to map a SQLException.
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.
DSRA9115E: Operation cannot be performed. Connection handle is INACTIVE and implicit reactivation is disabled.
DSRA9120E: WebSphere 'jdbcCall' method should only be used for proprietary, non-JDBC methods. The 'jdbcCall' method can be used to invoke the proprietary, non-standard extensions to JDBC. It should not be used to invoke the JDBC API methods.
DSRA9121E: Unable invoke method. Object is not a valid WebSphere JDBC Object.
DSRA9122E: {0} does not wrap any objects of type {1}.
DSRA9123E: Invocation of the {0} method on the {1} class is not permitted via jdbcPass.
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.
DSRA9510W: Custom property preTestSQLString should not be empty if the pre-test connection option is selected.
DSRA9520E: The passed-in Statement object cannot be set to null.
DSRA9530E: The object {0} is not cloneable.
DSRA9531E: Attempt to perform getConnection is not allowed because Passkey is not valid.
DSRA9532E: Attempt to perform getConnection is not allowed for JDBC applications when the jmsOnePhaseOptimization datasource checkbox is checked.
DSRA9533E: The jmsOnePhaseOptimization datasource checkbox cannot be checked when XA-capable datasource is used.
DSRA9534E: JMS failed to get an optimized connection. The jmsOnePhaseOptimization datasource checkbox must be checked.
DSRA9538W: The jmsOnePhaseOptimization custom property for data sources takes precedence over the nonTransactionalDataSource custom property for data sources. The Application Server will disable the nonTransactionalDataSource custom property on the data source at run time.
DSRA9539W: The nonTransactionalDataSource custom property for data sources cannot be enabled when connecting to IBM DB2 on z/OS using the DB2 Universal JDBC Driver Type 2.
DSRA9540E: The Connection cannot be null.
DSRA9541E: The JDBC Driver that is configured with the data source for the Application Server does not support Trusted Connection.
DSRA9542W: The JDBC Driver that is configured with the data source for the Application Server does not support the extending data source properties feature. The Application Server will not honor the extended data source properties.
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.
DSRA9544E: You must use the get/use/close connection pattern if you are using the extending data source properties feature and the optimizeDB2ForGetUseClose data source custom property is enabled.
DSRA9545W: Informix data servers that us the Java Common Client (JCC) Driver only support a driverType data source custom property with a value of 4. The driverType value has been changed to 4 to continue the operation successfully.
DSRA9546W: The application server could not lookup the {0} service. The exception is: {1}.
DSRA9547W: The application server could not add the {0} service. The exception is: {1}.
DSRA9548I: The application server could not find the following service: {0}.
DSRA9600W: The application server received an exception when posting data to CMX. The exception is: {0}.
DSRA9601W: The application server failed to register for CMX notification. The exception is: {0}
DSRA9602W: The application server received an exception when calling isMonitoringEnabled. Disabling CMX End-to-End monitoring feature. The exception is: {0}.
DSRA9603W: The application server received an exception while trying to change the value of the connection pool property {0}. The exception is: {1}.
DSRA9900I: The application server cannot automatically clean up resource type {0} because the JDBC driver does not comply with JDBC {1}.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.rsadapter.resources.IBMDataStoreAdapterNLS.dita
File name: com.ibm.ws.rsadapter.resources.IBMDataStoreAdapterNLS.html