Transactions that take place after a database is backup are lost when you restore the database. After you back up a database, enable transaction logging, which captures ongoing transactions that can be replayed 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, along with database backup and restore, as part of a comprehensive backup and recovery strategy. |
To view the list of logged transactions, you must have the Administrator role.
To view logged transactions:
From Enterprise View or a custom view, right-click a database for which transaction logging is enabled, and select Display Transactions.
To specify the transactions you want to view, select one of the following options:
Based on Last Replay Time
Administration Services Console lists the transactions that were logged after the last replay request was originally executed.
Since Time: Enter a time in format mm-dd-yyyy hh:mm:ss. For example, Mar 28, 2008 19:35:43.
Administration Services Console lists the transactions that were logged after the specified time.
You can sort the list by the following attributes:
The time the transaction was executed
The user who submitted the transaction request
The transaction sequence ID, which indicates the order in which the transaction was performed and the order in which it must be replayed
Click OK.
“Enabling Transaction Logging” and “Configuring Transaction Replay” in the Oracle Essbase Database Administrator's Guide
query database (MaxL) in the Oracle Essbase Technical Reference