recovery log

Database-1 looks at its recovery log and notices that it had an incomplete transaction.

Adding more than one server causes recovery log contention as both servers attempt to process recovery.

Adding two servers causes recovery log contention as both servers attempt to own the associated recovery logs.

If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.

A requirement of a recovery log is that only one server has access to it (either for recovery processing or standard logging) at any time.

The policy essentially provides the logic for determining updated recovery log ownership in the event of a server failure.

Database-2 writes Undo and Do records and state to its recovery log, again just as Database-1 did.

Access to a recovery log is only performed when the exclusive lock is held.

The recovery log size may also need to be increased depending on the current utilization.

Ownership of the recovery log is defined in the WebSphere Application Server configuration.

It writes records to a recovery log, plus transaction state information.

Server P is running on host P and holds an exclusive file lock for its own recovery log files.

File locking is used to ensure exclusive access to the files that make up a recovery log.

Primary log files establish a fixed amount of storage allocated to the recovery log files.

Enable Fail back to ensure that a failed server reclaims its recovery log when it restarts, and optionally enter a free-form description.

Log truncation frees any virtual logs whose records all appear in front of the minimum recovery log sequence number (MinLSN).

Safety of the recovery log is vital.

The first-time installation procedure creates a default 9-MB recovery log volume (log. dsm).

The recovery log is used insure data integrity during recovery processing, which we will illustrate later.