Filter
Top Products
Integrating SAP DB/MaxDB and Data Protector
Restoring an SAP DB/MaxDB Database
Chapter 3 303
Windows recover_start BACKDP-Data[2] DATA EBID "<inst_name>
<SessionID>:1 \\.\Pipe\<inst_name>.BACKDP-Data[2].1,TEST
<SessionID>:2 \\.\Pipe\<inst_name>.BACKDP-Data[2].2"
UNIX recover_start BACKDP-Data[2] DATA EBID "<inst_name>
<SessionID>:1
/var/opt/omni/tmp/<inst_name>.BACKDP-Data[2].1,<inst_name
> <SessionID>:2
/var/opt/omni/tmp/<inst_name>.BACKDP-Data[2].2"
Repeat this step for every session in the required chain of backup
sessions.
Recovery 8. When the restore has finished, the database can be recovered either
until the last redo log or until the specified point in time.
a. To recover the database until the last redo log, execute the
following command in the SAP DB/MaxDB database manager:
db_online
b. To recover the database until the specified point in time, execute
the following command in the SAP DB/MaxDB database manager:
db_warm -f -u <yyyymmdd> <hhmmss>
Where <yyyymmdd> and <hhmmss> parameters set the time for the
last redo log to be applied.
SAP DB/MaxDB Migration
When performing an SAP DB/MaxDB migration, some additional tasks
must first be done in order to prepare the SAP DB/MaxDB Server or
instance. These tasks are described in the“SAP DB/MaxDB Migration
Prerequisites” on page 294.
Follow the procedure in the section “SAP DB/MaxDB Restore and
Recovery” on page 300 to migrate the SAP DB/MaxDB database using
SAP DB/MaxDB utilities from existing Data Protector SAP DB/MaxDB
backup session(s). When following the mentioned procedure, before
executing the recover_start command, delete the existing redo logs on
the SAP DB/MaxDB Server by executing the following command in the
SAP DB/MaxDB database manager:
util_execute clear log