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. |
Explanation | A warning was reported by a JDBC resource. There may be other warnings chained to this warning. |
Action | Review all warnings. Note the SQLState and Error Code of each warning and refer to the documentation of the JDBC driver to resolve the issue. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A valid class name for a data source implementation is required when creating a JDBC provider. |
Action | Enter a valid class name for a data source implementation and attempt the operation again. |
Explanation | The Application Server was not able to locate the class for the data source implementation that you specified. |
Action | Verify that the class name for the data source is correct and that it is in your class path. |
Explanation | An error occurred instantiating the data source. |
Action | Verify the data source class has a public constructor that is taking no parameters. |
Explanation | The object cannot be cast to the interface that is specified, because the object does not implement it. |
Action | Verify that that the implementation class is correct and that it is provided. |
Explanation | An exception occurred when the application server checked the resource to determine if it was configured for class loader isolation. The code will proceed as if class loader isolation is not configured. |
Action | Refer to the exception message to help determine the cause of the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | An error occurred in the WebSphere code. |
Action | Collect all trace and system logs, along with a description of the operation that you were attempting. Visit the IBM support Web site for information on problem determination. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | The Application Server attempted to perform an operation on an object that is closed. |
Action | Retrieve a new instance of the object and attempt the operation again. |
Explanation | The database backend generated an exception that was caught by the Data Store Adapter. |
Action | Refer to the error text reported by the database software for possible sources of the error. |
Explanation | The possible reasons are that the database returned a null value, or this is an internal error. |
Action | If you think the database might have returned a null value, do not use the batch update feature, switch to a database that supports batch update, or visit the support Web site for the database vendor. If you suspect the problem is related to an internal error, use the following trace settings (RRA=all=enabled and PMGR=all=enabled) and the FFDC files to determine the source of the error. Visit the IBM support Web site for information on problem determination. |
Explanation | One of the batched updates did not complete successfully and caused the database to return -3 in the batch update count. -3 is returned if the database continues to run the batched updates after one fails. |
Action | Examine the database logs for possible sources of the error. |
Explanation | The operation was successful, but the number of rows that were updated is not known. The database returned -2 in the batch update count. This exception is created to avoid any possible issues with data integrity. |
Action | Repeat the operation to determine if this error persists. |
Explanation | Some or all of the rows were not updated because of a collision that is usually caused by the use of the optimistic-concurrency-control AccessIntent. |
Action | Repeat the operation, or change the AccessIntent if the error persists. |
Explanation | The operation resulted in an exception. |
Action | Examine the operation, the exception, and the database log files. |
Explanation | The batch operation that is specified above experienced an error. |
Action | Examine the database log files, and visit the IBM support Web site for problem determination if no cause is readily apparent. |
Explanation | An internal error has occurred. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | The Application Server has detected that the database started a transaction. The Application Server will attempt to resolve the transaction as configured in the custom properties for the data source. |
Action | There is no user action required. |
Explanation | The Application Server has detected that the database started a transaction. The Application Server will attempt to resolve the transaction as configured in the custom properties for the data source. An error occurred that prevented the transaction from being resolved. |
Action | Gather the FFDC log files and any server log files. If the error is not related to a database outage, visit the IBM support Web site for problem determination. |
Explanation | The database has started a transaction on the connection. The Application Server will rollback the transaction before returning the connection to the pool. |
Action | Evaluate the application code to determine what might be causing the implicit transaction. The application code might be able to prevent further implicit transactions explicity, or you could configure an explicit action to take for the data source. |
Explanation | This typically indicates a typographical error when configuring the custom property for the data source. |
Action | Ensure that one of the expected values is specified for the custom property. If there is a typographical error, correct it and save the changes to the configuration. |
Explanation | This typically indicates a typographical error when configuring the custom property for the data source. |
Action | Update the validation properties for the new connection with the desired values, and remove the deprecated properties. |
Explanation | This typically indicates a typographical error when configuring the custom property for the data source. The error 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 validation properties for the new connection with the desired values, and remove the deprecated properties. |
Explanation | An attempt was made to load a class that is not recognized by the Application Server. Only classes that are recognized are allowed to be loaded by internal utilities. |
Action | Do not use internal utilities to load classes that are not able to be recognized by the Application Server. If no such attempt was made, visit the IBM support Web site for information on problem determination. |
Explanation | Specified custom property has been made obsolete. |
Action | Use the new custom property in place of the old one. |
Explanation | The availability of certain features depends on the location where it is being used. For example, CMP 2 is not available in the Embeddable EJB Container. |
Action | Refer to the documentation to determine where the feature can be used. |
Explanation | The GenericDataStoreHelper has been initialized. |
Action | If this is expected, no user action is required. |
Explanation | An exception was detected cleaning up the ManagedConnection for a destroy operation. |
Action | Refer to the error reported by the database software to help determine the cause of the error. |
Explanation | The operation that was requested is not allowed during a transaction. |
Action | Perform the operation before starting the transaction or after completing the transaction. |
Explanation | A request was initiated by the user to purge the pool. This request makes existing connections in the pool no longer valid. |
Action | Exit the transaction, and the method boundary, and attempt the logic again with a new connection. |
Explanation | The JDBC driver did not identify the connection as valid during the connection validation interval. |
Action | Wait for any retries of connection attempts that could be remaining, then attempt to determine the cause of the connection error. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A two phase operation on the database resulted in an exception. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A two-phase operation on the database resulted in an exception. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Application Server attempted to perform an XAResource operation with an Xid other than the Xid that is used for XAResource.start. |
Action | Obtain a new connection and attempt the transaction again. |
Explanation | The data source custom property, oracleRACXARecoveryDelay, causes the application server to delay xa.commit and xa.rollback operations for the duration of the retry interval. |
Action | Wait for the transaction manager to retry the operation. You must configure heuristic retries on the transaction manager in order for oracleRACXARecoveryDelay to work properly. |
Explanation | The database or the jdbc provider specified by datasource does not support the tight branch coupling option. Tight branch coupling is only supported with a DB2 for z/OS database accessed by the DB2 Universal JCC driver. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The database or the jdbc provider specified by datasource does not support the tight branch coupling option. Either the DB2 for z/OS database or the DB2 Universal JCC driver has rejected the tight branch coupling xa_start option. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | Visit the IBM support Web site for information on problem determination. |
Explanation | The database specified by the datasource does not support the tight branch coupling option. Tight branch coupling is only supported with type 4 connections to DB2 for z/OS V8 (+ APAR PK47713) or DB2 for Linux, UNIX, Windows V8 and later versions. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The jdbc provider specified by datasource does not support the tight branch coupling option. Tight branch coupling is only supported with minimum levels of DB2 Universal JCC driver version 3.51 or 3.6, as bundled with DB2 9.5 or 9 service levels, or the JCC4 driver version 4.1. The default option of loose branch coupling will be used. This may cause lock timeouts, deadlocks and/or transaction rollbacks if the application is designed for tight branch coupling since database locks will not be shared across transaction branches within the same global transaction. |
Action | You must configure the datasource to use a supported level of JDBC driver and database, or configure your application to not require tight branch coupling. |
Explanation | The ResourceAdapter.endpointActivation method should not be used on the Relational Resource Adapter for the Application Server because it does not support message inflow. |
Action | Do not use the ResourceAdapter.endpointActivation method on the Relational Resource Adapter for the Application Server. |
Explanation | The default connection manager received an error resetting a ManagedConnection to the default state. |
Action | If necessary, take action to return the database to a state in which it can be used. |
Explanation | The default connection manager received an error destroying a ManagedConnection. |
Action | If necessary, take action to return the database to a state in which it can be used. |
Explanation | The default connection manager received an error requesting validation of pooled ManagedConnections. |
Action | If necessary, take action to return the database to a state in which it can be used. |
Explanation | The connection pool has reached its maximum limit for open connections. Additional connections cannot be established until some of the open connections are closed. |
Action | Adjust the application to require fewer connections to be open at the same time. |
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. |
Explanation | The connection cannot be reset for connection pooling because a connection error occurred while it was active. |
Action | If necessary, take action to return the database to a state in which it can be used. |
Explanation | The 'next' operation was invoked on an iterator that does not contain additional elements. |
Action | Invoke 'hasNext' on the iteration before invoking the 'next' operation to determine whether the iteration contains additional elements. |
Explanation | The 'remove' operation was invoked when the iterator was not positioned on any element. |
Action | Position the iterator to a valid element before you invoke the 'remove' operation. |
Explanation | The JNDI name of the delegate data source cannot be null or an empty string. |
Action | Set the JNDI name of the delegate data source on the map for that specific proxy data source. |
Explanation | The JNDI names for the delegate data source are configured in the custom property jndiNames using a syntax that is delimited by semicolons. The JNDI name is not in the jndiNames custom property. |
Action | Verify that the custom property jndiNames is set to a correct value. If so, set the JNDI name of the delegate data source to a valid value. |
Explanation | The data source lookup did not complete successfully. The data source might not be created, or it is created in the wrong scope. |
Action | Verify that the data source is created correctly. |
Explanation | The feature that was requested is not available. |
Action | Avoid using the feature, or switch to a driver version that supports the feature if possible. |
Explanation | There is an error with the connection that is specified. The connection will be purged according to the purge policy. |
Action | Create a new connection for future operations. |
Explanation | The command did not run because validation did not complete successfully. |
Action | Evaluate the reason that is specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and try the operation again. |
Explanation | The command did not complete successfully. |
Action | Evaluate the reason that is specified in the message to determine the problem. |
Explanation | The command was not run because a value for a parameter was specified that is not valid. |
Action | Specify a value for the specified parameter that is valid, and try the command again. |
Explanation | The command was not run because a provider name was specified that is not valid. |
Action | Specify a value for the provider name that is valid, and try the operation again. |
Explanation | The command was not run because an JDBC provider was specified that is not valid. |
Action | Specify a JDBC provider that is valid, and try the operation again. |
Explanation | The command step did not complete successfully. This is usually a problem with the command parameters. |
Action | Evaluate the reason that is specified in the message to determine the problem. Correct the problem, and try the operation again. |
Explanation | The command was not able to update the resource property that was specified with the value that was specified. |
Action | Specify a value for the resource property that is valid, and try the operation again. |
Explanation | The command step was not run because a value was not specified for a resource property that is required. |
Action | This is usually a problem with the command parameters. Correct the problem, and try the operation again. |
Explanation | The command step was not run because a parameter value that is not valid was specified for a resource property that is required. |
Action | This problem usually occurs when the parameter value does not conform to the parameter type. Correct the problem, and try the operation again. |
Explanation | The command was not run because the target object references an element in the configuration that is not the type expected by the command. For example, a data source was submitted as the target object to command deleteJDBCProvider, |
Action | This problem occurs when the configuration element referenced by the target object has an unexpected type. Correct the problem and try the operation again. |
Explanation | The Application Server could not map the exception. Refer to the exception that occurred during the mapping. |
Action | Verify the exception mapping in the error map table for the DataStoreHelper and in the exception constructor. |
Explanation | MSSQLhelper methods can only be called from DataDirect helpers. |
Action | Use DataDirectDataStoreHelper.class in your setup. |
Explanation | Some or all of the connection information that is required is missing. |
Action | See the Java documentation for the DataStoreHelper.showLockInfo() method for a description of the connection information which is required. |
Explanation | The showLockInfo method does not support the operating system that was specified. |
Action | Use the correct operating system, or configure the application to not use the showLockInfo method. |
Explanation | An exception occurred when an operation attempted collect lock information from the database. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | DB2 wrote the lock information into the file name that is listed. |
Action | Open the specified file. It contains information on locks in your database. This information might be helpful in resolving deadlocks in the application. |
Explanation | Oracle does not support the Serializable isolation level when using the XA protocol. |
Action | Do not use PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE, because it causes the Serializable isolation level to be used. |
Explanation | DB2 requires the use of the DB2 Universal driver. |
Action | Use the DB2 Universal driver. |
Explanation | The trace file that you specified on the data source does not exist. |
Action | Use an existing file for the trace file. |
Explanation | A custom property was set when creating the JDBC provider from Oracle. The property requires the Oracle patch 2511780. |
Action | If the patch is installed, no user action is required. Otherwise, visit the Oracle support Web site to obtain patch 2511780. |
Explanation | The driverType custom property for the data source was set to the value of 2, and this value is not supported on Cloudscape. The Application Server will change the value to 4 at run time. |
Action | To avoid future warnings, change the driverType value to 4 in the administrative console or with JACL scripts, or omit setting the driverType value and it will default to the value of 4. |
Explanation | The driverType custom property for the data source is not supported by the JDBC driver. |
Action | Remove the driverType from the custom properties for the data source. |
Explanation | The DB2 Universal JDBC driver has been switched to run in an RRS environment on DB2 for z/OS. |
Action | This is the informational message for the environment of the JDBC driver that is running. |
Explanation | The driverType custom property for the data source was set to the value of 2 on the DB2XADatasource. This configuration is not supported by DB2 for z/OS. |
Action | Use the DB2ConnectionPoolDatasource or switch to the DB2 Universal JDBC driver type 4 if it is available for your configuration. |
Explanation | An IOException occurred when the Application Server was trying to open the trace file that was specified. |
Action | Examine the exception, fix the IO problem, and start the Application Server again. |
Explanation | An exception occurred when the Application Server was trying to get or access the metadata object for the database. |
Action | Verify that the metadata is enabled on the backend database. |
Explanation | The data source for the Application Server is configured with the wrong DataStoreHelper. |
Action | Configure the data sources for the Application Server with the Oracle10gDataStoreHelper when you are using the JDBC driver for Oracle10g. |
Explanation | The GenericDataStoreHelper does not know how to collect the lock information. |
Action | Write or use a DataStoreHelper that is specific to the database. |
Explanation | The custom property for a DB2 Universal XA data source, retrieveMessagesFromServerOnGetMessage, was configured with a value of true. The Application Server has changed the value to false at run time to avoid problems during the processing of exceptions. |
Action | To avoid this message, change the retrieveMessagesFromServerOnGetMessage value to false in the admininstrative console or in the configuration scripts, or remove the property completely. This only applies to DB2 Universal XA data sources. |
Explanation | An API that is deprecated is being used. |
Action | Use a version of the API that is not deprecated. Refer to the Java documentation, or visit the IBM support site for information on problem determination. |
Explanation | The reauthentication custom property for the data source cannot be enabled if TrustedConnectionMapping login configuration is used. |
Action | Disable the reauthentication custom property for the data source if TrustedConnectionMapping login configuration is used. |
Explanation | The reauthentication custom property for the data source cannot be enabled when you are using the TrustedConnectionMapping login configuration. |
Action | Disable the reauthentication custom property for the data source, or do not use the TrustedConnectionMapping login configuration. |
Explanation | The Reauthentication property is enabled, and the implementation code for the connection reauthentication in the DataStoreHelper class was not provided. |
Action | Overwrite the doConnectionSetupPerTransaction DataStoreHelper method and provide the connection reauthentication implementation code, or disable connection reauthentication by one of the following: 1) Clear the "Enable database reauthentication" option for the Datasource properties in the Application Server or 2) set the reauthentication custom property to false for the data source. |
Explanation | The Application Server could not establish a connection to the database using Kerberos. |
Action | Resolve the problem that is described by referring to the exception that was created. Also, validate that the application is running with a version of the JDBC driver that supports getting connections using GSSCredentials. |
Explanation | The ThreadIdentity property cannot be enabled when you are using the TrustedConnectionMapping login configuration. |
Action | Disable the ThreadIdentity property for the data source, or do not use the TrustedConnectionMapping login configuration. |
Explanation | The propagateClientIdentityUsingTrustedContext custom property for the data source is no longer used, application server runtime will enable Trusted Connection feature if TrustedConnectionMapping login configuration is used. |
Action | Delete the propagateClientIdentityUsingTrustedContext custom property for the data source. |
Explanation | This is the lock information that is reported by the Cloudscape database for your application. |
Action | This is information on the locks in your database. You might want to use the information to resolve deadlocks in the application. |
Explanation | The custom property for the data source cannot be enabled in the current environment. |
Action | Disable the custom property for the data source. |
Explanation | The data source property is not valid in this context. |
Action | No user action is required. The Application Server will ignore the property at run time. |
Explanation | The useTrustedContextWithAuthentication custom property is enabled, but the implementation code for the DataStoreHelper method that will return the password that the application server will use to switch the identity is not provided. |
Action | Overwrite the getPasswordForUseWithTrustedContextWithAuthentication DataStoreHelper method and provide the implementation code that will return the password, or set the useTrustedContextWithAuthentication custom property for the data source to false. |
Explanation | The application server requires a password to switch trusted context identities if you enable trusted context with authentication. You must override the getPasswordForUseWithTrustedContextWithAuthentication DataStoreHelper method to get the password to the application server. |
Action | Verify that you implement code that will override the getPasswordForUseWithTrustedContextWithAuthentication DataStoreHelper method. |
Explanation | The method that is invoked is not found on the specified class. |
Action | Use a version of the class that has the missing method, or reconfigure the application server to avoid calling the missing method. |
Explanation | The method that is invoked did not complete successfully. |
Action | Examine the exception that was created to determine the reasons for the error. |
Explanation | The caching feature for the Oracle connection is not supported on the JDBC driver that is being used. The feature will not be enabled. |
Action | Configure the application server to use an Oracle non-XA data source. |
Explanation | The application server received an exception when attempting to remove the cache for an existing Oracle connection. |
Action | Examine the exception, correct the problem, and restart the application server. You could also manually remove the cache for the Oracle connection. |
Explanation | The application server received an exception when attempting to check the existence of the Oracle connection cache. |
Action | Examine the exception, correct the problem, and restart the application server. You could also manually remove the cache for the Oracle connection if it exists. |
Explanation | The application server has detected the enablement of connection caching through the database. Connection pooling in the application server will be disabled. |
Action | If you do not want to disable connection pooling in the application server, disable connection pooling for the database server. |
Explanation | The data source for the application server is configured with the wrong DataStoreHelper class. |
Action | Configure the data source for the application server with the correct data store helper class that corresponds to the JDBC driver that you have configured. |
Explanation | The application server uses a version of the Java runtime environment that Oracle does not support with this version of their JDBC driver. |
Action | You must use Oracle JDBC driver version 11g or later, even if you are connecting to Oracle databases that are earlier than version 11g. Refer to the Information Center for WebSphere Application Server for information on the version of the Oracle JDBC driver that you can use. |
Explanation | The migration of the Cloudscape instance failed, see the exception and the <dbinstance>_migration.log that is located in WAS_HOME/profiles/<profileName>/logs directory for details. |
Action | Fix the migration problem as described by the exception and the migration log. Delete the newly created database if it exists, and manually run the database migration tool again (WAS_HOME/derby/bin/embedded/db2jMigrate.bat/sh). |
Explanation | The migration of the Cloudscape instance was partially completed. See the steps that are missing for more details on what needs to be finished manually. |
Action | Fix the migration problem as described by migration log, and create the missing parts. There is no need to run the migration tool again, because the missing parts can be created manually. |
Explanation | An attempt is made to delete the new Derby database. |
Action | No user action is required. This is an informational message. |
Explanation | The attempt to delete the new Derby database has failed. |
Action | Manually delete the new Derby database. |
Explanation | The Attempt to delete the newly created Derby database was successful. |
Action | No user action is required. This is an information message. |
Explanation | The providerType was not found. |
Action | Visit the IBM support Web site for information on problem determination. Use the following data to help determine the possible causes of the error. |
Explanation | The migration of the Cloudscape database instance will create a new Derby database instance with the specified name. |
Action | No user action is required. This is an informational message. |
Explanation | The Application Server was not able to locate any Java archive (JAR) or compressed files in the class path that is specified for the JDBC provider. Another case is that the files exist, but the file or directory permissions do not give the Application Server the required access. |
Action | Verify that the path that is specified is correct, and verify that the necessary Java archive (JAR) or compressed files are present. Verify that the directories and files in the path have the required permissions. On z/OS, check the MVS SYSLOG for permission errors. |
Explanation | MalformedURLException occurred attempting to read a JDBC provider JAR or .zip file. |
Action | Verify that the path that is specified is correct, and verify that the necessary JAR files and .zip files are valid. |
Explanation | An IntrospectionException occurred attempting to retrieve setter methods from the data source. |
Action | The data source properties will not show up in the graphical user interface (GUI). You will need to enter them manually. |
Explanation | The Application Server could not find a setter method on the data source to set the property that is requested. |
Action | Verify that the property name that is specified is correct. |
Explanation | The Application Server was not able to locate the data source property that was specified. The possible reasons are: 1) The data source property is not spelled or capitalized correctly, 2) The property that is specified does not apply to the data source that is being configured, or 3) the Application Server contains the default configuration for a different version of the JDBC driver that was specified, and this caused a mismatch of data source properties. |
Action | Verify that the property that is specified is correct for the data source. Correct any errors with spellings or capitalization. Delete the property if it does not apply (or no longer applies) to the JDBC driver that is used. |
Explanation | An exception occurred setting the specified property on the data source. |
Action | Verify that the value that is specified is valid for the property. |
Explanation | The value that is configured is not valid for the attribute that is specified. |
Action | Verify that the value that is specified or the attribute is valid. |
Explanation | The attributes that are specified are not compatible. |
Action | Verify that the attributes that are specified are compatible. |
Explanation | The test of the data source connection was successful. |
Action | The data source can now be used by applications. |
Explanation | This property contains a value that is not expected. The reroute function for the client might be disabled. |
Action | Verify that the value that is specified for the property is valid. |
Explanation | This property contains a value that is not expected. The reroute function for the client might be disabled. |
Action | Verify that the value that is specified for the property is valid. |
Explanation | The DB2 JDBC driver type 2 has a built-in mechanism for updating and persisting the client reroute information. |
Action | Configure the data source to use the JDBC driver type 4, or remove the settings for persistence of client reroute information. |
Explanation | The test of data source connection was successful, but warnings were issued. |
Action | Review the data source configuration to fix the errors that are indicated by the warnings. |
Explanation | The unbind method for the Java Naming and Directory Interface (JNDI) caused an exception. The JNDI name might not be correct, or there might be a problem in the Naming service. |
Action | Verify that the JNDI name that was specified in the class properties for the data source is correct. |
Explanation | The lookup method for the Java Naming and Directory Interface (JNDI) caused an exception. The JNDI name might not be correct, or there might be a problem in the Naming service. |
Action | Verify that the JNDI name that was specified in the class properties for the data source is correct. |
Explanation | The bind method for the Java Naming and Directory Interface (JNDI) caused an exception. The JNDI name might be incorrect, or there might be a problem in the Naming service. |
Action | Verify that the JNDI name that was specified in the class properties for the data source is correct. |
Explanation | The creation of a DB2ClientRerouteServerList caused an exception. |
Action | Examine the exception. Verify that properties related to the reroute function for the client are specified correctly in the class properties for the data source. |
Explanation | The test of data source connection did not complete successfully. |
Action | Review the data source configuration to fix the error. |
Explanation | The test of data source connection failed. |
Action | Review the data source configuration to fix the error. |
Explanation | The database connection has been rerouted to an alternate database server. |
Action | This message is to notify you that a rerouting action has occurred. No user action is required. |
Explanation | The possible causes are: 1) The DataStoreHelper class that was specified is not correct, 2) the name or the package name for the DataStoreHelper class that was specified is not correct, 3) the DataStoreHelper class is not included in the class path, or 4) the JDBC provider that is used might not be supported in this release of the Application Server. |
Action | Based on the corresponding cause, perform one of the following actions: 1) Switch to the DataStoreHelper class that is appropriate, 2) correct the name or package name for the DataStoreHelper class, 3) correct the class path, or 4) use a different JDBC provider or a different version of the Application Server. |
Explanation | The implementation class for the DataStoreHelper cannot be an interface or an abstract class. |
Action | Provide a class that fully implements the DataStoreHelper interface. |
Explanation | The DataStoreHelper class cannot be instantiated, because it does not have a public constructor that takes a properties object as the parameter. |
Action | Create a public constructor for your DataStoreHelper that will take a properties object as its parameter. |
Explanation | The Application Server cannot access your DataStoreHelper constructor because it is not public. |
Action | Verify that your DataStoreHelper constructor is a public method. |
Explanation | The DataStoreHelper constructor issued an exception. |
Action | Verify that the properties that are passed to the constructor are correct, and verify that the DataStoreHelper constructor is implemented correctly. |
Explanation | The custom class for the DataStoreHelper does not implement the DataStoreHelper. |
Action | Update the custom class for the DataStoreHelper to implement the DataStoreHelper interface. |
Explanation | The Application Server was not able to issue the DataStoreHelper method that is specified. |
Action | If you are using a custom DataStoreHelper, ensure that the code in the DataStoreHelper method that is specified is correct. Otherwise, check the configuration properties for the data source. |
Explanation | See the linkedException for more information. |
Action | See the linkedException for more information. |
Explanation | The 'enable2Phase' property can only be set to false if the data source class implements the ConnectionPoolDatasource interface. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | The 'enable2Phase' property can only be set to true if the data source class implements XADatasource interface. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | The application server is unable to load the specified class. |
Action | Verify that the data source custom property is specified correctly and is accessible to the application server. |
Explanation | The application server is not able to parse the value that is supplied for the data source custom property. |
Action | Verify that the data source custom property is specified correctly. |
Explanation | This is a warning message that is displayed during data source configuration. |
Action | Read the warning message and take appropriate action to fix the problem, if necessary. |
Explanation | This is a warning message that is displayed during data source configuration. |
Action | Read the warning message and take appropriate action to fix the problem, if necessary. |
Explanation | This message displays the product name for the Database. |
Action | The Database name that is listed above is now being used by applications. |
Explanation | This message displays the product version for the Database. |
Action | The Database version that is listed above is now being used by applications. |
Explanation | This message displays the name of the Java Database Connectivity (JDBC) driver. |
Action | The name of the JDBC driver that is listed above is now being used by applications. |
Explanation | The version of the Java Database Connectivity (JDBC) driver. |
Action | The version that is listed above for the JDBC driver is now being used by applications. |
Explanation | Oracle databases do not implement the setReadOnly method. A setReadOnly(true) method will not make the connection as readonly connection. The setReadOnly(false) is also not implemented, and a transaction is implicitly started by an Oracle database. The Application Server will not invoke the setReadOnly(false) method on an Oracle database to prevent an unnecessary transaction from being started. |
Action | Inspect your application to verify that your application does not depend on a transaction after the setReadOnly(false) method is called. |
Explanation | The type of the Java Database Connectivity (JDBC) driver. |
Action | The type of JDBC driver that is listed above is now being used by applications. |
Explanation | The specified JDBC driver might not be officially certified in future releases of the Application Server. |
Action | Continue using the JDBC driver or switch to a JDBC driver that is recommended. |
Explanation | The database which is represented by the backend ID might not match the data source that is connected. |
Action | Inspect the database version between the deployment and the runtime data source. If they are not the same, use a backend ID that matches the data source to deploy the enterprise Java bean (EJB), or change the data source to match the backend ID. |
Explanation | Backend ID checking is disabled. No validation of the backend ID will be performed. |
Action | Set the disableBackendIdChecking custom property for the data source to false, or remove the property to enable backend ID checking. |
Explanation | The name of the DataStoreHelper. |
Action | This is an informational message. There is no user action required. |
Explanation | The application is using a JDBC provider that is no longer supported by the Application Server. |
Action | Use the JDBC provider that is provided in the error text. |
Explanation | The Application Server received an exception when attempting to configure a data source with the client reroute method. |
Action | Examine the exception, correct the problem, and restart the Application Server. |
Explanation | The Application Server received an exception when attempting to configure a data source with the client reroute method. This could be caused by the use of an older level of a JCC driver. |
Action | Check the level of the JCC driver, examine the exception, correct the problem, and restart the Application Server. |
Explanation | The Application Server received an exception when attempting to configure a data source with the client reroute method on the Java Naming and Directory Interface (JNDI) name. |
Action | Examine the exception, correct the problem, and restart the Application Server. |
Explanation | To configure a data source with the client reroute method, clientRerouteAlternateServerName and clientRerouteAlternatePortNumber must be set to a value that is not null, and the number of alternate servers must match the number of alternate ports. |
Action | Correct the problem, and restart the Application Server. |
Explanation | This message displays the specification level of the Java Database Connectivity (JDBC) driver. |
Action | The specification level of the JDBC driver listed above is now used by applications. |
Explanation | The Java Database Connectivity (JDBC) specification level that is specified in the error message is a prerequisite of the feature. |
Action | Disable the feature, or switch to a JDBC driver that is at the required level. |
Explanation | Test connection cannot be used to accurately test a connection that uses the Kerberos mapping alias. Instead, test connection will use authentication information that is specified in the component-managed alias. The result of the test might not accurately indicate whether a connection can be made within the context of an application if the connection is configured to use Kerberos authentication. |
Action | Verify that the connection to the data source can be made within the context of your application. |
Explanation | The application server could not create a trusted connection to the data source. The JDBC driver did not return a valid connection, or returned an error that was not expected. |
Action | Examine the exception, if available, and verify that the JDBC driver and database server support trusted context. |
Explanation | An attempt is made to pool a connection that has an AutoCommit value of False. The application server cannot determine if a transaction is active because the data source is configured as nontransactional. The application server will not attempt to resolve the transaction because the data source is not configured to automatically commit or roll back during connection cleanup. |
Action | Configure the data source to automatically commit or roll back on connection cleanup, or always reset the AutoCommit value to True. |
Explanation | An error occurred closing the JDBC object that is specified. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred closing the child object that is specified. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred closing the statement. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The application attempted to access a connection or the connection's corresponding Statements, ResultSets, or metadata from a different thread. This behavior is a violation of the programming model for the application server. Closing the objects that the application attempted to access in a finalize() method is also considered a programming model violation, because the finalize() method is run by the JVM in another thread. |
Action | Adjust the application to avoid multithreaded access. |
Explanation | The method being invoked is part of the Java Database Connectivty (JDBC) specification V3.0, and the method does not exist on the provider. |
Action | Ensure that your JDBC provider supports the JDBC specification V3.0, or do not use this method. |
Explanation | The connection handle is now associated with a pooled connection that is different and that does not implement the interface that is requested for the wrapper. |
Action | Wrappers for the interface that is specified should not be used when the Wrapper.isWrapperFor method indicates that the connection is not a wrapper of the interface. |
Explanation | The data source custom property allows you to choose which connection sharing behavior you want. |
Action | Verify that the data source custom property is configured for the behavior you want. |
Explanation | The data source custom property allows you to choose which connection sharing behavior you want. |
Action | Verify that the data source custom property is configured for the behavior you want. |
Explanation | A DataStoreAdapterException was created to map an SQLException. |
Action | There is no user action required. |
Explanation | The method that is specified is not supported by the implementation of the Application Server. |
Action | Do not use the method. |
Explanation | This method is provided only for internal use by the Application Server. |
Action | Do not call this method. |
Explanation | Attempted to perform an operation on an object that is closed. |
Action | Retrieve a new instance of the object on which to perform the operation. |
Explanation | Attempted to perform an operation on a Connection handle that is not active. |
Action | Enable the InactiveConnectionSupport property for the resource adapter. |
Explanation | The application attempted to use the 'jdbcCall' method to invoke a Java Database Connectivity (JDBC) method instead of a proprietary extension, or the application attempted to use the 'jdbcCall' method to invoke a proprietary method that is not supported by the application server. |
Action | If the method is from the JDBC API, invoke the method directly on the JDBC resource, instead of using the 'jdbcCall' method. If the method is a proprietary extension that is not supported by the application server, then do not use the method. |
Explanation | It is not allowed to use the 'jdbcCall' method from the Application Server on objects that are not JDBC objects. |
Action | Use the 'jdbcCall' method from the Application Server with JDBC objects only. |
Explanation | The wrapper that is specified does not contain the wrapped object type that is specified. |
Action | Verify that the wrapper and the parameters for the wrapped object are specified correctly. |
Explanation | The Application Server does not permit the specified method to be invoked through a jdbcPass. |
Action | If the method does not alter the state of its native parameters of the Java Database Connectity (JDBC) object, visit the IBM support Web site to request that the method be added to the list of permitted methods for jdbcPass. |
Explanation | The Application Server does not permit the operation that was requested. |
Action | Do not use the operation that is specified. |
Explanation | The Application Server does not allow calls to the setTypeMap, setReadOnly or setCatalog methods 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. |
Explanation | The Application Server does not allow calls to the commit, rollback, setSavepoint or releaseSavepoint methods on the Connection while a global transaction is active. |
Action | Do not call the commit, rollback, setSavepoint or releaseSavepoint methods on the connection when it is in a global transaction. If a non-transactional data source (for example, non-jta-data-source for Java Persistence API) is being used, then configure non-jta-data-source in persistence.xml and also configure the nonTransactionalDataSource custom property on the data source. |
Explanation | You cannot perform operations when the application is in the current transaction state. |
Action | Get a new Connection on which to perform the operation. |
Explanation | The current Connection handle could not be reassociated. |
Action | Try obtaining a new Connection. |
Explanation | Connection handles can only be reassociated from the INACTIVE state. |
Action | Close your current Connection handle, and obtain a new one. |
Explanation | Connection handles can only be reassociated if all the child objects are closed. |
Action | Close your current Connection handle, and obtain a new one. |
Explanation | An operation is currently being performed on the Connection handle. It cannot be dissociated during the operation. |
Action | Wait until all the operations on the handle have finished, then dissociate the handle. |
Explanation | The fetch size can only be set to a value that is not negative. |
Action | Choose a value for the fetch size that is not negative. |
Explanation | The preTestSQLString custom property cannot be empty if the pretest connection option is selected. If you choose to leave the preTestSQLString property unspecified, performance might be affected. |
Action | Provide an SQL statement for preTestSQLString that is valid. |
Explanation | The Statement object that was passed in cannot be set to null. |
Action | Set the Statement object to an object that is not null. |
Explanation | The object cannot be cloned. |
Action | Do not call the clone() method. |
Explanation | A passkey that is not valid was passed on the getConnection method. |
Action | Visit the IBM support Web site for problem determination information. |
Explanation | The getConnection method on this data source can only be issued by JMS and CMP Applications. |
Action | Define another data source for the JDBC applications or set the jmsOnePhaseOptimization property to false. |
Explanation | The jmsOnePhaseOptimization data source option can only be enabled on non XA-capable Datasources. |
Action | Use a data source that is not XA-capable, or clear the option for using jmsOnePhaseOptimization in the administrative console. |
Explanation | JMS is attempting to get an optimized connection. This action requires the jmsOnePhaseOptimization data source option to be enabled. |
Action | Enable the jmsOnePhaseOptimization option on the data source, or visit the IBM support Web site for information on problem determination. |
Explanation | The nonTransactionalDataSource custom property cannot be enabled when the jmsOnePhaseOptimization custom property for data sources is enabled. |
Action | Disable the nonTransactionalDataSource or the jmsOnePhaseOptimization data source custom property. |
Explanation | Transaction problems will occur when you enable the nonTransactionalDataSource custom property for data sources and connect to IBM DB2 on z/OS with the DB2 Universal JDBC Driver Type 2. |
Action | Disable the nonTransactionalDataSource custom property for data sources or use the DB2 Universal JDBC Driver Type 4. |
Explanation | The Connection cannot be null. |
Action | Pass a connection object that is valid. |
Explanation | The Trusted Connection feature is not supported on the JDBC Driver that is being used. |
Action | Configure the Application Server to use the DB2 Universal JDBC Driver, or stop using TrustedConnectionMapping login configuration. |
Explanation | The extending data source properties feature is not supported on the JDBC Driver that is being used. The extended data source properties are ignored. |
Action | Configure the Application Server to use the DB2 Universal JDBC Driver. |
Explanation | The Application Server does not support Kerberos authentication on the database that is used. User name and password will not be used when getting a connection. |
Action | Disable Kerberos, or use a DB2 backend with the DB2 universal JDBC driver. |
Explanation | Connections cannot be shared if you are using the extending data source properties feature and the optimizeDB2ForGetUseClose data source custom property is enabled. |
Action | Disable the optimizeDB2ForGetUseClose data source custom property, or use the get/use/close connection pattern when you use unique extended data source properties within the same transaction. |
Explanation | The driverType custom property for the data source was set to the value of 2, and this value is not supported on Informix. The application server will change the value to 4 at run time. |
Action | To avoid future warnings, change the driverType value to 4 in the administrative console or with JACL scripts, or omit setting the driverType value and it will default to the value of 4. |
Explanation | The application server could not lookup the service that was specified. Examine the exception for details. |
Action | Examine the exception, and correct the problem. Restart the application server. |
Explanation | The application server could not add the service that was specified. Examine the exception for details. |
Action | Examine the exception, and correct the problem. Restart the application server. |
Explanation | The application server could not find the service that was specified. |
Action | Visit the support site for WebSphere Application Server for more information. |
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. |
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. |
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. |
Explanation | The application server received an exeception while trying to update the value of the specified connection pool property with a new value supplied to it by CMX. |
Action | No action is required by the user.CMX should retry setting this property in case the initial attempt failed. |
Explanation | The application server attempts to clean up some resources in case the application relies on closing the connection to free some resources. The application server's ability to release certain resources is limited by the JDBC specification compliance level of the JDBC driver. |
Action | The application should ensure the resource is properly cleaned up instead of relying on closing the connection. |