WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


DSRA

DSRA0010E: SQL State = {0}, Error Code = {1}
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.
DSRA0011E: Exception: {0}
Explanation A stack is provided. This stack is related to the problem reported above.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Try to fix the primary problem reported by the database software.
DSRA0082E: The Batch update count is null.
Explanation possible reasons: 1)database returned null, 2) WebSphere internal error.
Action 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 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
Action 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
Action 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.
Action 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.
Action 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.
Action examine your database logs and contact WebSphere support if no obvious reason was found.
DSRA0091I: Method {0} is not supported for this backend database
Explanation An internal error has occurred.
Action Contact support
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.
Explanation WebSphere has detected that the database started a transaction and will attempt to resolve the transaction as configured in the DataSource's custom properties.
Action None.
DSRA0093I: An implicit database transaction was detected . WebSphere tried to {0} the transaction but an error occurred {1}.
Explanation WebSphere has detected that the database started a transaction and will attempt to resolve the transaction as configured in the DataSource's custom properties. An error occured preventing the transaction from being resolved
Action Gather FFDC and any server logs. If the error is not related to a database outage or otherwise expected contact support.
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.
Explanation The database has started a transaction on the connection, WebSphere will rollback the transaction before returning the connection to the pool.
Action Evaluate the application code to determine what may be causing the implicit transaction. The application code may be able to prevent further implicit transactions explicity, or an explicit action to take may be configured for the DataSource.
DSRA0096I: An unexpected value was specified on DataSource:{0} custom property:{1}. The value specified is {2}. Expected values are {3}.
Explanation Usually this indicates a typo when configuring the DataSource custom property.
Action Ensure that one of the expected values is specified for the custom property. If there is a typo correct it and save the changes to the configuration.
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}.
Explanation Usually this indicates a typo when configuring the DataSource custom properties.
Action Update the new connection validation properties with the desired values then remove the deprecated properties.
DSRA0098I: A deprecated custom property has been specified on DataSource:{0}. The property {1} has been replaced by {2}.
Explanation Usually this indicates a typo when configuring the DataSource custom properties, but it can be a remnant of an older configuration file, or from an older wsadmin script. The new properties will take precedence over the deprecated names, however the old properties may be used at this time.
Action Update the new connection validation properties with the desired values then remove the deprecated properties.
DSRA0099E: An illegal attempt was made to load an unknown class {0}.
Explanation An illegal attempt was made to load a non-WebSphere class. Only known WebSphere classes are allowed to be loaded by internal WebSphere utilities.
Action Do not attempt to use internal WebSphere utilities to load non-WebSphere classes. Contact IBM WebSphere support if no such attempt was made.
DSRA0174W: Warning: GenericDataStoreHelper is being used.
Explanation GenericDataStoreHelper has been initialized
Action 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.
Action 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.
Action 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.
Action Exit transaction and or method boundary and retry logic with a new connection.
DSRA0250E: An exception was received by the Data Store Adapter. See original exception message: {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
DSRA0302E: XAException occurred. Error code is: {0}. Exception is: {1}
Explanation A two phase operation on the database resulted in an exception.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Position the iterator to a valid element before invoking the 'remove' operation.
DSRA1211E: The JNDI name of the delegate datasource mapped from the Base Proxy DataSource JNDI name {0} is null or an empty string.
Explanation The JNDI name of the delegate datasource cannot be null or an empty string
Action Set the JNDI name of the delegate datasource on the map for that specific Base Proxy DataSource
DSRA1212E: {0} is not configured as a delegate datasource for the Base Proxy DataSource {1}.
Explanation The delegate datasource JNDI names are configured in the custom property jndiNames using semicolor-delimited syntax. The JNDI name is not in the jndiNames custom property.
Action Check whether the custom property jndiNames is set to a right value or not. If so, set the JNDI name of the delegate datasource to a valid value.
DSRA1213E: Failed to look up datasource {0}.
Explanation The datasource lookup failed. The DataSource is probably not created or created in a wrong scope.
Action Make sure the datasource is created correctly.
DSRA3600E: Validation for command {0} failed for the following reason: {1}.
Explanation The command was not executed because it failed validation.
Action Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation.
DSRA3601E: {0} command failed for the following reason: {1}.
Explanation The command failed while being executed.
Action Evaluate the reason specified in the message to determine the problem.
DSRA3602E: Invalid {0} parameter value specified: {1}
Explanation The command was not executed because an invalid parameter value was specified.
Action Specify a valid value for the specified parameter and retry the command.
DSRA3603E: Unable to locate a JDBC provider template for provider name: {0}
Explanation The command was not executed because an invalid provider name was specified.
Action Specify a valid value for the provider name parameter and retry the operation.
DSRA3604E: Unable to locate a datasource template for provider name: {0}
Explanation The command was not executed because an invalid JDBC provider was specified.
Action Specify a valid value for the JDBC provider parameter and retry the operation.
DSRA3605E: The {0} step of the {1} command failed for the following reason: {2}
Explanation The command step failed during execution.
Action Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation.
DSRA3606E: Unable to update {0} resource property name of type {1} with value {2}.
Explanation The command was unable to update the specified resource property with the specified value.
Action Specify a valid value for the resource property and retry the operation.
DSRA3607E: The {0} step of the {1} command requires a value for the {2} resource property of type {3}.
Explanation The command step was not executed because a value was not specified for a required resource property.
Action This is usually a problem with the command parameters. Correct the problem, and retry the operation.
DSRA3608E: Invalid parameter value {0} for parameter {1} of type {2} for the {3} step of the {4} command.
Explanation The command step was not executed because an invalid parameter value was specified for a required resource property.
Action This problem usually occurs when the parameter value does not conform to the parameter type. Correct the problem, and retry the operation.
DSRA7000W: Mapped Exception could not be instantiated, reason: {0}
Explanation Could not map the exception, see the exception that occurred during the mapping.
Action 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.
Action Use DataDirectDataStoreHelper.class in your setup.
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.
Action 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
Action 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.
Action 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.
Action 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.
Action Do not use PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE since it cause a Serializable isolation level to be used.
DSRA7009I: DB2 JDBC logging is enabled, DB2 Universal driver is required to display any traces.
Explanation DB2 requires the use of DB2 Universal driver
Action 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
Action 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
Action 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.
Action 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.
Action 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.
Action 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
Action 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.
Action 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.
Action Examine the exception, fix the IO problem, and start the WebSphere Application Server again.
DSRA7018I: Database metadata access caused a non-stale connection exception. Normal execution is resumed. Exception is: {0}
Explanation An Exception occurred when trying to get/access the database metadata object.
Action verify that metadata is enabled on your backend database.
DSRA7019W: Oracle10gDataStoreHelper or a subclass of it must be used when configuring WebSphere DataSources to run using Oracle10g jdbc driver.
Explanation WebSphere DataSource is configured with the wrong DataStoreHelper.
Action Configure WebSphere DataSources with Oracle10gDataStoreHelper when running using Oracle10g jdbc driver.
DSRA7020E: There is no locking information available from the GenericDataStoreHelper
Explanation GenericDataStoreHelper does not know how to collect lock information.
Action Write or use your database specific DataStoreHelper.
DSRA7021I: DB2 Universal XA datasource custom property, retrieveMessagesFromServerOnGetMessage value is changed from true to false.
Explanation The DB2 Universal XA datasource custom property, retrieveMessagesFromServerOnGetMessage, was configured with a value of true. WebSphere has changed the value to false at runtime to avoid problems during exception processing.
Action To avoid this message, user must change the retrieveMessagesFromServerOnGetMessage value to false in the admin console and/or the configuration scripts or remove the property completely. This only applies to DB2 Universal XA datasources.
DSRA7022W: {0} is a deprecated API. Using the API will disable some WebSphere new features.
Explanation Deprecated API is being used.
Action Use non deprecated version of the API, see java docs and/or contact IBM technical support.
DSRA7024W: The propagateClientIdentityUsingTrustedContext datasource custom property takes precedence over reauthentication datasource custom property. Disabling reauthentication datasource custom property.
Explanation The reauthentication datasource custom property cannot be enabled when propagateClientIdentityUsingTrustedContext datasource custom property is enabled.
Action Disable propagateClientIdentityUsingTrustedContext or reauthentication datasource custom property.
DSRA7025W: The propagateClientIdentityUsingTrustedContext datasource custom property cannot be enabled when ThreadIdentity is enabled. Disabling propagateClientIdentityUsingTrustedContext datasource custom property.
Explanation The ThreadIdentity cannot be enabled when propagateClientIdentityUsingTrustedContext datasource custom property is enabled.
Action Disable propagateClientIdentityUsingTrustedContext datasource custom property or ThreadIdentity.
DSRA7026W: Connection Reauthentication cannot be enabled without overwriting the doConnectionSetupPerTransaction DataStoreHelper method to provide actual connection authentication implementation.
Explanation Reauthentication is enabled without providing the connection reauthentication implementation code in the DataStoreHelper class.
Action ovewrite the doConnectionSetupPerTransaction DataStoreHelper method and provide connection reauthentication implementation code or disable connection reauthentication can be done by one of the following: 1)uncheck WebSphere Application Server data source properties "enable database reauthentication" checkbox. 2) set reauthentication DataSource custom property to false.
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.
Action This is information on locks in your database. You might want to use the information to resolve deadlocks in your application.
DSRA7031W: The {0} datasource custom property is not supported when using the {1} DataStoreHelper. Disabling {0} datasource custom property.
Explanation The datasource custom property cannot be enabled in the current environment.
Action Disable datasource custom property.
DSRA7032W: The {0} datasource property can not be specified in the {1}. The {0} datasource property will be ignored.
Explanation The datasource property is invalid in this context.
Action No action is needed as the WebSphere runtime will ignore the property.
DSRA7600E: Cloudscape migration of database instance {0} to new database instance {1} failed, reason: {2}
Explanation Migration of Cloudscape instance failed, see the exception and the <dbinstance>_migration.log located in WASHOME/profiles/<profileName>/logs file for details.
Action fix migration problem as described by exception and migration log, delete the newly created database if it exists, and rerun the database migration tool (WASHOME/derby/bin/embedded/db2jMigrate.bat/sh) manually.
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}
Explanation Migration of Cloudscape instance was partially completed, see missing steps for more details on what needs to be redone manually
Action fix migration problem as described by migration log, create the missing parts. Note that there is no need to rerun the migration tool as the missing parts can be recreated manually.
DSRA7602I: Attempting to delete newly created Derby database {0}
Explanation An attempt is made to delete the newly created Derby database.
Action No action is required, this is just an information message.
DSRA7603E: Failed to delete newly created Derby database {0}
Explanation The attempt to delete the newly created Derby database has failed.
Action Delete the newly created Derby database manually
DSRA7604I: Done deleting newly created Derby database {0}
Explanation The Attempt to delete the newly created Derby database was successful.
Action no action is required, this is just an information message.
DSRA7605E: Internal error, providerType not found based on {0}, returning null
Explanation The providerType was not found
Action Please contact WebSphere support with the following data: {0}
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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Verify that the value specified for the property is valid.
DSRA8025I: Successfully connected to DataSource.
Explanation Test of DataSource connection was successful.
Action 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.
Action 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.
Action 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.
Action Review the DataSource configuration to fix the error that is occurring.
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.
Action 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.
Action 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.
Action 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.
Action Make your DataStoreHelper constructor a public method.
DSRA8054W: DataStoreHelper, ''{0}'', constructor issued following exception: {1}.
Explanation The DataStoreHelper constructor issued an exception.
Action 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.
Action Update the custom DataStoreHelper class to implement the DataStoreHelper interface.
DSRA8065W: An error occurred executing the DataStoreHelper method {0}: {1}
Explanation Unable to execute the specified DataStoreHelper method.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Read the warning message and take appropriate action to fix the problem, if necessary.
DSRA8203I: Database product name : {0}
Explanation Database product name
Action The named Database product is now used by applications.
DSRA8204I: Database product version : {0}
Explanation Database product version
Action The Database product version is now used by applications.
DSRA8205I: JDBC driver name : {0}
Explanation The JDBC driver name.
Action The JDBC driver name is now used by applications.
DSRA8206I: JDBC driver version : {0}
Explanation The JDBC driver version.
Action 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.
Action 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.
Action The JDBC driver type is now used by applications.
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.
Explanation The specified JDBC driver might not be officially certified in future releases of WebSphere Application Server.
Action Continue using the JDBC driver or 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.
Action 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.
DSRA8211I: Backend id checking is disabled.
Explanation Backend id checking is disabled so no validation of backend id will be done.
Action Set disableBackendIdChecking DataSource custom property to false or remove property to enable backend id checking.
DSRA8212I: DataStoreHelper name is: {0}.
Explanation The DataStoreHelper name.
Action none, this is an information message.
DSRA8213W: JDBC provider, {0}, is no longer supported by WebSphere Application Server. Applications should use {1}.
Explanation Application is using a JDBC provider that is no longer supported by WebSphere Application Server.
Action Use a different JDBC provider as stated in the message.
DSRA8600W: Error closing {0}
{1}
Explanation An error occurred while closing the specified JDBC object.
Action 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.
Action 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.
Action 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/.
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.
Action If multithreaded access was intended, configure the WebSphere DataSource property 'enableMultithreadedAccessDetection' to false. Otherwise, adjust the application to avoid multithreaded access.
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.
Action Ensure that your JDBC Provider supports the JDBC 3.0 specification, or do not use this method.
DSRA9001E: DataStoreAdapterException was created to map a SQLException.
Explanation DataStoreAdapterException was created to map a SQLException.
Action None.
DSRA9010E: ''{0}'' is not supported on the WebSphere {1} implementation.
Explanation The specified method is not supported by the WebSphere implementation.
Action 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.
Action Do not call this method.
DSRA9110E: {0} is closed.
Explanation Attempted to perform an operation on an object which is closed.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
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.
Action Do not call setTypeMap, setReadOnly or setCatalog on Shareable Connections in a global transaction, or switch to Unshareable Connections.
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.
Action 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.
Action Get a new Connection for performing the operation.
DSRA9400E: Fatal error occurred during Connection reassociation: {0}
Explanation The current Connection handle could not be reassociated.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Set the Statement object to a non-null object.
DSRA9530E: The object {0} is not cloneable.
Explanation The object cannot be cloned.
Action 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.
Action 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.
Action Define another datasource for JDBC applications or set jmsOnePhaseOptimization property to false.
DSRA9533E: The jmsOnePhaseOptimization datasource checkbox cannot be checked when XA-capable datasource is used.
Explanation The jmsOnePhaseOptimization datasource checkbox can only be checked on non XA-capable datasources.
Action 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.
Action Check the jmsOnePhaseOptimization checkbox on the datasource, or contact IBM technical support
DSRA9537W: The {0} DataStoreHelper method is not called. Reason: {1}, Possible case: {2}
Explanation The DataStoreHelper method specified in the exception is not called.
Action Examine the reason and possible cause. Call WebSphere support for help if issue is not resolved after examining the reason and cause.
DSRA9540E: The Connection cannot be null.
Explanation The Connection cannot be null. Users have to pass a valid connection object.
Action Pass a valid connection object.
DSRA9600W: The application server received an exception when posting data to CMX. The exception is: {0}.
Explanation The application server received an exception when attempting to post data to CMX. This might mean that the data is not posted.
Action Examine the exception and the possible cause. Visit the WebSphere support website for troubleshooting help if you cannot resolve the issue after examining the exception.
DSRA9601W: The application server failed to register for CMX notification. The exception is: {0}
Explanation The application server received an exception when attempting to register for CMX notification.
Action Examine the exception. Visit the WebSphere support website for troubleshooting help if you cannot resolve the issue after examining the exception.
DSRA9602W: The application server received an exception when calling isMonitoringEnabled. Disabling CMX End-to-End monitoring feature. The exception is: {0}.
Explanation The application server received an exception when attempting to check if CMX monitoring is enabled.
Action Examine the exception and the possible cause, fix the problem, and restart the application server. Visit the WebSphere support website for troubleshooting help if you cannot resolve the issue after examining the exception.
Reference topic    

Terms of Use | Feedback

Last updated: May 3, 2010 12:31:27 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/IBMDataStoreAdapterNLS.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)