13 Managing the Recovery Catalog</titl e> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="Content-Language" content="EN"> <meta h ttp-equiv="Content-Style-Type" content="text/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta name="robo ts" content="all" scheme="http://www.robotstxt.org/"> <meta name="doctitle" content="Oracle® Database Backup and Recovery Advance d User's Guide 10g Release 1 (10.1)"> <meta name="partno" content="B10734-01"> <meta name="docid" content="BRADV"> <link rel="Start" href="../../index.htm" title="Home" type="text/html"> <link rel="Copyright" href="../../dcommon/html/cpyr.htm" title="Copyright" type ="text/html"> <link rel="Stylesheet" href="../../dcommon/css/doccd.css" title="Default" type="text/css"> <link rel="Contents" href="t oc.htm" title="Contents" type="text/html"> <link rel="Index" href="index.htm" title="Index" type="text/html"> <link rel="Prev" href=" rcmasm.htm" title="Previous" type="text/html"> <link rel="Next" href="rcmtunin.htm" title="Next" type="text/html"> <link rel="alterna te" href="../b10734.pdf" title="PDF version" type="application/pdf"> </head> <body> <div class="header"> <p><a name="top" id="top" hr ef="#BEGIN">Skip Headers</a></p> <table summary="" cellspacing="0" cellpadding="0" width="100%"> <tr> <td align="left" valign="top">< font color="#330099" face="Helvetica, Arial, sans-serif"><strong>Oracle® Database Backup and Recovery Advanced User's Guide<br> 1 0<i>g</i> Release 1 (10.1)</strong><br> Part Number B10734-01</font></td> <td valign="bottom" align="right"> <table summary="" cells pacing="0" cellpadding="0" width="270"> <tr> <td align="center" valign="top"><a href="../../index.htm"><img src="../../dcommon/gifs/p rodicon.gif" alt="Go to Documentation Home" border="0"><br> <font size="-2">Home</font></a></td> <td align="center" valign="top"><a h ref="../../nav/portal_3.htm"><img src="../../dcommon/gifs/bookicon.gif" alt="Go to Book List" border="0"><br> <font size="-2">Book Li st</font></a></td> <td align="center" valign="top"><a href="toc.htm"><img src="../../dcommon/gifs/conticon.gif" alt="Go to Table of C ontents" border="0"><br> <font size="-2">Contents</font></a></td> <td align="center" valign="top"><a href="index.htm"><img src="../.. /dcommon/gifs/indxicon.gif" alt="Go to Index" border="0"><br> <font size="-2">Index</font></a></td> <td align="center" valign="top">< a href="../../mix$101/b12039/toc.htm"><img src="../../dcommon/gifs/mix.gif" alt="Go to Master Index" border="0"><br> <font size="-2"> Master Index</font></a></td> <td align="center" valign="top"><a href="../../dcommon/html/feedback.htm"><img src="../../dcommon/g ifs/feedback.gif" alt="Go to Feedback page" border="0"><br> <font size="-2">Feedback</font></a></td></tr></table></td></tr></table> < hr> <table summary="layout table" cellspacing="0" cellpadding="0" width="100%"> <tr> <td align="left" valign="top"> <table summary="l ayout table" cellspacing="0" cellpadding="0" align="left" width="90"> <tr> <td align="center" valign="top"><a href="rcmasm.htm"><img src="../../dcommon/gifs/larrow.gif" alt="Go to previous page" border="0"><br> <font size="-2">Previous</font></a></td> <td align="cen ter" valign="top"><a href="rcmtunin.htm"><img src="../../dcommon/gifs/rarrow.gif" alt="Go to next page" border="0"><br> <font size="- 2">Next</font></a></td></tr></table></td> <td align="right" valign="top"><a href="../b10734.pdf"><font size="-2">View PDF</font></a>< /td></tr></table> <a name="BEGIN"></a></div> <div class="IND"> <a name="1011348"></a>  < h1 class="Title"><font face="Arial, Helvetica, sans-serif" color="#330099">13<br> <a name="BRADV015">Managing the Recovery Catalog</ a></font></h1>  <a name="1006088"></a> <p class="BP">This chapter describes how to manage an RMAN recovery catalog, which holds RMAN repository data for one or more databases in a separate database schema, in addition to using the control files of the databases.</p> <a name="1009171"></a> <p class="BP">This chapter contains these topics:</p> <ul class="LB1"> <li class="LB1" typ e="disc"><a name="1006092"></a><a href="rcmrepos.htm#1013601">Creating a Recovery Catalog</a></li> <li class="LB1" type="disc"><a nam e="1006096"></a><a href="rcmrepos.htm#1006296">Managing Target Database Records in the Recovery Catalog</a></li> <li class="LB1" type ="disc"><a name="1006100"></a><a href="rcmrepos.htm#1008662">Resynchronizing the Recovery Catalog</a></li> <li class="LB1" type="disc "><a name="1006104"></a><a href="rcmrepos.htm#1006679">Working with RMAN Stored Scripts in the Recovery Catalog</a></li> <li class="L B1" type="disc"><a name="1006108"></a><a href="rcmrepos.htm#1011154">Managing the Control File When You Use a Recovery Catalog</a></l i> <li class="LB1" type="disc"><a name="1006112"></a><a href="rcmrepos.htm#1006860">Backing Up and Recovering the Recovery Catalog</a ></li> <li class="LB1" type="disc"><a name="1006116"></a><a href="rcmrepos.htm#1006981">Exporting and Importing the Recovery Catalog< /a></li> <li class="LB1" type="disc"><a name="1006120"></a><a href="rcmrepos.htm#1007068">Increasing Availability of the Recovery Cat alog</a></li> <li class="LB1" type="disc"><a name="1008646"></a><a href="rcmrepos.htm#1010971">Querying the Recovery Catalog Views</a ></li> <li class="LB1" type="disc"><a name="1008933"></a><a href="rcmrepos.htm#1008889">Determining the Schema Version of the Recover y Catalog</a></li> <li class="LB1" type="disc"><a name="1013583"></a><a href="rcmrepos.htm#1008886">Upgrading the Recovery Catalog</a ></li> <li class="LB1" type="disc"><a name="1013597"></a><a href="rcmrepos.htm#1007187">Dropping the Recovery Catalog</a> <div align ="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table t o format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1013589"></a><f ont face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1013595"></a> <p class="NB"><em class= "Italic"><a class="xlinkSRC BRBSC007" href="../../server$101/b10735/maint.htm#BRBSC007">Oracle Database Backup and Recovery Basics</a ></em> to learn how to manage the RMAN control file repository without a recovery catalog</p></td></tr></table></div></li></ul> <a na me="1013601"></a>  <h2 class="H1"><a name="BRADV179"><font face="Arial, Helvetica, sans-serif" color="#330099" >Creating a Recovery Catalog</font></a></h2>  <a name="1006144"></a> <p class="BP">Creating a recovery catalog is a th ree-step process: you must configure the database that will contain the recovery catalog, create the recovery catalog owner, and then create the recovery catalog itself.</p> <a name="1006175"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Configuring the Recovery Catalog Database</font></h3>  <a name="1006176"></a> <p class="BP ">When you use a recovery catalog, RMAN requires that you maintain a recovery catalog schema. The recovery catalog is stored in the d efault tablespace of the schema. Note that <code>SYS</code> cannot be the owner of the recovery catalog.</p> <a name="1006177"></a> <p class="BP">Decide which database you will use to install the recovery catalog schema, and also how you will back up this database. You should not install the catalog in the target database: this tactic defeats the purpose of the catalog. Also, decide whether to o perate the catalog database in <code>ARCHIVELOG</code> mode, which is recommended.</p> <a name="1006178"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Planning the Size of the Recovery Catalog Schema</font></h4 >  <a name="1006179"></a> <p class="BP">You must allocate space to be used by the catalog schema. The size of the reco very catalog schema depends upon the number of databases monitored by the catalog, and the number and size of RMAN scripts stored in the catalog. The schema also grows as the number of archived redo log files and backups for each database grows.</p> <a name="1006183 "></a> <p class="BP">For an example, assume that the <code>trgt</code> database has 100 files, and you back up the database once a d ay, producing 50 backup sets containing 1 backup piece each. If you assume that each row in the backup piece table uses the maximum a mount of space, then one daily backup will consume less than 170 KB in the recovery catalog. So, if you back up once a day for a year , then the total storage in this period is about 62 MB. Assume approximately the same amount for archived logs. Hence, the worst case is about 120 MB for a year for metadata storage.</p> <a name="1012183"></a> <p class="BP">For a more typical case in which only a p ortion of the backup piece row space is used, 15 MB for each year is a realistic estimate.</p> <a name="1012201"></a> <p class="BP"> If you plan to register multiple databases in your recovery catalog, remember to add up the space required for each one based on the previous calculation to arrive at a total size for the default tablespace of the recovery catalog schema.</p> <a name="1006184"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Allocating Disk Space for the Recove ry Catalog Database</font></h4>  <a name="1006185"></a> <p class="BP">If you are creating your recovery catalog in an already-existing database, add enough room to hold the default tablespace to the recovery catalog schema. If you are creating a new d atabase to hold your recovery catalog, then, in addition to the space for the recovery catalog schema itself, you must allow space fo r other files in the recovery catalog database:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006186"></a><code>SYSTEM</ code> tablespace</li> <li class="LB1" type="disc"><a name="1006187"></a>Temporary tablespaces</li> <li class="LB1" type="disc"><a nam e="1006188"></a>Rollback segment tablespaces</li> <li class="LB1" type="disc"><a name="1006189"></a>Online redo log files</li></ul> < a name="1006191"></a> <p class="BP">Most of the space used in the recovery catalog database is devoted to supporting tablespaces, fo r example, the <code>SYSTEM</code>, temporary, and rollback or undo tablespaces. <a href="rcmrepos.htm#1006198">Table 13-1</a> d escribes typical space requirements.</p> <a name="1006225"></a> <h5 class="TT"><a name="1006225"></a><a name="1006198"></a> <strong> <font face="Arial, Helvetica, sans-serif"><em>Table 13-1 <strong class="Bold">Typical Recovery Catalog Space Requirements for 1 Year< /strong></em></font></strong></h5> <table summary="" class="RuleFormal" border="1" width="100%" cellpadding="3" cellspacing="0" dir=" ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="1006202"></a> <font f ace="Arial, Helvetica, sans-serif"><strong>Type of Space</strong></font></th> <th class="Formal" align="left" valign="bottom" scope=" col"><a name="1006204"></a> <font face="Arial, Helvetica, sans-serif"><strong>Space Requirement</strong></font></th></tr></thead> <tb ody> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006206"></a> <p class="TB"><code>SYSTEM</code> table space</p></td> <td class="Formal"><a name="1006208"></a> <p class="TB">90 MB</p></td></tr> <tr class="Formal" align="left" valign="t op"> <td class="Formal"><a name="1006210"></a> <p class="TB">Temp tablespace</p></td> <td class="Formal"><a name="1006212"></a> <p class="TB">5 MB</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006214"></a> <p class="TB"> Rollback or undo tablespace</p></td> <td class="Formal"><a name="1006216"></a> <p class="TB">5 MB</p></td></tr> <tr class="Formal" a lign="left" valign="top"> <td class="Formal"><a name="1006218"></a> <p class="TB">Recovery catalog tablespace</p></td> <td class="Fo rmal"><a name="1006220"></a> <p class="TB">15 MB for each database registered in the recovery catalog</p></td></tr> <tr class="Forma l" align="left" valign="top"> <td class="Formal"><a name="1006222"></a> <p class="TB">Online redo logs</p></td> <td class="Formal">< a name="1006224"></a> <p class="TB">1 MB each (3 groups, each with 2 members)</p></td></tr></tbody></table> <a name="1006230"></a> <div align="center"> <table class="NoteWarn" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layo ut table to format a warning" title="This is a layout table to format a warning"> <tr class="NoteWarn"> <td class="NoteWarn"> <hr> <a name="1006228"></a><font face="Arial, Helvetica, sans-serif"><strong class="NHW">Caution:</strong></font> <a name="1006229"></a> <p class="NB">Ensure that the recovery catalog and target databases do <em class="Italic">not</em> reside on the same disk. If a disk c ontaining both your recovery catalog and your target databases failed, your recovery process would be much more complicated. If possi ble, take other measures as well to eliminate common points of failure between your recovery catalog database and the databases you a re backing up.</p> <hr></td></tr></table></div> <a name="1006232"></a>  <h3 class="H2"><font face="Arial, Helv etica, sans-serif" color="#330099">Creating the Recovery Catalog Owner</font></h3>  <a name="1006233"></a> <p class="B P">After choosing the recovery catalog database and creating necessary space, you are ready to create the owner of the recovery catal og and grant this user necessary privileges.</p> <a name="1006234"></a> <p class="BP">Assume the following background information fo r the instructions in the following sections:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006235"></a>User <code>SYS</ code> with password <code>oracle</code> has <code>SYSDBA</code> privileges on the recovery catalog database <code>catdb</code>.</li> <li class="LB1" type="disc"><a name="1006236"></a>A tablespace called <code>tools</code> in the recovery catalog database <code>catdb </code> stores the recovery catalog. Note that to use an RMAN reserved word as a tablespace name, you must enclose it in quotes and p ut it in uppercase. (Refer to <em class="Italic"><a class="olinkSRC RCMRF" href="../../server$101/b10770/toc.htm">Oracle Database Rec overy Manager Reference</a></em> for a list of RMAN reserved words.)</li> <li class="LB1" type="disc"><a name="1006242"></a>A tablesp ace called <code>temp</code> exists in the recovery catalog database.</li> <li class="LB1" type="disc"><a name="1006243"></a>The data base is configured in the same way as all normal databases, for example, <code>catalog.sql</code> and <code>catproc.sql</code> have s uccessfully run.</li></ul> <a name="1006245"></a> <p class="BP"><strong class="Bold">To create the recovery catalog schema in the re covery catalog database:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006246"></a>Start SQL*Pl us and then connect with administrator privileges to the database containing the recovery catalog. For example, enter: <pre class="C E1"><a name="1006247"></a>CONNECT SYS/oracle@catdb AS SYSDBA <a name="1006248"></a> </pre> </li> <li class="LN1" type="1" value="2">< a name="1006249"></a>Create a user and schema for the recovery catalog. For example, enter: <pre class="CE1"><a name="1006250"></a>C REATE USER rman IDENTIFIED BY cat <a name="1006251"></a> TEMPORARY TABLESPACE temp <a name="1006252"></a> DEFAULT TABLESPACE tools <a name="1006253"></a> QUOTA UNLIMITED ON tools; <a name="1006254"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1 006255"></a>Grant the <code>RECOVERY_CATALOG_OWNER</code> role to the schema owner. This role provides the user with all privileges r equired to maintain and query the recovery catalog. <pre class="CE1"><a name="1006256"></a>SQL> GRANT RECOVERY_CATALOG_OWNER TO r man; </pre> </li></ol> <a name="1006261"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color=" #330099">Creating the Recovery Catalog</font></h3>  <a name="1006262"></a> <p class="BP">After creating the catalog ow ner, create the catalog tables with the RMAN <code>CREATE</code> <code>CATALOG</code> command. The command creates the catalog in the default tablespace of the catalog owner.</p> <a name="1006263"></a> <p class="BP"><strong class="Bold">To create the recovery catal og:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006265"></a>Connect to the database that will contain the catalog as the catalog owner. For example, enter the following from the operating system command line: <pre class="CE1" ><a name="1006266"></a>% rman CATALOG rman/cat@catdb <a name="1006267"></a> </pre> <a name="1006268"></a> <p class="BP1">You can als o connect from the RMAN prompt:</p> <pre class="CE1"><a name="1006269"></a>% rman <a name="1006270"></a>RMAN> CONNECT CATALOG rman /cat@catdb <a name="1006271"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1006272"></a>Run the <code>CREATE CATALOG< /code> command to create the catalog. The creation of the catalog can take several minutes. If the catalog tablespace is this user's default tablespace, then you can run this command: <pre class="CE1"><a name="1006273"></a>CREATE CATALOG; <a name="1006274"></a> </p re> <a name="1006275"></a> <p class="BP1">If you specify the tablespace name in the <code>CREATE</code> <code>CATALOG</code> command , <em class="Italic">and</em> if the tablespace name is an RMAN reserved word, then it <em class="Italic">must</em> be uppercase and enclosed in quotes. For example:</p> <pre class="CE1"><a name="1006276"></a>CREATE CATALOG TABLESPACE 'CATALOG'; <a name="1006277"></ a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1006278"></a>Optionally, start SQL*Plus and query the recovery catalog to see which tables were created: <pre class="CE1"><a name="1006279"></a>SQL> SELECT TABLE_NAME FROM USER_TABLES; </pre> <a name=" 1006294"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary=" This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"> <a name="1006282"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1006288"></a> <p class="NB"><em class="Italic"><a class="olinkSRC SQLRF" href="../../server$101/b10759/toc.htm">Oracle Database SQL Reference</a></ em> for the SQL syntax for the <code>GRANT</code> and <code>CREATE</code> <code>USER</code> statements, and <em class="Italic"><a cla ss="xlinkSRC RCMRF117" href="../../server$101/b10770/rcmsynta19a.htm#RCMRF117">Oracle Database Recovery Manager Reference</a></em> fo r <code>CREATE CATALOG</code> command syntax</p></td></tr></table></div></li></ol> <a name="1006296"></a>  <h2 class="H1"><a name="BRADV11001"><font face="Arial, Helvetica, sans-serif" color="#330099">Managing Target Database Records in the Re covery Catalog</font></a></h2>  <a name="1006297"></a> <p class="BP">This section describes how to register, unregiste r, and reset target database records in the recovery catalog.</p> <a name="1006312"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Registering a Database in the Recovery Catalog</font></h3>  <a nam e="1006314"></a> <p class="BP">The first step in using a recovery catalog with a target database is registering the database in the recovery catalog. Use the following procedure:</p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1010271"></a >After making sure the recovery catalog database is open, connect RMAN to the target database and recovery catalog database. For exam ple, issue the following to connect to the catalog database <code>catdb</code> as user <code>rman</code> (who owns the catalog schema ): <pre class="CE1"><a name="1010272"></a>% rman TARGET / CATALOG rman/cat@catdb <a name="1010273"></a> </pre> </li> <li class="LN1 " type="1" value="2"><a name="1010274"></a>If the target database is not mounted, then mount or open it: <pre class="CE1"><a name="1 010275"></a>RMAN> STARTUP MOUNT; <a name="1010494"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1010496"></a>Regi ster the target database in the connected recovery catalog: <pre class="CE1"><a name="1012260"></a>RMAN> REGISTER DATABASE; <a na me="1012261"></a> </pre> <a name="1012262"></a> <p class="BP1">RMAN creates rows in the catalog tables to contain information about the target database, then copies all pertinent data about the target database from the control file into the catalog, synchronizing t he catalog with the control file.</p></li></ol> <a name="1010283"></a> <p class="BP">Verify that the registration was successful by running <code>REPORT</code> <code>SCHEMA</code>:</p> <pre class="CE1"><a name="1010284"></a>RMAN> REPORT SCHEMA; <a name="1010285" ></a> <a name="1010286"></a>Report of database schema <a name="1010287"></a>File K-bytes Tablespace RB segs Datafile Name <a name="1010288"></a>---- ---------- ---------------- ------- ------------------- <a name="1010289"></a>1 307200 SYSTEM NO /oracle/oradata/trgt/system01.dbf <a name="1010290"></a>2 20480 UNDOTBS YES /oracle/oradata/trgt/undo tbs01.dbf <a name="1010291"></a>3 10240 CWMLITE NO /oracle/oradata/trgt/cwmlite01.dbf <a name="1010292"></a>4 10240 DRSYS NO /oracle/oradata/trgt/drsys01.dbf <a name="1010293"></a>5 10240 EXAMPLE NO /oracle/oradata/trgt/example01.dbf <a name="1010294"></a>6 10240 INDX NO /oracle/oradata/trgt/indx01.dbf <a name="1010295"></a>7 10240 TOOLS NO /oracle/oradata/trgt/tools01.dbf <a name="1010296"></a>8 10240 U SERS NO /oracle/oradata/trgt/users01.dbf <a name="1010297"></a> </pre> <a name="1010269"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Cataloging Older Files in the Recovery Catalog</font></h4>  <a name="1010621"></a> <p class="BP">If you have datafile copies, backup pieces or archive logs on disk, you can cata log them in the recovery catalog using the CATALOG command. When using a recovery catalog, cataloging older backups that have aged ou t of the control file lets RMAN use the older backups during restore operations. For example:</p> <pre class="CE"><a name="1010434">< /a>RMAN> CATALOG DATAFILECOPY '/disk1/old_datafiles/01_01_2003/users01.dbf'; <a name="1010435"></a>RMAN> CATALOG ARCHIVELOG '/d isk1/arch_logs/archive1_731.dbf', <a name="1013432"></a> '/disk1/arch_logs/archive1_732.dbf'; <a name="1012918"></a>RMAN> CAT ALOG BACKUPPIECE '/disk1/backups/backup_820.bkp'; <a name="1010436"></a> </pre> <a name="1010437"></a> <p class="BP">You can also c atalog multiple backup files in a directory at once, using the <code>CATALOG START WITH</code> command, as shown in this example:</p> <pre class="CE"><a name="1013033"></a>RMAN> CATALOG START WITH '/disk1/backups/'; <a name="1013040"></a> </pre> <a name="1013013 "></a> <p class="BP">RMAN lists the files to be added to the RMAN repository and prompts for confirmation before adding the backups.< /p> <a name="1013419"></a> <p class="BP">Be careful when creating your prefix for <code>CATALOG START WITH</code>. RMAN scans all pa ths for all files on disk which begin with your specified prefix. The wrong prefix may include more files than you intend. For exampl e, a group of directories <code>/disk1/backups</code> , <code>/disk1/backups-year2003</code>, <code>/disk1/backupsets</code>, and <co de>/disk1/backupsets/test</code> and so on, all contain backup files. The command</p> <pre class="CE"><a name="1013317"></a>RMAN> CATALOG START WITH '/disk1/backups'; <a name="1013342"></a> </pre> <a name="1013375"></a> <p class="BP">catalogs all files in all o f these directories, because <code>/disk1/backups</code> is a prefix for the paths for all of these directories. In order to catalog only backups in the <code>/disk1/backups</code> directory, the correct command would be:</p> <pre class="CE"><a name="1013376"></a>RM AN> CATALOG START WITH '/disk1/backups/'; <a name="1013335"></a> </pre> <a name="1013260"></a> <p class="BP">To determine whether log records have aged out of the control file, compare the number of logs on disk with the number of records in <code>V$ARCHIVED_LOG </code>.</p> <a name="1010586"></a>  <h5 class="H4"><font face="Arial, Helvetica, sans-serif" color="#330099"> Cataloging Oracle7 Datafile Copies in the Recovery Catalog</font></h5>  <a name="1010592"></a> <p class="BP">In genera l, only Oracle8 and higher files can be cataloged. Datafile copies from Oracle7 databases can also be cataloged, if they do not requi re the application of Oracle7 redo before they can be opened. Datafile copies made in the following circumstances satisfy this requir ement:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1010438"></a>Datafile copies made when the database was shut down co nsistently. The database must not have been opened again before migration to a higher version of Oracle.</li> <li class="LB1" type="d isc"><a name="1010439"></a>Datafile copies made after a tablespace became offline normal or read-only. The tablespaces must not have been brought online or made read/write again before migration to a higher version of Oracle. <p><a name="1012318"></a></p> <div alig n="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1012304"></a>< font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1012305"></a> <ul class="NL"> <li cla ss="NL" type="disc"><a name="1012311"></a><em class="Italic"><a class="xlinkSRC RCMRF141" href="../../server$101/b10770/rcmsynta45.ht m#RCMRF141">Oracle Database Recovery Manager Reference</a></em> for <code>REGISTER</code> syntax</li> <li class="NL" type="disc"><a n ame="1012317"></a><em class="Italic"><a class="olinkSRC UPGRD" href="../../server$101/b10763/toc.htm">Oracle Database Upgrade Guide</ a></em> for issues relating to database migration</li></ul></td></tr></table></div></li></ul> <a name="1006385"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Registering Multiple Databases in a Recovery Catalog </font></h4>  <a name="1006387"></a> <p class="BP">You can register multiple target databases in a single recovery cat alog, if they do not have duplicate DBIDs. RMAN uses the DBID to distinguish one database from another.</p> <a name="1012410"></a> < p class="BP">In general, if you use the DUPLICATE RMAN command or CREATE DATABASE SQL statement, the database created is assigned a u nique DBID. If you create a database by some other means, such as a user-managed copy, then the new database may have the same DBID a s the one from which it was copied. You will not be able to register both databases in the same recovery catalog until you change the DBID of the copied database using the <code>DBNEWID</code> utility.</p> <a name="1012405"></a> <p class="BP">Note that you can regi ster a single target databases in multiple recovery catalogs.</p> <a name="1006419"></a> <div align="center"> <table class="NoteAlso " border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1006393"></a><font face="Arial, Helvetica, sans- serif"><strong class="NH">See Also:</strong></font> <a name="1006394"></a> <ul class="NL"> <li class="NL" type="disc"><a name="10064 06"></a><em class="Italic"><a class="xlinkSRC RCMRF126" href="../../server$101/b10770/rcmsynta28.htm#RCMRF126">Oracle Database Recove ry Manager Reference</a></em> for <code>DUPLICATE</code> syntax</li> <li class="NL" type="disc"><a name="1006412"></a><a class="olink SRC SUTIL" href="../../server$101/b10825/toc.htm"><em class="Italic">Oracle Database Utilities</em></a> to learn how to use the <code >DBNEWID</code> utility to change the DBID</li> <li class="NL" type="disc"><a name="1006418"></a><em class="Italic"><a class="olinkSR C UPGRD" href="../../server$101/b10763/toc.htm">Oracle Database Upgrade Guide</a></em> for issues relating to database migration</li> </ul></td></tr></table></div> <a name="1006421"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Unregistering a Target Database from the Recovery Catalog</font></h3>  <a name="1006423"></a> <p clas s="BP">RMAN can unregister a database as well as register it. The <code>UNREGISTER DATABASE</code> command is used to unregister a da tabase from the recover catalog.</p> <a name="1012428"></a> <p class="BP">Make sure this procedure is what you intend, because if yo u make a mistake, then you must re-register the database. You will lose any RMAN repository records older than the <code>CONTROLFILE_ RECORD_KEEP_TIME</code> setting in the target database control file.</p> <a name="1006424"></a> <p class="BP"><strong class="Bold">T o unregister a database:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006425"></a>Start RMAN a nd connect to the target database. For example, enter: <pre class="CE1"><a name="1006426"></a>% rman TARGET / CATALOG rman/cat@catdb <a name="1006427"></a> <a name="1006428"></a>connected to target database: RDBMS (DBID=1237603294) <a name="1006429"></a>connected t o recovery catalog database <a name="1006430"></a> </pre> <a name="1012591"></a> <p class="BP1">Make a note of the DBID as displayed by RMAN. If there is more than one database registered in the recovery catalog, you will need the DBID to uniquely identify the data base.</p> <a name="1012419"></a> <p class="BP1">It is not necessary to connect to the target database, but if you do not, then you m ust specify the name of the target database in the <code>UNREGISTER</code> command. If more than one database has the same name in th e recovery catalog, then you must create a RUN block around the command and use SET DBID to set the DBID for the database .</p></li> <li class="LN1" type="1" value="2"><a name="1006433"></a>It may be useful to list all of the backups recorded in the recovery catalog using <code>LIST BACKUP SUMMARY</code> and <code>LIST COPY SUMMARY</code>.</li> <li class="LN1" type="1" value="3"><a name="1008289" ></a>If your intention is to actually delete all backups of the database completely, rather than just removing the database from the recovery catalog and relying on the control file to store the RMAN repository for this database, then run <code>DELETE</code> stateme nts to delete all existing physical backupsets and image copies. For example: <pre class="CE1"><a name="1006446"></a>DELETE BACKUP D EVICE TYPE sbt; <a name="1006447"></a>DELETE BACKUP DEVICE TYPE DISK; <a name="1012604"></a>DELETE COPY; <a name="1006448"></a> </pre > <a name="1006449"></a> <p class="BP1">RMAN will list the backups that it intends to delete and prompt for confirmation before dele ting them.</p></li> <li class="LN1" type="1" value="4"><a name="1006451"></a>Run the <code>UNREGISTER</code> <code>DATABASE</code> co mmand. For example: <pre class="CE1"><a name="1006452"></a>UNREGISTER DATABASE; </pre> </li></ol> <a name="1006454"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Resetting a Database Incarnation in the Recovery Catalog</font></h3>  <a name="1006455"></a> <p class="BP">When you run either the RMAN command or the SQL statement < code>ALTER</code> <code>DATABASE</code> <code>OPEN</code> <code>RESETLOGS</code>, you create a new incarnation of the database. You c an access a record of the new incarnation in the <code>V$DATABASE_INCARNATION</code> view of the target database.</p> <a name="100645 6"></a> <p class="BP">If you run the RMAN command or the SQL statement <code>ALTER</code> <code>DATABASE</code> <code>OPEN</code> <c ode>RESETLOGS</code>, then a new database incarnation record is automatically created in the recovery catalog. The database also impl icitly and automatically issues a <code>RESET</code> <code>DATABASE</code> command, which specifies that this new incarnation of the database is the current incarnation. All subsequent backups and log archiving done by the target database is associated with the new database incarnation.</p> <a name="1006461"></a> <p class="BP">In the rare situation in which you wish to restore backups of a prior incarnation of the database, use the <code>RESET DATABASE TO INCARNATION</code> <em><code>key</code></em> command to change the curr ent incarnation to an older incarnation. For example, if you accidentally drop a table immediately after the most recent <code>RESETL OGS</code>, then you may want to recover the database to just before the time of the most recent <code>RESETLOGS</code> and then open it with the <code>RESETLOGS</code> option, thereby creating a new incarnation.</p> <a name="1006466"></a> <a name="1006467"></a> <p class="BP"><strong class="Bold">To reset the recovery catalog to an older incarnation:</strong></p> <ol class="LN1" type="1"> <li cl ass="LN1" type="1" value="1"><a name="1012819"></a>Determine the incarnation key of the desired database incarnation. Obtain the inca rnation key value by issuing a <code>LIST</code> command: <pre class="CE1"><a name="1012832"></a>LIST INCARNATION OF DATABASE trgt; <a name="1012833"></a> <a name="1012834"></a>List of Database Incarnations <a name="1012835"></a>DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time <a name="1012836"></a>------- ------- ------- ------ ------- ---------- -------- -- <a name="1012837"></a>1 2 TRGT 1224038686 PARENT 1 02-JUL-02 <a name="1012838"></a>1 582 TRGT 1224038686 CURRENT 59727 10-JUL-02 <a name="1012839"></a> <a name="1012827"></a> </pre> <a name="1012828" ></a> <p class="BP1">The incarnation key is listed in the "Inc Key" column.</p></li> <li class="LN1" type="1" value="2"><a name="1012 611"></a>Reset the database to the old incarnation. For example, enter: <pre class="CE1"><a name="1006478"></a>RESET DATABASE TO INC ARNATION 2; <a name="1006479"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1006480"></a>If the control file of the p revious incarnation is available and mounted, then skip to step 6 of this procedure. Otherwise, shut down the database and start it w ithout mounting. For example: <pre class="CE1"><a name="1006481"></a>SHUTDOWN IMMEDIATE <a name="1006482"></a>STARTUP NOMOUNT <a nam e="1006483"></a> </pre> </li> <li class="LN1" type="1" value="4"><a name="1006484"></a>Restore a control file from the old incarnatio n. If you have a control file tagged, then specify the tag. Otherwise, you can run the <code>SET</code> <code>UNTIL</code> command, a s in this example: <pre class="CE1"><a name="1006485"></a>RUN <a name="1006486"></a>{ <a name="1006487"></a> SET UNTIL 'SYSDATE-45 '; <a name="1006488"></a> RESTORE CONTROLFILE; # only if current control file is not available <a name="1006489"></a>} <a name="1006 490"></a> </pre> </li> <li class="LN1" type="1" value="5"><a name="1006491"></a>Mount the restored control file: <pre class="CE1"><a name="1006492"></a>ALTER DATABASE MOUNT; <a name="1006493"></a> </pre> </li> <li class="LN1" type="1" value="6"><a name="1006494"></ a>Run <code>RESTORE</code> and <code>RECOVER</code> commands to restore and recover the database files from the prior incarnation, th en open the database with the <code>RESETLOGS</code> option. For example, enter: <pre class="CE1"><a name="1008761"></a>RESTORE DATA BASE; <a name="1008789"></a>RECOVER DATABASE; <a name="1008958"></a>ALTER DATABASE OPEN RESETLOGS; </pre> <a name="1008808"></a> <di v align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1008792" ></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1008799"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF148" href="../../server$101/b10770/rcmsynta50.htm#RCMRF148">Oracle Database Recovery Manager Reference</a></em> for <code>RESET</code> <code>DATABASE</code> syntax, <em class="Italic"><a class="xlinkSRC RCMRF132" href="../../s erver$101/b10770/rcmsynta36.htm#RCMRF132">Oracle Database Recovery Manager Reference</a></em> for <code>LIST</code> syntax</p></td></ tr></table></div></li></ol> <a name="1008811"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" c olor="#330099">Removing Recovery Catalog Records with Status DELETED</font></h3>  <a name="1008666"></a> <p class="BP" >Use the <code>prgrmanc.sql</code> script to remove recovery catalog records with status <code>DELETED</code>. In releases prior to O racle9<em class="Italic">i</em>, RMAN updated recovery catalog records to <code>DELETED</code> status after deleting the physical fil es rather than removing the records.</p> <a name="1008667"></a> <p class="BP">In Oracle9<em class="Italic">i</em> and later, RMAN al ways removes catalog records and never updates them to status <code>DELETED</code>. However, records with status <code>DELETED</code> can appear in the recovery catalog when you upgrade a recovery catalog created prior to Oracle9<em class="Italic">i</em> to the curr ent release. For this special case, you can run the <code>prgrmanc.sql</code> script.</p> <a name="1008668"></a> <p class="BP"><stro ng class="Bold">To remove all backup records with status DELETED:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" val ue="1"><a name="1008669"></a>Start a SQL*Plus session and connect to the recovery catalog. This example connects to the database <cod e>rcat</code> as user <code>rman</code>: <pre class="CE1"><a name="1008670"></a>% sqlplus rman/cat@catdb <a name="1008671"></a> </pr e> </li> <li class="LN1" type="1" value="2"><a name="1008672"></a>Run the script <code>prgrmanc.sql</code> script, which is stored in an operating system specific location (<code>$ORACLE_HOME/rdbms/admin</code> on UNIX): <pre class="CE1"><a name="1008673"></a>SQL&g t; @prgrmanc <a name="1008674"></a> </pre> <a name="1008675"></a> <p class="BP1">The script removes all records with status <code>DE LETED</code> from the recovery catalog.</p></li></ol> <a name="1008662"></a>  <h2 class="H1"><a name="BRADV181 "><font face="Arial, Helvetica, sans-serif" color="#330099">Resynchronizing the Recovery Catalog</font></a></h2>  <a na me="1010798"></a> <p class="BP">When RMAN performs a <strong class="GlossaryTerm">resynchronization</strong>, it compares the recove ry catalog to either the current control file of the target database or a backup control file and updates the recovery catalog with i nformation that is missing or changed. When resynchronizing, RMAN does the following:</p> <ol class="LN1" type="1"> <li class="LN1" t ype="1" value="1"><a name="1010799"></a>Creates a snapshot control file.</li> <li class="LN1" type="1" value="2"><a name="1010800"></ a>Compares the recovery catalog to the snapshot control file.</li> <li class="LN1" type="1" value="3"><a name="1010801"></a>Updates t he recovery catalog with missing or changed information.</li></ol> <a name="1006521"></a> <p class="BP">RMAN performs resynchronizat ions automatically as needed when you execute certain commands, including <code>BACKUP</code>. You can also manually perform a full r esynchronization using the <code>RESYNC CATALOG</code> command.</p> <a name="1010751"></a>  <h3 class="H2"><fo nt face="Arial, Helvetica, sans-serif" color="#330099">Types of Records That Are Resynchronized</font></h3>  <a name="1 010755"></a> <p class="BP"><a href="rcmrepos.htm#1010759">Table 13-2</a> describes the types of records that RMAN resynchronize s.</p> <a name="1010784"></a> <h5 class="TT"><a name="1010784"></a><a name="1010759"></a> <strong><font face="Arial, Helvetica, sans -serif"><em>Table 13-2 <strong class="Bold">Records Updated during a Resynchronization</strong></em></font></strong></h5> <table summ ary="" class="RuleFormal" border="1" width="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="1010763"></a> <font face="Arial, Helvetica, sans-serif"><strong>Rec ords</strong></font></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="1010765"></a> <font face="Arial, Helve tica, sans-serif"><strong>Description</strong></font></th></tr></thead> <tbody> <tr class="Formal" align="left" valign="top"> <td cla ss="Formal"><a name="1010767"></a> <p class="TB">Log history</p></td> <td class="Formal"><a name="1010769"></a> <p class="TB">Creat ed when an online redo log switch occurs.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="101 0771"></a> <p class="TB">Archived redo logs</p></td> <td class="Formal"><a name="1010773"></a> <p class="TB">Associated with archiv ed logs that were created by archiving an online log, copying an existing archived redo log, or restoring an archived redo log backup set. RMAN tracks this information so that it knows which archived logs it should expect to find.</p></td></tr> <tr class="Formal" al ign="left" valign="top"> <td class="Formal"><a name="1010775"></a> <p class="TB">Backup history</p></td> <td class="Formal"><a name= "1010777"></a> <p class="TB">Associated with backup sets, backup pieces, proxy copies, and file copies. The <code>RESYNC CATALOG</co de> command updates these records when a <code>BACKUP</code> command is executed.</p></td></tr> <tr class="Formal" align="left" valig n="top"> <td class="Formal"><a name="1012934"></a> <p class="TB">Incarnation history</p></td> <td class="Formal"><a name="1012936">< /a> <p class="TB">Associated with database incarnations.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Form al"><a name="1010779"></a> <p class="TB">Physical schema</p></td> <td class="Formal"><a name="1010781"></a> <p class="TB">Associate d with datafiles and tablespaces. If the target database is open, then undo segment information is also updated. <a name="1010782"></ a></p> <p class="TB">Physical schema information in the recovery catalog is updated only when the target has the current control file mounted. <a name="1010783"></a></p> <p class="TB">If the target database has mounted a backup control file, a freshly created contro l file, or a control file that is less current than a control file that was seen previously, then physical schema information in the recovery catalog is <em class="Italic">not</em> updated. Physical schema information is also not updated when you use the <code>RESYN C</code> <code>CATALOG</code> <code>FROM</code> <code>CONTROLFILECOPY</code> command.</p></td></tr></tbody></table> <a name="1006544" ></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Full and Partial Resynchroniza tion</font></h3>  <a name="1013642"></a> <p class="BP">Resynchronizations can be full or partial. In a partial resynch ronization, RMAN reads the current control file to update changed information about new backups, new archived logs, and so forth. How ever, RMAN does not resynchronize metadata about the database physical schema: datafiles, tablespaces, redo threads, rollback segment s (only if the database is open), and online redo logs. In a full resynchronization, RMAN updates all changed records, including thos e for the database schema.</p> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="l tr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="N ote"> <hr> <a name="1013645"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="1013646" ></a> <p class="NB">Although RMAN performs partial resynchronizations when using a backup control file, it does not perform full res ynchronizations. A backup control file may not have correct information about the database physical schema, so a full resynchronizati on could update the recovery catalog with incorrect information.</p> <hr></td></tr></table></div> <div align="center"> <table class=" Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="1013649"></a><font face="Arial, Helvetica, san s-serif"><strong class="NH">Note:</strong></font> <a name="1013650"></a> <p class="NB">You can use Oracle Enterprise Manager to perf orm catalog resynchronizations.</p> <hr></td></tr></table></div> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1013653"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH" >See Also:</strong></font> <a name="1013659"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF150" href="../../server.1 01/b10770/rcmsynta52.htm#RCMRF150">Oracle Database Recovery Manager Reference</a></em> for more information about the <code>RESYNC</c ode> command</p></td></tr></table></div> <br> <br> <a name="1013661"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">When Should You Resynchronize?</font></h3>  <a name="1010810"></a> <p class="BP ">RMAN automatically performs full or partial resynchronizations in most situations in which they are needed. Most RMAN commands such as <code>BACKUP</code>, <code>DELETE</code>, and so forth perform a full or partial resynchronization (depending on whether the sche ma metadata has changed) automatically when the target database control file is mounted and the recovery catalog database is availabl e. Thus, you should not need to manually run <code>RESYNC</code> <code>CATALOG</code> very often.</p> <a name="1010743"></a> <p clas s="BP">The following sections describe situations in which a manual resynchronization is required.</p> <a name="1006613"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Resynchronizing When the Recovery Catalog i s Unavailable</font></h4>  <a name="1006614"></a> <p class="BP">If the recovery catalog is unavailable when you issue RMAN commands that cause a partial resynchronization, then open the catalog database later and resynchronize it manually with the <co de>RESYNC CATALOG</code> command.</p> <a name="1006615"></a> <p class="BP">For example, the target database may be in New York while the recovery catalog database is in Japan. You may not want to make daily backups of the target database in <code>CATALOG</code> mod e, to avoid depending on the availability of a geographically distant database. In such a case you could connect to the catalog as of ten as feasible (for example, once each week) and run the <code>RESYNC CATALOG</code> command.</p> <a name="1006616"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Resynchronizing in ARCHIVELOG Mode When You Bac k Up Infrequently</font></h4>  <a name="1006617"></a> <p class="BP">Assume that you do the following:</p> <ul class="L B1"> <li class="LB1" type="disc"><a name="1006618"></a>Run the database in <code>ARCHIVELOG</code> mode</li> <li class="LB1" type="di sc"><a name="1006619"></a>Back up the database infrequently (for example, hundreds of archive logs are archived between database back ups)</li> <li class="LB1" type="disc"><a name="1006620"></a>Generate a high number of log switches every day (for example, 1000 switc hes between catalog resynchronizations)</li></ul> <a name="1010899"></a> <p class="BP">In this case, you may want to manually resync hronize the recovery catalog regularly because the recovery catalog is <em class="Italic">not</em> updated automatically when a redo log switch occurs or when a redo log is archived. The database stores information about log switches and archived redo logs only in t he control file. You must periodically resynchronize in order to propagate this information into the recovery catalog.</p> <a name="1 006622"></a> <p class="BP">How frequently you need to resynchronize the recovery catalog depends on the rate at which the database a rchives redo logs. The cost of the operation is proportional to the number of records in the control file that have been inserted or changed since the previous resynchronization. If no records have been inserted or changed, then the cost of resynchronization is very low; if many records have been inserted or changed, then the resynchronization is more time-consuming.</p> <a name="1006623"></a> <! --TOC=h3-"1006623"--> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Resynchronizing After Physical Databas e Changes</font></h4>  <a name="1006625"></a> <p class="BP">Resynchronize the recovery catalog after making any change to the physical structure of the target database. As with redo log archive operations, the recovery catalog is <em class="Italic">no t</em> updated automatically after physical schema change, including:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="10066 27"></a>Adding or dropping a tablespace</li> <li class="LB1" type="disc"><a name="1006628"></a>Adding a new datafile to an existing t ablespace</li> <li class="LB1" type="disc"><a name="1006629"></a>Adding or dropping a rollback segment</li></ul> <a name="1006631"></ a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Forcing a Full Resynchronization of the Recovery Catalog</font></h3>  <a name="1006632"></a> <p class="BP">Use <code>RESYNC CATALOG</code> to force a f ull resynchronization of the recovery catalog.</p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006637"></a >Connect RMAN to the target and recovery catalog databases, and then mount or open the target database if it is not already mounted o r open: <pre class="CE1"><a name="1006638"></a>STARTUP MOUNT; <a name="1006639"></a> </pre> </li> <li class="LN1" type="1" value="2" ><a name="1006640"></a>Run the <code>RESYNC CATALOG</code> command at the RMAN prompt: <pre class="CE1"><a name="1006641"></a>RESYNC CATALOG; </pre> <a name="1006651"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspac ing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteA lso"> <td class="NoteAlso"><a name="1006644"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></fon t> <a name="1006650"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF150" href="../../server$101/b10770/rcmsynta52.htm #RCMRF150">Oracle Database Recovery Manager Reference</a></em> for <code>RESYNC CATALOG</code> command syntax</p></td></tr></table></ div></li></ol> <a name="1006653"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099 ">Resynchronizing the Recovery Catalog and CONTROLFILE_RECORD_KEEP_TIME</font></h3>  <a name="1006654"></a> <p class=" BP">If you maintain a recovery catalog, then use the RMAN <code>RESYNC CATALOG</code> command often enough to ensure that control fil e records are propagated to the recovery catalog before they are reused.</p> <a name="1006655"></a> <p class="BP">Make sure that <co de>CONTROLFILE_RECORD_KEEP_TIME</code> is longer than the interval between backups or resynchronizations, or else control file record s could be lost. An extra week is a safe margin in most circumstances.</p> <a name="1006660"></a> <div align="center"> <table class= "NoteWarn" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a warning" titl e="This is a layout table to format a warning"> <tr class="NoteWarn"> <td class="NoteWarn"> <hr> <a name="1006658"></a><font face="Ar ial, Helvetica, sans-serif"><strong class="NHW">Caution:</strong></font> <a name="1006659"></a> <p class="NB">Never set <code>CONTRO L_FILE_RECORD_KEEP_TIME</code> to <code>0</code>. If you do, then backup records may be overwritten in the control file before RMAN i s able to add them to the catalog.</p> <hr></td></tr></table></div> <a name="1006672"></a> <div align="center"> <table class="NoteAl so" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1006663"></a><font face="Arial, Helvetica, san s-serif"><strong class="NH">See Also:</strong></font> <a name="1006670"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC BRB SC206" href="../../server$101/b10735/maint.htm#BRBSC206"></a><a class="xlinkSRC RCMRF150" href="../../server$101/b10770/rcmsynta52.ht m#RCMRF150">Oracle Database Backup and Recovery Basics</a></em> to learn how to monitor the overwriting of control file records</p></ td></tr></table></div> <a name="1006679"></a>  <h2 class="H1"><a name="BRADV182"><font face="Arial, Helvetica, sans-serif" color="#330099">Working with RMAN Stored Scripts in the Recovery Catalog</font></a></h2>  <a name="1009555 "></a> <p class="BP"><strong class="GlossaryTerm">Stored scripts</strong> offer an alternative to command files for managing frequen tly used sequences of RMAN commands.</p> <a name="1009581"></a> <p class="BP">The chief advantage of a stored script over a command file is that a stored script is always available to any RMAN client that can connect to the target database and recovery catalog, whe reas command files are only available if the RMAN client has access to the file system on which they are stored.</p> <a name="1006717 "></a> <p class="BP">Stored scripts can be global or local. A local stored script is associated with the target database to which RM AN is connected when the script is created, and can only be executed when you are connected to that target database. A global stored script can be run against any database registered in the recovery catalog, if the RMAN client is connected to the recovery catalog an d a target database.</p> <a name="1011442"></a> <p class="BP">Note that to work with stored scripts, even global ones, you must be c onnected to both a recovery catalog and a target instance.</p> <a name="1009758"></a>  <h3 class="H2"><font fa ce="Arial, Helvetica, sans-serif" color="#330099">Creating Stored Scripts: CREATE SCRIPT</font></h3>  <a name="1009760" ></a> <p class="BP">Make sure RMAN is connected to the right target database and the recovery catalog. Then run the <code>CREATE</co de> <code>SCRIPT</code> command, as shown in this example:</p> <pre class="CE"><a name="1009184"></a>CREATE SCRIPT full_backup <a na me="1009185"></a>{ <a name="1006742"></a> BACKUP DATABASE PLUS ARCHIVELOG; <a name="1006743"></a>DELETE OBSOLETE; <a name="1006 744"></a>} <a name="1008842"></a> </pre> <a name="1006746"></a> <p class="BP">Examine the output. If no errors are displayed, then t he script was successfully created and stored in the recovery catalog.</p> <a name="1009347"></a> <p class="BP">For a global script, the syntax is similar:</p> <pre class="CE"><a name="1009457"></a>CREATE GLOBAL SCRIPT global_full_backup <a name="1009458"></a>{ <a name="1009459"></a> BACKUP DATABASE PLUS ARCHIVELOG; <a name="1009460"></a>DELETE OBSOLETE; <a name="1009461"></a>} <a name="1 009783"></a> </pre> <a name="1009763"></a> <p class="BP">You can also provide a <code>COMMENT</code> with descriptive information:</ p> <pre class="CE"><a name="1009775"></a>CREATE GLOBAL SCRIPT global_full_backup <a name="1009782"></a>COMMENT 'use only with ARCHIV ELOG mode databases' <a name="1009776"></a>{ <a name="1009777"></a> BACKUP DATABASE PLUS ARCHIVELOG; <a name="1009778"></a>DELE TE OBSOLETE; <a name="1009779"></a>} <a name="1010024"></a> </pre> <a name="1009773"></a> <p class="BP">Finally, you can create a lo cal or global script, reading its contents from a text file:</p> <pre class="CE"><a name="1010028"></a>CREATE SCRIPT full_backup FROM FILE 'my_script_file.txt'; <a name="1010042"></a> </pre> <a name="1012639"></a> <p class="BP">The file must begin with a <code>{</c ode> character, contain a series of commands valid within a RUN block, and end with a <code>}</code> character. Otherwise, a syntax e rror is signalled, just as if the commands were entered at the keyboard.</p> <a name="1010065"></a>  <h3 class ="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Running Stored Scripts: EXECUTE SCRIPT</font></h3>  <a name="1010066"></a> <p class="BP">To run a stored script, connect to the target database and recovery catalog, and use <code>EXECUTE </code> <code>SCRIPT</code>. <code>EXECUTE SCRIPT</code> requires a <code>RUN</code> block, as shown:</p> <pre class="CE"><a name="10 10067"></a>RUN { EXECUTE SCRIPT full_backup; } <a name="1010068"></a> </pre> <a name="1010069"></a> <p class="BP">This command invok es a local script if one is with the name specified. If no local script is found, but there is a global script with the name specifie d, RMAN will execute the global script. You can also use <code>EXECUTE GLOBAL SCRIPT</code> to control which script is invoked if a l ocal and a global script have the same name. Assuming there is no local script called <code>global_full_backup</code>, the following two commands have the same effect:</p> <pre class="CE"><a name="1010070"></a>RUN { EXECUTE GLOBAL SCRIPT global_full_backup; } <a nam e="1010071"></a>RUN { EXECUTE SCRIPT global_full_backup; } <a name="1010072"></a> </pre> <a name="1010073"></a> <p class="BP">Execut ing a global script only affects the connected target database; to run a global script across multiple databases, you must connect th e RMAN client to each one separately and execute the script.</p> <a name="1010074"></a> <p class="BP">Your script will use the autom atic channels configured at the time you execute the script. Use <code>ALLOCATE</code> <code>CHANNEL</code> commands in the script if you need to override the configured channels. Note that, because of the RUN block, if an RMAN command in the script fails, subsequen t RMAN commands in the script will not execute.</p> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding=" 0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr c lass="NoteAlso"> <td class="NoteAlso"><a name="1010077"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</s trong></font> <a name="1010083"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF127" href="../../server$101/b10770/rcm synta29.htm#RCMRF127">Oracle Database Recovery Manager Reference</a></em> for <code>EXECUTE SCRIPT</code> command syntax</p></td></tr ></table></div> <br> <br> <a name="1010044"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" co lor="#330099">Displaying a Stored Script: PRINT SCRIPT</font></h3>  <a name="1009854"></a> <p class="BP">The <code>PRI NT</code> <code>SCRIPT</code> command displays a stored script or writes it out to a file. With RMAN connected to the target database and recovery catalog, use the PRINT SCRIPT command as shown here:</p> <pre class="CE"><a name="1009855"></a>PRINT SCRIPT full_backup ; <a name="1009856"></a> </pre> <a name="1009857"></a> <p class="BP">To send the contents of a script to a file, use this form of th e command:</p> <pre class="CE"><a name="1009858"></a>PRINT SCRIPT full_backup TO FILE 'my_script_file.txt'; <a name="1009859"></a> </ pre> <a name="1009860"></a> <p class="BP">For global scripts, the analogous syntax would be:</p> <pre class="CE"><a name="1009861">< /a>PRINT GLOBAL SCRIPT global_full_backup; <a name="1009862"></a> </pre> <a name="1009863"></a> <p class="BP">and</p> <pre class="CE "><a name="1009864"></a>PRINT GLOBAL SCRIPT global_full_backup TO FILE 'my_script_file.txt'; </pre> <div> <table> <tr><td> <a name=" 1009916"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH"><strong class="Bold">See Also</strong>:</strong></font> <a name="1009922"></a> <em class="Italic"><a class="xlinkSRC RCMRF136" href="../../server$101/b10770/rcmsynta41.htm#RCMRF136">Oracle D atabase Recovery Manager Reference</a></em> for PRINT SCRIPT command syntax </td> </tr> </table> </div> <a name="1009880"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Listing Stored Scripts: LIST SCRIPT NAME S</font></h3>  <a name="1009934"></a> <p class="BP">Use the <code>LIST SCRIPT NAMES</code> command to display the name s of scripts defined in the recovery catalog. This command displays the names of all stored scripts, both global and local, that can be executed for the currently connected target database:</p> <pre class="CE"><a name="1009944"></a>LIST SCRIPT NAMES; <a name="100998 1"></a> </pre> <a name="1009939"></a> <p class="BP">If RMAN is not connected to a target database when the <code>LIST</code> <code>S CRIPT</code> <code>NAMES</code> command is run, then RMAN will respond with an error.</p> <a name="1010009"></a> <p class="BP">To vi ew only global script names, use this form of the command:</p> <pre class="CE"><a name="1009961"></a>LIST GLOBAL SCRIPT NAMES; <a nam e="1009982"></a> </pre> <a name="1009958"></a> <p class="BP">To view the names of all scripts stored in the current recovery catalog , including global scripts and local scripts for all target databases registered in the recovery catalog, use this form of the comman d:</p> <pre class="CE"><a name="1011593"></a>LIST ALL SCRIPT NAMES; <a name="1011598"></a> </pre> <a name="1012658"></a> <p class="B P">The output will indicate for each script listed which target database the script is defined for (or whether a script is global).</ p> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layou t table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="1011596" ></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="1011597"></a> <p class="NB"><code>L IST GLOBAL SCRIPT NAMES</code> and <code>LIST ALL SCRIPT NAMES</code> are the only commands that work when RMAN is connected to a rec overy catalog without connecting to a target instance.</p> <hr></td></tr></table></div> <br> <br> <a name="1011608"></a> <div align ="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table t o format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1011601"></a><f ont face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1011607"></a> <p class="NB"><em class= "Italic"><a class="xlinkSRC RCMRF136" href="../../server$101/b10770/rcmsynta41.htm#RCMRF136">Oracle Database Recovery Manager Referen ce</a></em> for <code>LIST SCRIPT NAMES</code> command syntax and output format.</p></td></tr></table></div> <a name="1009744"></a> < !--TOC=h2-"1009744"--> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Updating Stored Scripts: REPLACE SCRI PT</font></h3>  <a name="1009745"></a> <p class="BP">To update stored scripts, connect to the target database and reco very catalog and use the <code>REPLACE</code> <code>SCRIPT</code> command. If the script does not already exist, then RMAN creates it .</p> <a name="1006775"></a> <p class="BP">This command updates stored script script <code>full_backup</code> with new contents:</p> <pre class="CE"><a name="1006776"></a>REPLACE SCRIPT full_backup <a name="1006777"></a>{ <a name="1006778"></a> BACKUP DATABASE PL US ARCHIVELOG; <a name="1006779"></a>} <a name="1010177"></a> </pre> <a name="1010178"></a> <p class="BP">Global scripts can be upda ted using the <code>REPLACE GLOBAL SCRIPT</code> command when connected to a recovery catalog, as follows:</p> <pre class="CE"><a nam e="1010186"></a>REPLACE GLOBAL SCRIPT global_full_backup <a name="1013153"></a>COMMENT 'A script for full backup to be used with any database' <a name="1010187"></a>{ <a name="1010188"></a> BACKUP AS BACKUPSET DATABASE PLUS ARCHIVELOG; <a name="1010189"></a>} <a n ame="1010190"></a> </pre> <a name="1010184"></a> <p class="BP">As with <code>CREATE SCRIPT</code>, you can update a local or global stored script from a text file, with this form of the command:</p> <pre class="CE"><a name="1010203"></a>REPLACE GLOBAL SCRIPT global _full_backup FROM FILE 'my_script_file.txt'; <a name="1010207"></a> </pre> <a name="1011060"></a> <div align="center"> <table class= "NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title=" This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1011053"></a><font face="Arial, Helveti ca, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1011059"></a> <p class="NB"><em class="Italic"><a class="xlink SRC RCMRF145" href="../../server$101/b10770/rcmsynta48.htm#RCMRF145">Oracle Database Recovery Manager Reference</a></em> for <code>RE PLACE SCRIPT</code> command syntax</p></td></tr></table></div> <a name="1011159"></a>  <h3 class="H2"><font fa ce="Arial, Helvetica, sans-serif" color="#330099">Deleting Stored Scripts: DELETE SCRIPT</font></h3>  <a name="1011160" ></a> <p class="BP">To delete a stored script from the recovery catalog, connect to the catalog and a target database, and use the < code>DELETE</code> <code>SCRIPT</code> command:</p> <pre class="CE"><a name="1011167"></a>DELETE SCRIPT 'full_backup'; <a name="10114 55"></a> </pre> <a name="1011456"></a> <p class="BP">To delete a global stored script, use <code>DELETE GLOBAL SCRIPT</code>:</p> <p re class="CE"><a name="1011474"></a>DELETE GLOBAL SCRIPT 'global_full_backup'; <a name="1011478"></a> </pre> <a name="1011471"></a> <p class="BP">If you use <code>DELETE SCRIPT</code> without <code>GLOBAL</code>, and there is no stored script for the target databas e with the specified name, RMAN will look for a global stored script by the specified name and delete the global script if it exists. So, if you were to enter the command</p> <pre class="CE"><a name="1011507"></a>DELETE SCRIPT 'global_full_backup'; <a name="1011511" ></a> </pre> <a name="1011530"></a> <p class="BP">RMAN would look for a script '<code>global_full_backup</code>' defined for the con nected target database, and if it did not find one, it would search the global scripts for a script called '<code>global_full_backup< /code>' and delete that script.</p> <a name="1011177"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellp adding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note "> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1011170"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1011176"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF122" href="../../server$101/b1 0770/rcmsynta24.htm#RCMRF122">Oracle Database Recovery Manager Reference</a></em> for <code>DELETE SCRIPT</code> command syntax</p></ td></tr></table></div> <a name="1011618"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color= "#330099">Starting the RMAN Client and Running a Stored Script</font></h3>  <a name="1011619"></a> <p class="BP">To ru n the RMAN client and start a stored script in the recovery catalog on startup, use the <code>SCRIPT</code> argument when starting th e RMAN client.</p> <pre class="CE"><a name="1011620"></a>% rman TARGET SYS/oracle@trgt CATALOG rman/cat@catdb SCRIPT 'full_backup'; < a name="1011621"></a> </pre> <a name="1011622"></a> <p class="BP">You must connect to a recovery catalog (which contains the stored script) and target database (to which the script will apply) when starting the RMAN client.</p> <a name="1011632"></a> <div align="c enter"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to f ormat a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1011625"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1011631"></a> <p class="NB"><em class="It alic"><a class="xlinkSRC RCMRF122" href="../../server$101/b10770/rcmsynta24.htm#RCMRF122">Oracle Database Recovery Manager Reference< /a></em> for full RMAN client command line syntax</p></td></tr></table></div> <a name="1011636"></a>  <h3 clas s="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Restrictions on Stored Script Names</font></h3>  <a na me="1011768"></a> <p class="BP">There are some issues to be aware of about how RMAN resolves script names, especially when a local a nd global script share the same name.</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1011640"></a>RMAN permits but general ly does not require that you use quotes around the name of a stored script. However, if the name begins with a digit or if the name i s an RMAN reserved word, you will have to put quotes around the name to use it as a stored script name. Consider avoiding stored scri pt names that begin with characters other than A-Z or that are the same as RMAN reserved words. <div align="center"> <table class="N oteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="Th is is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1011804"></a><font face="Arial, Helvetica , sans-serif"><strong class="NH">See Also:</strong></font> <a name="1011807"></a> <p class="NB"><em class="Italic">Oracle Database R ecovery Manager Reference</em></p></td></tr></table></div></li> <li class="LB1" type="disc"><a name="1011790"></a>When starting the R MAN client with a SCRIPT argument on the command line, if local and global scripts are defined with the same name, then RMAN will alw ays execute the local script.</li> <li class="LB1" type="disc"><a name="1011778"></a>For the <code>EXECUTE SCRIPT</code>, <code>DELET E SCRIPT</code> and <code>PRINT SCRIPT</code> commands, if the script name passed as an argument is not the name of a script defined for the connected target instance, RMAN will look for a global script by the same name to execute, delete or print. For example, if t he a stored script <code>global_full_backup</code> is in the recovery catalog as a global script, but no local stored script <code>gl obal_full_backup</code> is defined for the target database, the following command will delete the global script: <pre class="CE1"><a name="1011714"></a>DELETE SCRIPT global_full_backup; </pre> <pre class="CE"><a name="1011721"></a> </pre> </li></ul> <a name="10117 22"></a> <p class="BP">Consider using some naming convetion to avoid mistakes due to confusion between global stored scripts and loca l stored scripts.</p> <a name="1011650"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cel lspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class=" NoteAlso"> <td class="NoteAlso"><a name="1011643"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong> </font> <a name="1011649"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF909" href="../../server$101/b10770/rcmcomma. htm#RCMRF909">Oracle Database Recovery Manager Reference</a></em> for the list of RMAN reserved words.</p></td></tr></table></div> <a name="1011154"></a>  <h2 class="H1"><a name="BRADV183"><font face="Arial, Helvetica, sans-serif" color="#3300 99">Managing the Control File When You Use a Recovery Catalog</font></a></h2>  <a name="1006811"></a> <p class="BP">Yo ur goal is to ensure that the metadata in the recovery catalog is current. Because the recovery catalog obtains its metadata from the target control file, the currency of the data in the catalog depends on the currency of the data in the control file. You need to ma ke sure that the backup metadata in the control file is recorded in the catalog before it is overwritten with new records.</p> <a nam e="1006812"></a> <p class="BP">The <code>CONTROL_FILE_RECORD_KEEP_TIME</code> initialization parameter determines the minimum number of days that records are retained in the control file before they are candidates for being overwritten. Hence, you must ensure that you resynchronize the recovery catalog with the control file records before these records are erased. As described in <a href="rcmrep os.htm#1006653">"Resynchronizing the Recovery Catalog and CONTROLFILE_RECORD_KEEP_TIME"</a><a href="rcmrepos.htm#1006653"></a>, you s hould perform either of the following actions at intervals less than the <code>CONTROL_FILE_RECORD_KEEP_TIME</code> setting:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006819"></a>Make a backup, thereby performing an implicit resynchronization of the recovery catalog</li> <li class="LB1" type="disc"><a name="1006820"></a>Manually resynchronize the recovery catalog with the <code>R ESYNC</code> <code>CATALOG</code> command</li></ul> <a name="1006821"></a> <p class="BP">So, to ensure the currency of the informati on in the recovery catalog, the frequency of resynchronizations should be related to the value for the <code>CONTROL_FILE_RECORD_KEEP _TIME</code> initialization parameter.</p> <a name="1006823"></a> <p class="BP">One problem can arise if the control file becomes to o large. The size of the target database control file grows depending on the number of:</p> <ul class="LB1"> <li class="LB1" type="di sc"><a name="1006824"></a>Backups that you perform</li> <li class="LB1" type="disc"><a name="1006825"></a>Archived redo logs that the database generates</li> <li class="LB1" type="disc"><a name="1006826"></a>Days that this information is stored in the control file</ li></ul> <a name="1006832"></a> <p class="BP">As explained in <em class="Italic"><a class="xlinkSRC BRBSC206" href="../../server$101 /b10735/maint.htm#BRBSC206">Oracle Database Backup and Recovery Basics</a></em>, if the control file grows so large that it can no lo nger expand because it has reached either the maximum number of blocks or the maximum number of records, then the database may overwr ite the oldest records even if their age is less than the <code>CONTROL_FILE_RECORD_KEEP_TIME</code> setting. In this case, the datab ase writes a message to the alert log. If you discover that this situation occurs frequently, then reducing the value of <code>CONTRO L_FILE_RECORD_KEEP_TIME</code> and increase the frequency of resynchronizations.</p> <a name="1006838"></a> <div align="center"> <ta ble class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" t itle="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="1006836"></a><font face="Arial, Hel vetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="1006837"></a> <p class="NB">The maximum size of the control fi le is port-specific. Typically, the maximum size is 20,000 Oracle blocks. Refer to your operating system-specific Oracle documentatio n for more information.</p> <hr></td></tr></table></div> <a name="1006855"></a> <div align="center"> <table class="NoteAlso" border= "0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout t able to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1006841"></a><font face="Arial, Helvetica, sans-serif"><s trong class="NH">See Also:</strong></font> <a name="1006842"></a> <ul class="NL"> <li class="NL" type="disc"><a name="1006848"></a>< em class="Italic"><a class="olinkSRC REFRN" href="../../server$101/b10755/toc.htm">Oracle Database Reference</a></em> for more inform ation about the <code>CONTROL_FILE_RECORD_KEEP_TIME</code> parameter</li> <li class="NL" type="disc"><a name="1006854"></a><em class= "Italic"><a class="olinkSRC ADMIN" href="../../server$101/b10739/toc.htm">Oracle Database Administrator's Guide</a></em> for more det ailed information on all aspects of control file management</li></ul></td></tr></table></div> <a name="1006860"></a>  <h2 class="H1"><a name="BRADV184"><font face="Arial, Helvetica, sans-serif" color="#330099">Backing Up and Recovering the Rec overy Catalog</font></a></h2>  <a name="1006861"></a> <p class="BP">Include the recovery catalog database in your back up and recovery strategy. If you do not back up the recovery catalog and a disk failure occurs that destroys the recovery catalog dat abase, then you may lose the metadata in the catalog.</p> <a name="1006876"></a>  <h3 class="H2"><font face="A rial, Helvetica, sans-serif" color="#330099">Backing Up the Recovery Catalog</font></h3>  <a name="1010937"></a> <p cl ass="BP">Here are some general guidelines you should follow when developing a strategy for backing up the recovery catalog.</p> <a na me="1010951"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Back Up the Recove ry Catalog Often</font></h4>  <a name="1006893"></a> <p class="BP">The recovery catalog database is a database like an y other, and is also a key part of your backup and recovery strategy. Protect the recovery catalog as you would protect any other par t of your database, by backing it up. The backup strategy for your recovery catalog database should be part of your overall backup an d recovery strategy.</p> <a name="1013211"></a> <p class="BP">Back up the recovery catalog with the same frequency that you back up the target database. For example, if you make a weekly whole database backup of the target database, then back up the recovery catalo g immediately after all target database backups, in order to protect the record of the whole database backup. This backup can help yo u in a disaster recovery scenario. Even if you have to restore the recovery catalog database using a control file autobackup, you can then use the full record of backups in your restored recovery catalog database to restore the target database without using a contro l file autobackup for the target database.</p> <a name="1006895"></a>  <h4 class="H3"><font face="Arial, Helve tica, sans-serif" color="#330099">Choosing the Appropriate Method for Physical Backups</font></h4>  <a name="1006896">< /a> <p class="BP">When backing up the recovery catalog database, you can use RMAN to make the backups. As illustrated in <a href="rc mrepos.htm#1013683">Figure 13-1</a>, you should start RMAN with the <code>NOCATALOG</code> option so that the repository for the recovery catalog is the control file in the catalog database.</p> <a name="1006900"></a> <p class="BP">Follow these guidelines when developing an RMAN backup strategy for the recovery catalog database:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006 901"></a>Run the recovery catalog database in <code>ARCHIVELOG</code> mode so that you can do point-in-time recovery if needed.</li> <li class="LB1" type="disc"><a name="1006902"></a>Set the retention policy to a <code>REDUNDANCY</code> value greater than <code>1</c ode>.</li> <li class="LB1" type="disc"><a name="1006903"></a>Back up the database onto two separate media (for example, disk and tape ).</li> <li class="LB1" type="disc"><a name="1008852"></a>Run <code>BACKUP</code> <code>DATABASE</code> <code>PLUS</code> <code>ARCHI VELOG</code> at regular intervals, to a media manager if available, or just to disk.</li> <li class="LB1" type="disc"><a name="100690 5"></a>Do not use another recovery catalog as the repository for the backups.</li> <li class="LB1" type="disc"><a name="1006906"></a> Configure the control file autobackup feature to <code>ON</code>.</li></ul> <a name="1006907"></a> <p class="BP">With this strategy, the control file autobackup feature ensures that the recovery catalog database can always be recovered, so long as the control file autobackup is available.</p> <a name="1011014"></a> <p class="BP">Exporting the Recovery Catalog Data for Logical Backups</p> <a nam e="1011026"></a> <p class="BP">Logical backups of the RMAN recovery catalog created with one of Oracle's export utilities can be a u seful supplement for physical backups. In the event of damage to the recovery catalog database, you can quickly reimport the exported recovery catalog data into another database and rebuild the catalog this way.</p> <a name="1013683"></a> <h4 class="FT"><font face= "Arial, Helvetica, sans-serif"><em>Figure 13-1 Using the Control File as the Repository for Backups of the Catalog</em></font></h4> < a name="1013697"><img src="bradv009.gif" alt="Text description of bradv009.gif follows"></a> <p><a href="img_text/bradv009.htm">Text description of the illustration bradv009.gif</a></p> <a name="1013694"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout tabl e to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1013686"></a><font face="Arial, Helvetica, sans-serif"><stro ng class="NH">See Also:</strong></font> <a name="1013693"></a> <p class="NB"><a href="rcmrecov.htm#1007667">"Performing Disaster Rec overy"</a><a href="rcmrecov.htm#1007667"></a> for more information for recovery with a control file autobackup</p></td></tr></table>< /div> <a name="1006926"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Storing the Recovery Catalog in an Appropriate Place</font></h4>  <a name="1006927"></a> <p class="BP">Never store a recovery catalog containing the RMAN repository for a database in the same database as the target database or on the same disks as the target database. For example, do not store the catalog for database <code>prod1</code> in <code>prod1</code>. A recovery catalog for <code> prod1</code> is only effective if it is separated from the data that it is designed to protect.</p> <a name="1006928"></a> <p class= "BP">If <code>prod1</code> suffers a total media failure, and if the recovery catalog data for <code>prod1</code> is also stored in < code>prod1</code>, then you have no catalog to aid in recovery. You will probably have to restore an autobackup of the control file f or <code>prod1</code> and use it to restore and recover the database.</p> <a name="1006929"></a> <p class="BP">Separating the target and catalog databases is especially important when you back up a recovery catalog database. The following example shows what you sho uld <em class="Italic">not</em> do. For example, consider the following:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="10 06930"></a>Target database <code>prod1</code> and catalog database <code>catdb</code> are on different hosts.</li> <li class="LB1" ty pe="disc"><a name="1006931"></a><code>catdb</code> contains the recovery catalog repository for target database <code>prod1</code>.</ li></ul> <a name="1006932"></a> <p class="BP">You decide to use a recovery catalog to back up <code>catdb</code>, but are not sure w here to create it. If you create the catalog containing the repository for <code>catdb</code> in database <code>catdb</code>, then if you lose <code>catdb</code> due to a media failure, you will have difficulty restoring <code>catdb</code> <em class="Italic">and</em > will leave <code>prod1</code> without a recovery catalog to use in a restore scenario.</p> <a name="1006935"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Restoring and Recovering the Recovery Catalog from Ba ckup</font></h3>  <a name="1006936"></a> <p class="BP">Restoring and recovering the recovery catalog is much like rest oring and recovering any other database, if you backed it up with RMAN.</p> <a name="1012700"></a> <p class="BP">You can restore the control file and SPFILE for the recovery catalog database from an autobackup, then restore and perform complete recovery on the rest of the database. The processes required are all described in <a class="xlinkSRC BRBSC005" href="../../server$101/b10735/recov.htm#BR BSC005"><em class="Italic">Oracle Database Backup and Recovery Basics</em></a> You can also use another recovery catalog to record me tadata about backups of this recovery catalog database, if you are in a situation where you are using multiple recovery catalogs.</p> <a name="1006944"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Re-Creating the Recovery Catalog</font></h3>  <a name="1006946"></a> <p class="BP">If the recovery catalog database is lost or dam aged, and recovery of the recovery catalog database through the normal Oracle recovery procedures is not possible, then you must re-c reate the catalog. Examples of this worst-case scenario include:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006947">< /a>A recovery catalog database that has never been backed up</li> <li class="LB1" type="disc"><a name="1006948"></a>A recovery catalo g database that has been backed up, but cannot be recovered because the datafile backups or archived logs are not available</li></ul> <a name="1006949"></a> <p class="BP">You have these options for partially re-creating the contents of the missing recovery catalog: </p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006950"></a>Issue <code>CATALOG START WITH...</code> commands to recatalo g backups.</li> <li class="LB1" type="disc"><a name="1006952"></a>Use the <code>RESYNC CATALOG</code> command to extract metadata fro m a control file and rebuild the recovery catalog. Note that you automatically lose any metadata that was contained in old control fi le records that aged out of the control file. <p><a name="1006953"></a></p> <p class="BP1">Depending on the state of the target cont rol file, you can:</p> <ul class="LD2"> <li class="LD2" type="CIRCLE"><a name="1006954"></a>Resynchronize from the current control fi le</li> <li class="LD2" type="CIRCLE"><a name="1006955"></a>Resynchronize from a control file copy <p><a name="1006979"></a></p> <di v align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1006958" ></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1006959"></a> <ul class="NL"> < li class="NL" type="disc"><a name="1006965"></a><em class="Italic"><a class="xlinkSRC RCMRF109" href="../../server$101/b10770/rcmsynt a11.htm#RCMRF109">Oracle Database Recovery Manager Reference</a></em> for information about the <code>CATALOG</code> command</li> <li class="NL" type="disc"><a name="1006971"></a><em class="Italic"><a class="xlinkSRC RCMRF119" href="../../server$101/b10770/rcmsynta2 1.htm#RCMRF119">Oracle Database Recovery Manager Reference</a></em> for information about the <code>CROSSCHECK</code> command</li> <l i class="NL" type="disc"><a name="1006977"></a><a href="rcmrepos.htm#1011154">"Managing the Control File When You Use a Recovery Cata log"</a><a href="rcmrepos.htm#1011154"></a> to learn about how records age out of the control file</li></ul></td></tr></table></div>< /li></ul></li></ul> <a name="1006981"></a>  <h2 class="H1"><a name="BRADV185"><font face="Arial, Helvetica, sa ns-serif" color="#330099">Exporting and Importing the Recovery Catalog</font></a></h2>  <a name="1006983"></a> <p clas s="BP">To move the recovery catalog from one database to another, export the catalog from the old database, and import it into the ne w one. You can only import the catalog into a supported version of the Oracle database server. In general, you can import the catalog into a database of the same release or later.</p> <a name="1010991"></a> <p class="BP">Exports can also serve as logical backups of the RMAN recovery catalog. If the recovery catalog database is damaged, you can quickly reimport the exported recovery catalog data into another database and rebuild the catalog.</p> <a name="1006984"></a> <p class="BP">This section contains the following topics:< /p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006988"></a><a href="rcmrepos.htm#1006998">Considerations When Moving Cata log Data</a></li> <li class="LB1" type="disc"><a name="1006992"></a><a href="rcmrepos.htm#1007024">Exporting the Recovery Catalog</a> </li> <li class="LB1" type="disc"><a name="1006996"></a><a href="rcmrepos.htm#1007043">Importing the Recovery Catalog</a></li></ul> < a name="1006998"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Considerations When Moving Catalog Data</font></h3>  <a name="1006999"></a> <p class="BP">You should only import the recover catalog into a schema that does not already contain a recovery catalog schema. In other words, the user who will own the imported recovery c atalog schema should not already own a recovery catalog schema. For example, if user <code>rman</code> owns the recovery catalog on d atabase <code>catdb</code>, and you want to export the recovery catalog on <code>catdb</code> and import it into database <code>catdb 2</code>, then <code>rman</code> should not already own a recovery catalog on <code>catdb2</code>. You should either create a new rec overy catalog owner on <code>catdb2</code>, or drop the current user <code>rman</code> on <code>catdb2</code> and then re-create the user. You cannot merge a recovery catalog into an existing recovery catalog.</p> <a name="1007000"></a> <p class="BP">The basic step s for exporting a recovery catalog from a primary database and importing the catalog into a secondary database are as follows:</p> <o l class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007001"></a>Use one of the Oracle Export utilities to export the catalog data from the primary database. See <a href="rcmrepos.htm#1007024">"Exporting the Recovery Catalog"</a><a href="rcmrepos.htm #1007024"></a> for an example.</li> <li class="LN1" type="1" value="2"><a name="1007010"></a>Create a user on the secondary database as described in <a href="rcmrepos.htm#1006232">"Creating the Recovery Catalog Owner"</a><a href="rcmrepos.htm#1006232"></a>, and gran t the user necessary privileges.</li> <li class="LN1" type="1" value="3"><a name="1007015"></a>Use the import utility corresponding t o the export utility in step 1 to import the catalog data into the schema created in the previous step. See <a href="rcmrepos.htm#100 7043">"Importing the Recovery Catalog"</a><a href="rcmrepos.htm#1007043"></a> for an example.</li></ol> <a name="1007022"></a> <p cl ass="BP">You should <em class="Italic">not</em> run the <code>CREATE</code> <code>CATALOG</code> command either before or after the I mport of the catalog into the secondary database. By importing the catalog data into the new schema, you effectively create the catal og in the secondary database.</p> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir ="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class ="Note"> <hr> <a name="1012706"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="10127 07"></a> <p class="NB">You cannot import data exported from two different recovery catalogs to merge them into one catalog. It is no t currently possible to merge two or more recovery catalog schemas into one.</p> <hr></td></tr></table></div> <br> <br> <a name="100 7024"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Exporting the Recovery Ca talog</font></h3>  <a name="1011998"></a> <p class="BP">This example uses the Original Export utility described in <em class="Italic"><a class="xlinkSRC SUTIL001" href="../../server$101/b10825/exp_imp.htm#SUTIL001">Oracle Database Utilities</a></em> t o create a logical export of the recovery catalog. Refer to <em class="Italic"><a class="xlinkSRC SUTIL100" href="../../server$101/b1 0825/dp_overview.htm#SUTIL100">Oracle Database Utilities</a></em> for concepts and procedures relating to the Data Pump Export utilit y.</p> <a name="1011999"></a> <p class="BP">The following procedure creates a logical export of the recovery catalog.</p> <ol class= "LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007033"></a>Execute the Oracle export utility at the operating system co mmand line, making sure to do the following: <ol class="LA2" type="a"> <li class="LA2" type="a" value="1"><a name="1007034"></a>Conn ect as the owner of the recovery catalog</li> <li class="LA2" type="a"><a name="1007035"></a>Specify the <code>OWNER</code> option</l i> <li class="LA2" type="a"><a name="1007036"></a>Specify an output file</li></ol> <a name="1007037"></a> <p class="BP1">For example , if the owner of the catalog in database <code>catdb</code> is <code>rman</code>, you can issue the following at the UNIX command li ne to export the catalog to file <code>cat.dmp</code>:</p> <pre class="CE1"><a name="1007038"></a>% exp rman/cat@catdb FILE=cat.dmp O WNER=rman <a name="1007039"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007040"></a>Examine the output to make sur e you were successful: <pre class="CE1"><a name="1007041"></a>Export terminated successfully without warnings. </pre> </li></ol> <a name="1007043"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Importing the Rec overy Catalog</font></h3>  <a name="1012069"></a> <p class="BP">This example uses the Original Import utility describe d in <em class="Italic"><a class="xlinkSRC SUTIL001" href="../../server$101/b10825/exp_imp.htm#SUTIL001">Oracle Database Utilities</a ></em> to create a logical export of the recovery catalog. Refer to <em class="Italic"><a class="xlinkSRC SUTIL100" href="../../serve r$101/b10825/dp_overview.htm#SUTIL100">Oracle Database Utilities</a></em> for concepts and procedures relating to the Data Pump Impor t utility.</p> <a name="1007045"></a> <p class="BP"><strong class="Bold">To make a logical import of the recovery catalog from the c ommand line:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007047"></a>Create a new user in ano ther database. For the recommended SQL syntax for creating a new user in a recovery catalog database, see <a href="rcmrepos.htm#10062 32">"Creating the Recovery Catalog Owner"</a><a href="rcmrepos.htm#1006232"></a>. Be sure to grant the new user the necessary privile ges.</li> <li class="LN1" type="1" value="2"><a name="1007054"></a>Import the catalog data from the export file. Execute the import a t the command line, making sure to do the following: <ol class="LA2" type="a"> <li class="LA2" type="a" value="1"><a name="1007055"> </a>Connect as the new owner of the recovery catalog.</li> <li class="LA2" type="a"><a name="1007056"></a>Specify the old owner with the <code>FROMUSER</code> parameter.</li> <li class="LA2" type="a"><a name="1007057"></a>Specify the new owner with the <code>TOUSER< /code> parameter.</li> <li class="LA2" type="a"><a name="1007058"></a>Specify the import file.</li></ol> <a name="1007059"></a> <p c lass="BP1">For example, assume the following:</p> <ul class="LB2"> <li class="LB2" type="disc"><a name="1007060"></a>The old owner of the catalog in database <code>prod1</code> is <code>rman</code>.</li> <li class="LB2" type="disc"><a name="1007061"></a>The user in the new recovery catalog database <code>catdb2</code> is <code>rman2</code>.</li> <li class="LB2" type="disc"><a name="1007062"></a>T he file containing the export of the catalog is <code>cat.dmp</code>.</li></ul> <a name="1007063"></a> <p class="BP1">The command is then as follows:</p> <pre class="CE1"><a name="1007064"></a>% imp USERID=rman2/cat2@catdb2 FILE=cat.dmp FROMUSER=rman TOUSER=rman2 <a name="1007065"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1007066"></a>Use the imported catalog data for restor e and recovery of your target database.</li></ol> <a name="1007068"></a>  <h2 class="H1"><a name="BRADV186"><f ont face="Arial, Helvetica, sans-serif" color="#330099">Increasing Availability of the Recovery Catalog</font></a></h2>  <h2 class="H1"><a name="BRADV193"><font face="Arial, Helvetica, sans-serif" color="#330099">Querying the R ecovery Catalog Views</font></a></h2>  <a name="1008567"></a> <p class="BP">The <code>LIST</code>, <code>REPORT</code> , and <code>SHOW</code> commands should provide you with all the repository information that you require. Nevertheless, you can somet imes also obtain useful information from the recovery catalog views, which are views in the catalog schema prefixed with <code>RC_</c ode>.</p> <a name="1008586"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> < td class="NoteAlso"><a name="1008579"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a n ame="1008585"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF003" href="../../server$101/b10770/rcviews.htm#RCMRF003" >Oracle Database Recovery Manager Reference</a></em> for reference information about the recovery catalog views</p></td></tr></table> </div> <a name="1008589"></a> <p class="BP">RMAN obtains backup and recovery metadata from the target database control file and stor es it in the catalog tables. The recovery catalog views are derived from these tables. Note that these views are not normalized or op timized for user queries.</p> <a name="1008590"></a> <p class="BP">In general, the recovery catalog views are not as user-friendly a s the RMAN reporting commands. For example, when you start RMAN and connect to a target database, you obtain the information for this target database only when you issue <code>LIST</code>, <code>REPORT</code>, and <code>SHOW</code> commands. If you have 10 different target databases registered in the same recovery catalog, then the catalog views show the information for all incarnations of all da tabases registered in the catalog. You often have to perform joins among the views to distinguish the specific incarnation of the tar get database that you are interested in.</p> <a name="1012728"></a> <p class="BP">Most of the catalog views have a corresponding dyn amic performance view (or V$ view) in the database server. For example, <code>RC_BACKUP_PIECE</code> corresponds to <code>V$BACKUP_PI ECE</code>. The primary difference between the recovery catalog view and corresponding server view is that each catalog view contains information about all the databases registered in the catalog, whereas the database server view contains information only about itse lf. The RC_ views and corresponding V$ views use different primary keys to uniquely identify rows.</p> <a name="1008592"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Distinguishing a Database in the Catalog Vi ews</font></h4>  <a name="1008593"></a> <p class="BP">Most of the catalog views contain the columns <code>DB_KEY</code > and <code>DBINC_KEY</code>. Each target database can be uniquely identified by either the primary key, which is the <code>DB_KEY</c ode> column value, or the <code>DBID</code>, which is the 32-bit unique database identifier. Each incarnation of each target database is uniquely identified by the <code>DBINC_KEY</code> primary key. When querying data about a specific incarnation of a target databa se, you should use these columns to specify the database. Then, you can perform joins with most of the other catalog views to obtain the desired information.</p> <a name="1008594"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Distinguishing a Database Object in the Catalog Views</font></h4>  <a name="1008595"></a> <p class="BP ">An important difference between catalog and <code>V$</code> views is that a different system of unique identifiers is used for back up and recovery objects. For example, many <code>V$</code> views such as <code>V$ARCHIVED_LOG</code> use the <code>RECID</code> and < code>STAMP</code> columns to form a concatenated primary key. The corresponding catalog view uses a derived value as its primary keys and stores this value in a single column. For example, the primary key in <code>RC_ARCHIVED_LOG</code> is the <code>AL_KEY</code> co lumn. The <code>AL_KEY</code> column value is the primary key that RMAN displays in the <code>LIST</code> command output.</p> <a name ="1008597"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Querying Catalog Vie ws for the Target DB_KEY or DBID Values</font></h3>  <a name="1008598"></a> <p class="BP">The <code>DB_KEY</code> valu e, which is the primary key for a target database, is used only in the recovery catalog. The easiest way is to obtain the <code>DB_KE Y</code> is to use the DBID of the target database, which is displayed whenever you connect RMAN to the target database. The DBID, wh ich is a unique system-defined number given to every Oracle database, is what distinguishes one target database from another target d atabase in the RMAN metadata.</p> <a name="1008599"></a> <p class="BP">Assume that you want to obtain information about one of the t arget databases registered in the recovery catalog. You can easily determine the DBID from this database either by looking at the out put displayed when RMAN connects to the database, querying <code>V$RMAN_OUTPUT</code>, or querying a <code>V$DATABASE</code> view as in the following:</p> <pre class="CE"><a name="1008600"></a>SELECT DBID <a name="1008601"></a>FROM V$DATABASE; <a name="1008602"></a > <a name="1008603"></a>DBID <a name="1008604"></a>--------- <a name="1008605"></a>598368217 <a name="1008606"></a> </pre> <a name=" 1008607"></a> <p class="BP">You can then obtain the <code>DB_KEY</code> for a target database by running the following query, where < em><code>dbid_of_target</code></em> is the DBID that you previously obtained:</p> <pre class="CE"><a name="1008608"></a>SELECT DB_KEY <a name="1008609"></a>FROM RC_DATABASE <a name="1008610"></a>WHERE DBID = <em class="Italic">dbid_of_target</em>; <a name="1008611 "></a> </pre> <a name="1008612"></a> <p class="BP">To obtain information about the current incarnation of a target database, specify the target database <code>DB_KEY</code> value and perform a join with <code>RC_DATABASE_INCARNATION</code> by using a <code>WHERE</c ode> condition to specify that the <code>CURRENT_INCARNATION</code> column value is set to <code>YES</code>. For example, to obtain i nformation about backup sets in the current incarnation of a target database with the <code>DB_KEY</code> value of <code>1</code>, yo u can execute the following script:</p> <pre class="CE"><a name="1008613"></a>SELECT BS_KEY, BACKUP_TYPE, COMPLETION_TIME <a name="10 08614"></a> FROM RC_DATABASE_INCARNATION i, RC_BACKUP_SET b <a name="1008615"></a> WHERE i.DB_KEY = 1 <a name="1008616"></a> AND i .DB_KEY = b.DB_KEY <a name="1008617"></a> AND i.CURRENT_INCARNATION = 'YES'; <a name="1008618"></a> </pre> <a name="1008619"></a> < p class="BP">You should use the <code>DB_NAME</code> column to specify a database <em class="Italic">only</em> <em class="Italic">if< /em> you do not have more than one database registered in the recovery catalog with the same <code>DB_NAME</code>. RMAN permits you t o register more than one database with the same database name, but requires that the DBID values be different. For example, you can h ave ten databases with the <code>DB_NAME</code> value of <code>prod1</code>, each with a different DBID. Because the DBID is the uniq ue identifier for every database in the metadata, use this value to obtain the <code>DB_KEY</code> and then use <code>DB_KEY</code> t o uniquely identify the database.</p> <a name="1008889"></a>  <h2 class="H1"><font face="Arial, Helvetica, san s-serif" color="#330099">Determining the Schema Version of the Recovery Catalog</font></h2>  <a name="1008890"></a> <p class="BP">The schema version of the recovery catalog is stored in the recovery catalog itself. The information is important in case you maintain multiple databases of different versions in your production system, and need to determine whether the catalog schema ve rsion is usable with a specific target database version.</p> <a name="1008900"></a> <div align="center"> <table class="NoteAlso" bor der="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layo ut table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1008893"></a><font face="Arial, Helvetica, sans-serif "><strong class="NH">See Also:</strong></font> <a name="1008899"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF005" href="../../server$101/b10770/compat.htm#RCMRF005">Oracle Database Recovery Manager Reference</a></em> for the complete set of compat ibility rules governing the RMAN environment</p></td></tr></table></div> <a name="1008901"></a> <p class="BP"><strong class="Bold">T o determine the schema version of the recovery catalog:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1008902"></a>Start SQL*Plus and connect to the recovery catalog database as the catalog owner. For example: <pre class="CE1">< a name="1008903"></a>% sqlplus rman/cat@catdb <a name="1008904"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1008905 "></a>Query the <code>RCVER</code> table to obtain the schema version, as in the following example (sample output included): <pre cl ass="CE1"><a name="1008906"></a>SELECT * <a name="1008907"></a>FROM rcver; <a name="1008908"></a> <a name="1008909"></a>VERSION <a na me="1008910"></a>------------ <a name="1008911"></a>09.02.00 <a name="1008912"></a> </pre> </li></ol> <a name="1008913"></a> <p class ="BP">If the table displays multiple rows, then the highest version in the <code>RCVER</code> table is the current catalog schema ver sion. The table stores only the major version numbers and not the patch numbers. For example, assume that the <code>rcver</code> tabl e displays the following rows:</p> <pre class="CE"><a name="1008914"></a>VERSION <a name="1008915"></a>------------ <a name="1008916" ></a>08.01.07 <a name="1008917"></a>09.00.01 <a name="1008918"></a>09.02.00 <a name="1008919"></a> </pre> <a name="1008920"></a> <p class="BP">These rows indicate that the catalog was created with a release 8.1.7 executable, then upgraded to release 9.0.1, and fina lly upgraded to release 9.2.0. The current version of the catalog schema is 9.2.0.</p> <a name="1008886"></a>  <h2 class="H1"><a name="BRADV188"><font face="Arial, Helvetica, sans-serif" color="#330099">Upgrading the Recovery Catalog</font></a ></h2>  <a name="1007128"></a> <p class="BP">If you use a version of the recovery catalog that is older than that requ ired by the RMAN client, then you must upgrade it. For example, you must upgrade the catalog if you use a release 8.1 version of the RMAN client with a release 8.0 version of the recovery catalog.</p> <a name="1007129"></a> <p class="BP">You receive an error when i ssuing <code>UPGRADE CATALOG</code> if the recovery catalog is already at a version greater than that required by the RMAN client. RM AN permits the <code>UPGRADE CATALOG</code> command to be run if the recovery catalog is current and does not require upgrading, howe ver, so that you can re-create packages at any time if necessary. Check the message log for error messages generated during the upgra de.</p> <a name="1007144"></a> <p class="BP"><strong class="Bold">To upgrade the recovery catalog:</strong></p> <ol class="LN1" type ="1"> <li class="LN1" type="1" value="1"><a name="1012976"></a>To install the new recovery catalog schema, the recovery catalog user must have TYPE privilege: <pre class="CE1"><a name="1012988"></a>sqlplus> connect sys/oracle@catdb as sysdba; <a name="1012993">< /a>sqlplus> grant TYPE to rman; <a name="1012992"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1012971"></a>Use R MAN to connect to the target and recovery catalog databases. For example, enter: <pre class="CE1"><a name="1007146"></a>% rman TARGE T / CATALOG rman/cat@catdb <a name="1007147"></a> <a name="1007148"></a>connected to recovery catalog database <a name="1007149"></a >PL/SQL package rcat.DBMS_RCVCAT version 08.00.04 in RCVCAT database <a name="1008187"></a>is too old <a name="1007150"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1007151"></a>Issue the <code>UPGRADE CATALOG</code> command: <pre class="CE1"><a n ame="1007152"></a>UPGRADE CATALOG; <a name="1007153"></a> <a name="1007154"></a>recovery catalog owner is rman <a name="1007155"></a >enter UPGRADE CATALOG command again to confirm catalog upgrade <a name="1007156"></a> </pre> </li> <li class="LN1" type="1" value=" 4"><a name="1007157"></a>Enter the <code>UPDATE CATALOG</code> command again to confirm: <pre class="CE1"><a name="1007158"></a>UPGR ADE CATALOG; <a name="1007159"></a> <a name="1007160"></a>recovery catalog upgraded to version 09.02.00 <a name="1007161"></a>DBMS_RC VMAN package upgraded to version 09.02.00 <a name="1007162"></a>DBMS_RCVCAT package upgraded to version 09.02.00 </pre> <a name="100 7185"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="Thi s is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1007165"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1007166"></a> <ul class="NL"> <li class="NL" type="disc"><a name="1007172"></a><em class="Italic"><a class="xlinkSRC RCMRF161" href="../../server$101/ b10770/rcmsynta64.htm#RCMRF161">Oracle Database Recovery Manager Reference</a></em> for <code>UPGRADE CATALOG</code> command syntax</ li> <li class="NL" type="disc"><a name="1007178"></a><em class="Italic"><a class="xlinkSRC RCMRF114" href="../../server$101/b10770/rc msynta16.htm#RCMRF114">Oracle Database Recovery Manager Reference</a></em> for information about recovery catalog compatibility</li> <li class="NL" type="disc"><a name="1007184"></a><em class="Italic"><a class="olinkSRC UPGRD" href="../../server$101/b10763/toc.htm"> Oracle Database Upgrade Guide</a></em> for complete compatibility and migration information</li></ul></td></tr></table></div></li></o l> <a name="1007187"></a>  <h2 class="H1"><a name="BRADV189"><font face="Arial, Helvetica, sans-serif" color=" #330099">Dropping the Recovery Catalog</font></a></h2>  <a name="1007189"></a> <p class="BP">If you do not want to mai ntain a recovery catalog, then you can drop the recovery catalog schema from the tablespace. The <code>DROP CATALOG</code> command de letes all information from the recovery catalog. Hence, if you have no backups of the recovery catalog schema, then backups of all ta rget databases managed by this catalog may become unusable. (The control file of the target database will still retain a record of re cent backups.)</p> <a name="1007190"></a> <p class="BP">The <code>DROP CATALOG</code> command is not appropriate for unregistering a single database from a recovery catalog that has multiple target databases registered. Dropping the catalog deletes the recovery cat alog record of backups for all target databases registered in the catalog.</p> <a name="1007191"></a> <p class="BP"><strong class="B old">To drop the recovery catalog schema:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007192" ></a>Use RMAN to connect to the target and recovery catalog databases. <pre class="CE1"><a name="1007193"></a>% rman TARGET / CATALO G rman/cat@catdb <a name="1007194"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007195"></a>Issue the <code>DROP CA TALOG</code> command twice to confirm: <pre class="CE1"><a name="1007196"></a>DROP CATALOG; <a name="1007197"></a> <a name="1007198" ></a>recovery catalog owner is rman <a name="1007199"></a>enter DROP CATALOG command again to confirm catalog removal <a name="100720 0"></a> <a name="1007201"></a>DROP CATALOG; </pre> <a name="1009099"></a> <div align="center"> <table class="Note" border="0" width= "80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to fo rmat a note"> <tr class="Note"> <td class="Note"> <hr> <a name="1009097"></a><font face="Arial, Helvetica, sans-serif"><strong class= "NH">Note:</strong></font> <a name="1009098"></a> <p class="NB">Even after you drop the recovery catalog, the control file still con tains records about the backups. To purge RMAN repository records from the control file, re-create the control file.</p> <hr></td></t r></table></div> <a name="1007222"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspac ing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteA lso"> <td class="NoteAlso"><a name="1009102"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></fon t> <a name="1009108"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF125" href="../../server$101/b10770/rcmsynta26.htm #RCMRF125">Oracle Database Recovery Manager Reference</a></em> for <code>DROP CATALOG</code> command syntax, and <a href="rcmrepos.ht m#1006421">"Unregistering a Target Database from the Recovery Catalog"</a><a href="rcmrepos.htm#1006421"></a> to learn how to unregis ter a database from the catalog</p></td></tr></table></div></li></ol> <div class="footer"> <hr> </div> <table summary="" cellspacing= "0" cellpadding="0" width="100%"> <tr> <td style="width: 33%;" align="left"> <table summary="layout table" cellspacing="0" cellpaddin g="0" align="left" width="90"> <tr> <td align="center" valign="top"><a href="rcmasm.htm"><img src="../../dcommon/gifs/larrow.gif" alt ="Go to previous page" border="0"><br> <font size="-2">Previous</font></a></td> <td align="center" valign="top"><a href="rcmtunin.htm "><img src="../../dcommon/gifs/rarrow.gif" alt="Go to next page" border="0"><br> <font size="-2">Next</font></a></td></tr></table></t d> <td style="width: 34%;" align="center"><img src="../../dcommon/gifs/oracle.gif" alt="Oracle"><br> <a href="../../dcommon/html/cpyr .htm"><font size="-2">Copyright © 2003 Oracle Corporation</font></a><br> <font size="-2">All Rights Reserved.</font></td> <td st yle="width: 33%;" align="right"> <table summary="" cellspacing="0" cellpadding="0" width="270"> <tr> <td align="center" valign="top"> <a href="../../index.htm"><img src="../../dcommon/gifs/prodicon.gif" alt="Go to Documentation Home" border="0"><br> <font size="-2">H ome</font></a></td> <td align="center" valign="top"><a href="../../nav/portal_3.htm"><img src="../../dcommon/gifs/bookicon.gif" alt=" Go to Book List" border="0"><br> <font size="-2">Book List</font></a></td> <td align="center" valign="top"><a href="toc.htm"><img src ="../../dcommon/gifs/conticon.gif" alt="Go to Table of Contents" border="0"><br> <font size="-2">Contents</font></a></td> <td align=" center" valign="top"><a href="index.htm"><img src="../../dcommon/gifs/indxicon.gif" alt="Go to Index" border="0"><br> <font size="-2" >Index</font></a></td> <td align="center" valign="top"><a href="../../mix$101/b12039/toc.htm"><img src="../../dcommon/gifs/mix.gif" a lt="Go to Master Index" border="0"><br> <font size="-2">Master Index</font></a></td> <td align="center" valign="top"><a href=".. /../dcommon/html/feedback.htm"><img src="../../dcommon/gifs/feedback.gif" alt="Go to Feedback page" border="0"><br> <font size="-2">F eedback</font></a></td></tr></table></td></tr></table></div> </body> </html>