Integrating Oracle and Data Protector

Backing Up an Oracle Database

3.Start SQL*Plus and type: alter database archivelog; alter database open;

alter system archive log start SCOPE=SPFILE;

If PFILE is used:

1.Shut down the database.

2.Change PFILE to enable log archiving by setting: log_archive_start = true

3.Mount the database.

4.Start SQL*Plus and type:

alter database archivelog;

alter database open;

Oracle Data Guard: The archive logs generated after an archive log backup must be manually cataloged so that they are known to RMAN for future backups when:

•The primary or standby control file is re-created. The archive logs must be re-cataloged because RMAN uses the control file to determine which archive logs must be backed up.

•The primary database role changes to standby after a failover. The archive logs must be re-cataloged because a change in database role resets the version time of the mounted control file.

Use the RMAN command CATALOG ARCHIVELOG

'<archive_log_file_name>'; to manually catalog the archived redo logs.

Now you are ready to run an online backup of the Oracle database, using any of the following methods:

Backup Methods • Schedule a backup of an existing Oracle backup specification using the Data Protector Scheduler. See “Scheduling a Backup” on page 58.

•Start an interactive backup of an existing Oracle backup specification using the Data Protector GUI or the Data Protector CLI. See “Running an Interactive Backup” on page 60.

Chapter 1

57