OGG-01423 No valid default archive log destination directory found for thread :EXTRACT ABENDED

OGG-01423 No valid default archive log destination directory found for thread  :EXTRACT ABENDED

If any of the archive log thread is missing are not Readable by the Golden gate the warning message will be in the extract report file and the extract will move in to the Abended state 

Step 1

check the extract status ..in the ggsci command prompt

GGSCI (db) > info TRANE

EXTRACT    TRANE     Last Started 2012-07-19 01:05   Status ABENDED

Checkpoint Lag       00:00:00 (updated 134:26:36 ago)

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:37  Thread 1, Seqno 71824, RBA 14858240

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:42  Thread 2, Seqno 83766, RBA 93465600

Note the sequence number of the Redo log and make sure that all the redo logs are available and the redo log destination is reachable by the GG

GGSCI (db) > send TRANE status

2012-07-25 23:38:56  INFO    OGG-00987  GGSCI command (prod): send TRANE status.

ERROR: EXTRACT TRANE not currently running.

Step 2

View the report file and Check for the warning and the error messages the rpt file is located under dirrpt in the gg root directory

2012-07-25 21:24:26  WARNING OGG-01423  No valid default archive log destination directory found for thread 1.

Maximum supported ASM read buffer size is 28 KB

2012-07-25 21:24:26  WARNING OGG-01423  No valid default archive log destination directory found for thread 2.

2012-07-25 21:24:26  INFO    OGG-00546  Default thread stack size: 262144.

2012-07-25 21:24:26  INFO    OGG-01513  Positioning to (Thread 1) Sequence 71796, RBA 35363856, SCN 3.2783180541.

If youa re getting this kind of warning messages better check the archive log  sequence which is mentioned  in the error and if the particular archive log is not available restore it to the archive log destination from that point of archive log the golden will proceed to read the data from it to till now so check all the archive log up to date

In case if you don't have the archive log then  also we can start the gg  by altering the extract checkpoint to the lease archive log which is available,,,  in are omitting some archive log there will be data loss during that time period

for example if you're extract had stopped at Sunday and   you are trying to start on Wednesday but if you don't have the archive log  for  Monday then we can alter the gg checkpoint o the Tuesday and we can proceed from Tuesday to until present ... but the monday's data will be loss and you have to think for alter arrangement to move the data for that day

Step3

Alter the extract to the least available the archive-log

and if you are using the GG in the Rac environment then you have to alter all the threads according to the archive log available 

 GGSCI (db) > alter ext trane, thread 1, extseqno71831 , extrba 0

2012-07-25 23:39:50  INFO    OGG-00987  GGSCI command (oraprod): alter ext trane  thread 1, extseqno 71831, extrba 0.

EXTRACT altered.

GGSCI (db) > alter ext trane, thread 2, extseqno 83777, extrba 0

2012-07-25 23:40:34  INFO    OGG-00987  GGSCI command (oraprod): alter ext trane  thread 2, extseqno 83777, extrba 0.

EXTRACT altered.

In this situation we have archive log's starting from the 71831,and 83777 as we are  in the two node RAC environment  

Step 4

Alter the extract for the io checkpoint also

alter extract trane ,thread 1, ioextseqno 71831 ,ioextrba 0

2012-07-25 23:40:11  INFO    OGG-00988  WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying input checkpoint #1, Oracle thread #1 of EXTRACT: ioseq = 71831 iorba = 0.

Are you sure you want to continue? Y

EXTRACT altered.

alter extract trane ,thread 2,ioextseqno 8377 ,ioextrba 0

2012-07-25 23:40:57  INFO    OGG-00988  WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying input checkpoint #2, Oracle thread #2 of EXTRACT: ioseq = 83777 iorba = 0.

Are you sure you want to continue? Y

EXTRACT altered.

Step 5

start the extract and check the status 

GGSCI (db) > start TRANE

GGSCI (db) > info TRANE

EXTRACT    TRANE     Last Started 2012-07-25 23:41   Status RUNNING

Checkpoint Lag       134:30:52 (updated 00:00:00 ago)

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:37  Thread 1, Seqno 71831, RBA 0

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-20 09:10:42  Thread 2, Seqno 83777, RBA 0

Step 6

Check the lag point and wait until all the lag's are processed and it becomes zero

GGSCI (db) > info all

Program               Status              Group       Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       134:30:52     00:00:09

EXTRACT     RUNNING     TRANE       121:40:09     00:00:07

GGSCI (db) > info all

Program              Status              Group       Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       42:11:29      00:00:08

EXTRACT     RUNNING     TRANP       00:00:00      00:00:01

REPLICAT    RUNNING     SETUPR      00:00:00      00:00:07

REPLICAT    RUNNING     TRANR       00:00:00      00:00:02

GGSCI (db01) 38> info all

Program             Status              Group        Lag           Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     TRANE       00:00:00      00:00:01

EXTRACT     RUNNING     TRANP       00:00:00      00:00:06

REPLICAT    RUNNING     SETUPR      00:00:00      00:00:05

REPLICAT    RUNNING     TRANR       00:00:00      00:00:01

Wait until the Lag becomes zero .. once it is zero then it will proceed  Normally .... 

OGG-01028 encountered commit SCN that is not greater than the highest SCN already processed

 OGG-01028  encountered commit SCN  that is not greater than the highest SCN already processed

when implementing the golden gate with the RAC then scn commit point error occur's the SCN commit point difference between the two nodes are not Captured  the golden gate and the database heart beat cluster is not Captured  by the  Golden gate in the latest version of the golden gate This issue is resolved if you are in the older version 11.1.1.o then you may upgrade to the latest version there was the work around suggest by the meta link note and start the abended process if you have the pump extract then the master extract only fails  and goes to the abended state 

The steps to start the extract

   go the gg root directory and issue info * and verify the process status

EXTRACT    TRANE     Last Started 2012-07-09 22:39   Status ABENDED

Checkpoint Lag       00:00:04 (updated 57:54:28 ago)

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-16 10:28:05  Thread 1, Seqno 71663, RBA 37061648

Log Read Checkpoint  Oracle Redo Logs

                     2012-07-16 10:28:05  Thread 2, Seqno 83522, RBA 97637256

EXTRACT    TRANP     Last Started 2012-07-10 00:10   Status RUNNING

Checkpoint Lag       00:00:00 (updated 00:00:07 ago)

Log Read Checkpoint  File ./dirdat/tt000132

                     2012-07-15 23:55:11.000000  RBA 1614803

     In the ggsci command prompt type the   command to view report of the extract which is failing view report TRANE

Source Context :

  SourceModule            : [er.main]

  SourceID                : [/home/ecloud/workspace/Build_OpenSys_r11.1.1.0.0_07

8_[34100]/perforce/src/app/er/rep.c]

  SourceFunction          : [process_extract_loop]

  SourceLine              : [22135]

2012-07-16 10:28:19  ERROR   OGG-01028  encountered commit SCN 3.2740850914 (156

25752802) that is not greater than the highest SCN already processed 3.274085101

3 (15625752901) Redo Thread 1 (1) xid 124.15.403910 (0x007c.000f.000629c6), star

ting seq.rba 71663.37062672, scn 3.2740850913 (15625752801), commit seq.rba 7166

3.37095672 commit timestamp 2012-07-16 10:28:17.000000.

In the ggsi command prompt do the info <extract name> ,showch and conform the read and write check point of the current EXTRACT

1]Do an ETROLLOVER on Extract, and take note of the new sequence number of the trail file 



Before doing the extract etrollover make a note of the trail file write check point .. to know the trail file checkpoint
in the ggsci command prompt  type info <extract name > ,showch

Write Checkpoint #1
  GGS Log Trail


  Current Checkpoint (current write position):
    Sequence #: 132
    RBA: 1614803
    Timestamp: 2012-07-16 10:28:09.090854
    Extract Trail: ./dirdat/tt

GGSCI (db) > ALTER EXTRACT TRANE  ETROLLOVER


2012-07-18 20:43:15  INFO    OGG-01520  Rollover performed.  For each affected output trail of Version 10 or higher format, after starting the source extract,  issue ALTER EXTSEQNO for that trail's reader (either pump EXTRACT or REPLICAT) to  move the reader's scan to the new trail file;  it will not happen automatically 

EXTRACT altered.


after doing the extract etrollover you can see the new sequence number of the trail file had been created at the write checkpoint the previous was 132 and after rollover you can see the new trail file number 133 at the write check point

Write Checkpoint #1
GGS Log Trail
  Current Checkpoint (current write position):
    Sequence #: 133
    RBA: 856
    Timestamp: 2012-07-18 20:50:28.313045
    Extract Trail: ./dirdat/tt

2]  Start the extract



GGSCI (db) > START EXTRACT TRANE


Sending START request to MANAGER ...
EXTRACT TRANE starting

 2a} check whether the extract is in the running state

GGSCI (db) > info TRANE


EXTRACT    TRANE     Last Started 2012-07-18 20:44   Status RUNNING
Checkpoint Lag       58:16:47 (updated 00:00:05 ago)
Log Read Checkpoint  Oracle Redo Logs
                     2012-07-16 10:28:05  Thread 1, Seqno 71663, RBA 37061648
Log Read Checkpoint  Oracle Redo Logs
                     2012-07-16 10:28:05  Thread 2, Seqno 83522, RBA 97637256




3]Send PUMP, LOGEND, and note the trail file number as it moves to the previous trail file 



GGSCI (db) > info TRANP


EXTRACT    TRANP     Last Started 2012-07-10 00:10   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:02 ago)
Log Read Checkpoint  File ./dirdat/tt000132
                     2012-07-15 23:55:11.000000  RBA 1614803

GGSCI (db) > SEND EXTRACT TRANP LOGEND


Sending LOGEND request to EXTRACT TRANP ...
YES.


wait until the log end command end's with YES 


4. Once you have got the output  as YES then , You must stop the pump, and do an ETROLLOVER for it too. Take note of the new trail file sequence number that is created from this step



GGSCI (db) > info TRANP


EXTRACT    TRANP     Last Started 2012-07-10 00:10   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:00 ago)
Log Read Checkpoint  File ./dirdat/tt000132
                     2012-07-15 23:55:11.000000  RBA 1614803

  GGSCI (db) > info   TRANP showch
Write Checkpoint #1
GGS Log Trail


Current Checkpoint (current write position):
    Sequence #: 135
    RBA: 1614836
    Timestamp: 2012-07-18 20:56:50.275291
    Extract Trail: ./dirdat/t1

make the note of the write check Point of the and the after the etrollover it will be increased stop the extract


GGSCI (db) > STOP EXTRACT  TRANP    --- stop the extract


Sending STOP request to EXTRACT TRANP ...
Request processed.

GGSCI (db) > info tranp                           --check the status of the extract


EXTRACT    TRANP     Last Started 2012-07-10 00:10   Status STOPPED
Checkpoint Lag       00:00:00 (updated 00:00:05 ago)
Log Read Checkpoint  File ./dirdat/tt000132
                     2012-07-15 23:55:11.000000  RBA 1614803

GGSCI (db) 34> ALTER EXTRACT TRANP ETROLLOVER



2012-07-18 21:00:50  INFO   OGG-01520  Rollover performed.  For each affected output trail of Version 10 or higher format, after starting the source extract, issue ALTER EXTSEQNO for that trail's reader (either pump EXTRACT or REPLICAT) to move the reader's scan to the new trail file;  it will not happen automatically.
EXTRACT altered



GGSCI (db) > info   TRANP showch

Write Checkpoint #1
 GGS Log Trail
  Current Checkpoint (current write position):
    Sequence #: 136 
    RBA: 0
    Timestamp: 2012-07-18 20:59:06.625434
    Extract Trail: ./dirdat/t1

Make a note of this number which we need to use in the replicate etrollover

5.] Alter the pump to SEQNO to the new trail file created from step #1

At this scenario we have got the new trail file number in the first step write checkpoint  and from 132 to it is changed to 133 after the etrollover and now the TRANP is in the 132 trail file and we have to change  it to the new trail file 133...

GGSCI (db) 38> ALTER EXTRACT TRANP EXTSEQNO 133 EXTRBA 0

EXTRACT altered.

6.] Start pump Extract

GGSCI (db) > start EXTRACT    TRANP

Sending START request to MANAGER ...

EXTRACT TRANP starting

GGSCI (db) > info  EXTRACT tranp

EXTRACT    TRANP     Last Started 2012-07-18 21:09   Status RUNNING

Checkpoint Lag       00:00:00 (updated 00:00:03 ago)

Log Read Checkpoint  File ./dirdat/tt000133

                     2012-07-16 15:36:02.000000  RBA 1207

Now you can see the extract Pump tranp  had been switched to the new trail file which is created at the master extract etrollover

These are the steps we have done in the source system and in the target system replicate we have run the LOGEND and Change the trail file t th new trail file created at the step 4

1] Login to the ggsci fo the target system where replicate is running  

REPLICAT   TRANR1    Last Started 2012-07-11 19:28   Status RUNNING

Checkpoint Lag       00:00:00 (updated 00:00:09 ago)

Log Read Checkpoint  File ./dirdat/t1000135

                     2012-07-16 00:03:32.629052  RBA 1614836

2]Send the replicate to the log end and wait until the out YES and stop the replicate 

GGSCI (fahdb) > SEND REPLICAT TRANR1 LOGEND

Sending LOGEND request to REPLICAT TRANR1 ...

YES.

GGSCI (fahdb.) > STOP REPLICAT TRANR1

Sending STOP request to REPLICAT TRANR1 ...

Request processed.

3 ]Alter the extract to the sequence number generated the PUMP extract had been etrollover  in our scenario it is 136 is the new trail file number...

GGSCI (fahdb) > ALTER REPLICAT TRANR1 EXTSEQNO 136 EXTRBA 0

REPLICAT altered.

GGSCI (fahdb) > START REPLICAT TRANR1

Sending START request to MANAGER ...

REPLICAT TRANR1 starting

GGSCI (fahdb) > info TRANR1

REPLICAT   TRANR1    Last Started 2012-07-18 21:46   Status RUNNING

Checkpoint Lag       00:00:00 (updated 00:00:04 ago)

Log Read Checkpoint  File ./dirdat/t1000136

                     2012-07-16 15:44:22.657553  RBA 1240

Now you can notice the same number in the RBA  between both the source and the 

target now both the node are in the synchronous and this is the way to start the Extract and we have to add two parameter in your master extract    

THREADOPTIONS MAXCOMMITPROPAGATIONDELAY 15000 IOLATENCY 80000

As per metalink note this is the workaround and you shoud upgraded the GG to the new version

To cross verify the RBA you can check the trail file created in the both the GG's the RBA number will be as same as the trail file record size

IN extract GG


GGSCI (db) 5> sh ls -latr /fah/oracle/gg/dirdat/tt00013*


-rw-rw-rw-   1 oraprod    oinstall   9999233 Jul 12 09:31 /fah/oracle/gg/dirdat/tt000130
-rw-rw-rw-   1 oraprod    oinstall   9998804 Jul 15 17:19 /fah/oracle/gg/dirdat/tt000131
-rw-rw-rw-   1 oraprod    oinstall   1614803 Jul 15 23:55 /fah/oracle/gg/dirdat/tt000132
-rw-rw-rw-   1 oraprod    oinstall      1207 Jul 18 20:50 /fah/oracle/gg/dirdat/tt000133 


IN Replicate GG



GGSCI (fahdb.oasiserp.com) 4> sh ls -latr /u01/app/oracle/oracle/product/gg/dirdat/t100013*


-rw-rw-rw- 1 oracle oinstall 6850827 Jul  9 22:31 /u01/app/oracle/oracle/product/gg/dirdat/t1000130
-rw-rw-rw- 1 oracle oinstall 7418909 Jul 10 00:09 /u01/app/oracle/oracle/product/gg/dirdat/t1000131
-rw-rw-rw- 1 oracle oinstall 9235743 Jul 10 00:19 /u01/app/oracle/oracle/product/gg/dirdat/t1000132
-rw-rw-rw- 1 oracle oinstall 9999384 Jul 12 09:39 /u01/app/oracle/oracle/product/gg/dirdat/t1000133
-rw-rw-rw- 1 oracle oinstall 9998837 Jul 15 17:28 /u01/app/oracle/oracle/product/gg/dirdat/t1000134
-rw-rw-rw- 1 oracle oinstall 1614836 Jul 16 00:03 /u01/app/oracle/oracle/product/gg/dirdat/t1000135
-rw-rw-rw- 1 oracle oinstall    1240 Jul 18 21:18 /u01/app/oracle/oracle/product/gg/dirdat/t1000136

Rman Duplicate Database creation with the recovery catalog

Duplicating the database buy using the Rman 

In this environment we have used the fahdb database as the target database and the ORACAT database as the catalog database
and the  fahdb as the auxiliary database

If the target database was in the ASM file system then you have to create the backup in the shared [NFS]  file system  which can be accessed by both the PROD and the Auxiliary database's


[oracat@fahtestdb ~]$ rman

Recovery Manager: Release 11.2.0.2.0 - Production on Tue Jul 17 22:49:57 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target sys/<password>@fahdb

connected to target database: FAHDB (DBID=728861041)

RMAN> connect catalog <username>/<password>@ORACAT

connected to recovery catalog database

RMAN> connect auxiliary sys/<password>@fahdb_test

connected to auxiliary database: FAHDB (not mounted)

This command can be given in the single line also  #   rman connect target <usernane>/password@SID catalog <username>/password@SID Auxiliary <username>/password@SID

The auxiliary database should be in the no mount stage and all the database server must Tns ping each other and you should make the Tns entry of catalog database And the PROD and the auxiliary  database in all three database's and then in the 11g now there was a new future introduced for the active database cloning just you can clone the active database to the new environment but here we are using the traditional method od writing the script to clone in the active cloning if you need to have the same name from the test and the PROD database then it will not allow.. the auxiliary database should be in the different name



For this we need to prepare the script and using the simple command we can do that 

Recovery Manager: Release 11.2.0.2.0 - Production on Wed Jul 11 17:30:49 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: FAHDB (DBID=728861041)
connected to recovery catalog database
connected to auxiliary database: FAHDB (not mounted)

RMAN> @omrman.sql

RMAN> run
2> {
3>
4> set newname for datafile    1        to      '/u06/app/oracle/oradata/datafile/system.dbf';
5> set newname for datafile    2        to       '/u06/app/oracle/oradata/datafile/sysaux.dbf';
6> set newname for datafile    3        to      '/u06/app/oracle/oradata/datafile/fusion_undots.dbf';
7> set newname for datafile    4        to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data01.dbf';
8> set newname for datafile    5        to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data02.dbf';
9> set newname for datafile    6        to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data03.dbf';
10> set newname for datafile    7      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data04.dbf';
11> set newname for datafile    8       to  '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data05.dbf';
12> set newname for datafile    9        to  '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data06.dbf';
13> set newname for datafile    10      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data07.dbf';
14> set newname for datafile    11      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data08.dbf';
15> set newname for datafile    12      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data09.dbf';
16> set newname for datafile    13      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data10.dbf';
17> set newname for datafile    14      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx01.dbf';
18> set newname for datafile    15      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx02.dbf';
19> set newname for datafile    16      to      '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx03.dbf';
20> set newname for datafile    17      to       '/u06/app/oracle/oradata/datafile/fusion_ts_tools.dbf';
21> set newname for datafile    18      to      '/u06/app/oracle/oradata/datafile/search_index.dbf';
22> set newname for datafile    19  to   '/u06/app/oracle/oradata/datafile/fusion_ias_orasdpm_aq.dbf';
23> set newname for datafile    20      to      '/u06/app/oracle/oradata/datafile/fusion_ts_archive.dbf';
24> set newname for datafile    21      to      '/u06/app/oracle/oradata/datafile/fusion_ts_dq.dbf';
25> set newname for datafile    22  to  '/u06/app/oracle/oradata/datafile/fusion_ts_interface.dbf';
26> set newname for datafile    23  to  '/u06/app/oracle/oradata/datafile/fusion_ts_nologging.dbf';
27> set newname for datafile    24      to      '/u06/app/oracle/oradata/datafile/biacmts.dbf';
28> set newname for datafile    25      to      '/u06/app/oracle/oradata/datafile/fusion_ts_seed.dbf';
29> set newname for datafile    26      to      '/u06/app/oracle/oradata/datafile/fusion_dyn_ts.dbf';
30> set newname for datafile    27      to      '/u06/app/oracle/oradata/datafile/fusion_ts_queues.dbf';
31> set newname for datafile    28      to      '/u06/app/oracle/oradata/datafile/fusion_ts_aq.dbf';
32> set newname for datafile    29      to      '/u06/app/oracle/oradata/datafile/search_data.dbf';
33> set newname for datafile    30      to      '/u06/app/oracle/oradata/datafile/fusion_ts_media.dbf';
34> set newname for datafile    31      to      '/u06/app/oracle/oradata/datafile/fusion_ts_summary.dbf';
35>
36>
37>
38> duplicate target database to 'fahdb' --- if you are not mentioning the time then it will restore from the latest backup
39> LOGFILE
40> GROUP 1 ('/u06/app/oracle/oradata/redo01.log','/u06/app/oracle/oradata/redo01a.log') SIZE 2048M ,
41> GROUP 2 ('/u06/app/oracle/oradata/redo02.log','/u06/app/oracle/oradata/redo02a.log') SIZE 2048M ,
42> GROUP 3 ('/u06/app/oracle/oradata/redo03.log','/u06/app/oracle/oradata/redo03a.log') SIZE 2048M ,
43> GROUP 4 ('/u06/app/oracle/oradata/redo04.log','/u06/app/oracle/oradata/redo04a.log') SIZE 2048M ;
44>
45> }
executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting Duplicate Db at 11-JUL-12
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=2828 device type=DISK

contents of Memory Script:
{
   sql clone "alter system set  db_name =
 ''FAHDB'' comment=
 ''Modified by RMAN duplicate'' scope=spfile";
   sql clone "alter system set  db_unique_name =
 ''FAHDB'' comment=
 ''Modified by RMAN duplicate'' scope=spfile";
   shutdown clone immediate;
   startup clone force nomount
   restore clone primary controlfile;
   alter clone database mount;
}
executing Memory Script

sql statement: alter system set  db_name =  ''FAHDB'' comment= ''Modified by RMAN duplicate'' scope=spfile

sql statement: alter system set  db_unique_name =  ''FAHDB'' comment= ''Modified by RMAN duplicate'' scope=spfile

Oracle instance shut down

Oracle instance started

Total System Global Area   19241058304 bytes

Fixed Size                     2234616 bytes
Variable Size               3087009544 bytes
Database Buffers           16106127360 bytes
Redo Buffers                  45686784 bytes

Starting restore at 11-JUL-12
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=2828 device type=DISK

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /shared/oracle/c-728861041-20120711-01
channel ORA_AUX_DISK_1: piece handle=/shared/oracle/c-728861041-20120711-01 tag=TAG20120711T172737
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u06/app/oracle/oradata/datafile/control01.ctl
output file name=/u06/app/oracle/oradata/datafile/control02.ctl
Finished restore at 11-JUL-12

database mounted

contents of Memory Script:
{
   set until scn  15574861794;
   set newname for datafile  1 to
 "/u06/app/oracle/oradata/datafile/system.dbf";
   set newname for datafile  2 to
 "/u06/app/oracle/oradata/datafile/sysaux.dbf";
   set newname for datafile  3 to
 "/u06/app/oracle/oradata/datafile/fusion_undots.dbf";
   set newname for datafile  4 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data01.dbf";
   set newname for datafile  5 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data02.dbf";
   set newname for datafile  6 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data03.dbf";
   set newname for datafile  7 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data04.dbf";
   set newname for datafile  8 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data05.dbf";
   set newname for datafile  9 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data06.dbf";
   set newname for datafile  10 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data07.dbf";
   set newname for datafile  11 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data08.dbf";
   set newname for datafile  12 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data09.dbf";
   set newname for datafile  13 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_data10.dbf";
   set newname for datafile  14 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx01.dbf";
   set newname for datafile  15 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx02.dbf";
   set newname for datafile  16 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx03.dbf";
   set newname for datafile  17 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_tools.dbf";
   set newname for datafile  18 to
 "/u06/app/oracle/oradata/datafile/search_index.dbf";
   set newname for datafile  19 to
 "/u06/app/oracle/oradata/datafile/fusion_ias_orasdpm_aq.dbf";
   set newname for datafile  20 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_archive.dbf";
   set newname for datafile  21 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_dq.dbf";
   set newname for datafile  22 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_interface.dbf";
   set newname for datafile  23 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_nologging.dbf";
   set newname for datafile  24 to
 "/u06/app/oracle/oradata/datafile/biacmts.dbf";
   set newname for datafile  25 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_seed.dbf";
   set newname for datafile  26 to
 "/u06/app/oracle/oradata/datafile/fusion_dyn_ts.dbf";
   set newname for datafile  27 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_queues.dbf";
   set newname for datafile  28 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_aq.dbf";
   set newname for datafile  29 to
 "/u06/app/oracle/oradata/datafile/search_data.dbf";
   set newname for datafile  30 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_media.dbf";
   set newname for datafile  31 to
 "/u06/app/oracle/oradata/datafile/fusion_ts_summary.dbf";
   restore
   clone database
   ;
}
executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 11-JUL-12
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /u06/app/oracle/oradata/datafile/system.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /u06/app/oracle/oradata/datafile/sysaux.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /u06/app/oracle/oradata/datafile/fusion_undots.dbf
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data03.dbf
channel ORA_AUX_DISK_1: restoring datafile 00007 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data04.dbf
channel ORA_AUX_DISK_1: restoring datafile 00008 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data05.dbf
channel ORA_AUX_DISK_1: restoring datafile 00009 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data06.dbf
channel ORA_AUX_DISK_1: restoring datafile 00010 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data07.dbf
channel ORA_AUX_DISK_1: restoring datafile 00011 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data08.dbf
channel ORA_AUX_DISK_1: restoring datafile 00012 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data09.dbf
channel ORA_AUX_DISK_1: restoring datafile 00013 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_data10.dbf
channel ORA_AUX_DISK_1: restoring datafile 00014 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_idx01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00015 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_idx02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00016 to /u06/app/oracle/oradata/datafile/fusion_ts_tx_idx03.dbf
channel ORA_AUX_DISK_1: restoring datafile 00017 to /u06/app/oracle/oradata/datafile/fusion_ts_tools.dbf
channel ORA_AUX_DISK_1: restoring datafile 00018 to /u06/app/oracle/oradata/datafile/search_index.dbf
channel ORA_AUX_DISK_1: restoring datafile 00019 to /u06/app/oracle/oradata/datafile/fusion_ias_orasdpm_aq.dbf
channel ORA_AUX_DISK_1: restoring datafile 00020 to /u06/app/oracle/oradata/datafile/fusion_ts_archive.dbf
channel ORA_AUX_DISK_1: restoring datafile 00021 to /u06/app/oracle/oradata/datafile/fusion_ts_dq.dbf
channel ORA_AUX_DISK_1: restoring datafile 00022 to /u06/app/oracle/oradata/datafile/fusion_ts_interface.dbf
channel ORA_AUX_DISK_1: restoring datafile 00023 to /u06/app/oracle/oradata/datafile/fusion_ts_nologging.dbf
channel ORA_AUX_DISK_1: restoring datafile 00024 to /u06/app/oracle/oradata/datafile/biacmts.dbf
channel ORA_AUX_DISK_1: restoring datafile 00025 to /u06/app/oracle/oradata/datafile/fusion_ts_seed.dbf
channel ORA_AUX_DISK_1: restoring datafile 00026 to /u06/app/oracle/oradata/datafile/fusion_dyn_ts.dbf
channel ORA_AUX_DISK_1: restoring datafile 00027 to /u06/app/oracle/oradata/datafile/fusion_ts_queues.dbf
channel ORA_AUX_DISK_1: restoring datafile 00028 to /u06/app/oracle/oradata/datafile/fusion_ts_aq.dbf
channel ORA_AUX_DISK_1: restoring datafile 00029 to /u06/app/oracle/oradata/datafile/search_data.dbf
channel ORA_AUX_DISK_1: restoring datafile 00030 to /u06/app/oracle/oradata/datafile/fusion_ts_media.dbf
channel ORA_AUX_DISK_1: restoring datafile 00031 to /u06/app/oracle/oradata/datafile/fusion_ts_summary.dbf
channel ORA_AUX_DISK_1: reading from backup piece /shared/oracle/1jnfr8su_1_1
channel ORA_AUX_DISK_1: piece handle=/shared/oracle/1jnfr8su_1_1 tag=TAG20120711T165347
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 01:03:25
Finished restore at 11-JUL-12

contents of Memory Script:

{

   switch clone datafile all;

}

executing Memory Script

datafile 1 switched to datafile copy

input datafile copy RECID=33 STAMP=788316450 file name=/u06/app/oracle/oradata/datafile/system.dbf

datafile 2 switched to datafile copy

input datafile copy RECID=34 STAMP=788316450 file name=/u06/app/oracle/oradata/datafile/sysaux.dbf

datafile 3 switched to datafile copy

input datafile copy RECID=35 STAMP=788316450 file name=/u06/app/oracle/oradata/datafile/fusion_undots.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=36 STAMP=788316450 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data01.dbf

datafile 5 switched to datafile copy

input datafile copy RECID=37 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data02.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=38 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data03.dbf

datafile 7 switched to datafile copy

input datafile copy RECID=39 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data04.dbf

datafile 8 switched to datafile copy

input datafile copy RECID=40 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data05.dbf

datafile 9 switched to datafile copy

input datafile copy RECID=41 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data06.dbf

datafile 10 switched to datafile copy

input datafile copy RECID=42 STAMP=788316451 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data07.dbf

datafile 11 switched to datafile copy

input datafile copy RECID=43 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data08.dbf

datafile 12 switched to datafile copy

input datafile copy RECID=44 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data09.dbf

datafile 13 switched to datafile copy

input datafile copy RECID=45 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_data10.dbf

datafile 14 switched to datafile copy

input datafile copy RECID=46 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx01.dbf

datafile 15 switched to datafile copy

input datafile copy RECID=47 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx02.dbf

datafile 16 switched to datafile copy

input datafile copy RECID=48 STAMP=788316452 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx03.dbf

datafile 17 switched to datafile copy

input datafile copy RECID=49 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/fusion_ts_tools.dbf

datafile 18 switched to datafile copy

input datafile copy RECID=50 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/search_index.dbf

datafile 19 switched to datafile copy

input datafile copy RECID=51 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/fusion_ias_orasdpm_aq.dbf

datafile 20 switched to datafile copy

input datafile copy RECID=52 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/fusion_ts_archive.dbf

datafile 21 switched to datafile copy

input datafile copy RECID=53 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/fusion_ts_dq.dbf

datafile 22 switched to datafile copy

input datafile copy RECID=54 STAMP=788316453 file name=/u06/app/oracle/oradata/datafile/fusion_ts_interface.dbf

datafile 23 switched to datafile copy

input datafile copy RECID=55 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/fusion_ts_nologging.dbf

datafile 24 switched to datafile copy

input datafile copy RECID=56 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/biacmts.dbf

datafile 25 switched to datafile copy

input datafile copy RECID=57 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/fusion_ts_seed.dbf

datafile 26 switched to datafile copy

input datafile copy RECID=58 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/fusion_dyn_ts.dbf

datafile 27 switched to datafile copy

input datafile copy RECID=59 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/fusion_ts_queues.dbf

datafile 28 switched to datafile copy

input datafile copy RECID=60 STAMP=788316454 file name=/u06/app/oracle/oradata/datafile/fusion_ts_aq.dbf

datafile 29 switched to datafile copy

input datafile copy RECID=61 STAMP=788316455 file name=/u06/app/oracle/oradata/datafile/search_data.dbf

datafile 30 switched to datafile copy

input datafile copy RECID=62 STAMP=788316455 file name=/u06/app/oracle/oradata/datafile/fusion_ts_media.dbf

datafile 31 switched to datafile copy

input datafile copy RECID=63 STAMP=788316455 file name=/u06/app/oracle/oradata/datafile/fusion_ts_summary.dbf

contents of Memory Script:

{

   set until scn  15560381088;

   recover

   clone database

    delete archivelog

   ;

}

executing Memory Script

executing command: SET until clause

Starting recover at 11-JUL-12

using channel ORA_AUX_DISK_1

starting media recovery

Oracle instance started

Total System Global Area   19241058304 bytes

Fixed Size                     2234616 bytes

Variable Size               3087009544 bytes

Database Buffers           16106127360 bytes

Redo Buffers                  45686784 bytes

contents of Memory Script:

{

   sql clone "alter system set  db_name =

 ''FAHDB'' comment=

 ''Reset to original value by RMAN'' scope=spfile";

   sql clone "alter system reset  db_unique_name scope=spfile";

   shutdown clone immediate;

}

executing Memory Script

sql statement: alter system set  db_name =  ''FAHDB'' comment= ''Reset to original value by RMAN'' scope=spfile

sql statement: alter system reset  db_unique_name scope=spfile

Oracle instance shut down

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 07/11/2012 00:47:55

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-06053: unable to perform media recovery because of missing log

RMAN-06025: no backup of archived log for thread 1 with sequence 25 and starting SCN of 15560381085 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 24 and starting SCN of 15560381071 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 23 and starting SCN of 15560381058 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 22 and starting SCN of 15560381055 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 21 and starting SCN of 15560268398 found to restore

RMAN>

RMAN> **end-of-file**

so if you are getting the error message for the archive log then you can  copy from the prod to the  auxiliary archive log location

[oratest@fahtestapp ~]$ sqlplus

SQL*Plus: Release 11.2.0.2.0 Production on Wed Jul 11 01:04:27 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

Enter user-name: sys as sysdba

Enter password:

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, Oracle Label Security, OLAP, Data Mining

and Real Application Testing options

SQL> alter database mount;

Database altered.

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-19838: Cannot use this control file to open database

SQL> recover database ;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

SQL> recover database using backup controlfile;

ORA-00279: change 15560374524 generated at 07/10/2012 18:04:15 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/o1_mf_1_21_%u_.ar

c

ORA-00280: change 15560374524 for thread 1 is in sequence #21

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

auto

ORA-00308: cannot open archived log

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/o1_mf_1_21_%u_.a

rc'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00308: cannot open archived log

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/o1_mf_1_21_%u_.a

rc'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

[oratest@fahtestapp ~]$ mkdir /u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/ -p

Manually  copy the files from the prod to the specific directory and recover the database 

SQL> recover database using backup controlfile;

ORA-00279: change 15560374524 generated at 07/10/2012 18:04:15 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_21.3

53.788294345

ORA-00280: change 15560374524 for thread 1 is in sequence #21

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

auto

ORA-00279: change 15560381055 generated at 07/10/2012 18:39:05 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_22.3

54.788294347

ORA-00280: change 15560381055 for thread 1 is in sequence #22

ORA-00278: log file

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_21.

353.788294345' no longer needed for this recovery

ORA-00279: change 15560381058 generated at 07/10/2012 18:39:07 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_23.3

55.788294351

ORA-00280: change 15560381058 for thread 1 is in sequence #23

ORA-00278: log file

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_22.

354.788294347' no longer needed for this recovery

ORA-00279: change 15560381071 generated at 07/10/2012 18:39:10 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_24.3

56.788294355

ORA-00280: change 15560381071 for thread 1 is in sequence #24

ORA-00278: log file

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_23.

355.788294351' no longer needed for this recovery

ORA-00279: change 15560381085 generated at 07/10/2012 18:39:14 needed for

thread 1

ORA-00289: suggestion :

/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_25.3

57.788294359

ORA-00280: change 15560381085 for thread 1 is in sequence #25

ORA-00278: log file

'/u06/app/oracle/fast_recovery_area/FAHDB/archivelog/2012_07_11/thread_1_seq_24.

again login with the database and mount the database and recreate the Control file with the proper locations of the files and open the database

SQL> alter database backup controlfile to trace as '/shared/oracle/controfile';


open the Trace file of the control file and find the script for creating the control file and you can recreate it by using the script in it 

SQL> startup nomount

ORACLE instance started.

Total System Global Area 1.9241E+10 bytes

Fixed Size                  2234616 bytes

Variable Size            3087009544 bytes

Database Buffers         1.6106E+10 bytes

Redo Buffers               45686784 bytes

SQL> CREATE CONTROLFILE REUSE DATABASE "FAHDB" RESETLOGS  ARCHIVELOG

  2      MAXLOGFILES 16

  3      MAXLOGMEMBERS 3

  4      MAXDATAFILES 100

  5      MAXINSTANCES 8

  6      MAXLOGHISTORY 292

  7  LOGFILE

  8    GROUP 1 (

  9      '/u06/app/oracle/oradata/redo01.log',

 10      '/u06/app/oracle/oradata/redo01a.log'

 11    ) SIZE 2048M BLOCKSIZE 512,

 12    GROUP 2 (

 13      '/u06/app/oracle/oradata/redo02.log',

 14      '/u06/app/oracle/oradata/redo02a.log'

 15    ) SIZE 2048M BLOCKSIZE 512,

 16    GROUP 3 (

    '/u06/app/oracle/oradata/redo03.log',

 17   18      '/u06/app/oracle/oradata/redo03a.log'

 19    ) SIZE 2048M BLOCKSIZE 512,

 20    GROUP 4 (

 21      '/u06/app/oracle/oradata/redo04.log',

 22      '/u06/app/oracle/oradata/redo04a.log'

 23    ) SIZE 2048M BLOCKSIZE 512

 24  -- STANDBY LOGFILE

 25  DATAFILE

 26    '/u06/app/oracle/oradata/datafile/system.dbf',

  '/u06/app/oracle/oradata/datafile/sysaux.dbf',

 27   28    '/u06/app/oracle/oradata/datafile/fusion_undots.dbf',

 29    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data01.dbf',

 30    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data02.dbf',

 31    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data03.dbf',

 32    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data04.dbf',

 33    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data05.dbf',

 34    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data06.dbf',

 35    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data07.dbf',

 36    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data08.dbf',

 37    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data09.dbf',

 38    '/u06/app/oracle/oradata/datafile/fusion_ts_tx_data10.dbf',

  '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx01.dbf',

  '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx02.dbf',

  '/u06/app/oracle/oradata/datafile/fusion_ts_tx_idx03.dbf',

 39   40   41   42    '/u06/app/oracle/oradata/datafile/fusion_ts_tools.dbf',

 43    '/u06/app/oracle/oradata/datafile/search_index.dbf',

 44    '/u06/app/oracle/oradata/datafile/fusion_ias_orasdpm_aq.dbf',

 45    '/u06/app/oracle/oradata/datafile/fusion_ts_archive.dbf',

 46    '/u06/app/oracle/oradata/datafile/fusion_ts_dq.dbf',

 47    '/u06/app/oracle/oradata/datafile/fusion_ts_interface.dbf',

 48    '/u06/app/oracle/oradata/datafile/fusion_ts_nologging.dbf',

 49    '/u06/app/oracle/oradata/datafile/biacmts.dbf',

 50    '/u06/app/oracle/oradata/datafile/fusion_ts_seed.dbf',

 51    '/u06/app/oracle/oradata/datafile/fusion_dyn_ts.dbf',

  '/u06/app/oracle/oradata/datafile/fusion_ts_queues.dbf',

 52   53    '/u06/app/oracle/oradata/datafile/fusion_ts_aq.dbf',

 54    '/u06/app/oracle/oradata/datafile/search_data.dbf',

 55    '/u06/app/oracle/oradata/datafile/fusion_ts_media.dbf',

 56    '/u06/app/oracle/oradata/datafile/fusion_ts_summary.dbf'

 57  CHARACTER SET AL32UTF8

;

 58

Control file created.

SQL> alter database open resetlogs;

Database altered.

And After restoring the backup it will go through the recovery process automatically and open the database if you get any  error after restore of the database then you have to manually recover the database for recovering the database manual  by using the archive log
and in the process we need to create the new control file by taking the trace of the existing control file ..

Note: recovering until SCN is not advisable because of the data files the SCN may not changed during the backup and it may give the error messages like

Oracle instance shut down

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 07/10/2012 21:27:11

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-06026: some targets not found - aborting restore

RMAN-06023: no backup or copy of datafile 17 found to restore

and it you check the backup you can find the database copies also in it but the SCN number of the particular datafile may be lower than you specified and it will go to the previous backup if present to read it if there is no backup present then it will give the error message

so for cloning it is advisable with the UNTIL TIME with your own date format's