11g active database clone failed

I recently experienced some type of a network hiccup of some sort resulting in a failed duplicate database using active database methodology for Oracle 11g.  The below error was the one I received for several datafile copies which is the first steps in the duplicate with active database process.  Some were missed/didn't get copied over for some reason.


RMAN-03009: failure of backup command on prm2 channel at 05/01/2011 04:50:02
ORA-17629: Cannot connect to the remote database server
ORA-17629: Cannot connect to the remote database server
continuing other job steps, job failed will not be re-run

This resulted in the below error:

RMAN-03009: failure of backup command on prm4 channel at 05/01/2011 23:20:53
ORA-17629: Cannot connect to the remote database server
ORA-17629: Cannot connect to the remote database server

Here is how I manually completed the clone after the failure occurred:

1. Copy over the missing datafiles from primary via RMAN.
connect target sys/password@prmrydb;
connect auxiliary sys/password@clonedb;
run {
allocate channel prm1 type disk;
allocate channel prm2 type disk;
allocate channel prm3 type disk;
allocate auxiliary channel stb1 type disk;
backup as copy reuse datafile 350  auxiliary format
"/u01/oradata/clonedb/eodslrg01_sml.dbf"
datafile 439 auxiliary format
"/u01/oradata/clonedb/pcapp2.dbf";
}

2. Create controlfile with all datafiles for the clone database.

3. copy over missing archivelogs from primary via RMAN.

connect target sys/password@prmrydb;
connect auxiliary sys/password@clonedb;
run {
backup as copy reuse
archivelog like  "/orabase/admin/prmrydb/arch/fs90prd_749760667_2_1.arc" auxiliary format
"/ora1110base/admin/clonedb/arch/clonedb_749760667_2_1.arc";
catalog clone archivelog  "/ora1110base/admin/clonedb/arch/clonedb_749760667_2_1.arc";
}

4. Get your SCN from which you would like to recover the database to and recover the clone database accordingly via RMAN.

connect target sys/password@prmrydb;
connect auxiliary sys/password@clonedb;
run {
   set until scn  321485877049;
   recover
   clone database
    delete archivelog
   ;
}

5. After recovery is completed, open the database.
alter database open resetlogs;

Comments

Post a Comment

Popular posts from this blog

ORA-17630: Mismatch in the remote file protocol version client 2 server 3

I was trying to create an Oracle Data Guard environment (physical standby) from an Oracle database running version 12.1.0.2. The database was running an older PSU version ("Database Patch Set Update : 12.1.0.2.161018 (24006101)") to be specific. Upon trying to build the standby by using RMAN DUPLICATE with ACTIVE DATABASE, I ran into the below error: executing Memory Script Starting backup at 16-JUL-18 RMAN-03009: failure of backup command on prm1 channel at 07/16/2018 13:51:46 ORA-17629: Cannot connect to the remote database server ORA-17630: Mismatch in the remote file protocol version client 2 server 3 continuing other job steps, job failed will not be re-run released channel: prm1 released channel: prm2 released channel: prm3 released channel: prm4 released channel: prm5 released channel: stb1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ====================...
Read more

ORA-00338: log {n} of thread {n} is more recent than control file

I received the following error in a primary database's alert log that I was supporting recently.   ORA-00312: online log 5 thread 1: '+DATA/db_name/onlinelog/group_5.297.846947859' ORA-00338: log 5 of thread 1 is more recent than control file The database has a DataGuard environment as well and below are the steps that I took to resolve the issue. 1.  First, I checked the status of the redo logs and their current sizes and status. SQL> select group#,bytes/1024/1024,status from v$log;     GROUP# BYTES/1024/1024 STATUS ---------- --------------- ----------------          1              50 INACTIVE          2              50 INACTIVE          3              50 INACTIVE          4             250 INACTIVE   ...
Read more

RMAN-10038: database session for channel prm3 terminated unexpectedly

Problem: I had an issue where I was trying to build a 1.7 TB Data Guard environment and kept receiving the highlighted error below.  I thought it was some type of fluke so I restarted the job 2 more times only to receive the same error. Fix: After researching the issue, I found it was because the sqlnet.ora needed to be configured correctly.  I added the entry " SQLNET.EXPIRE_TIME = 10 " to the sqlnet.ora on both the source and the target database servers under the RDBMS $ORACLE_HOME/network/admin.  Upon restarting the RMAN active database standby build, it was able to move past this error and built successfully. Starting backup at 07-MAY-17 channel prm1: starting datafile copy input datafile file number=00003 name=+DATA/testdb/datafile/undotbs1.262.940412881 channel prm2: starting datafile copy input datafile file number=00129 name=+DATA/testdb/datafile/welldoc1.390.940509955 channel prm3: starting datafile copy input datafile file number=00130 name=+DATA/...
Read more