Oracle Database 11 g - Online Public Access Catalog

308 CHAPTER 6 ■ BACKUP AND RECOVERYConfiguring RMAN Without a Database ConnectionYou can now connect to any database in a Data Guard setup and make persistent RMAN configurationchanges for any other standby site in the Data Guard configuration. That is, you don’thave to connect to the particular database you’re making RMAN configuration changes to,unlike in the previous releases. The new for db_unique_name clause, which you can use withthe configure, show, list, and report schema commands, makes it possible for you to view andmake changes to the persistent RMAN configuration for a database without connecting to thatdatabase using the keyword target. Most of the RC_* views, such as the RC_DATAFILE and RC_RMAN_OUTPUT views, now contain a new column named DB_UNIQUE_NAME that relates aspecific row to a standby site.Viewing Configuration InformationYou can view configuration information configuration by using the db_unique_name option of theshow command. You must be connected to a recovery catalog and any target database that ismounted or open in order to use the for db_unique_name clause. You can also use this optionafter executing the set dbid command. Here’s an example showing how to use the for db_unique_name option:RMAN> show for db_unique_name ;The previous command will show the persistent RMAN configuration settings for the siteyou specify with the site_name clause. You can similarly use the for db_unique_name option aspart of the list, report, and show schema commands, as shown here:RMAN> list for db_unique_name ;RMAN> report for db_unique_name ;RMAN> report schema for db_unique_name ;The for db_unique_name clause isn’t applicable to just a single site. You can use any of thecommands listed in this section—show, list, report, and report schema with the for db_unique_name option and the all clause—to view the configuration or other information for all sites.That is, you just replace the site_name clause with the all clause to make the command applyto all sites. For example, to view the current persistent configuration settings set for all sites inyour Data Guard configuration, issue the following command:RMAN> show for db_unique_name all;You can use the list, report, and report schema commands in the same way.Making Configuration Changes for a SiteUse the for db_unique_name clause of RMAN’s configure command to make persistent configurationchanges to a specific standby site, without actually connecting to it. The for db_unique_name clause leads RMAN to automatically connect to the specified standby site and update itscontrolfile with the new configuration changes.If you use the for db_unique_name clause with the all option instead of the site_name option,RMAN will connect to all databases registered in the recovery catalog and will update theircontrolfiles with the new settings.