title: How do you re-duplicate a broken physical standby database?
body: <p>first some data: we are using Oracle 11g databases. A primary database running on a dedicated server and a physical standby database on a separate dedicated server. We use the DataGuard feature to automatically replicate the primary database to the physical standby database in real time. The primary database is also backeed up through RMAN.</p>
  
  <p>currently I am unable to cope a problem with our physical standby database. Somehow the transfer of the archive logs from the primary database to the physical standyby database has stopped, what it makes worse some of the archive logs already got deleted from some of our employees, now I can't issue a recovery by performing the following statement:</p>
  
  <pre><code>RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE;
  </code></pre>
  
  <p>since the required archive logs are gone.</p>
  
  <p>So my thought was to re-duplicate the physical standby database. I shutdown the physical standby database and restarted it with STARTUP NOMOUNT. Then logged onto the server hosting the primary database and started a RMAN-session with:</p>
  
  <pre><code>RMAN target / auxiliary sys@PRIMARY_DB_DG
     RMAN&gt; sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
     RMAN&gt; DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE DORECOVER
           NOFILENAMECHECK;
  </code></pre>
  
  <p>but shortly after altering the the physical standby database to MOUNT status the process crashes due to either</p>
  
  <ol>
  <li><p>RMAN-04006: error from auxiliary database: ORA-12537: TNS:connection closed,</p></li>
  <li><p>RMAN-03009: failure of switch command on clone_default channel at 11/15/2011 11:13:58
  ORA-03113: end-of-file on communication channel or </p></li>
  <li><p>RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel</p></li>
  </ol>
  
  <p>I have googled around for solutions, but only found guides to setup a physical standby database from scratch. So anybody knows howe to fix the physical database without setting it up completely new?</p>
  
  <p>Greetings,
  CB</p>