1 |
3 |
4 |
• |
Database Name: Name of the selected database as identified in the NAME column of the sys.v$database v$ table. |
• |
DBID: Oracle® DBID for the selected database. DBID is the internal, uniquely generated number that differentiates databases and is required during the disaster recovery process. |
• |
Oracle Version: Oracle version or release of the selected database. When the selected database is the Oracle Enterprise Edition, this information is also displayed. If the selected database is any other edition of Oracle, only the Oracle version is displayed. |
• |
NLS_LANG: Displays the default language of the database. This language is used for messages, day and month names, symbols for AD, BC, a.m., and p.m., and the default sorting mechanism. |
• |
Flash Recovery Area Destination: When FRA is enabled, displays the destination of the FRA. |
• |
Flashback Database Enabled: Indicates YES if the Flashback Database feature is enabled or NO if not. |
• |
Real Application Clusters: Displays TRUE if the instance is part of multi-instance RAC environment or FALSE if the instance is a single-instance environment. |
• |
Block Media Recovery: Displays TRUE if Block Media Recovery is available for the selected database and is based on the Oracle Edition of the database. |
• |
Block Change Tracking: Displays ENABLED if Block Change Tracking has been enabled for the database or DISABLED if not. |
• |
Control File Autobackup: Displays ON if Control File Autobackups have been enabled for the database or OFF if not. |
• |
Log Mode: Displays ARCHIVELOG if the database has automatic archiving of the redo logs enabled or NOARCHIVELOG if not. |
The plug-in provides a feature to run a script containing RMAN commands on completion of a backup job. For example, you can use this feature to perform an RMAN Repository crosscheck; this crosscheck ensures that data about backups in the RMAN Repository are synchronized with corresponding data in the NetVault Database by running a post-backup script that contains the appropriate RMAN commands. This functionality is designed for Oracle® DBAs with advanced RMAN and scripting experience.
1 |
3 |
4 |
b |
5 |
On the Add RMAN Post-Backup Script dialog box, enter the script details: |
• |
Script Name: Enter a name for the post-backup script. The script name must not contain the following characters: |
• |
• |
Script: Enter the RMAN commands, including the connection strings required for connecting to the target, Catalog, or auxiliary database used in the script. |
• |
Use ‘catalog’/Use ‘nocatalog’: Select whether the script connects to the Catalog with these options. |
6 |
Click Save to store the script and close the dialog box. |
1 |
Open the database node, and double-click the script listed beneath the Post-Backup Scripts node. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center