15 Recovery Manager Troubleshooting</t itle> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="Content-Language" content="EN"> <met a http-equiv="Content-Style-Type" content="text/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta name="r obots" content="all" scheme="http://www.robotstxt.org/"> <meta name="doctitle" content="Oracle® Database Backup and Recovery Adva nced User's Guide 10g Release 1 (10.1)"> <meta name="partno" content="B10734-01"> <meta name="docid" content="BRADV"> <link rel="Star t" href="../../index.htm" title="Home" type="text/html"> <link rel="Copyright" href="../../dcommon/html/cpyr.htm" title="Copyright" t ype="text/html"> <link rel="Stylesheet" href="../../dcommon/css/doccd.css" title="Default" type="text/css"> <link rel="Contents" href ="toc.htm" title="Contents" type="text/html"> <link rel="Index" href="index.htm" title="Index" type="text/html"> <link rel="Prev" hre f="rcmtunin.htm" title="Previous" type="text/html"> <link rel="Next" href="part3.htm" title="Next" type="text/html"> <link rel="alter nate" href="../b10734.pdf" title="PDF version" type="application/pdf"> </head> <body> <div class="header"> <p><a name="top" id="top" href="#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> 10<i>g</i> Release 1 (10.1)</strong><br> Part Number B10734-01</font></td> <td valign="bottom" align="right"> <table summary="" cel lspacing="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">Home</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" 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 /gifs/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= "layout table" cellspacing="0" cellpadding="0" align="left" width="90"> <tr> <td align="center" valign="top"><a href="rcmtunin.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="part3.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="1006083"></a>  <h1 class="Title"><font face="Arial, Helvetica, sans-serif" color="#330099">15<br> <a name="BRADV012">Recovery Manager Troubleshooti ng</a></font></h1>  <a name="1006087"></a> <p class="BP">This chapter describes how to troubleshoot Recovery Manage r. This chapter contains these topics:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006091"></a><a href="rcmtroub.htm#1 010097">Interpreting RMAN Message Output</a></li> <li class="LB1" type="disc"><a name="1006095"></a><a href="rcmtroub.htm#1006547">Te sting the Media Management API</a></li> <li class="LB1" type="disc"><a name="1006099"></a><a href="rcmtroub.htm#1006621">Terminating an RMAN Command</a></li> <li class="LB1" type="disc"><a name="1010737"></a><a href="rcmtroub.htm#1010302">RMAN Troubleshooting Scenar ios</a></li></ul> <a name="1010097"></a>  <h2 class="H1"><a name="BRADV174"><font face="Arial, Helvetica, sans -serif" color="#330099">Interpreting RMAN Message Output</font></a></h2>  <a name="1010099"></a> <p class="BP">Recover y Manager provides detailed error messages that can aid in troubleshooting problems. Also, the Oracle database server and third-party media vendors generate useful debugging output of their own. The discussion which follows explains how to identify and interpret the different errors you may encounter.</p> <a name="1006143"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Identifying Types of Message Output</font></h3>  <a name="1006144"></a> <p class="BP">Outp ut that is useful for troubleshooting failed or hung RMAN jobs is located in several different places, as explained in the following table.</p> <a name="1006208"></a> <table summary="" class="RuleInformalWide" border="1" width="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Informal"> <th class="Informal" align="left" valign="bottom" scope="col"><a name="1006148"></ a> <font face="Arial, Helvetica, sans-serif"><strong><strong class="Bold">Type of Output</strong></strong></font></th> <th class="Inf ormal" align="left" valign="bottom" scope="col"><a name="1006150"></a> <font face="Arial, Helvetica, sans-serif"><strong>Produced By< /strong></font></th> <th class="Informal" align="left" valign="bottom" scope="col"><a name="1006152"></a> <font face="Arial, Helvetic a, sans-serif"><strong>Location</strong></font></th> <th class="Informal" align="left" valign="bottom" scope="col"><a name="1006154"> </a> <font face="Arial, Helvetica, sans-serif"><strong>Description</strong></font></th></tr></thead> <tbody> <tr class="Informal" ali gn="left" valign="top"> <td class="Informal"><a name="1006156"></a> <p class="TB">RMAN messages</p></td> <td class="Informal"><a nam e="1006158"></a> <p class="TB">RMAN</p></td> <td class="Informal"><a name="1006160"></a> <p class="TB">Completed job information is in <code>V$RMAN_STATUS</code> and <code>RC_RMAN_STATUS</code>. Current job information is in <code>V$RMAN_OUTPUT</code>. <a name="10 06161"></a></p> <p class="TB">When running RMAN from the command line, you can direct output to the following places:</p> <ul class=" TLB"> <li class="TLB" type="disc"><a name="1006162"></a>Standard output</li> <li class="TLB" type="disc"><a name="1006163"></a>A log file specified by <code>LOG</code> on the command line or the <code>SPOOL</code> <code>LOG</code> command</li> <li class="TLB" type=" disc"><a name="1006164"></a>A file created by redirecting RMAN output (for example, UNIX <code>></code> operator)</li></ul></td> < td class="Informal"><a name="1006166"></a> <p class="TB">Contains actions relevant to the RMAN job as well as error messages generat ed by RMAN, the database server, and the media vendor. RMAN error messages have an <code>RMAN-</code><em class="Italic">xxxxx</em> pr efix. Normal action descriptions do not have a prefix.</p></td></tr> <tr class="Informal" align="left" valign="top"> <td class="Infor mal"><a name="1006169"></a> <p class="TB"><code>alert_</code><em class="Italic">SID</em><code>.log</code></p></td> <td class="Inform al"><a name="1006171"></a> <p class="TB">Oracle database server</p></td> <td class="Informal"><a name="1006173"></a> <p class="TB"> The directory named in the <code>BACKGROUND_DUMP_DEST</code> initialization parameter.</p></td> <td class="Informal"><a name="1006175 "></a> <p class="TB">Contains a chronological log of errors, initialization parameter settings, and administration operations. Recor ds values for overwritten control file records (refer to <em class="Italic"><a class="olinkSRC SBYDB" href="../../server$101/b10823/t oc.htm">Oracle Data Guard Concepts and Administration</a></em>).</p></td></tr> <tr class="Informal" align="left" valign="top"> <td cl ass="Informal"><a name="1006184"></a> <p class="TB">Oracle trace file</p></td> <td class="Informal"><a name="1006186"></a> <p class ="TB">Oracle database server</p></td> <td class="Informal"><a name="1006188"></a> <p class="TB">The directory specified in the <code >USER_DUMP_DEST</code> initialization parameter.</p></td> <td class="Informal"><a name="1006190"></a> <p class="TB">Contains detaile d output generated by Oracle server processes. This file is created when an <code>ORA-600</code> or <code>ORA-3113</code> error messa ge occurs, whenever RMAN cannot allocate a channel, and when the database fails to load the media management library.</p></td></tr> < tr class="Informal" align="left" valign="top"> <td class="Informal"><a name="1010752"></a> <p class="TB"><code>sbtio.log</code></p>< /td> <td class="Informal"><a name="1006195"></a> <p class="TB">Third-party media management software</p></td> <td class="Informal">< a name="1006197"></a> <p class="TB">The directory specified in the <code>USER_DUMP_DEST</code> initialization parameter.</p></td> <t d class="Informal"><a name="1006199"></a> <p class="TB">Contains vendor-specific information written by the media management softwar e. This log does not contain Oracle server or RMAN errors.</p></td></tr> <tr class="Informal" align="left" valign="top"> <td class="I nformal"><a name="1006201"></a> <p class="TB">Media manager log file</p></td> <td class="Informal"><a name="1006203"></a> <p class= "TB">Third-party media management software</p></td> <td class="Informal"><a name="1006205"></a> <p class="TB">The filenames for any media manager logs other than <code>sbtio.log</code> are determined by the media management software.</p></td> <td class="Informal">< a name="1006207"></a> <p class="TB">Contains information on the functioning of the media management device.</p></td></tr></tbody></t able> <a name="1006210"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Recogni zing RMAN Error Message Stacks</font></h3>  <a name="1006211"></a> <p class="BP">RMAN reports errors as they occur. If an error is not retriable, that is, RMAN cannot perform failover to another channel to complete a particular job step, then RMAN als o reports a summary of the errors after all job sets complete. This feature is known as <strong class="Bold">deferred error reporting </strong>.</p> <a name="1006212"></a> <p class="BP">One way to determine whether RMAN encountered an error is to examine its return code, as described in <a href="rcmtroub.htm#1006542">"Identifying RMAN Return Codes"</a><a href="rcmtroub.htm#1006542"></a>. A second way is to search the RMAN output for the string <code>RMAN-00569</code>, which is the message number for the error stack banner. All RMAN errors are preceded by this error message. If you do not see an <code>RMAN-00569</code> message in the output, then there are n o errors. Following is sample output for a syntax error:</p> <pre class="CE"><a name="1006219"></a>RMAN-00571: ====================== ===================================== <a name="1006220"></a>RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== < a name="1006221"></a>RMAN-00571: =========================================================== <a name="1006222"></a>RMAN-00558: error encountered while parsing input commands <a name="1006223"></a>RMAN-01005: syntax error: found ")": expecting one of: "archivelog, ba ckup, backupset, controlfilecopy, current, database, datafile, datafilecopy, (, plus, ;, tablespace" <a name="1006224"></a>RMAN-010 07: at line 1 column 18 file: standard input </pre> <a name="1006226"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Identifying Error Codes</font></h3>  <a name="1006228"></a> <p class="BP">Typic ally, you find the following types of error codes in RMAN message stacks:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1 006229"></a>Errors prefixed with <code>RMAN-</code></li> <li class="LB1" type="disc"><a name="1006230"></a>Errors prefixed with <code >ORA-</code></li> <li class="LB1" type="disc"><a name="1006231"></a>Errors preceded by the line <code>Additional information:</code> <p><a name="1006241"></a></p> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" di r="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="1006234"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name ="1006240"></a> <p class="NB"><em class="Italic"><a class="olinkSRC ERRMG" href="../../server$101/b10744/toc.htm">Oracle Database Er ror Messages</a></em> for explanations of <code>RMAN</code> and <code>ORA</code> error codes</p></td></tr></table></div></li></ul> <a name="1006242"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Error Mess age Numbers</font></h4>  <a name="1006247"></a> <p class="BP"><a href="rcmtroub.htm#1006259">Table 15-1</a> indic ates the error ranges for common RMAN error messages, all of which are described in <em class="Italic"><a class="olinkSRC ERRMG" href ="../../server$101/b10744/toc.htm">Oracle Database Error Messages</a></em>.</p> <a name="1006322"></a> <h5 class="TT"><a name="10063 22"></a><a name="1006259"></a> <strong><font face="Arial, Helvetica, sans-serif"><em>Table 15-1 RMAN Error Message Ranges </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="1006263"></a> <font face="Arial, He lvetica, sans-serif"><strong>Error Range</strong></font></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="10 06265"></a> <font face="Arial, Helvetica, sans-serif"><strong>Cause</strong></font></th></tr></thead> <tbody> <tr class="Formal" alig n="left" valign="top"> <td class="Formal"><a name="1006267"></a> <p class="TB">0550-0999</p></td> <td class="Formal"><a name="100626 9"></a> <p class="TB">Command-line interpreter</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a nam e="1006271"></a> <p class="TB">1000-1999</p></td> <td class="Formal"><a name="1006273"></a> <p class="TB">Keyword analyzer</p></td> </tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006275"></a> <p class="TB">2000-2999</p></td> <td c lass="Formal"><a name="1006277"></a> <p class="TB">Syntax analyzer</p></td></tr> <tr class="Formal" align="left" valign="top"> <td c lass="Formal"><a name="1006279"></a> <p class="TB">3000-3999</p></td> <td class="Formal"><a name="1006281"></a> <p class="TB">Main layer</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006283"></a> <p class="TB">4000-4999< /p></td> <td class="Formal"><a name="1006285"></a> <p class="TB">Services layer</p></td></tr> <tr class="Formal" align="left" valign ="top"> <td class="Formal"><a name="1006287"></a> <p class="TB">5000-5499</p></td> <td class="Formal"><a name="1006289"></a> <p cla ss="TB">Compilation of <code>RESTORE</code> or <code>RECOVER</code> command</p></td></tr> <tr class="Formal" align="left" valign="top "> <td class="Formal"><a name="1006291"></a> <p class="TB">5500-5999</p></td> <td class="Formal"><a name="1006293"></a> <p class="T B">Compilation of <code>DUPLICATE</code> command</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a na me="1006295"></a> <p class="TB">6000-6999</p></td> <td class="Formal"><a name="1006297"></a> <p class="TB">General compilation</p>< /td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006299"></a> <p class="TB">7000-7999</p></td> < td class="Formal"><a name="1006301"></a> <p class="TB">General execution</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006303"></a> <p class="TB">8000-8999</p></td> <td class="Formal"><a name="1006305"></a> <p class="TB" >PL/SQL programs</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006307"></a> <p class="TB" >9000-9999</p></td> <td class="Formal"><a name="1006309"></a> <p class="TB">Low-level keyword analyzer</p></td></tr> <tr class="Form al" align="left" valign="top"> <td class="Formal"><a name="1006311"></a> <p class="TB">10000-10999</p></td> <td class="Formal"><a na me="1006313"></a> <p class="TB">Server-side execution</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal" ><a name="1006315"></a> <p class="TB">11000-11999</p></td> <td class="Formal"><a name="1006317"></a> <p class="TB">Interphase error s between PL/SQL and RMAN</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006319"></a> <p c lass="TB">12000-12999</p></td> <td class="Formal"><a name="1006321"></a> <p class="TB">Recovery catalog packages</p></td></tr></tbod y></table> <a name="1006323"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">OR A-19511: Media Manager Errors</font></h4>  <a name="1006325"></a> <p class="BP">In the event of a media manager error, ORA-19511 is signalled, and the media manager is expected to provide RMAN a descriptive error. RMAN will display the error passed ba ck to it by the media manager. For example, you might see this:</p> <pre class="CE"><a name="1010651"></a>ORA-19511: Error received f rom media manager layer, error text: <a name="1010652"></a> sbtpvt_open_input: file .* does not exist or cannot be accessed, errno = 2 <a name="1010649"></a> </pre> <a name="1010658"></a> <p class="BP">The message from the media manager should provide you with en ough information to let you fix the root problem. If it does not, you should refer to the documentation for your media manager or con tact your media management vendor support representative for further information. <code>ORA-19511</code> errors originate with the me dia manager, not the Oracle database. The database merely passes the message on from the media manager. The cause can only be address ed by the media management vendor.</p> <a name="1010668"></a> <p class="BP">Note that if you are still using an SBT 1.1-compliant me dia management layer, you may see some additional error message text. Output from an SBT 1.1-compliant media management layer is simi lar to the following:</p> <pre class="CE"><a name="1011588"></a>ORA-19507: failed to retrieve sequential file, handle="c-140148591-20 031014-06", parms="" <a name="1011589"></a>ORA-27007: failed to open file <a name="1011590"></a>Additional information: 7000 <a name ="1011591"></a>Additional information: 2 <a name="1011592"></a>ORA-19511: Error received from media manager layer, error text: <a nam e="1011593"></a> SBT error = 7000, errno = 0, sbtopen: backup file not found <a name="1011594"></a> </pre> <a name="1011586"></a> <p class="BP">The "Additional information" provided uses error codes specific to SBT 1.1. The values displayed correspond to the medi a manager message numbers and error text listed in <a href="rcmtroub.htm#1006338">Table 15-2</a>. RMAN re-signals the error, as an ORA-19511 <code>Error received from media manager layer</code> error, and a general error message related to the error code return ed from the media manager and including the SBT 1.1 error number is then displayed.</p> <a name="1006331"></a> <p class="BP">The SBT 1.1 error messages are listed here for your reference. <a href="rcmtroub.htm#1006338">Table 15-2</a> lists media manager messag e numbers and their corresponding error text. In the error codes, <em><code>O/S</code></em> stands for <em class="Italic">operating s ystem</em>. The errors prefixed with an asterisk are internal and should not typically be seen during normal operation.</p> <a name=" 1006467"></a> <h5 class="TT"><a name="1006467"></a><a name="1006338"></a> <strong><font face="Arial, Helvetica, sans-serif"><em>Tabl e 15-2 Media Manager Error Message Ranges (Page 1 of 2)</em></font></strong></h5> <table summary="" class="RuleFormal" border="1" wid th="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bot tom" scope="col"><a name="1006344"></a> <font face="Arial, Helvetica, sans-serif"><strong>Cause</strong></font></th> <th class="Forma l" align="left" valign="bottom" scope="col"><a name="1006346"></a> <font face="Arial, Helvetica, sans-serif"><strong>No.</strong></fo nt></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="1006348"></a> <font face="Arial, Helvetica, sans-serif" ><strong>Message</strong></font></th></tr></thead> <tbody> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name=" 1006350"></a> <p class="TB">sbtopen</p></td> <td class="Formal"><a name="1006352"></a> <p class="TB">7000 <a name="1006353"></a></p > <p class="TB">7001 <a name="1006354"></a></p> <p class="TB">7002* <a name="1006355"></a></p> <p class="TB">7003 <a name="1006356">< /a></p> <p class="TB">7004 <a name="1006357"></a></p> <p class="TB">7005 <a name="1006358"></a></p> <p class="TB">7006 <a name="10063 59"></a></p> <p class="TB">7007 <a name="1006360"></a></p> <p class="TB">7008 <a name="1006361"></a></p> <p class="TB">7009 <a name=" 1006362"></a></p> <p class="TB">7010 <a name="1006363"></a></p> <p class="TB">7011 <a name="1006364"></a></p> <p class="TB">7012*</p> </td> <td class="Formal"><a name="1006366"></a> <p class="TB">Backup file not found (only returned for read) <a name="1006367"></a>< /p> <p class="TB">File exists (only returned for write) <a name="1006368"></a></p> <p class="TB">Bad mode specified <a name="1006369" ></a></p> <p class="TB">Invalid block size specified <a name="1006370"></a></p> <p class="TB">No tape device found <a name="1006371"> </a></p> <p class="TB">Device found, but busy; try again later <a name="1006372"></a></p> <p class="TB">Tape volume not found <a name ="1006373"></a></p> <p class="TB">Tape volume is in-use <a name="1006374"></a></p> <p class="TB">I/O Error <a name="1006375"></a></p> <p class="TB">Can't connect with Media Manager <a name="1006376"></a></p> <p class="TB">Permission denied <a name="1006377"></a></p> <p class="TB">O/S error for example malloc, fork error <a name="1006378"></a></p> <p class="TB">Invalid argument(s) to sbtopen</p></ td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006380"></a> <p class="TB">sbtclose</p></td> <td class="Formal"><a name="1006382"></a> <p class="TB">7020* <a name="1006383"></a></p> <p class="TB">7021* <a name="1006384"></a></p> <p class="TB">7022 <a name="1006385"></a></p> <p class="TB">7023 <a name="1006386"></a></p> <p class="TB">7024* <a name="1006387"></ a></p> <p class="TB">7025</p></td> <td class="Formal"><a name="1006389"></a> <p class="TB">Invalid file handle or file not open <a n ame="1006390"></a></p> <p class="TB">Invalid flags to sbtclose <a name="1006391"></a></p> <p class="TB">I/O error <a name="1006392">< /a></p> <p class="TB">O/S error <a name="1006393"></a></p> <p class="TB">Invalid argument(s) to sbtclose <a name="1006394"></a></p> < p class="TB">Can't connect with Media Manager</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name= "1006396"></a> <p class="TB">sbtwrite</p></td> <td class="Formal"><a name="1006398"></a> <p class="TB">7040* <a name="1006399"></a> </p> <p class="TB">7041 <a name="1006400"></a></p> <p class="TB">7042 <a name="1006401"></a></p> <p class="TB">7043 <a name="1006402" ></a></p> <p class="TB">7044*</p></td> <td class="Formal"><a name="1006404"></a> <p class="TB">Invalid file handle or file not open <a name="1006405"></a></p> <p class="TB">End of volume reached <a name="1006406"></a></p> <p class="TB">I/O error <a name="1006407">< /a></p> <p class="TB">O/S error <a name="1006408"></a></p> <p class="TB">Invalid argument(s) to sbtwrite</p></td></tr> <tr class="For mal" align="left" valign="top"> <td class="Formal"><a name="1006410"></a> <p class="TB">sbtread</p></td> <td class="Formal"><a name= "1006412"></a> <p class="TB">7060* <a name="1006413"></a></p> <p class="TB">7061 <a name="1006414"></a></p> <p class="TB">7062 <a na me="1006415"></a></p> <p class="TB">7063 <a name="1006416"></a></p> <p class="TB">7064 <a name="1006417"></a></p> <p class="TB">7065* </p></td> <td class="Formal"><a name="1006419"></a> <p class="TB">Invalid file handle or file not open <a name="1006420"></a></p> <p class="TB">EOF encountered <a name="1006421"></a></p> <p class="TB">End of volume reached <a name="1006422"></a></p> <p class="TB">I /O error <a name="1006423"></a></p> <p class="TB">O/S error <a name="1006424"></a></p> <p class="TB">Invalid argument(s) to sbtread</ p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006426"></a> <p class="TB">sbtremove</p></td > <td class="Formal"><a name="1006428"></a> <p class="TB">7080 <a name="1006429"></a></p> <p class="TB">7081 <a name="1006430"></a>< /p> <p class="TB">7082 <a name="1006431"></a></p> <p class="TB">7083 <a name="1006432"></a></p> <p class="TB">7084 <a name="1006433"> </a></p> <p class="TB">7085 <a name="1006434"></a></p> <p class="TB">7086*</p></td> <td class="Formal"><a name="1006436"></a> <p cla ss="TB">Backup file not found <a name="1006437"></a></p> <p class="TB">Backup file in use <a name="1006438"></a></p> <p class="TB">I/ O Error <a name="1006439"></a></p> <p class="TB">Can't connect with Media Manager <a name="1006440"></a></p> <p class="TB">Permission denied <a name="1006441"></a></p> <p class="TB">O/S error <a name="1006442"></a></p> <p class="TB">Invalid argument(s) to sbtremove< /p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006444"></a> <p class="TB">sbtinfo</p></td> <td class="Formal"><a name="1006446"></a> <p class="TB">7090 <a name="1006447"></a></p> <p class="TB">7091 <a name="1006448"></a></ p> <p class="TB">7092 <a name="1006449"></a></p> <p class="TB">7093 <a name="1006450"></a></p> <p class="TB">7094 <a name="1006451">< /a></p> <p class="TB">7095*</p></td> <td class="Formal"><a name="1006453"></a> <p class="TB">Backup file not found <a name="1006454" ></a></p> <p class="TB">I/O Error <a name="1006455"></a></p> <p class="TB">Can't connect with Media Manager <a name="1006456"></a></p > <p class="TB">Permission denied <a name="1006457"></a></p> <p class="TB">O/S error <a name="1006458"></a></p> <p class="TB">Invalid argument(s) to sbtinfo</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="1006460"></a> <p cla ss="TB">sbtinit</p></td> <td class="Formal"><a name="1006462"></a> <p class="TB">7110* <a name="1006463"></a></p> <p class="TB">7111 </p></td> <td class="Formal"><a name="1006465"></a> <p class="TB">Invalid argument(s) to sbtinit <a name="1006466"></a></p> <p class ="TB">O/S error</p></td></tr></tbody></table> <a name="1006469"></a>  <h3 class="H2"><font face="Arial, Helvet ica, sans-serif" color="#330099">Interpreting RMAN Error Stacks</font></h3>  <a name="1006472"></a> <p class="BP">Some times you may find it difficult to identify the useful messages in the RMAN error stack. Note the following tips and suggestions:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006475"></a>Read the messages from the bottom up, because this is the order i n which RMAN issues the messages. The last one or two errors displayed in the stack are often the most informative.</li> <li class="L B1" type="disc"><a name="1011659"></a>When using an SBT 1.1 media management layer and presented with SBT 1.1 style error messages co ntaining the "<code>Additional information:</code>" numeric error codes, look for the <code>ORA-19511</code> message that follows for the text of error messages passed back to RMAN by the media manager. These should identify the real failure in the media management layer.</li> <li class="LB1" type="disc"><a name="1006476"></a>Look for the <code>RMAN-03002</code> or <code>RMAN-03009</code> message (<code>RMAN-03009</code> is the same as <code>RMAN-03002</code> but includes the channel ID), immediately following the error banner . These messages indicate which command failed. Syntax errors generate <code>RMAN-00558</code>.</li> <li class="LB1" type="disc"><a n ame="1006480"></a>Identify the basic type of error according to the error range chart in <a href="rcmtroub.htm#1006259">Table 15 -1</a> and then refer to <em class="Italic"><a class="olinkSRC ERRMG" href="../../server$101/b10744/toc.htm">Oracle Database Error Me ssages</a></em> for information on the most important messages.</li></ul> <a name="1006486"></a>  <h4 class="H 3"><font face="Arial, Helvetica, sans-serif" color="#330099">Interpreting RMAN Errors: Example</font></h4>  <a name="10 06487"></a> <p class="BP">You attempt a backup of tablespace <code>users</code> and receive the following message:</p> <pre class="C E"><a name="1006488"></a>Starting backup at 29-AUG-02 <a name="1006489"></a>using channel ORA_DISK_1 <a name="1006490"></a>RMAN-00571 : =========================================================== <a name="1006491"></a>RMAN-00569: =============== ERROR MESSAGE STACK F OLLOWS =============== <a name="1006492"></a>RMAN-00571: =========================================================== <a name="1006493 "></a>RMAN-03002: failure of backup command at 08/29/2002 15:14:03 <a name="1006494"></a>RMAN-20202: tablespace not found in the reco very catalog <a name="1006495"></a>RMAN-06019: could not translate tablespace name "USESR" <a name="1006496"></a> </pre> <a name="10 06497"></a> <p class="BP">The <code>RMAN-03002</code> error indicates that the <code>BACKUP</code> command failed. You read the last two messages in the stack first and immediately see the problem: no tablespace <code>usesr</code> appears in the recovery catalog bec ause you mistyped the name.</p> <a name="1006498"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-seri f" color="#330099">Interpreting Server Errors: Example</font></h4>  <a name="1006499"></a> <p class="BP">Assume that y ou attempt to recover a tablespace and receive the following errors:</p> <pre class="CE"><a name="1006500"></a>RMAN> RECOVER TABLE SPACE users; <a name="1006501"></a> <a name="1006502"></a>Starting recover at 29-AUG-01 <a name="1006503"></a>using channel ORA_DISK_ 1 <a name="1006504"></a> <a name="1006505"></a>starting media recovery <a name="1006506"></a>media recovery failed <a name="1006507"> </a>RMAN-00571: =========================================================== <a name="1006508"></a>RMAN-00569: =============== ERROR M ESSAGE STACK FOLLOWS =============== <a name="1006509"></a>RMAN-00571: =========================================================== <a name="1006510"></a>RMAN-03002: failure of recover command at 08/29/2001 15:18:43 <a name="1006511"></a>RMAN-11003: failure during pa rse/execution of SQL statement: alter database recover if needed tablespace USERS <a name="1006513"></a>ORA-00283: recovery session canceled due to errors <a name="1006514"></a>ORA-01124: cannot recover data file 8 - file is in use or recovery <a name="1006515"></a >ORA-01110: data file 8: '/oracle/oradata/trgt/users01.dbf' <a name="1006516"></a> </pre> <a name="1006517"></a> <p class="BP">As su ggested, you start reading from the bottom up. The <code>ORA-01110</code> message explains there was a problem with the recovery of d atafile <code>users01.dbf</code>. The second error indicates that the database cannot recover the datafile because it is in use or al ready being recovered. The remaining RMAN errors indicate that the recovery session was cancelled due to the server errors. Hence, yo u conclude that because you were not already recovering this datafile, the problem must be that the datafile is online and you need t o take it offline and restore a backup.</p> <a name="1011683"></a>  <h4 class="H3"><font face="Arial, Helvetic a, sans-serif" color="#330099">Interpreting SBT 2.0 Media Management Errors: Example</font></h4>  <a name="1011684"></a > <p class="BP">Assume that you use a tape drive and receive the following output during a backup job:</p> <pre class="CE"><a name=" 1011689"></a>RMAN-00571: =========================================================== <a name="1011690"></a>RMAN-00569: ============== = ERROR MESSAGE STACK FOLLOWS =============== <a name="1011691"></a>RMAN-00571: ===================================================== ====== <a name="1011692"></a>ORA-19624: operation failed, retry possible <a name="1011693"></a>ORA-19507: failed to retrieve sequenti al file, handle="/tmp/foo", parms="" <a name="1011837"></a>ORA-27029: skgfrtrv: sbtrestore returned error <a name="1011838"></a>ORA-1 9511: Error received from media manager layer, error text: <a name="1011839"></a> sbtpvt_open_input:file /tmp/foo does not exist or cannot be accessed, errno=2 <a name="1011833"></a> </pre> <a name="1011687"></a> <p class="BP">The error text displayed following th e <code>ORA-19511</code> error is generated by the media manager and describes the real source of the failure. Refer to the media man ager documentation to interpret this error.</p> <a name="1006518"></a>  <h4 class="H3"><font face="Arial, Helv etica, sans-serif" color="#330099">Interpreting SBT 1.1 Media Management Errors: Example</font></h4>  <a name="1006519" ></a> <p class="BP">Assume that you use a tape drive and receive the following output during a backup job:</p> <pre class="CE"><a na me="1006520"></a>RMAN-00571: =========================================================== <a name="1006521"></a>RMAN-00569: ========== ===== ERROR MESSAGE STACK FOLLOWS =============== <a name="1006522"></a>RMAN-00571: ================================================= ========== <a name="1006523"></a>RMAN-03009: failure of backup command on c1 channel at 09/04/2001 13:18:19 <a name="1006524"></a>ORA -19506: failed to create sequential file, name="07d36ecp_1_1", parms="" <a name="1006525"></a>ORA-27007: failed to open file <a name= "1006526"></a>SVR4 Error: 2: No such file or directory <a name="1006527"></a>Additional information: 7005 <a name="1006528"></a>Addit ional information: 1 <a name="1006529"></a>ORA-19511: Error received from media manager layer, error text: <a name="1006530"></a> S BT error = 7005, errno = 2, sbtopen: system error <a name="1006531"></a> </pre> <a name="1006532"></a> <p class="BP">The main inform ation of interest returned by SBT 1.1 media managers is the error code in the "Additional information" line:</p> <pre class="CE"><a n ame="1006533"></a>Additional information: 7005 <a name="1006534"></a> </pre> <a name="1006535"></a> <p class="BP">Referring to <a hr ef="rcmtroub.htm#1006338">Table 15-2, "Media Manager Error Message Ranges"</a>, you discover that error <code>7005</code> means that the media management device is busy. So, the media management software is not able to write to the device because it is in use o r there is a problem with it.</p> <a name="1006540"></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 format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="1006538"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</stron g></font> <a name="1006539"></a> <p class="NB">The <code>sbtio.log</code> contains information written by the media management softw are, <em class="Italic">not</em> the Oracle database server. Hence, you must consult your media vendor documentation to interpret the error codes and messages. If no information is written to the <code>sbtio.log</code>, contact your media manager support to ask whet her they are writing error messages in some other location, or whether there are steps you need to take to have the media manager err ors appear in sbtio.log.</p> <hr></td></tr></table></div> <a name="1006542"></a>  <h3 class="H2"><font face="A rial, Helvetica, sans-serif" color="#330099">Identifying RMAN Return Codes</font></h3>  <a name="1006544"></a> <p clas s="BP">One way to determine whether RMAN encountered an error is to examine its return code or exit status. The RMAN client returns 0 to the shell from which it was invoked if no errors occurred, and a nonzero error value otherwise.</p> <a name="1011730"></a> <p cl ass="BP">How you access this return code depends upon the environment from which you invoked the RMAN client. For example, if you are running UNIX with the C shell, then, when RMAN completes, the return code is placed in a shell variable called <code>$status</code>. The method of returning exit status is a detail specific to the host operating system rather than the RMAN client.</p> <a name="1006 547"></a>  <h2 class="H1"><a name="BRADV175"><font face="Arial, Helvetica, sans-serif" color="#330099">Testing the Media Management API</font></a></h2>  <a name="1006549"></a> <p class="BP">On some platforms, Oracle provides a d iagnostic tool called <code>sbttest</code>. This utility performs a simple test of the media management software by attempting to com municate with the media manager as the Oracle database server would.</p> <a name="1006550"></a>  <h3 class="H2 "><font face="Arial, Helvetica, sans-serif" color="#330099">Obtaining the sbttest Utility</font></h3>  <a name="1006552 "></a> <p class="BP">On UNIX, the <code>sbttest</code> utility is typically located in <code>$ORACLE_HOME/bin</code>. If for some re ason the utility is not included with your platform, then contact Oracle Support to obtain the C version of the program. You can comp ile this version of the program on all UNIX platforms.</p> <a name="1006553"></a> <p class="BP">Note that on platforms such as Solar is, you do not have to relink when using <code>sbttest</code>. On other platforms, relinking may be necessary.</p> <a name="1006554"> </a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Obtaining Online Documentation for the sbttest Utility</font></h3>  <a name="1006555"></a> <p class="BP">For online documentation of <code>sbttest</c ode>, issue the following on the command line:</p> <pre class="CE"><a name="1006556"></a>% sbttest <a name="1006557"></a> </pre> <a name="1006558"></a> <p class="BP">The program displays the list of possible arguments for the program:</p> <pre class="CE"><a name="1 006559"></a>Error: backup file name must be specified <a name="1010176"></a>Usage: sbttest backup_file_name # this is the only requir ed parameter <a name="1010177"></a> <-dbname database_name> <a name="1010178"></a> <-trace trace _file_name> <a name="1010179"></a> <-remove_before> <a name="1010180"></a> <-no_remove_after& gt; <a name="1010181"></a> <-read_only> <a name="1010182"></a> <-no_regular_backup_restore> <a name="1010183"></a> <-no_proxy_backup> <a name="1010184"></a> <-no_proxy_restore> <a name= "1010185"></a> <-file_type n> <a name="1010186"></a> <-copy_number n> <a name="1010187"></a> <-media_pool n> <a name="1010188"></a> <-os_res_size n> <a name="1010189"></a> <-pl_res_size n> <a name="1010190"></a> <-block_size block_size> <a name="1010191"></a> < -block_count block_count> <a name="1010192"></a> <-proxy_file os_file_name bk_file_name <a name="1010193"></a> [os_res_size pl_res_size block_size block_count]> <a name="1010194"></a> <-libname sbt_l ibrary_name> <a name="1006577"></a> </pre> <a name="1006579"></a> <p class="BP">The display also indicates the meaning of each ar gument. For example, following is the description for two optional parameters:</p> <pre class="CE"><a name="1006580"></a>Optional par ameters: <a name="1006581"></a> -dbname specifies the database name which will be used by SBT <a name="1006582"></a> to i dentify the backup file. The default is "sbtdb" <a name="1006583"></a> -trace specifies the name of a file where the Media Managem ent <a name="1006584"></a> software will write diagnostic messages. </pre> <a name="1006585"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Using the sbttest Utility</font></h3>  <a name ="1006586"></a> <p class="BP">Use <code>sbttest</code> to perform a quick test of the media manager. The following table explains ho w to interpret the output.</p> <a name="1006600"></a> <table summary="" class="RuleInformal" border="1" width="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Informal"> <th class="Informal" align="left" valign="bottom" scope="col"><a n ame="1006589"></a> <font face="Arial, Helvetica, sans-serif"><strong>If sbttest returns . . .</strong></font></th> <th class="Informa l" align="left" valign="bottom" scope="col"><a name="1006591"></a> <font face="Arial, Helvetica, sans-serif"><strong>Then . . .</stro ng></font></th></tr></thead> <tbody> <tr class="Informal" align="left" valign="top"> <td class="Informal"><a name="1006593"></a> <p class="TB">0</p></td> <td class="Informal"><a name="1006595"></a> <p class="TB">The program ran without error. In other words, the m edia manager is installed and can accept a data stream and return the same data when requested.</p></td></tr> <tr class="Informal" al ign="left" valign="top"> <td class="Informal"><a name="1006597"></a> <p class="TB">a nonzero value</p></td> <td class="Informal"><a name="1006599"></a> <p class="TB">The program encountered an error. Either the media manager is not installed or it is not configure d correctly.</p></td></tr></tbody></table> <a name="1006601"></a> <p class="BP"><strong class="Bold">To use sbttest:</strong></p> <o l class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006602"></a>Make sure the program is installed and included in t he system path by typing <code>sbttest</code> at the command line: <pre class="CE1"><a name="1006603"></a>% sbttest <a name="1006604 "></a> </pre> <a name="1006605"></a> <p class="BP1">If the program is operational, then you should see a display of the online docum entation.</p></li> <li class="LN1" type="1" value="2"><a name="1006606"></a>Execute the program, specifying any of the arguments desc ribed in the online documentation. For example, enter the following to create test file <code>some_file.f</code> and write the output to <code>sbtio.log</code>: <pre class="CE1"><a name="1006607"></a>% sbttest some_file.f -trace sbtio.log <a name="1006608"></a> </p re> <a name="1006609"></a> <p class="BP1">You can also test a backup of an existing datafile. For example, this command tests datafi le <code>tbs_33.f</code> of database <code>prod</code>:</p> <pre class="CE1"><a name="1006610"></a>% sbttest tbs_33.f -dbname prod <a name="1006611"></a> </pre> </li> <li class="LN1" type="1" value="3"><a name="1006612"></a>Examine the output. If the program encount ers an error, then it provides messages describing the failure. For example, if the database cannot find the library, you see: <pre class="CE1"><a name="1006613"></a>libobk.so could not be loaded. Check that it is installed properly, and that LD_LIBRARY_PATH envir onment variable (or its equivalent on your platform) includes the directory where this file can be found. Here is some additional i nformation on the cause of this error: <a name="1006614"></a>ld.so.1: sbttest: fatal: libobk.so: open failed: No such file or directo ry <a name="1006615"></a> </pre> </li></ol> <a name="1006616"></a> <p class="BP">Note that in some cases <code>sbttest</code> can wor k but an RMAN backup does not. The reasons can be the following:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006617">< /a>The user who starts <code>sbttest</code> is not the owner of the Oracle processes.</li> <li class="LB1" type="disc"><a name="10066 18"></a>If the database server is not linked with the media management library or cannot load it dynamically when needed, then RMAN b ackups to the media manager fail, but <code>sbttest</code> may still work.</li> <li class="LB1" type="disc"><a name="1006619"></a>The <code>sbttest</code> program passes all environment parameters from the shell but RMAN does not.</li></ul> <a name="1006621"></a> <! --TOC=h1-"1006621"--> <h2 class="H1"><a name="BRADV176"><font face="Arial, Helvetica, sans-serif" color="#330099">Terminating an RMAN Command</font></a></h2>  <a name="1006623"></a> <p class="BP">There are several ways to terminate an RMAN command in the middle of execution:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1006624"></a>The preferred method is to press <cod e>CTRL+C</code> (or the equivalent "attention" key combination for your system) in the RMAN interface. This will also terminates allo cated channels, unless they are hung in the media management code, as happens when, for example, when they are waiting for a tape to be mounted.</li> <li class="LB1" type="disc"><a name="1010689"></a>You can kill the server session corresponding to the RMAN channel by running the SQL <code>ALTER</code> <code>SYSTEM KILL SESSION</code> statement.</li> <li class="LB1" type="disc"><a name="1006626"> </a>You can terminate the server session corresponding to the RMAN channel on the operating system.</li></ul> <a name="1006627"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Terminating the Session with ALTER S YSTEM KILL SESSION</font></h3>  <a name="1006628"></a> <p class="BP">You can identify the Oracle session ID for an RMA N channel by looking in the RMAN log for messages with the format shown in the following example:</p> <pre class="CE"><a name="100662 9"></a>channel ch1: sid=15 devtype=SBT_TAPE <a name="1006630"></a> </pre> <a name="1006631"></a> <p class="BP">The <code>sid</code> and <code>devtype</code> are displayed for each allocated channel. Note that the Oracle <code>sid</code> is different from the operat ing system process ID. You can kill the session using a SQL <code>ALTER</code> <code>SYSTEM</code> <code>KILL</code> <code>SESSION</c ode> statement.</p> <a name="1011757"></a> <p class="BP"><code>ALTER SYSTEM KILL SESSION</code> takes two arguments, the <code>sid</ code> printed in the RMAN message and a serial number, both of which can be obtained by querying <code>V$SESSION</code>. For example, run the following statement, where <em><code>sid_in_rman_output</code></em> is the number from the RMAN message:</p> <pre class="CE" ><a name="1006633"></a>SELECT SERIAL# FROM V$SESSION WHERE SID=<em>sid_in_rman_output</em>; <a name="1006634"></a> </pre> <a name="1 006636"></a> <p class="BP">Then, run the following statement, substituting the <em><code>sid_in_rman_output</code></em> and serial nu mber obtained from the query:</p> <pre class="CE"><a name="1006637"></a>ALTER SYSTEM KILL SESSION '<em>sid_in_rman_output</em><em cla ss="Italic">,</em><em>serial#</em>'; <a name="1011774"></a> </pre> <a name="1011775"></a> <p class="BP">Note that this will not unha ng the session if the session is hung in media manager code..</p> <a name="1011776"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Terminating the Session at the Operating System Level</font></h3>  <a name="1006641"></a> <p class="BP">Finding and killing the processes that are associated with the server sessions is operating sy stem specific. On some platforms the server sessions are not associated with any processes at all. Refer to your operating system spe cific documentation for more information.</p> <a name="1006646"></a>  <h3 class="H2"><font face="Arial, Helvet ica, sans-serif" color="#330099">Terminating an RMAN Session That Is Hung in the Media Manager</font></h3>  <a name="10 06647"></a> <p class="BP">You may sometimes need to kill an RMAN job that is hung in the media manager. The best way to terminate RM AN when the channel connections are hung in the media manager is to kill the session in the media manager. If this action does not so lve the problem, then on some platforms, such as Unix, you may be able to kill the Oracle processes of the connections. (Note that ki lling the Oracle processes may cause problems from the media manager. See your media manager documentation for details.)</p> <a name= "1006662"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Components of an RMAN Session</font></h4>  <a name="1010324"></a> <p class="BP">The nature of an RMAN session depends on the operating syst em. In UNIX, an RMAN session has the following processes associated with it:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name ="1010325"></a>The <strong class="GlossaryTerm">RMAN client process</strong> itself</li> <li class="LB1" type="disc"><a name="1010374 "></a>The <strong class="Bold">default channel</strong>, the initial connection to the target database</li> <li class="LB1" type="dis c"><a name="1010352"></a>One <strong class="Bold">target connection</strong> to the target database corresponding to each allocated c hannel</li> <li class="LB1" type="disc"><a name="1010326"></a>The <strong class="Bold">catalog connection</strong> to the recovery ca talog database, if you use a recovery catalog</li> <li class="LB1" type="disc"><a name="1006666"></a>An <strong class="GlossaryTerm"> auxiliary connection</strong> to an auxiliary instance, during <code>DUPLICATE</code> or TSPITR operations</li> <li class="LB1" type= "disc"><a name="1006668"></a>A <strong class="Bold">polling connection</strong> to the target database, used for monitoring RMAN comm and execution on the various allocated channels. By default, RMAN makes one polling connection. RMAN makes additional polling connect ions if you use different connect strings in the <code>ALLOCATE</code> <code>CHANNEL</code> or <code>CONFIGURE</code> <code>CHANNEL</ code> commands. One polling connection exists for each distinct connect string used in the <code>ALLOCATE</code> <code>CHANNEL</code> or <code>CONFIGURE</code> <code>CHANNEL</code> command.</li></ul> <a name="1006671"></a>  <h4 class="H3"><fon t face="Arial, Helvetica, sans-serif" color="#330099">Process Behavior During a Hung Job</font></h4>  <a name="1006672" ></a> <p class="BP">RMAN usually hangs because one of the channel connections is waiting in the media manager code for a tape resour ce. The catalog connection and the default channel appear to hang, because they are waiting for RMAN to tell them what to do. Polling connections seem to be in an infinite loop while polling the RPC under the control of the RMAN process.</p> <a name="1006673"></a> <p class="BP">If you kill the RMAN process itself, then you also kill the catalog connection, the auxiliary connection, the default c hannel, and the polling connections. If target and auxiliary connections are not hung in the media manager code, they also terminate. If either the target connection or any of the auxiliary connections are executing in the media management layer, they will not termi nate until the processes are manually killed at the operating system level.</p> <a name="1010379"></a> <p class="BP">Not all media m anagers can detect the termination of the Oracle process. Those which cannot may keep resources busy or continue processing. Consult your media manager documentation for details.</p> <a name="1006674"></a> <p class="BP">Terminating the catalog connection does not c ause the RMAN process to terminate because RMAN is not performing catalog operations while the backup or restore is in progress. Remo ving default channel and polling connections causes the RMAN process to detect that one of the channels has died and then proceed to exit. In this case, the connections to the hung channels remain active as described previously.</p> <a name="1011784"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Terminating an RMAN Session: Basic Steps</font ></h4>  <a name="1011785"></a> <p class="BP">Once the hung channels in the media manager code are killed, the RMAN pro cess detects this termination and proceed to exit, removing all connections except target connections that are still operative in the media management layer. The caveat about the media manager resources still applies in this case.</p> <a name="1006678"></a> <p clas s="BP"><strong class="Bold">To terminate an Oracle process that is hung in the media manager:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1006681"></a>Query <code>V$SESSION</code> and <code>V$SESSION_WAIT</code> as described in <a href="rcmconc3.htm#1008554">"Monitoring RMAN Through V$ Views"</a><a href="rcmconc3.htm#1008554"></a>. For example, execute the f ollowing query: <pre class="CE1"><a name="1006686"></a>COLUMN EVENT FORMAT a10 <a name="1006687"></a>COLUMN SECONDS_IN_WAIT FORMAT 9 99 <a name="1006688"></a>COLUMN STATE FORMAT a20 <a name="1006689"></a>COLUMN CLIENT_INFO FORMAT a30 <a name="1006690"></a> <a name=" 1006691"></a>SELECT p.SPID, EVENT, SECONDS_IN_WAIT AS SEC_WAIT, <a name="1006692"></a> STATE, CLIENT_INFO <a name="1006693"></ a>FROM V$SESSION_WAIT sw, V$SESSION s, V$PROCESS p <a name="1006694"></a>WHERE sw.EVENT LIKE 'sbt%' <a name="1006695"></a> AND s.SID=sw.SID <a name="1006696"></a> AND s.PADDR=p.ADDR <a name="1010412"></a>; <a name="1006698"></a> </pre> <a name="1006699" ></a> <p class="BP1">Examine the SQL output to determine which sbt functions are waiting. For example, the output may be as follows:< /p> <pre class="CE1"><a name="1006700"></a>SPID EVENT SEC_WAIT STATE CLIENT_INFO <a name="1006701"></a>---- --- ------- ---------- -------------------- ------------- <a name="1006702"></a>8642 sbtwrite2 600 WAITING rman chan nel=ORA_SBT_TAPE_1 <a name="1006703"></a>8374 sbtwrite2 600 WAITING rman channel=ORA_SBT_TAPE_2 <a name="1006704 "></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1006705"></a>Using operating system-level tools appropriate to your p latform, kill the hung sessions. For example, on Solaris execute a <code>kill</code> <code>-9</code> command: <pre class="CE1"><a na me="1006706"></a>% kill -9 8642 8374 <a name="1006707"></a> </pre> <a name="1011364"></a> <p class="BP1">On Windows, there is a comm and-line utility called <code>ORAKILL</code> which lets you kill a specific thread in this situation. From a command prompt, run the following command:</p> <pre class="CE1"><a name="1011390"></a>orakill <em class="Italic">sid</em> <em class="Italic">thread_id </em>< a name="1011415"></a> </pre> <a name="1011380"></a> <p class="BP1">where <em><code>sid</code></em> identifies the database instance to target, and the <em><code>thread_id</code></em> is the <code>SPID</code> value from the query in step 1.</p></li> <li class="LN1" type="1" value="3"><a name="1006708"></a>Check that the media manager also clears its processes. If any remain, the next backup or re store operation may hang again, due to the previous hang. In some media managers, the only solution is to shut down and restart the m edia manager. If the documentation from the media manager does not provide the needed information, contact technical support for the media manager. <p><a name="1006713"></a></p> <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="1010427"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong> </font> <a name="1006711"></a> <p class="NB">Your operating system specific documentation for the relevant commands</p></td></tr></t able></div></li></ol> <a name="1010302"></a>  <h2 class="H1"><a name="BRADV178"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Troubleshooting Scenarios</font></a></h2>  <a name="1010256"></a> <p class="BP">This section contains these topics:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1007143"></a><a href="rcmtroub.htm#1007193"> After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario</a></li> <li class="LB1" type="disc"><a name="1007147">< /a><a href="rcmtroub.htm#1007240">Backup Job Is Hanging: Scenario</a></li> <li class="LB1" type="disc"><a name="1007151"></a><a href= "rcmtroub.htm#1007309">RMAN Fails to Start RPC Call: Scenario</a></li> <li class="LB1" type="disc"><a name="1007155"></a><a href="rcm troub.htm#1007325">Backup Fails with Invalid RECID Error: Scenario</a></li> <li class="LB1" type="disc"><a name="1007159"></a><a href ="rcmtroub.htm#1007444">Backup Fails Because of Control File Enqueue: Scenario</a></li> <li class="LB1" type="disc"><a name="1007163" ></a><a href="rcmtroub.htm#1007482">RMAN Fails to Delete All Archived Logs: Scenario</a></li> <li class="LB1" type="disc"><a name="10 07167"></a><a href="rcmtroub.htm#1007500">Backup Fails Because RMAN Cannot Locate an Archived Log: Scenario</a></li> <li class="LB1" type="disc"><a name="1007175"></a><a href="rcmtroub.htm#1007539">RMAN Does Not Recognize Character Set Name: Scenario</a></li> <li cl ass="LB1" type="disc"><a name="1007179"></a><a href="rcmtroub.htm#1011443">RMAN Denies Logon to Target Database: Scenario</a></li> <l i class="LB1" type="disc"><a name="1007183"></a><a href="rcmtroub.htm#1007582">Database Duplication Fails Because of Missing Log: Sce nario</a></li> <li class="LB1" type="disc"><a name="1007187"></a><a href="rcmtroub.htm#1007613">Duplication Fails with Multiple RMAN- 06023 Errors: Scenario</a></li> <li class="LB1" type="disc"><a name="1007191"></a><a href="rcmtroub.htm#1007637">UNKNOWN Database Nam e Appears in Recovery Catalog: Scenario</a></li></ul> <a name="1007193"></a>  <h3 class="H2"><font face="Arial , Helvetica, sans-serif" color="#330099">After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario</font></h3> <!- -/TOC=h2--> <a name="1007195"></a> <p class="BP">In this scenario, you install and test the media manager as explained in <a href="r cmconfg.htm#1006528">"Configuring RMAN to Make Backups to a Media Manager"</a><a href="rcmconfg.htm#1006528"></a>, but you still cann ot make RMAN back up to tape. For example, after allocating the <code>sbt</code> channel, you receive an error stack similar to the f ollowing:</p> <pre class="CE"><a name="1007202"></a>RMAN-00571: =========================================================== <a name=" 1007203"></a>RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== <a name="1007204"></a>RMAN-00571: ============== ============================================= <a name="1007205"></a>RMAN-03009: failure of allocate command on c1 channel at 08/29/20 01 17:16:54 <a name="1007206"></a>ORA-19554: error allocating device, device type: SBT_TAPE, device name: <a name="1007207"></a><str ong class="Bold">ORA-27211: Failed to load Media Management Library </strong><a name="1007208"></a>Additional information: 25 <a name ="1011788"></a> </pre> <a name="1011789"></a> <p class="BP">The most important line of the error output is the ORA-27211 error. It i ndicates the basic problem, that the media management library could not be loaded. Typically, there is no need to refer to the trace file or sbtio.log in such a case.</p> <a name="1011790"></a>  <h4 class="H3"><font face="Arial, Helvetica, san s-serif" color="#330099">After Installation of Media Manager, RMAN Channel Allocation Fails: Diagnosis</font></h4>  <a name="1007210"></a> <p class="BP">The <code>ORA-27211</code> error indicates that the channel allocation is failing because the data base is not loading the media management library. If the channel allocation fails, then the database generates a trace file in the <c ode>USER_DUMP_DEST</code> location that contains the error that caused the channel allocation to fail. The trace file should have the complete path name of the media management library loaded by the database as well as any other media manager errors or operating sys tem errors. For example, the trace file on UNIX may be called something like <code>/oracle/rdbms/log/prod1_ora_16226.trc</code>, and may contain information such as the following:</p> <pre class="CE"><a name="1007211"></a>*** 2001-08-29 17:16:54.385 <a name="1007212 "></a>SKGFQ OSD: Error in function sbtinit on line 2396 <a name="1007213"></a>SKGFQ OSD: Look for SBT Trace messages in file /oracle/ rdbms/log/sbtio.log <a name="1007214"></a>SBT Initialize failed for oracle.static <a name="1007215"></a> </pre> <a name="1007216">< /a> <p class="BP">The last line of this output indicates that Oracle is loading the default static library instead of the media manag ement library that you installed.</p> <a name="1010768"></a> <p class="BP">You may find more detailed information in the file <code> sbtio.log</code>, as described in the error message. Note, however, that writing SBT trace messages is the responsibility of the medi a management software, not the Oracle database or RMAN. The media management vendor may not have implemented the writing of trace mes sages in a particular situation. Contact the media management vendor for details about the trace messages written to sbtio.log.</p> < a name="1007217"></a> <p class="BP">To test the loading of the media management library, try allocating a channel by using the <code >PARMS</code> parameter <code>SBT_LIBRARY</code> to force the loading of the media management library. For example, if your library i s called <code>/vendor/lib/some_mm_lib.so</code>, then run a command such as the following, making sure to specify whatever <code>PAR MS</code> settings are required by your media manager:</p> <pre class="CE"><a name="1007218"></a>RUN <a name="1007219"></a>{ <a name= "1007220"></a> ALLOCATE CHANNEL c1 DEVICE TYPE sbt <a name="1007221"></a> PARMS='SBT_LIBRARY=/vendor/lib/some_mm_lib.so', <a nam e="1007222"></a> 'ENV=(NSR_SERVER=tape_svr,NSR_CLIENT=oracleclnt,NSR_GROUP=oracle_tapes)'; <a name="1007223"></a>} <a name="100722 4"></a> </pre> <a name="1007225"></a> <p class="BP">If the channel allocation fails, then check the trace file again to see whether you can learn anything new. If the channel allocation with <code>SBT_LIBRARY</code> succeeds, but an ordinary <code>sbt</code> channe l allocation fails, then the database is probably trying to load a library other than the one you installed. By default, the database expects to find the media management library at <code>$ORACLE_HOME/lib/libobk.so</code> on UNIX, or <code>%ORACLE_HOME%/bin/orasbt.d ll</code> on NT. You may have more than one library in the operating system path, and the database is loading the wrong one.</p> <a n ame="1007226"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">After Installatio n of Media Manager, RMAN Channel Allocation Fails: Solution</font></h4>  <a name="1007227"></a> <p class="BP">If the p roblem is that the database is not loading the correct library, then make sure that the library is named correctly in the <code>SBT_L IBRARY</code> parameter.</p> <a name="1007237"></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 format a note"> <tr clas s="Note"> <td class="Note"> <hr> <a name="1007230"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong ></font> <a name="1007236"></a> <p class="NB"><em class="Italic"><a class="xlinkSRC RCMRF104" href="../../server$101/b10770/rcmsynta 6.htm#RCMRF104">Oracle Database Recovery Manager Reference</a></em> for descriptions of the legal <code>PARMS</code> parameters</p> < hr></td></tr></table></div> <a name="1007240"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" c olor="#330099">Backup Job Is Hanging: Scenario</font></h3>  <a name="1007242"></a> <p class="BP">In this scenario, an RMAN backup job starts as normal and then pauses inexplicably:</p> <pre class="CE"><a name="1011258"></a>Recovery Manager: Release 10 .1.0.2.0 - Production <a name="1011259"></a> <a name="1011260"></a>Copyright (c) 1995, 2003, Oracle. All rights reserved. <a name="1 011261"></a> <a name="1007244"></a>connected to target database: TRGT <a name="1007245"></a>connected to recovery catalog database <a name="1007246"></a> <a name="1007247"></a>RMAN> BACKUP TABLESPACE SYSTEM, tools; <a name="1007248"></a> <a name="1007249"></a>all ocated channel: t1 <a name="1007250"></a>channel t1: sid=16 devtype=SBT_TAPE <a name="1007251"></a> <a name="1007252"></a>channel t1: starting datafile backupset <a name="1007253"></a>set_count=15 set_stamp=338309600 <a name="1007254"></a>channel t1: including dataf ile 2 in backupset <a name="1007255"></a>channel t1: including datafile 1 in backupset <a name="1007256"></a>channel t1: including cu rrent controlfile in backupset <a name="1007257"></a># Hanging here for 30 minutes now </pre> <a name="1007258"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Job Is Hanging: Diagnosis</font></h4>  <a name="1007259"></a> <p class="BP">If a backup job is hanging, that is, not proceeding, then several scenarios are possibl e:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1007261"></a>A server-side or media management error occurred.</li> <li class="LB1" type="disc"><a name="1007262"></a>RMAN is waiting for an event such as the insertion of a new cassette into the tape devi ce.</li></ul> <a name="1007268"></a> <p class="BP">Query <code>sbt</code> wait events to gain more information. For example, run the following query on the target instance:</p> <pre class="CE"><a name="1007270"></a>COLUMN EVENT FORMAT a10 <a name="1007271"></a>COLU MN SECONDS_IN_WAIT FORMAT 999 <a name="1007272"></a>COLUMN STATE FORMAT a20 <a name="1007273"></a>COLUMN CLIENT_INFO FORMAT a30 <a na me="1007274"></a> <a name="1007275"></a>SELECT p.SPID, EVENT, SECONDS_IN_WAIT AS SEC_WAIT, <a name="1007276"></a> STATE, CLIEN T_INFO <a name="1007277"></a>FROM V$SESSION_WAIT sw, V$SESSION s, V$PROCESS p <a name="1007278"></a>WHERE sw.EVENT LIKE 'sbt%' <a nam e="1007279"></a> AND s.SID=sw.SID <a name="1007280"></a> AND s.PADDR=p.ADDR <a name="1007281"></a>; <a name="1007282"></a> </pre> <a name="1007283"></a> <p class="BP">Examine the SQL output to determine which sbt functions are waiting. For example, the o utput may be as follows:</p> <pre class="CE"><a name="1007284"></a>SPID EVENT SEC_WAIT STATE CLIENT_INFO <a nam e="1007285"></a>---- ---------- ---------- -------------------- ------------------------------ <a name="1007286"></a>8642 sbtbackup 1500 WAITING rman channel=ORA_SBT_TAPE_1 </pre> <a name="1007288"></a> <h4 class="H3"><fon t face="Arial, Helvetica, sans-serif" color="#330099">Backup Job Is Hanging: Solution</font></h4>  <a name="1007289"></ a> <p class="BP">Because the causes of a hung backup job can be varied, so are the solutions. For example, backup jobs often hang si mply because the tape device has completely filled the current cassette and is waiting for a new tape to be inserted. Ideally, the qu ery of the <code>sbt</code> wait events should indicate the problem.</p> <a name="1010818"></a> <p class="BP">In this example, a sin gle sbtbackup has taken 1500 seconds, so RMAN is waiting on the media manager to finish its write operation. Check that the media man ager is functioning normally, and contact the media management vendor's technical support for assistance.</p> <a name="1007290"></a> <p class="BP">If the <code>sbt</code> wait event query is unhelpful, then examine media manager process, log, and trace files for si gns of abnormal termination or other errors (refer to the description of message files in <a href="rcmtroub.htm#1006143">"Identifying Types of Message Output"</a><a href="rcmtroub.htm#1006143"></a>).</p> <a name="1007307"></a> <div align="center"> <table class="Not e" 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="1007299"></a><font face="Arial, Helvetica, sans-s erif"><strong class="NH">See Also:</strong></font> <a name="1007305"></a> <p class="NB"><a href="rcmtroub.htm#1011784">"Terminating an RMAN Session: Basic Steps"</a><a href="rcmtroub.htm#1011784"></a> to learn how to kill an RMAN session that is hanging</p> <hr></t d></tr></table></div> <a name="1007309"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color=" #330099">RMAN Fails to Start RPC Call: Scenario</font></h3>  <a name="1007311"></a> <p class="BP">In this scenario, yo u run a backup job and receive message output similar to the following:</p> <pre class="CE"><a name="1007312"></a>channel c8: includi ng datafile number 47 in backupset <a name="1007313"></a>RPC call appears to have failed to start on channel c9 <a name="1007314"></a >RPC call ok on channel c9 <a name="1007315"></a>channel c3: including datafile number 18 in backupset </pre> <a name="1007316"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Fails to Start RPC Call: Diagno sis</font></h4>  <a name="1007317"></a> <p class="BP">The <code>RPC</code> <code>call</code> <code>appears</code> <cod e>to</code> <code>have</code> <code>failed</code> message does not usually indicate a problem. The message indicates one of the follo wing:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="1007318"></a>The target database instance is slow.</li> <li class="LB 1" type="disc"><a name="1007319"></a>A timing problem occurred.</li></ul> <a name="1007320"></a> <p class="BP">Timing problems occur in this way. When RMAN begins an RPC, it checks the <code>V$SESSION</code> performance view. The RPC updates the information in the view to indicate when it starts and finishes. Sometimes RMAN checks <code>V$SESSION</code> before the RPC has indicated it has starte d, which in turn generates the following message:</p> <pre class="CE"><a name="1007321"></a>RPC call appears to have failed <a name=" 1007322"></a> </pre> <a name="1007323"></a> <p class="BP">If a message stating "<code>RPC</code> <code>call</code> <code>ok</code>" does not appear in the output immediately following the message stating "<code>RPC</code> <code>call</code> <code>appears</code> <cod e>to</code> <code>have</code> <code>failed</code>", then the backup job encountered an internal problem. Contact Oracle Support for f urther assistance.</p> <a name="1007325"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color= "#330099">Backup Fails with Invalid RECID Error: Scenario</font></h3>  <a name="1007327"></a> <p class="BP">In this sc enario, you attempt a backup and receive the following error messages:</p> <pre class="CE"><a name="1007328"></a>RMAN-3014: Implicit resync of recovery catalog failed <a name="1007329"></a>RMAN-6038: Recovery catalog package detected an error <a name="1007330"></a>R MAN-20035: Invalid high RECID error </pre> <a name="1007331"></a> <h4 class="H3"><font face="Arial, Helvetica , sans-serif" color="#330099">Backup Fails with Invalid RECID Error: Diagnosis</font></h4>  <a name="1007332"></a> <p class="BP">In one common scenario, you restore a backup control file created through a non-Oracle mechanism, and then open the databa se without the <code>RESETLOGS</code> option. If you had created the backup control file through the RMAN <code>BACKUP</code> command or the SQL <code>ALTER</code> <code>DATABASE</code> <code>BACKUP</code> <code>CONTROLFILE</code> statement, then the database would have required you to reset the online logs.</p> <a name="1007333"></a> <p class="BP">The control file and the recovery catalog are n ow not synchronized. The database control file is older than the recovery catalog, because at one time the recovery catalog resynchro nized with the old current control file, and now the database is using a backup control file. RMAN detects that the control file curr ently in use is older than the control file previously used to resynchronize.</p> <a name="1007334"></a> <p class="BP">Another commo n scenario occurs when you attempt to copy the target database to a new machine as follows:</p> <ol class="LN1" type="1"> <li class=" LN1" type="1" value="1"><a name="1007335"></a>On machine 1, you shut down the database and make a copy of the control file with an op erating system utility. You do not use <code>CATALOG</code> to add this control file copy to the repository.</li> <li class="LN1" typ e="1" value="2"><a name="1007336"></a>You transfer the control file copy to machine 2.</li> <li class="LN1" type="1" value="3"><a nam e="1007337"></a>On machine 2, you create a new initialization parameter file and new database instance.</li> <li class="LN1" type="1" value="4"><a name="1007338"></a>You mount the control file copy on machine 2. The database does not recognize the control file as a backup control file: to the database it looks like the current control file.</li> <li class="LN1" type="1" value="5"><a name="1007339 "></a>You start RMAN and connect to the new target database and the recovery catalog on machine 2. Because the control file was not c reated with RMAN and was not cataloged as a control file copy, RMAN sees the database on machine 2 as the database on machine 1.</li> <li class="LN1" type="1" value="6"><a name="1007340"></a>You restore and recover database the new database on machine 2 and then ope n it. As a consequence, various records are added to the recovery catalog during the restore and recovery. For example, the highest < code>RECID</code> in the recovery catalog moves from 90 to 100.</li> <li class="LN1" type="1" value="7"><a name="1007341"></a>On mach ine 1, you start RMAN and connect to the original target database and recovery catalog. The recovery catalog indicates that the highe st <code>RECID</code> is 100, but the control file indicates that the highest <code>RECID</code> is 90. The control file <code>RECID< /code> should always be greater than or equal to the recovery catalog <code>RECID</code>, so RMAN issues <code>RMAN-20035</code>.</li ></ol> <a name="1007342"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails with Invalid RECID Error: Solution 1</font></h4>  <a name="1007343"></a> <p class="BP">This solution is safest and is strongly recommended. It preserves the control file, so that the historical information about the database stored in the contr ol file continues to be available after the procedure.</p> <a name="1007344"></a> <p class="BP"><strong class="Bold">To reset the da tabase with RMAN:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007345"></a>Connect to the targ et database with SQL*Plus. For example, enter: <pre class="CE1"><a name="1007346"></a>% sqlplus '/ AS SYSDBA' <a name="1007347"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007348"></a>Mount the database if it is not already mounted. For example, enter: <pre class="CE1"><a name="1007349"></a>ALTER DATABASE MOUNT; <a name="1007350"></a> </pre> </li> <li class="LN1" type="1" val ue="3"><a name="1007351"></a>Start cancel-based recovery by using the backup control file, then cancel it. The reason for canceling i s that the <code>USING</code> <code>BACKUP</code> <code>CONTROLFILE</code> clause stamps the controlfile as a backup, which then perm its <code>OPEN</code> <code>RESETLOGS</code>. For example, enter: <pre class="CE1"><a name="1007352"></a>ALTER DATABASE RECOVER DATA BASE UNTIL CANCEL USING BACKUP CONTROLFILE; <a name="1007353"></a>ALTER DATABASE RECOVER CANCEL; <a name="1007354"></a> </pre> </li> <li class="LN1" type="1" value="4"><a name="1010836"></a>Use RMAN to connect to the target database and recovery catalog. For example , enter: <pre class="CE1"><a name="1010837"></a>% rman TARGET SYS/oracle@trgt CATALOG rman/cat@catdb <a name="1010838"></a> </pre> < /li> <li class="LN1" type="1" value="5"><a name="1007355"></a>Open the database with the <code>RESETLOGS</code> option. For example, enter: <pre class="CE1"><a name="1007356"></a>RMAN> ALTER DATABASE OPEN RESETLOGS; <a name="1007357"></a> </pre> </li> <li class= "LN1" type="1" value="6"><a name="1007364"></a>Take new backups so that you can recover the database if necessary. For example, enter : <pre class="CE1"><a name="1007365"></a>BACKUP DATABASE PLUS ARCHIVELOG; </pre> </li></ol> <a name="1007366"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails with Invalid RECID Error: Solution 2</fon t></h4>  <a name="1007367"></a> <p class="BP">This solution is similar to the previous one, but does require that you re-create your control file. It is better-suited for the case in which you are copying your database to a second system, where you ma y not want to keep the history from the control file for the copy of the database on the second system, or where you might drop a few datafiles or change the online logs by editing your control file.</p> <a name="1007368"></a> <p class="BP"><strong class="Bold">To create the control file with SQL*Plus:</strong></p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007369"></ a>Connect to the target database with SQL*Plus. For example, enter: <pre class="CE1"><a name="1007370"></a>% sqlplus 'SYS/oracle@trg t AS SYSDBA' <a name="1007371"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007372"></a>Mount the database if it is not already mounted: <pre class="CE1"><a name="1007373"></a>SQL> ALTER DATABASE MOUNT; <a name="1007374"></a> </pre> </li> <li c lass="LN1" type="1" value="3"><a name="1007375"></a>Back up the control file to a trace file: <pre class="CE1"><a name="1007376"></a >SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; <a name="1007377"></a> </pre> </li> <li class="LN1" type="1" value="4"><a name=" 1007378"></a>Edit the trace file as necessary. The relevant section of the trace file looks something like the following: <pre class ="CE1"><a name="1007379"></a># The following commands will create a new control file and use it <a name="1007380"></a># to open the d atabase. <a name="1007381"></a># Data used by the recovery manager will be lost. Additional logs may <a name="1007382"></a># be requi red for media recovery of offline data files. Use this <a name="1007383"></a># only if the current version of all online logs are ava ilable. <a name="1007384"></a>STARTUP NOMOUNT <a name="1007385"></a>CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG <a name="1007386"></a>-- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED <a name="1007387"></a> MAXLOGFILES 32 <a name="10073 88"></a> MAXLOGMEMBERS 2 <a name="1007389"></a> MAXDATAFILES 32 <a name="1007390"></a> MAXINSTANCES 1 <a name="1007391"></a> MAXLOGHISTORY 226 <a name="1007392"></a>LOGFILE <a name="1007393"></a> GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M, <a n ame="1007394"></a> GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M, <a name="1007395"></a> GROUP 3 '/oracle/oradata/trgt/redo03 .log' SIZE 500K <a name="1007396"></a>-- STANDBY LOGFILE <a name="1007397"></a>DATAFILE <a name="1007398"></a> '/oracle/oradata/trg t/system01.dbf', <a name="1007399"></a> '/oracle/oradata/trgt/undotbs01.dbf', <a name="1007400"></a> '/oracle/oradata/trgt/cwmlite0 1.dbf', <a name="1007401"></a> '/oracle/oradata/trgt/drsys01.dbf', <a name="1007402"></a> '/oracle/oradata/trgt/example01.dbf', <a name="1007403"></a> '/oracle/oradata/trgt/indx01.dbf', <a name="1007404"></a> '/oracle/oradata/trgt/tools01.dbf', <a name="1007405" ></a> '/oracle/oradata/trgt/users01.dbf' <a name="1007406"></a>CHARACTER SET WE8DEC <a name="1007407"></a>; <a name="1007408"></a># Take files offline to match current control file. <a name="1007409"></a>ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OF FLINE; <a name="1007410"></a>ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE; <a name="1007411"></a># Configure RM AN configuration record 1 <a name="1007412"></a>VARIABLE RECNO NUMBER; <a name="1007413"></a>EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTOR E.SETCONFIG('CHANNEL','DEVICE TYPE DISK DEBUG 255'); <a name="1007415"></a># Recovery is required if any of the datafiles are restor ed backups, <a name="1007416"></a># or if the last shutdown was not normal or immediate. <a name="1007417"></a>RECOVER DATABASE <a na me="1007418"></a># All logs need archiving and a log switch is needed. <a name="1007419"></a>ALTER SYSTEM ARCHIVE LOG ALL; <a name="1 007420"></a># Database can now be opened normally. <a name="1007421"></a>ALTER DATABASE OPEN; <a name="1007422"></a># Commands to add tempfiles to temporary tablespaces. <a name="1007423"></a># Online tempfiles have complete space information. <a name="1007424"></a> # Other tempfiles may require adjustment. <a name="1007425"></a>ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE; <a name="1007426"></a># End of tempfile additions. <a name="1007427"></a> </pre> </li> <li class="LN1" type="1" value="5"><a n ame="1007428"></a>Shut down the database: <pre class="CE1"><a name="1007429"></a>SHUTDOWN IMMEDIATE <a name="1007430"></a> </pre> </ li> <li class="LN1" type="1" value="6"><a name="1007431"></a>Execute the script to create the control file, recover (if necessary), a rchive the logs, and open the database: <pre class="CE1"><a name="1007432"></a>STARTUP NOMOUNT <a name="1007433"></a>CREATE CONTROLF ILE ...; <a name="1007434"></a>EXECUTE ...; <a name="1007435"></a>RECOVER DATABASE <a name="1007436"></a>ALTER SYSTEM ARCHIVE LOG CUR RENT; <a name="1007437"></a>ALTER DATABASE OPEN ...; </pre> </li> <li class="LN1" type="1" value="7"><a name="1010873"></a>If you int end to keep and continue using this copy of the database, use the DBNEWID utility to change the name and DBID of the new database as needed. <p><a name="1007442"></a></p> <div align="center"> <table class="NoteWarn" border="0" width="80%" cellpadding="0" cellspacin g="0" dir="ltr" summary="This is a layout table to format a warning" title="This is a layout table to format a warning"> <tr class="N oteWarn"> <td class="NoteWarn"> <hr> <a name="1007440"></a><font face="Arial, Helvetica, sans-serif"><strong class="NHW">Caution:</st rong></font> <a name="1007441"></a> <p class="NB">If you do <em class="Italic">not</em> open with the <code>RESETLOGS</code> option, then two copies of an archived redo log for a given log sequence number may exist--even though these two copies have completely diff erent contents. For example, one log may have been created on the original host and the other on the new host. If you accidentally co nfuse the logs during a media recovery, then the database will be corrupted but Oracle and RMAN cannot detect the problem.</p> <hr></ td></tr></table></div></li></ol> <a name="1007444"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-ser if" color="#330099">Backup Fails Because of Control File Enqueue: Scenario</font></h3>  <a name="1007446"></a> <p clas s="BP">In this scenario, a backup job fails because RMAN cannot make a snapshot control file. The message stack is as follows:</p> <p re class="CE"><a name="1007447"></a>RMAN-00571: =========================================================== <a name="1007448"></a>RMA N-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== <a name="1007449"></a>RMAN-00571: ============================== ============================= <a name="1007450"></a>RMAN-03002: failure of backup command at 08/30/2001 22:48:44 <a name="1007451"></ a>ORA-00230: operation disallowed: snapshot controlfile enqueue unavailable </pre> <a name="1007452"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails Because of Control File Enqueue: Diagnosis</font>< /h4>  <a name="1007453"></a> <p class="BP">When RMAN needs to back up or resynchronize from the control file, it first creates a <strong class="Bold">snapshot</strong> or consistent image of the control file. If one RMAN job is already backing up the control file while another needs to create a new snapshot control file, then you may see the following message:</p> <pre class="CE">< a name="1007454"></a>waiting for snapshot controlfile enqueue <a name="1007455"></a> </pre> <a name="1007456"></a> <p class="BP">Und er normal circumstances, a job that must wait for the control file enqueue waits for a brief interval and then successfully obtains t he enqueue. RMAN makes up to five attempts to get the enqueue and then fails the job. The conflict is usually caused when two jobs ar e both backing up the control file, and the job that first starts backing up the control file waits for service from the media manage r.</p> <a name="1007457"></a> <p class="BP"><strong class="Bold">To determine which job is holding the conflicting enqueue:</strong> </p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007458"></a>After you see the first message stating "<cod e>RMAN-08512:</code> <code>waiting</code> <code>for</code> <code>snapshot</code> <code>controlfile</code> <code>enqueue</code>", star t a new SQL*Plus session on the target database: <pre class="CE1"><a name="1007459"></a>% sqlplus 'SYS/oracle@trgt AS SYSDBA' <a nam e="1007460"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007461"></a>Execute the following query to determine which job is causing the wait: <pre class="CE1"><a name="1007462"></a>SELECT s.SID, USERNAME AS "User", PROGRAM, MODULE, <a name="100746 3"></a> ACTION, LOGON_TIME "Logon", l.* <a name="1007464"></a>FROM V$SESSION s, V$ENQUEUE_LOCK l <a name="1007465"></a>WHERE l .SID = s.SID <a name="1007466"></a>AND l.TYPE = 'CF' <a name="1007467"></a>AND l.ID1 = 0 <a name="1007468"></a>AND l.ID2 = 2; <a name ="1007469"></a> </pre> <a name="1007470"></a> <p class="BP1">You should see output similar to the following (the output in this exam ple has been truncated):</p> <pre class="CE1"><a name="1007471"></a>SID User Program Module Action Logon <a name="1009986"></a>--- ---- -------------------- ------------------- ---------------- --------- <a name="1009987">< /a>9 SYS rman@h13 (TNS V1-V3) backup full datafile: c10000210 STARTED 21-JUN-01 </pre> </li></ol> <a name="1007474"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails Because of Control File Enqueue: Sol ution</font></h4>  <a name="1010937"></a> <p class="BP">Commonly, enqueue situations occur when a job is writing to a tape drive, but the tape drive is waiting for new tape to be inserted. If you start a new job in this situation, then you will probab ly receive the enqueue message because the first job cannot complete until the new tape is loaded.</p> <a name="1007475"></a> <p cla ss="BP">After you have determined which job is creating the enqueue, you can do one of the following:</p> <ul class="LB1"> <li class= "LB1" type="disc"><a name="1007476"></a>Wait until the job holding the enqueue completes</li> <li class="LB1" type="disc"><a name="10 07477"></a>Cancel the current job and restart it after the job holding the enqueue completes</li> <li class="LB1" type="disc"><a name ="1007478"></a>Cancel the job creating the enqueue</li></ul> <a name="1007482"></a>  <h3 class="H2"><font face ="Arial, Helvetica, sans-serif" color="#330099">RMAN Fails to Delete All Archived Logs: Scenario</font></h3>  <a name=" 1007484"></a> <p class="BP">In this scenario, the database archives automatically to two directories: <em class="Italic">ORACLE_HOME </em>/<code>oradata/trgt/arch</code> and <em class="Italic">ORACLE_HOME</em>/<code>oradata/trgt/arch2</code>. You tell RMAN to perfor m a backup and delete the input archived redo logs afterward in the following script:</p> <pre class="CE"><a name="1007485"></a>BACKU P ARCHIVELOG ALL DELETE INPUT; <a name="1007486"></a> </pre> <a name="1007487"></a> <p class="BP">You then run a crosscheck to make sure the logs are gone and find the following:</p> <pre class="CE"><a name="1007488"></a>CROSSCHECK ARCHIVELOG ALL; <a name="1007489" ></a> <a name="1007490"></a>validation succeeded for archived log <a name="1007491"></a>archivelog filename=/oracle/oradata/trgt/arch 2/archive1_964.arc recid=19 stamp=368726072 <a name="1007492"></a> </pre> <a name="1007493"></a> <p class="BP">RMAN deleted one set of logs but not the other.</p> <a name="1007494"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-seri f" color="#330099">RMAN Fails to Delete All Archived Logs: Diagnosis</font></h4>  <a name="1007495"></a> <p class="BP" >This problem is not an error. When you specify <code>DELETE</code> <code>INPUT</code> without the <code>ALL</code> keyword, RMAN del etes only one copy of each input log. Even if you archive to five destinations, RMAN deletes logs from only one directory.</p> <a nam e="1007496"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Fails to Delet e All Archived Logs: Solution</font></h4>  <a name="1007497"></a> <p class="BP">To force RMAN to delete all existing a rchived redo logs, use the <code>DELETE</code> <code>ALL</code> <code>INPUT</code> clause of the <code>BACKUP</code> command. For exa mple, enter:</p> <pre class="CE"><a name="1007498"></a>BACKUP ARCHIVELOG ALL DELETE ALL INPUT; </pre> <a name="1007500"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails Because RMAN Cannot Locate an A rchived Log: Scenario</font></h3>  <a name="1007502"></a> <p class="BP">In this scenario, you schedule regular backups of the archived redo logs. The next time you make a backup, you receive this error:</p> <pre class="CE"><a name="1007503"></a>RMAN-6 089: archive log NAME not found or out of sync with catalog </pre> <a name="1007504"></a> <h4 class="H3"><fo nt face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails Because RMAN Cannot Locate an Archived Log: Diagnosis</font></h4>  <a name="1007505"></a> <p class="BP">This problem occurs when the archived log that RMAN is looking for cannot be ac cessed by RMAN, or the recovery catalog needs to be resynchronized. Often, this error occurs when you delete archived logs with an op erating system command, which means that RMAN is unaware of the deletion. The <code>RMAN-6089</code> error occurs because RMAN attemp ts to back up a log that the repository indicates still exists.</p> <a name="1007506"></a>  <h4 class="H3"><fo nt face="Arial, Helvetica, sans-serif" color="#330099">Backup Fails Because RMAN Cannot Locate an Archived Log: Solution</font></h4>  <a name="1007507"></a> <p class="BP">Make sure that the archived logs exists in the specified directory and that the RMAN catalog is synchronized. Check the following:</p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007508" ></a>Make sure the archived log file that is specified by the <code>RMAN-6089</code> error exists in the correct directory.</li> <li class="LN1" type="1" value="2"><a name="1007509"></a>Check that the operating system permissions are correct for the archived log (<c ode>owner</code> <code>=</code> <code>oracle</code>, <code>group</code> <code>=</code> <code>DBA</code>) to make sure that RMAN can a ccess the file.</li> <li class="LN1" type="1" value="3"><a name="1007510"></a>If the file appears to be correct, then try synchronizi ng the catalog by running the following command from the RMAN prompt: <pre class="CE1"><a name="1007511"></a>RESYNC CATALOG; <a name ="1007512"></a> </pre> </li></ol> <a name="1007513"></a> <p class="BP">If you know that the logs are unavailable because you deleted them by using an operating system utility, then run the following command at the RMAN prompt to update RMAN metadata:</p> <pre class= "CE"><a name="1007514"></a>CROSSCHECK ARCHIVELOG ALL; <a name="1007515"></a> </pre> <a name="1007516"></a> <p class="BP">It is alway s better to use RMAN to delete logs than to use an operating system utility. The easiest method to remove unwanted logs is to specify the <code>DELETE</code> <code>INPUT</code> option when backing up archived logs. For example, enter:</p> <pre class="CE"><a name="10 07517"></a>BACKUP DEVICE TYPE sbt <a name="1007518"></a> ARCHIVELOG ALL <a name="1007519"></a> DELETE ALL INPUT; </pre> <a name= "1007539"></a> <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Does Not Recogniz e Character Set Name: Scenario</font></h3>  <a name="1007540"></a> <p class="BP">In this scenario, you are connected t o the target database while it is not open and attempting to perform an RMAN operation. You receive the following error:</p> <pre cla ss="CE"><a name="1007541"></a>PLS-00553: character set name is not recognized </pre> <a name="1007542"></a> < h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Does Not Recognize Character Set Name: Diagnosis</font>< /h4>  <a name="1007543"></a> <p class="BP">Typically, this message means that the character set in the client environm ent, that is, the environment in which you are running the RMAN client, is different from the character set in the target database en vironment.</p> <a name="1007544"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099 ">RMAN Does Not Recognize Character Set Name: Solution</font></h4>  <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="1007545"></a>Query the target database to determine the value of the <code>NLS_CHARACTERSET</code> parameter. For example, run this query: <pre class="CE1"><a name="1007546"></a>SQL> SELECT VALUE FROM V$NLS_PARAMETERS WHERE PARAMETER='NL S_CHARACTERSET'; <a name="1007547"></a> </pre> </li> <li class="LN1" type="1" value="2"><a name="1007548"></a>Set the character set e nvironment variable in the client to the same value as the variable in the server. For example, you can set the <code>NLS_LANG</code> environment variable on a UNIX system as follows: <pre class="CE1"><a name="1007549"></a>% setenv NLS_LANG american_america.we8dec <a name="1007550"></a>% setenv NLS_DATE_FORMAT "MON DD YYYY HH24:MI:SS" <a name="1010910"></a> </pre> </li></ol> <a name="1011441"></ a> <p class="BP">If the connection is made througfh a listener, then the listener must be started with the correct Globalization Supp ort settings. Otherwise, the spawned connections inherit the incorrect Globalization Support settings from the listener.</p> <a name= "1011443"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Denies Logon to Target Database: Scenario</font></h3>  <a name="1007553"></a> <p class="BP">RMAN fails with ORA-01031 (insufficient pr ivileges) or ORA-01017 (invalid username/password) errors when trying to connect to the target database:</p> <pre class="CE"><a name= "1007554"></a>% rman <a name="1011266"></a>Recovery Manager: Release 10.1.0.2.0 - Production <a name="1011267"></a> <a name="1011268" ></a>Copyright (c) 1995, 2003, Oracle. All rights reserved. <a name="1011269"></a> <a name="1007557"></a>RMAN> CONNECT TARGET sys /mypass@inst1 <a name="1007558"></a> <a name="1007559"></a>RMAN-00571: =========================================================== <a name="1007560"></a>RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== <a name="1007561"></a>RMAN-00571: ======= ==================================================== <a name="1010948"></a>ORA-01031: insufficient privileges </pre> <a name="101094 9"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Denies Logon to Target D atabase: Diagnosis</font></h4>  <a name="1010950"></a> <p class="BP">RMAN automatically requests a connection to the t arget database as <code>SYSDBA</code>. In order to connect to the target as <code>SYSDBA</code>, you must do one of the following:</p > <ul class="LB1"> <li class="LB1" type="disc"><a name="1007565"></a>Be part of the operating system <code>DBA</code> group with resp ect to the target database (that is, have the ability to connect with <code>SYSDBA</code> privileges to the target database without a password).</li> <li class="LB1" type="disc"><a name="1007566"></a>Create a password file with the <code>orapwd</code> command and th e initialization parameter <code>REMOTE_LOGIN_PASSWORDFILE</code>.</li> <li class="LB1" type="disc"><a name="1010921"></a>Make sure y ou are connecting with the correct username and password.</li></ul> <a name="1007567"></a> <p class="BP">If the target database does not have a password file, then the user you are logged in as must be validated with operating system authentication.</p> <a name="10 10962"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">RMAN Denies Logon to Tar get Database: Solution</font></h4>  <a name="1007569"></a> <p class="BP">Either create a password file for the target database or add yourself to the administrator list in the operating system.</p> <a name="1007579"></a> <div align="center"> <table c lass="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" ti tle="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="1007572"></a><font face="Arial, He lvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1007578"></a> <p class="NB"><em class="Italic"><a class=" olinkSRC ADMIN" href="../../server$101/b10739/toc.htm">Oracle Database Administrator's Guide</a></em> to learn how to create a passwo rd file</p></td></tr></table></div> <a name="1007582"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans- serif" color="#330099">Database Duplication Fails Because of Missing Log: Scenario</font></h3>  <a name="1007584"></a> <p class="BP">In this scenario, you attempt to duplicate a database with the <code>DUPLICATE</code> command, but receive the followi ng error stack:</p> <pre class="CE"><a name="1007585"></a>RMAN-00571: =========================================================== <a name="1007586"></a>RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== <a name="1007587"></a>RMAN-00571: ======== =================================================== <a name="1007588"></a>RMAN-03002: failure of Duplicate Db command at 09/04/2001 1 2:11:29 <a name="1007589"></a>RMAN-03015: error occurred in stored script Memory Script <a name="1007590"></a>RMAN-06053: unable to p erform media recovery because of missing log <a name="1007591"></a>RMAN-06025: no backup of log thread 1 seq 16 scn 145858 found to r estore </pre> <a name="1007592"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099" >Database Duplication Fails Because of Missing Log: Diagnosis</font></h4>  <a name="1007593"></a> <p class="BP">The pr oblem is that RMAN is not able to apply all the archived logs needed for complete recovery. For example, if you only backed up logs t hrough sequence <code>15</code>, but the most recent archived log is sequence <code>16</code>, then <code>DUPLICATE</code> fails.</p> <a name="1007594"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Database Dup lication Fails Because of Missing Log: Solution</font></h4>  <a name="1007595"></a> <p class="BP">When creating the du plication script, use the <code>SET</code> <code>UNTIL</code> command to specify a log sequence number for incomplete recovery. For e xample, to terminate recovery after applying log sequence <code>15</code>, enter:</p> <pre class="CE"><a name="1007596"></a>RUN <a na me="1007597"></a>{ <a name="1007598"></a> SET UNTIL SEQUENCE 16 THREAD 1; # recovers up to but not including log 16 <a name="100759 9"></a> DUPLICATE TARGET DATABASE TO 'dupdb'; </pre> <a name="1007600"></a> <p class="BP">}</p> <a name="1007611"></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="1007603"></a><fo nt face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="1007609"></a> <p class="NB"><a href="rc mdupdb.htm#1006983">"Creating Duplicate of the Database at a Past Point in Time: Example"</a><a href="rcmdupdb.htm#1006983"></a> for more information about performing incomplete recovery during the duplication operation</p></td></tr></table></div> <a name="1007613"> </a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Duplication Fails with Multiple RMAN-06023 Errors: Scenario</font></h3>  <a name="1007614"></a> <p class="BP">In this scenario, you back up the datab ase, then run the <code>DUPLICATE</code> command. You receive the following error stack:</p> <pre class="CE"><a name="1007615"></a>RM AN-00571: =========================================================== <a name="1007616"></a>RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== <a name="1007617"></a>RMAN-00571: =========================================================== <a name= "1007618"></a>RMAN-03002: failure of Duplicate Db command at 09/04/2001 13:55:11 <a name="1007619"></a>RMAN-03015: error occurred in stored script Memory Script <a name="1007620"></a>RMAN-06026: some targets not found - aborting restore <a name="1007621"></a>RMAN-06 023: no backup or copy of datafile 8 found to restore <a name="1007622"></a>RMAN-06023: no backup or copy of datafile 7 found to rest ore <a name="1007623"></a>RMAN-06023: no backup or copy of datafile 6 found to restore <a name="1007624"></a>RMAN-06023: no backup or copy of datafile 5 found to restore <a name="1007625"></a>RMAN-06023: no backup or copy of datafile 4 found to restore <a name="1007 626"></a>RMAN-06023: no backup or copy of datafile 3 found to restore <a name="1007627"></a>RMAN-06023: no backup or copy of datafile 2 found to restore <a name="1007628"></a>RMAN-06023: no backup or copy of datafile 1 found to restore </pre> <a name="1007629"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Duplication Fails with Multiple RMAN -06023 Errors: Diagnosis</font></h4>  <a name="1007630"></a> <p class="BP">The <code>DUPLICATE</code> command recovers to archived redo logs, but cannot recover into online redo logs. Thus, if the restored backup cannot be made consistent without appl ying the online redo logs, then duplication fails with RMAN-06023 errors because RMAN is looking for backups created <em class="Itali c">before</em> the most recent archived log.</p> <a name="1007631"></a>  <h4 class="H3"><font face="Arial, Hel vetica, sans-serif" color="#330099">Duplication Fails with Multiple RMAN-06023 Errors: Solution</font></h4>  <a name="1 007632"></a> <p class="BP">After backing up the source database, archive and back up the current redo log:</p> <pre class="CE"><a na me="1011332"></a>RMAN> SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT'; <a name="1011336"></a>RMAN> BACKUP ARCHIVELOG ALL; <a name="1007 634"></a> </pre> <a name="1007635"></a> <p class="BP">This archives all records in the online redo logs so that RMAN can now recover the backup by applying the most recent archived redo log.</p> <a name="1007637"></a>  <h3 class="H2"><font fa ce="Arial, Helvetica, sans-serif" color="#330099">UNKNOWN Database Name Appears in Recovery Catalog: Scenario</font></h3>  <a name="1007639"></a> <p class="BP">In this scenario, you list the database incarnations registered in the recovery catalog and see a database with the name <code>UNKNOWN</code>:</p> <pre class="CEM"><a name="1007640"></a>LIST INCARNATION OF DATABASE; <a nam e="1007641"></a> <a name="1007642"></a>RMAN-03022: compiling command: list <a name="1007643"></a>List of Database Incarnations < a name="1007644"></a>DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time <a name="1007645"></a>------- ------- ------- ------ ------ ---------- ---------- <a name="1011234"></a>56 57 TRGT 4052472287 CURRENT 1 Sep 03 2001 06:45:51 <a name="1011235"></a>1 19 UNKNOWN 4141147584 PARENT 1 Jan 08 2001 14:47 :28 <a name="1011253"></a>. <a name="1011254"></a>. <a name="1011255"></a>. </pre> <a name="1007649"></a> <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">UNKNOWN Database Name Appears in Recovery Catalog: Diagnosis</f ont></h4>  <a name="1007650"></a> <p class="BP">One way you get the <code>DB_NAME</code> of <code>UNKNOWN</code> is wh en you register a database that was once opened with the <code>RESETLOGS</code> option. The <code>DB_NAME</code> can be changed durin g a <code>RESETLOGS</code> operation, so RMAN does not know what the <code>DB_NAME</code> was for those old incarnations of the datab ase because it was not registered in the recovery catalog at the time. Consequently, RMAN sets the <code>DB_NAME</code> column to <co de>UNKNOWN</code> when creating the <code>DBINC</code> record.</p> <a name="1007651"></a>  <h4 class="H3"><fon t face="Arial, Helvetica, sans-serif" color="#330099">UNKNOWN Database Name Appears in Recovery Catalog: Solution</font></h4>  <a name="1007652"></a> <p class="BP">The <code>UNKNOWN</code> name entry is expected behavior after a <code>RESETLOGS</code> operation. You should <em class="Italic">not</em> attempt to remove <code>UNKNOWN</code> entries from the recovery catalog.</p> <a n ame="1010625"></a></div> <div class="footer"> <hr> <table summary="" cellspacing="0" cellpadding="0" width="100%"> <tr> <td style="wi dth: 33%;" align="left"> <table summary="layout table" cellspacing="0" cellpadding="0" align="left" width="90"> <tr> <td align="cente r" valign="top"><a href="rcmtunin.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="part3.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 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 Co rporation</font></a><br> <font size="-2">All Rights Reserved.</font></td> <td style="width: 33%;" align="right"> <table summary="" ce llspacing="0" cellpadding="0" width="270"> <tr> <td align="center" valign="top"><a href="../../index.htm"><img src="../../dcommon/gif s/prodicon.gif" alt="Go to Documentation Home" border="0"><br> <font size="-2">Home</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 o f 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" 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="../../dcommo n/gifs/feedback.gif" alt="Go to Feedback page" border="0"><br> <font size="-2">Feedback</font></a></td></tr></table></td></tr></table ></div> </body> </html>