About performing a DBA-initiated backup job for Oracle

A Database Administrator (DBA) can initiate a backup or restore operation for Oracle from the RMAN console. Example scripts for backup and restore operations that you can run from the RMAN console are installed to the following location:

\Program Files\Symantec\Backup Exec\scripts\Oracle

Refer to your Oracle documentation for more information on using the RMAN console.

Review the following notes before initiating backup jobs for Oracle from the RMAN console:

Make sure that you have completed all of the preparations for configuring the Oracle Agent.

See Configuring the Oracle Agent on Windows computers.
The channel is not released if the RMAN console is not exited, or if a new manual channel is not allocated on that console.

See Troubleshooting the Oracle Agent.

During a DBA-initiated backup job, the control file and information that are required for you to browse DBA-initiated backup sets from the Backup Exec Administration Console are not backed up by default.

Caution:

The SKIP INACCESSIBLE option is available in RMAN to skip corrupt data and log files. Jobs that include this option may complete successfully, but it is likely that if this data is restored, the database will be in an inoperable state. The SKIP INACCESSIBLE option is not available for media server operations. If a backup job encounters corrupt data or log files, the job fails. Symantec recommends that you do not use this option.

In a CASO environment, the destination device that you select in the DBA-initiated job template must be locally attached to the central administration server.

If the destination device includes a device pool, all devices in the pool must be locally attached to the central administration server.