When you restore a backed up database, the transactions that took place after the archive operation are lost. If you enable transaction logging after you back up the database, you can replay the logged transactions to recover a database to its most recent state.
You can log and replay only block storage database transactions.
Note: | Oracle recommends that you use transaction logging and replay with database backup and restore, as part of a comprehensive backup and recovery strategy. |
Each logged transaction is assigned a sequence ID, indicating the order in which the transaction was performed. To ensure the integrity of the restored data after a replay, Essbase enforces the replay of transactions in the same order in which they originally were performed. The order of sequence IDs are tracked across multiple replay commands. After a transaction has been replayed, you can replay only transactions with a greater sequence ID.
To replay transactions:
From Enterprise View or a custom view, right-click a database and select Replay Transactions.
To specify the transactions you want to replay, select one of the following options:
Based on Last Replay Time
Administration Services Console replays the transactions that were logged after the last replay request was originally executed.
Using Sequence ID Ranges
To selectively replay transactions, enter a comma-separated string of sequence ID ranges. A range can consist of one or more transactions:
One transaction: n to n; for example, 1 to 1
Multiple transactions: x to y; for example, 20 to 100
Since Time: Enter a time in format mm-dd-yyyy hh:mm:ss. For example, Mar 28, 2008 19:35:43.
Administration Services Console replays the transactions that were logged after the specified time.
Click OK.
“Enabling Transaction Logging” and “Configuring Transaction Replay” in the Oracle Essbase Database Administrator's Guide
alter database (MaxL) in the Oracle Essbase Technical Reference