After you have loaded the database, use the load transaction command to load each transaction log dump in the order in which it was made.
This process reconstructs the database by reexecuting the changes recorded in the transaction log. If necessary, you can recover a database by rolling it forward to a particular time in its transaction log, using the until_time option of load transaction.
Users cannot make changes to the database between the load database and load transaction commands, due to the “offline” status set by load database.
You can load only transaction log dumps that are at the same release level as the associated database.
When the entire sequence of transaction log dumps has been loaded, the database reflects all transactions that had committed at the time of the last transaction log dump.