Oracle Database migration to a remote Data Protector cell--Best practices

8
Figure 4. Jukebox configuration on hpu015
iii. Add a device type Jukebox on the target system.
iv. ADD the files in the repository window
4. Import the media into the target cell.
An import will re-read all the backup session information in the media into the internal database.
a. Scan the devices and import all media
b. Verify after the import that you can see the session imported in the Internal Database.
Oracle Recovery Manager Settings
Control File Autobackup
Oracle Control Files backup should be a key element of every Oracle backup procedure. Starting
with Oracle 9i, Oracle introduced the Control File Autobackup functionality.
Among other things, it enables to restore the Control File from a backup, although your current
SPFILE Control File and recovery catalog are not available.
Every time the Control File autobackup is performed, it will be logged in the instance alert log file:
Figure 5: Alert log entry for the control file autobackup. Below the explanation for the red boxes
Starting control autobackup
Tue May 6 15:00:39 2008
Control autobackup written to SBT_TAPE device
comment 'API Version 2.0,MMS Version 65.6.0.0',
media '10394b75:48205542:5c7d:0053[ita022_file_lib_MediaPool_27]' (1)
handle 'c-38758237-20080506-01'
(2) (3)
From in the above figure, we can gather the following information:
1. Data Protector media ID and media label
2. Database DBID
3. Data Protector Session ID (Backup Date - Session number)