Explanation | The Recovery Log Service has been placed into pending state in order to allow the system to backup the recovery log files. |
Action | No action is required by the user. |
Explanation | The previously suspended Recovery Log Service has been restored to running state. |
Action | No action is required by the user. |
Explanation | This message code is used to support messages that have not yet been allocated their own message code. |
Action | Refer to the message text for more information. |
Explanation | The Recovery Log Service was unable to create the file indicated in the message. Either the target directory is inaccessible or the system does not have sufficient permissions to create the required file. |
Action | Ensure the required directory hierarchy is valid and accessible to the Recovery Log Service. |
Explanation | The Recovery Log Service was unable to exclusively lock the file indicated in the message. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | A new recovery log file has been established in order to store persistent data. |
Action | No action is required by the user. |
Explanation | Either previously recovery log files have been deleted or this is the first time recovery log files have been stored in this location. In either case, the associated service will start and perform no recovery processing |
Action | No action is required by the user. |
Explanation | The recovery log has failed, and not further access to the recovery log can occur. The component is indicated in the message along with the exception taken. |
Action | The server must be restarted so that the log can be repaired. Attempt to fix any conditions indicated by the exception in the message. If the problem persists, please contact IBM Support. |
Explanation | This message is issued with message CWRLS0008E to indicate the details of the recovery log failure. |
Action | Use the information in this message along with message CWRLS0008E to correct whatever condition caused the recovery log to fail. |
Explanation | The recovery log service is directing recovery processing of associated client services. |
Action | No user action is required. |
Explanation | The recovery log service is directing recovery processing of associated client services for the peer server. |
Action | No user action is required. |
Explanation | The recovery log service has prompted all associated client services to begin recovery. |
Action | No user action is required. |
Explanation | The recovery log service has prompted all associated client services to begin recovery for the peer server. |
Action | No user action is required. |
Explanation | Recovery processing is being transferred to an alternate WebSphere server. Typically, this occurs when a server is restarted and retakes ownership of its recovery logs. |
Action | No action is required by the user. |
Explanation | The file locking mechanism used by the recovery log service to ensure exclusive access to recovery log files has been explicitly disabled. |
Action | Ensure the appropriate constraints are in place to support this configuration setting. |
Explanation | Either the target server is active or the recovery log configuration is incorrect. |
Action | Ensure that recovery log configuration is valid. If you are unable to correct the problem, please contact IBM support. |
Explanation | This message indicates that control of a recovery log has been passed between to WebSphere servers. |
Action | No action is required by the user. |
Explanation | The recovery log service has prevented the local server relinquishing control of its own recovery logs. This may be due to inappropriate Core group policy configuration. |
Action | Ensure that the policy configuration does not assign ownership of an active server's recovery log to an alternate server. |
Explanation | If a snapshot of the log files is taken then the this snapshot will be consistent with other system state. |
Action | No user action is required. |
Explanation | If a snapshot of the log files is taken then the this snapshot may not be consistent with other system state. |
Action | No user action is required. |
Explanation | The Recovery Log Service will be resumed only when there are no outstanding suspends. |
Action | No action is required by the user. |
Explanation | If there are no outstanding suspend operations the Recovery Log Service will resume. |
Action | No action is required by the user. |
Explanation | Informational. |
Action | No action is required by the user. |
Explanation | An exception was caught whilst attempting to recover from a previous server failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | In a High Availability configuration, server recovery may be automatically initiated on a peer server. |
Action | Do not attempt to start a HA enabled server in recovery mode. |
Explanation | The Recovery Log Service was unable to exclusively lock the file indicated in the message during recovery as the file appears to be in use. The recovery service will continue to periodically attempt to gain the exclusive lock so that recovery can proceed. If the recovery log file is one of the main server recovery logs, then startup will be suspended until access to the logs is possible. If the recovery log file belongs to another peer server, then another server may gain the locks and peer recover - in which case this server will stop retrying to recover. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages check the location of the recovery logs and ensure they are not being accessed by another server. For instance, this condition could occur if more than one server was accidentally configured to use another server's recovery logs. |
Explanation | Transaction logs from two servers are using a common directory configuration. This may possibily lead to recovery lock contention or a failure of data integrity. |
Action | Configure separate log directory paths for each server. |
Explanation | Compensation logs from two servers are using a common directory configuration. This may possibily lead to recovery lock contention or a failure of data integrity. |
Action | Configure separate log directory paths for each server. |
Explanation | The Recovery Log Service is unable to perform or complete recovery for the local server and no further work can proceed, so the server is being terminated. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The Recovery Log Service is unable to initiate recovery processing for the local server as it is waiting for the HAManager to activate group membership for this local server's recovery logs. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages check the configuration of the DefaultCoreGroup settings and associated policy definitions for the recovery log service for the server. For instance, if the Clustered TM policy has been set to not support fail back, then another server may have a hold onto the logs and will stop this server from being activated. |