Reason:
Restart encountered one or more pending LOGPR commands for RRS, but RRS cannot resolve them for various reasons, described by vvvvv in the message
is one of the following:
Means that the RRS MUF startup option is not specified.
Indicates that RRS has lost some hardened data.
Means that the RRS log was cold started.
Indicates that RRS is currently unavailable.
Means that a prior Multi-User Facility had a data lost or cold start RRS transaction which was not resolved.
is the unit recovery ID (URID) from RRS.
is the sequence number assigned by CA Datacom/DB. This sequence number is visible on a STATUS command for MUF or other methods to provide STATUS information.
Action:
These pending LOGPR commands represent pending commits from an RRS application that the Multi-User Facility cannot resolve without RRS. The Multi-User Facility enables, but the rollback/RRS phase of restart is not completed until these pending RRS commits are resolved. Research the URID given in the message to determine whether a REQCOMIT or REQROLBK for the sequence number listed is appropriate, and if it is, you can then use a REQCOMIT or REQROLBK console command to commit or roll back the CA Datacom work that occurred in the specified URID.
Note: If IS DOWN is the condition, you cannot issue the REQCOMIT or REQROLBK. Instead, you must wait for RRS to be available, at which time the Multi-User Facility communicates with RRS and resolves the outstanding transaction.
|
Copyright © 2014 CA.
All rights reserved.
|
|