ORA:01013 with Duplicate Database - RMAN

Hi,
I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
server1 in open status and server2 in nomount state.
the command i ran was:
duplicate target database to clonedb
until logseq 338 thread 1
pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
logfile
'/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
'/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
Please let me know how to overcome this error..
Thanks,
Raj
This is the error i got along with the log it created...
Starting Duplicate Db at 28-OCT-04
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=14 devtype=DISK
printing stored script: Memory Script
set until scn 130734;
set newname for datafile 1 to
"/u02/oradata/clonedb/system01.dbf";
set newname for datafile 2 to
"/u03/oradata/clonedb/undotbs01.dbf";
set newname for datafile 3 to
"/u02/oradata/clonedb/testtbs_01.dbf";
set newname for datafile 4 to
"/u02/oradata/clonedb/system02.dbf";
set newname for datafile 5 to
"/u02/oradata/clonedb/rmantbs_01.dbf";
restore
check readonly
clone database
executing script: 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
Starting restore at 28-OCT-04
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 680
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
DATAFILE
'/u02/oradata/clonedb/system01.dbf'
CHARACTER SET WE8ISO8859P1
printing stored script: Memory Script
switch clone datafile all;
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
printing stored script: Memory Script
set until scn 130734;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 28-OCT-04
using channel ORA_AUX_DISK_1
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
Recovery Manager complete.

HI,
# STBY:
SQL> startup nomount
ORACLE instance started.
Total System Global Area  242208768 bytes
Fixed Size            2227176 bytes
Variable Size          184550424 bytes
Database Buffers       50331648 bytes
Redo Buffers            5099520 bytes
# PRIMARY:
RMAN> CONNECT TARGET sys/oracle@JOHN;
connected to target database: JOHN (DBID=1575580406)
RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
Until this you did correct. now just in a run block, like
eg
run
allocate channel ....
allocate channel...
duplicate target database for standby from active database;

Similar Messages

  • Problems with DUPLICATE DATABASE when datafile was added after full backup

    Hi,
    I'm facing a problem when performing database duplication with the RMAN duplicate database command on a 10g database. If I preform the duplication from a full backup that is missing a datafile which was added to the database after the full backup, I get the following error message:
    Starting restore at 10-10-2009 18:00:38
    released channel: t1
    released channel: t2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/10/2009 18:00:39
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06100: no channel to restore a backup or copy of datafile 43The redo log which was CURRENTat the time of the datafile's 43 creation is also available in the backups. It seems like RMAN can't use the information from the archived redo logs to reconstruct the contents of datafile 43. I suppose that because the failure is reported already in the RESTORE and not in the RECOVER phase, so the archived redo logs aren't even accessed yet. I get the same message even if I make a separate backup of datafile 43 (so a backup that is not in the same backupset as the backup of all other datafiles).
    From the script the duplicate command produces, I guess that RMAN reads the contents of the source database's controlfile and tries to get a backup which contains all the datafiles to restore them on the auxiliary database - if such a backup is not found, it fails.
    Of course if I try to perform a restore/recover of the source database it works without problems:
    RMAN> restore database;
    Starting restore at 13.10.09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    creating datafile fno=43 name=F:\ORA10\ORADATA\SOVDEV\SOMEDATAFILE01.DBF
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to F:\ORA10\ORADATA\SOVDEV\SYSTEM01.DBF
    .....The datafile 43 is recreated and then redo is applied over.
    So, does anyone know if duplicate database can't use archived redo logs to recreate the contents of a datafile as a normal restore/recover does? If it's so, then it means it's necessary to perform a full database backup before every run of duplicate database if a datafile was added after such a backup.
    Thanks in advance for any answers.
    Regards,
    Jure

    Hi Jure,
    I have hit exactly the same problem during duplication.
    Because we backup the archive logs every 6 hours with rman I added an extra run block to this script.
    run
    backup incremental level 0
    format 'bk_%d_%s_%p_%t'
    filesperset 4
    database not backed up;
    (I also than hit a bug in the catalog which was solved by patching up the catalog dbs from 11.1.0.6 to 11.1.0.7.)
    This will narrow down the datafile not being part of any rman backup to 6 hours while skipping datafiles for which a backup already exists.
    Regards,
    Tycho

  • ORA-01013 with Oracle ODBC Driver 8.1.6.3

    I have a very strange problem occuring with the latest Oracle 8.1.6 Driver. I am able to set up the ODBC connection and it tests correctly. I'll open an Access 97 database and attempt to link to a table in an Oracle 8.1.6 through ODBC. I can connect to the database fine and it brings back a list of the available tables. However, when I select a table and attempt to link to it, I get the following error:
    ORA-01013: user requested cancel of current operation.
    This behavior also occurs if I try this operation through VB 6.0 code.
    Has anyone seen this before or better yet, have an answer as to why it is occurring?
    P.S., I'm using MDAC 2.51

    As an update, when I turn tracing on, here is the section of the log file that contains the error.
    MSACCESS d5-cb ENTER SQLStatisticsW
    HSTMT 01861988
    WCHAR * 0x00000000 [ -3] <empty string>
    SWORD -3
    WCHAR * 0x01862528 [ 5] "HQ"
    SWORD 5
    WCHAR * 0x01862548 [ -3] "AS"
    SWORD -3
    UWORD 1 <SQL_INDEX_ALL>
    UWORD 0 <SQL_QUICK>
    MSACCESS d5-cb EXIT SQLStatisticsW with return code -1 (SQL_ERROR)
    HSTMT 01861988
    WCHAR * 0x00000000 [ -3] <empty string>
    SWORD -3
    WCHAR * 0x01862528 [ 5] "HQ"
    SWORD 5
    WCHAR * 0x01862548 [ -3] "AS"
    SWORD -3
    UWORD 1 <SQL_INDEX_ALL>
    UWORD 0 <SQL_QUICK>
    DIAG [S1T00] [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
    (1013)

  • RMAN incompatible with TARGET database

    I have two databases:
    The database with the catalog, version 8.1.7.
    The database to be backed up (target), version 8.0.6.
    When I try to connect to the target, I get an error stating: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
    I've tried changing the "compatible" parameter to 8.0.4, but then I get an error when I restart the database (regarding locally managed tablespaces, which I am not using).
    Any idea what I need to do to connect to the target database?
    thanks....

    Hi !
    I guess you have confused the compatible init.ora parameter with RMAN compatible parameter ,
    They are entirely different. The excerpts here, which i have taken from the Oracle online docs should
    clear your problem.
    The compatible parameter specifies the minimum acceptable release of the RMAN executable that can function with the catalog. For example, if the recovery catalog compatibility is set to 8.1.4, then only an RMAN executable of release 8.1.4 or later can connect to the catalog.
    You cannot set the compatible parameter to a version that is not supported by the currently-installed DBMS_RCVMAN or DBMS_RCVCAT packages. If you try to set compatibility to a version that is not supported by one of the packages, then you receive an error message that indicates the lowest and highest value you can set, as in the following example:
    RMAN> configure compatible = 8.0.1;
    RMAN-03022: compiling command: configure
    RMAN-03026: error recovery releasing channel resources
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: configure
    RMAN-06455: illegal compatible value 8.0.1: must be between 08.00.04 and 08.01.06
    To view the compatibility level of the recovery catalog:
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Start a SQL*Plus session and connect to the recovery catalog database as the recovery catalog owner. For example, enter:
    SQL> connect rman/rman@rcat
    Issue the following query:
    SQL> SELECT value FROM config WHERE name='compatible';
    VALUE
    080106
    To create an 8.1.6 recovery catalog that is usable with a pre-8.1.6 RMAN executable:
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    This procedure assumes that you have the use of both an 8.1.6 and pre-8.1.6 RMAN executable. The method employed it to use a pre-8.1.6 RMAN executable to create the recovery catalog, and a release 8.1.6 RMAN executable to upgrade it. The compatibility level is automatically set to 8.0.4, which has the implications described in Table 3-1.
    Use a pre-8.1.6 RMAN executable to connect to the catalog database. For example, enter:
    % rman catalog rman/rman@rcat
    Recovery Manager: Release 8.1.5.0.0
    RMAN-06008: connected to recovery catalog database
    Create the recovery catalog and then exit. For example, enter:
    RMAN> create catalog;
    RMAN> exit
    Note:
    If you use a release 8.0 RMAN executable to create the catalog, you must use the catrman.sql script to create the recovery catalog.
    Use the 8.1.6 RMAN executable to connect to the newly created recovery catalog:
    % rman catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0
    RMAN-06008: connected to recovery catalog database
    Upgrade the recovery catalog to release 8.1.6:
    RMAN> upgrade catalog;
    RMAN> exit
    The compatibility level of the recovery catalog is now automatically set to 8.0.4.
    Regards,
    Mohamed Iqbal.
    [email protected]

  • Duplicate database command fails with RMAN-06023

    Hello,
    I am trying to test out the duplicate database command in RMAN and am running into some issues.
    I did a backup of my test database, copied the backup files to a second server, and now I'm trying to run the duplicate command and I get RMAN-06023 errors for all of my datafiles.
    I did crosschecks on my backupsets and they showed as available. They are in the same location on the new server, with the same permissions. There are no recent archived logs, as this is a very quiet environment.
    My commands and output (edited slightly) were as follows:
    RMAN> run {
    2> allocate channel d1 device type disk;
    3> allocate channel d2 device type disk;
    4> backup database;
    5> }
    allocated channel: d1
    channel d1: sid=32 devtype=DISK
    allocated channel: d2
    channel d2: sid=36 devtype=DISK
    Starting backup at 03-JUL-07
    channel d1: starting full datafile backupset
    channel d1: specifying datafile(s) in backupset
    channel d2: starting full datafile backupset
    channel d2: specifying datafile(s) in backupset
    input datafile fno=00012 name=/database/oradata/source/matrix_ts01.dbf
    input datafile fno=00004 name=/database/oraindex/source/ind_ts01.dbf
    input datafile fno=00006 name=/database/oradata/source/users_ts01.dbf
    input datafile fno=00003 name=/database/oradata/source/drsys01.dbf
    input datafile fno=00007 name=/database/oradata/source/ORACLEORADATATST2CWMLITE01.DBF
    input datafile fno=00009 name=/database/oradata/source/ORACLEORADATATST2ODM01.DBF
    input datafile fno=00005 name=/database/oradata/source/tools_ts01.dbf
    channel d2: starting piece 1 at 03-JUL-07
    including current SPFILE in backupset
    including current controlfile in backupset
    input datafile fno=00011 name=/database/oradata/source/ORACLEORADATADATA.DBF
    input datafile fno=00001 name=/database/oradata/source/system_ts01.dbf
    input datafile fno=00002 name=/database/oradata/source/undo_ts01.dbf
    input datafile fno=00008 name=/database/oradata/source/ORACLEORADATATST2EXAMPLE01.DBF
    input datafile fno=00010 name=/database/oradata/source/ORACLEORADATATST2XDB01.DBF
    channel d1: starting piece 1 at 03-JUL-07
    channel d2: finished piece 1 at 03-JUL-07
    piece handle=/database/oracle/product/9.2.0/dbs/0ciltjgn_1_1 comment=NONE
    channel d2: backup set complete, elapsed time: 00:08:17
    channel d1: finished piece 1 at 03-JUL-07
    piece handle=/database/oracle/product/9.2.0/dbs/0biltjgn_1_1 comment=NONE
    channel d1: backup set complete, elapsed time: 00:09:22
    Finished backup at 03-JUL-07
    released channel: d1
    released channel: d2
    ** at this point I copied the files listed above to same directory on destination server **
    RMAN> connect auxiliary sys/[email protected]
    connected to auxiliary database: destination (not mounted)
    RMAN> run {
    2> allocate auxiliary channel aux1 device type disk;
    3> allocate auxiliary channel aux2 device type disk;
    4> duplicate target database to destination nofilenamecheck;
    5> }
    llocated channel: aux1
    channel aux1: sid=10 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=13 devtype=DISK
    Starting Duplicate Db at 03-JUL-07
    printing stored script: Memory Script
    set until scn 4873550;
    set newname for datafile 1 to
    "/database/oradata/destination/system_ts01.dbf";
    set newname for datafile 2 to
    "/database/oradata/destination/undo_ts01.dbf";
    set newname for datafile 3 to
    "/database/oradata/destination/drsys01.dbf";
    set newname for datafile 4 to
    "/database/oraindex/destination/ind_ts01.dbf";
    set newname for datafile 5 to
    "/database/oradata/destination/tools_ts01.dbf";
    set newname for datafile 6 to
    "/database/oradata/destination/users_ts01.dbf";
    set newname for datafile 7 to
    "/database/oradata/destination/ORACLEORADATATST2CWMLITE01.DBF";
    set newname for datafile 8 to
    "/database/oradata/destination/ORACLEORADATATST2EXAMPLE01.DBF";
    set newname for datafile 9 to
    "/database/oradata/destination/ORACLEORADATATST2ODM01.DBF";
    set newname for datafile 10 to
    "/database/oradata/destination/ORACLEORADATATST2XDB01.DBF";
    set newname for datafile 11 to
    "/database/oradata/destination/ORACLEORADATADATA.DBF";
    set newname for datafile 12 to
    "/database/oradata/destination/matrix_ts01.dbf";
    restore
    check readonly
    clone database
    executing script: 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
    Starting restore at 03-JUL-07
    released channel: aux1
    released channel: aux2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/03/2007 14:35:13
    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 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Thanks for any help,

    Hi,
    Where is you RMAN catalog? I think you forgot to connect to it.
    To duplicate a database check that folowing applies:
    1-the auxiliary instance is mounted
    2-the listener for the auxiliary db is up
    3-the backup pieces that RMAN is going to restore ARE AVAILABLE on the
    secondary/auxilary server with SAME NAME the have on the primary server (you can use NFS to avoid the copy of the pieces from primary to auxuliary box)
    Remember to be conected to both: target and auxiliary db.
    I have extracted the folowing lines from an RMAN script I used to create an standby database with the DUPLICATE command (the RMAN catalog was in the primary db controlfile, and the command was run on the primary server:
    $ rman target / nocatalog auxiliary sys/pwd@standbycard log=crCARD.log
    RMAN> duplicate target database for standby nofilenamecheck dorecover;
    I hope this helps
    Gustavo Restuccia

  • Rman Duplicate database synchronization problem

    Hi
    I have the Oracle database 9.2.0.1.0 .I've created Duplicate database on another computer with the same structure and Oracle 9.2.0.1.0 too.
    Now, I want to synchronize my duplicate by primary database, and I copied backup of all datafiles & archive logs & and backup that was taken by RMAN, but in the middle of processing I got this error.
    printing stored script: Memory Script
    set until scn 443620578;
    recover
    clone database
    delete archivelog
    executing script: Memory Script
    executing command: SET until clause
    Starting recover at 31-MAR-03
    starting media recovery
    channel ch1: starting archive log restore to default destination
    channel ch1: restoring archive log
    archive log thread=1 sequence=106
    channel ch1: restored backup piece 1
    piece handle=C:\ORACLE\ORA9I\DATABASE\23EJCO3D_1_1 tag=TAG20030331T114405 params=NULL
    channel ch1: restore complete
    archive log filename=C:\ORACLE\ORADATA\DELLDUP\ARCHIVE\DELLDUPT001S00106.ARC thr
    ead=1 sequence=106
    channel clone_default: deleting archive log(s)
    archive log filename=C:\ORACLE\ORADATA\DELLDUP\ARCHIVE\DELLDUPT001S00106.ARC rec
    id=1 stamp=490112362
    media recovery complete
    Finished recover at 31-MAR-03
    printing stored script: Memory Script
    shutdown clone;
    startup clone nomount ;
    executing script: Memory Script
    RMAN-00571:===============================================
    RMAN-00569: ===============ERROR MESSAGE STACK FOLLOWS
    RMAN-00571:===============================================
    RMAN-03002: failure of Duplicate Db command at 03/31/2003 15:20:53
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
    What should I Do?
    tx

    I beleive... and correct me if I'm wrong, but the duplicate command will open the db created with RESET LOGS. Thereby meaning you can't use the archive logs.

  • RMAN 11gr2 ORA-00308 when dulplicate database from active

    Hi,
    I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
    the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
    but the RMAN fails at end of the process:
    Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: SIN (DBID=634625013)
    connected to recovery catalog database
    connected to auxiliary database: SIN (not mounted)
    RMAN> run
    +2> {+
    +3> allocate channel c1 type disk;+
    +4> allocate channel c2 type disk;+
    +5> allocate channel c3 type disk;+
    +6> allocate channel c4 type disk;+
    +7> allocate auxiliary channel a1 type disk;+
    +8> allocate auxiliary channel a2 type disk;+
    +9> set newname for datafile 1 to '+DG_DATA';+
    +10> set newname for datafile 2 to '+DG_DATA';+
    +11> set newname for datafile 3 to '+DG_DATA';+
    +12> set newname for datafile 4 to '+DG_DATA';+
    +13> set newname for datafile 5 to '+DG_DATA';+
    +14> set newname for datafile 6 to '+DG_DATA';+
    +15> set newname for datafile 7 to '+DG_DATA';+
    +16> set newname for datafile 8 to '+DG_DATA';+
    +17> set newname for datafile 9 to '+DG_DATA';+
    +18> set newname for datafile 10 to '+DG_DATA';+
    +... to...+
    +398> set newname for datafile 390 to '+DG_DATA';+
    +399> set newname for datafile 391 to '+DG_DATA';+
    +400> duplicate target database to "sin" from active database nofilenamecheck+
    +401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
    +402> '/u11/oradata/sin/','+DG_DATA/',+
    +403> '/u07/oradata/sin/','+DG_DATA/',+
    +404> '/u08/oradata/sin/','+DG_DATA/',+
    +405> '/u09/oradata/sin/','+DG_DATA/');+
    +406> }+
    +407>+
    starting full resync of recovery catalog
    full resync complete
    allocated channel: c1
    channel c1: SID=1787 device type=DISK
    allocated channel: c2
    channel c2: SID=2406 device type=DISK
    allocated channel: c3
    channel c3: SID=850 device type=DISK
    allocated channel: c4
    channel c4: SID=1146 device type=DISK
    allocated channel: a1
    channel a1: SID=1325 device type=DISK
    allocated channel: a2
    channel a2: SID=1514 device type=DISK
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    +...+
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting Duplicate Db at 22-AUG-12
    contents of Memory Script:
    +{+
    sql clone "create spfile from memory";
    +}+
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
    +{+
    shutdown clone immediate;
    startup clone nomount;
    +}+
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    7317790720 bytes
    Fixed Size                     2173456 bytes
    Variable Size               3808433648 bytes
    Database Buffers            3489660928 bytes
    Redo Buffers                  17522688 bytes
    allocated channel: a1
    channel a1: SID=1325 device type=DISK
    allocated channel: a2
    channel a2: SID=758 device type=DISK
    contents of Memory Script:
    +{+
    sql clone "alter system set  control_files =
    +''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
    +''Set by RMAN'' scope=spfile";+
    +''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
    +''Set by RMAN'' scope=spfile";+
    sql clone "alter system set  db_name =
    +''SIN'' comment=+
    +''Modified by RMAN duplicate'' scope=spfile";+
    +sql clone "alter system set db_unique_name =+
    +''SIN'' comment=+
    +''Modified by RMAN duplicate'' scope=spfile";+
    +shutdown clone immediate;+
    +startup clone force nomount+
    +backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
    +restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
    +'+DG_DATA/sin/controlfile/current.512.791978153';+
    +sql clone "alter system set control_files =+
    +''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
    +''Set by RMAN'' scope=spfile";+
    +shutdown clone immediate;+
    +startup clone nomount;+
    +alter clone database mount;+
    +}+
    +executing Memory Script+
    +sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
    +rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
    +sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
    +sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
    +Oracle instance shut down+
    +Oracle instance started+
    +Total System Global Area 7317790720 bytes+
    +Fixed Size 2173456 bytes+
    +Variable Size 3808433648 bytes+
    +Database Buffers 3489660928 bytes+
    +Redo Buffers 17522688 bytes+
    +allocated channel: a1+
    +channel a1: SID=1514 device type=DISK+
    +allocated channel: a2+
    +channel a2: SID=2081 device type=DISK+
    +Starting backup at 22-AUG-12+
    +channel c1: starting datafile copy+
    +copying current control file+
    +output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
    +channel c1: datafile copy complete, elapsed time: 00:00:01+
    +Finished backup at 22-AUG-12+
    +Starting restore at 22-AUG-12+
    +channel a2: skipped, AUTOBACKUP already found+
    +channel a1: copied control file copy+
    +Finished restore at 22-AUG-12+
    +sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
    +rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
    +Oracle instance shut down+
    +connected to auxiliary database (not started)+
    +Oracle instance started+
    +Total System Global Area 7317790720 bytes+
    +Fixed Size 2173456 bytes+
    +Variable Size 3808433648 bytes+
    +Database Buffers 3489660928 bytes+
    +Redo Buffers 17522688 bytes+
    +allocated channel: a1+
    +channel a1: SID=1514 device type=DISK+
    +allocated channel: a2+
    +channel a2: SID=2081 device type=DISK+
    +database mounted+
    +Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
    +Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
    +...+
    +Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
    +Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
    +Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
    +contents of Memory Script:+
    +{+
    +sql 'alter system archive log current';+
    +}+
    +executing Memory Script+
    +sql statement: alter system archive log current+
    +contents of Memory Script:+
    +{+
    +backup as copy reuse+
    +archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
    +"+DG_DATA" archivelog like+
    +"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
    +"+DG_DATA" archivelog like+
    +"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
    +"+DG_DATA" archivelog like+
    +"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
    +"+DG_DATA" archivelog like+
    +"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
    +"+DG_DATA" ;+
    +catalog clone start with "+DG_DATA";+
    +catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
    +"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
    +"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
    +"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
    +"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
    +"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
    +"+DG_DATA/sin/datafile/drsys.621.791939555",+
    +"+DG_DATA/sin/datafile/high_idx.663.791914889",+
    +"+DG_DATA/sin/datafile/tools.507.791939555",+
    +...+
    +"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
    +"+DG_DATA/sin/datafile/med_dat.498.791939115",+
    +"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
    +"+DG_DATA/sin/datafile/med_dat.499.791939115";+
    +switch clone datafile 1 to datafilecopy+
    +"+DG_DATA/sin/datafile/system.666.791914845";+
    +switch clone datafile 2 to datafilecopy+
    +"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
    +switch clone datafile 3 to datafilecopy+
    +...+
    +"+DG_DATA/sin/datafile/med_dat.498.791939115";+
    +switch clone datafile 390 to datafilecopy+
    +"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
    +switch clone datafile 391 to datafilecopy+
    +"+DG_DATA/sin/datafile/med_dat.499.791939115";+
    +}+
    +executing Memory Script+
    +Starting backup at 22-AUG-12+
    +channel c1: starting archived log copy+
    +input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
    +channel c2: starting archived log copy+
    +input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
    +channel c3: starting archived log copy+
    +input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
    +channel c4: starting archived log copy+
    +input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
    +output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
    +channel c3: archived log copy complete, elapsed time: 00:00:35+
    +channel c3: starting archived log copy+
    +input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
    +output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
    +channel c1: archived log copy complete, elapsed time: 00:00:51+
    +output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
    +channel c2: archived log copy complete, elapsed time: 00:01:41+
    +output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
    +channel c3: archived log copy complete, elapsed time: 00:01:06+
    +output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
    +channel c4: archived log copy complete, elapsed time: 00:01:41+
    +Finished backup at 22-AUG-12+
    +searching for all files that match the pattern +DG_DATA+
    +List of Files Unknown to the Database+
    +=====================================+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
    +...+
    +File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
    +File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
    +File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
    +cataloging files...+
    +cataloging done+
    +List of Cataloged Files+
    +=======================+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
    +File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
    +...+
    +File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
    +File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
    +List of Files Which Where Not Cataloged+
    +=======================================+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
    +RMAN-07517: Reason: The file header is corrupted+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
    +RMAN-07517: Reason: The file header is corrupted+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
    +RMAN-07517: Reason: The file header is corrupted+
    +File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
    +RMAN-07517: Reason: The file header is corrupted+
    +File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
    +RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
    +cataloged datafile copy+
    +...+
    +datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
    +cataloged datafile copy+
    +datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
    +datafile 1 switched to datafile copy+
    +input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
    +datafile 2 switched to datafile copy+
    +input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
    +datafile 3 switched to datafile copy+
    +input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
    +datafile 4 switched to datafile copy+
    +input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
    +...+
    +datafile 389 switched to datafile copy+
    +input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
    +datafile 390 switched to datafile copy+
    +input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
    +datafile 391 switched to datafile copy+
    +input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
    +contents of Memory Script:+
    +{+
    +set until scn 46167049411;+
    +recover+
    +clone database+
    +delete archivelog+
    +;+
    +}+
    +executing Memory Script+
    +executing command: SET until clause+
    +Starting recover at 22-AUG-12+
    +starting media recovery+
    +archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
    +91978259+
    +archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
    +91978259+
    +archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
    +91978259+
    +archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
    +91978259+
    +archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
    +91978295+
    +archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
    +released channel: c1+
    +released channel: c2+
    +released channel: c3+
    +released channel: c4+
    +Oracle Error:+
    +ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
    +ORA-01194: file 1 needs more recovery to be consistent+
    +ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
    *+released channel: a1+*
    *+released channel: a2+*
    *+RMAN-00571: ===========================================================+*
    *+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
    *+RMAN-00571: ===========================================================+*
    *+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
    *+RMAN-05501: aborting duplication of target database+*
    *+RMAN-03015: error occurred in stored script Memory Script+*
    *+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
    *+ad_1_seq_65832.513.791978259'+*
    *+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
    +Recovery Manager complete.+
    the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
    Please help me to find what is wrong here!!

    Hi mseberg
    that's exactly i'm doing:
    1. Create an Oracle Password File for the Auxiliary Database
    a. done, passwd file created*
    2. Create the Directory Structure on the remote server
    a. done, all the admin structure wa created.*
    3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
    a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
    4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
    a. done, this is my initialization file:*
    *.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
    *.audit_trail='db'*
    *.compatible='11.2.0.0.0'*
    *.db_block_size=8192*
    *.db_create_file_dest='DG_DATA'+*
    *.db_domain=''*
    *.db_files=2048*
    *.db_name='sin'*
    *.db_recovery_file_dest='DG_DATA'+*
    *.db_recovery_file_dest_size=20G*
    *.diagnostic_dest='/u01/app/oracle'*
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
    *.log_archive_format='%t_%s_%r.dbf'*
    *.memory_target=7340032000*
    *.open_cursors=300*
    *.processes=2000*
    *.remote_login_passwordfile='EXCLUSIVE'*
    *.sessions=2205*
    *.undo_tablespace='UNDOTBS1'*
    DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
    +'/u11/oradata/sin/','+DG_DATA/',+
    +'/u07/oradata/sin/','+DG_DATA/',+
    +'/u08/oradata/sin/','+DG_DATA/',+
    +'/u09/oradata/sin/','+DG_DATA/')+
    LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
    +'/u05/oradata/sin/','+DG_DATA/',+
    +'/u03/oradata/sin/','+DG_DATA/',+
    +'/u02/oradata/sin/','+DG_DATA/')+
    and this is my command from RMAN:
    run*
    *+{+*
    allocate channel c1 type disk;*
    allocate channel c2 type disk;*
    allocate channel c3 type disk;*
    allocate channel c4 type disk;*
    allocate auxiliary channel a1 type disk;*
    allocate auxiliary channel a2 type disk;*
    set newname for datafile 1 to 'DG_DATA';+*
    set newname for datafile 2 to 'DG_DATA';+*
    set newname for datafile 3 to 'DG_DATA';+*
    set newname for datafile 4 to 'DG_DATA';+*
    set newname for datafile 5 to 'DG_DATA';+*
    set newname for datafile 6 to 'DG_DATA';+*
    set newname for datafile 7 to 'DG_DATA';+*
    set newname for datafile 8 to 'DG_DATA';+*
    set newname for datafile 9 to 'DG_DATA';+*
    set newname for datafile 10 to 'DG_DATA';+*
    +...+
    set newname for datafile 390 to 'DG_DATA';+*
    set newname for datafile 391 to 'DG_DATA';+*
    duplicate target database to "sin" from active database nofilenamecheck*
    DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
    +'/u11/oradata/sin/','+DG_DATA/',+
    +'/u07/oradata/sin/','+DG_DATA/',+
    +'/u08/oradata/sin/','+DG_DATA/',+
    +'/u09/oradata/sin/','+DG_DATA/');+
    +}+
    do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
    and when I get the error, I have the same dbid in both databases (source and destination)
    Thanks
    MM

  • Rman clone duplicate database from active database

    Hi All,
    I read document saying that rman can duplicate database from active database (prod) to a remote server, so long as you configure listener and tnsname.
    I am working toward it.
    I met a problem, which is when i bring up auxiliary database in nomount mode, the listener service of that auxiliary database is in BLOCKED status, and throw out ora-12528 error when I rman auxiliary sys/pass@clonedb. Isn't nomount mode the mode which auxiliary db is supposed to be in?
    (ora-12528: TNS:listener: all appropriate instances are blocking new connections)
    Thanks,
    milic

    You may have run into the same problem like I did recently:
    The (UR=A) clause in tnsnames.ora is intended to work with a dynamically registered handler so the use of SERVICE_NAME versus SID is preferred.
    ORA-12528: TNS listener BLOCKED - trying to duplicate database
    Also for further problems:
    RMAN 11gR2 duplicate database ORA-17627 ORA-01017 RMAN-03009 ORA-17628

  • DUPLICATE DATABASE IN ANOTHER HOST WITH THE SAME DATABASE NAME

    Hi all.
    I want duplicate a database(dbteste1 host:wander) to another host(magda) with the same database name.
    My tnsnames in host wander is this:
    DBTESTE1 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = wander)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = dbteste1)
    DBTEST1 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = magda)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = dbteste1)
    Tnsping is ok !!!
    Follow the rman command;
    RMAN> run
    duplicate target database to dbtest1 nofilenamecheck;
    and i get the following message:
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE falhou
    ORA-01504: o nome 'dbtest1' do banco de dados nÒo corresponde ao parÔmetro db_name 'dbteste1'
    If i run this command:
    RMAN> run
    duplicate target database to dbteste1 nofilenamecheck;
    and i get the following message:
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: RMAN-20021: database not set
    RMAN-06031: could not translate database keyword
    I´m using oracle 9.2.0.7 on Windows

    Wrong procedure and connection command,
    check Oracle document,
    Duplicating a Database with Recovery Manager
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmdupdb.htm#RCMUG012
    Follow all steps listed.

  • Problems creating control file in RMAN duplicate database

    There is so much detail involved in this operation that I don't know what might be useful, so I'll start simple. I'm attempting to clone a database on the same host using RMAN "duplicate database". I finally got all the setup done, the OS authentication hurdles hurdled, etc. and entered the command:
    duplicate target database to COPYCH2M until time "to_date('March 15 2012 12:00:00', 'Mon DD YYYY HH24:MI:SS')";
    The first time I got:
    ORA-19504: failed to create file "/u01/app/oracle/oradata/COPYCH2M/control01.ctl"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 2: No such file or directory
    There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/21/2012 15:59:25
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 11.1.0.1.0
    ORA-00202: control file: '/u01/app/oracle/oradata/COPYCH2M/control01.ctl'
    Sounds straightforward, if frustrating, right? Apparently you can't duplicate a database that's not in the exact same version. But:
    1) The backuppiece we got the control file from was from last November.
    2) The version of Oracle has not been updated since that time.
    How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
    Thanks, I'm hoping this is easy but I can post more info if needed.

    >
    There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
    >
    The database is limited as to what it can create. Since you defined where you wanted the controlfiles to go (pfile/spfile), it's up to you to make sure the directory is valid and exists. :)
    >
    How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
    >
    As for your controlfiles, make sure the compatible parameter is set the same on both the source and the target unless you are using the default (11.1.0.1 for you, and you aren't)
    Keep going, you'll get there. RMAN duplicate is a great feature.
    Good luck.

  • Duplicate database from RMAN. Physical Dataguard. Error

    Hi All,
    it is really frustrating. I have used the same script and it worked. versions are same 11.2.0.3.2 on both AIX 5.3 servers. tns entries are correct . listener entries correct.
    Here is script and errors
    set -x
    export NLS_DATE_FORMAT='mm/dd/yyyy hh24:mi:ss'
    export ORACLE_BASE=/a0277/oracle
    export ORACLE_HOME=/a0277/oracle/app/oracle/product/11203/db_1
    export LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32
    export LD_LIBRARY_PATH=$LIBPATH
    export CLASSPATH=$ORACLE_HOME/jlib
    export PATH=/a0277/oracle/app/oracle/product/11203/db_1/bin:/usr/ccs/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/local/bin
    export ORACLE_SID=ufms777
    rman <<EOF
    connect auxiliary sys/sys_143_npr#555@ufms777
    connect target sys/sys_143_npr#555@ufms555
    run
    allocate channel d01 type disk;
    allocate channel d02 type disk;
    allocate channel d03 type disk;
    allocate channel d04 type disk;
    allocate channel d05 type disk;
    allocate auxiliary channel stby01 type disk;
    allocate auxiliary channel stby02 type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert '+DATA/ufms555/','+DATA/','ufms555','ufms777' set db_create_file_dest='+DATA'
    set db_unique_name='ufms777'
    set control_files='+DATA'
    set audit_file_dest='/a0277/oracle/admin/ufms777/adump'
    set diagnostic_dest='/a0277/oracle';
    release channel d01;
    release channel d02;
    release channel d03;
    release channel d04;
    release channel d05;
    release channel stby01 ;
    release channel stby02 ;
    quit;
    EOF
    ERROR.
    + export NLS_DATE_FORMAT=mm/dd/yyyy hh24:mi:ss
    + export ORACLE_BASE=/a0277/oracle
    + export ORACLE_HOME=/a0277/oracle/app/oracle/product/11203/db_1
    + export LIBPATH=/a0277/oracle/app/oracle/product/11203/db_1/lib:/a0277/oracle/app/oracle/product/11203/db_1/lib32
    + export LD_LIBRARY_PATH=/a0277/oracle/app/oracle/product/11203/db_1/lib:/a0277/oracle/app/oracle/product/11203/db_1/lib32
    + export CLASSPATH=/a0277/oracle/app/oracle/product/11203/db_1/jlib
    + export PATH=/a0277/oracle/app/oracle/product/11203/db_1/bin:/usr/ccs/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/local/bin
    + export ORACLE_SID=ufms777
    + rman
    + 0< /tmp/sh4391202.2
    Recovery Manager: Release 11.2.0.3.0 - Production on Mon Oct 15 10:47:25 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    connected to auxiliary database: UFMS555 (not mounted)
    RMAN>
    connected to target database: UFMS555 (DBID=1402717741)
    RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24>
    using target database control file instead of recovery catalog
    allocated channel: d01
    channel d01: SID=629 device type=DISK
    allocated channel: d02
    channel d02: SID=681 device type=DISK
    allocated channel: d03
    channel d03: SID=733 device type=DISK
    allocated channel: d04
    channel d04: SID=785 device type=DISK
    allocated channel: d05
    channel d05: SID=837 device type=DISK
    allocated channel: stby01
    channel stby01: SID=583 device type=DISK
    allocated channel: stby02
    channel stby02: SID=699 device type=DISK
    Starting Duplicate Db at 10/15/2012 10:47:35
    contents of Memory Script:
    backup as copy reuse
    targetfile '/a0143/oracle/product/11203/db_1/dbs/orapwufms555' auxiliary format
    '/a0277/oracle/app/oracle/product/11203/db_1/dbs/orapwufms777' targetfile
    '/a0143/oracle/product/11203/db_1/dbs/spfileufms555.ora' auxiliary format
    '/a0277/oracle/app/oracle/product/11203/db_1/dbs/spfileufms777.ora' ;
    sql clone "alter system set spfile= ''/a0277/oracle/app/oracle/product/11203/db_1/dbs/spfileufms777.ora''";
    executing Memory Script
    Starting backup at 10/15/2012 10:47:35
    Finished backup at 10/15/2012 10:47:36
    sql statement: alter system set spfile= ''/a0277/oracle/app/oracle/product/11203/db_1/dbs/spfileufms777.ora''
    contents of Memory Script:
    sql clone "alter system set dispatchers =
    ''(PROTOCOL=TCP) (SERVICE=ufms777XDB)'' comment=
    '''' scope=spfile";
    sql clone "alter system set log_archive_dest_1 =
    ''LOCATION=USE_DB_RECOVERY_FILE_DEST DB_UNIQUE_NAME=ufms777'' comment=
    '''' scope=spfile";
    sql clone "alter system set db_create_file_dest =
    ''+DATA'' comment=
    '''' scope=spfile";
    sql clone "alter system set db_unique_name =
    ''ufms777'' comment=
    '''' scope=spfile";
    sql clone "alter system set control_files =
    ''+DATA'' comment=
    '''' scope=spfile";
    sql clone "alter system set audit_file_dest =
    ''/a0277/oracle/admin/ufms777/adump'' comment=
    '''' scope=spfile";
    sql clone "alter system set diagnostic_dest =
    ''/a0277/oracle'' comment=
    '''' scope=spfile";
    shutdown clone immediate;
    startup clone nomount;
    executing Memory Script
    sql statement: alter system set dispatchers = ''(PROTOCOL=TCP) (SERVICE=ufms777XDB)'' comment= '''' scope=spfile
    sql statement: alter system set log_archive_dest_1 = ''LOCATION=USE_DB_RECOVERY_FILE_DEST DB_UNIQUE_NAME=ufms777'' comment= '''' scope=spfile
    sql statement: alter system set db_create_file_dest = ''+DATA'' comment= '''' scope=spfile
    sql statement: alter system set db_unique_name = ''ufms777'' comment= '''' scope=spfile
    sql statement: alter system set control_files = ''+DATA'' comment= '''' scope=spfile
    sql statement: alter system set audit_file_dest = ''/a0277/oracle/admin/ufms777/adump'' comment= '''' scope=spfile
    sql statement: alter system set diagnostic_dest = ''/a0277/oracle'' comment= '''' scope=spfile
    Oracle instance shut down
    released channel: d01
    released channel: d02
    released channel: d03
    released channel: d04
    released channel: d05
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/15/2012 10:47:44
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied
    RMAN>
    Recovery Manager complete.

    Thanks Osama for quick response.
    Here is output
    (NP) SYS@ufms777 AS SYSDBA> startup nomount pfile=$ORACLE_HOME/dbs/initufms777.oraORACLE instance started.
    Total System Global Area 1770434560 bytes
    Fixed Size 2222320 bytes
    Variable Size 1056966416 bytes
    Database Buffers 704643072 bytes
    Redo Buffers 6602752 bytes
    (NP) SYS@ufms777 AS SYSDBA> eit
    SP2-0042: unknown command "eit" - rest of line ignored.
    (NP) SYS@ufms777 AS SYSDBA> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    k801ora@jd1su277 in /exports/scripts : sqlplus sys/sys_143_npr#555@ufms777 as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Mon Oct 15 11:08:04 2012
    Copyright (c) 1982, 2011, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    (NP) SYS@ufms777 AS SYSDBA>

  • Problem with duplicate target database from active database

    Hi all,
    i try duplicate database from active database
    - I have von target and auxiliary the same SYS Password
    - tnsping wogks in both directions fine
    - sqlplus to target and auxilairy works from both server
    - Metalink Solution 1056174.1 not help
    but in the Rman log become this error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on a1 channel at
    ORA-17629: Cannot connect to the remote database server
    ORA-17629: Cannot connect to the remote database server
    i do do :
    rman target sys/PASSWD@TARGET auxiliary sys/PASSWD
    run
    ALLOCATE CHANNEL a1 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL d1 DEVICE TYPE DISK;
    duplicate target database to XXXXX
    from active database
    DB_FILE_NAME_CONVERT ('/XXXX/XXXX/XXXXXX','/XXXXX/XXXXXX/XXXXX/')
    spfile
    parameter_value_convert '/XXXX/','/XXXXX/'
    set log_file_name_convert '/XXXXX/','/XXXXX/'
    any Idea ?
    Best Regards

    Don't know if this will help, but I use the connect string below to connect, then run the command below. This is, of course, after the rman backup from the prod system has been copied to the flash_recovery_area of the aux database. All file paths are the same between the two systems. Works like a charm most nights. The local tnsnames file on the rman catalog server has working entries for @SDPROD, @rman and @SDSTB.
    [Connect String]
    rman TARGET SYS/xxxxx@SDPROD CATALOG rman/xxxxx@rman AUXILIARY SYS/xxxxx@SDSTB cmdfile D:\cladmin\Scripts\DuplicateSD.rcv LOG=D:\cladmin\Logs\DuplicateSD.f
    [Command file block]
    RUN{
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    DUPLICATE TARGET DATABASE TO DATABASENAME
    NOFILENAMECHECK;
    Edited by: user522620 on Jun 27, 2011 6:36 PM

  • RMAN duplicate Database

    Hi ALL,
    While doing duplicate database using RMAN i m getting following error.
    released channel: d1
    RMAN-00571: =================================
    RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ======
    RMAN-00571: =======================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2008 08:08:23
    RMAN-03015: error occurred in stored script Memory Script
    ORA-06550: line 1, column 1730:
    PLS-00302: component 'LOGTERMINAL_OBJ' must be declared
    ORA-06550: line 1, column 1716:
    PL/SQL: Statement ignored
    Recovery Manager complete.
    Please Help
    Regards
    Mital

    thanks Werner for reply ,
    the above problem is solved, the proble was that you have said. the problem was realted to version . the target db was of 10.2.0.3 and the rman aux db is at 10.2.0.4
    i have changed auxiliary db to 10.2.0.3 and the problem is resolved.
    but now i am facing some diff. error.
    setup:
    backup server :\\bkpsvr\backup$\
    backup location : \\bkpsvr\backup$\
    target server \\tgt_svr
    auxiliary server :\\aux_svr\ :
    restore location : G:\ORACLE\ORADATA\ERPBI2DV\
    during duplicate db commad while reading from backup piece it is givnig following error.
    ORA-19870: error reading backup piece \\BRNORA10\BACKUP$\BI2\DF_ERPBI2_654625830_4599_1
    ORA-19504: failed to create file "G:\ORACLE\ORADATA\ERPBI2DV\OWB_ERPBI2DV_01"
    ORA-27040: file create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    released channel: d1
    RMAN-00571: ==============================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ======================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2008 12:39:14
    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 100 found to restore
    RMAN-06023: no backup or copy of datafile 99 found to restore
    please help.
    Message was edited by:
    mits

  • RMAN duplicate database suddenly slow

    Hi Everyone,
    I posted at wrong forum last time, sorry about that.
    I used RMAN to duplicate database to different box in the same local network area. Here are the scenario:
    boxA: target database (PROD) -- 250G
    database:Oracle 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    OS:Windows Server 2003 Enterprise x64 Edition
    boxB: cloned database
    database:Oracle 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    OS:Windows Server 2003 Enterprise x64 Edition
    After prepared necessary steps,listener and tnsnames,etc, I run the following scripts:
    C:\>rman target sys/[email protected] auxiliary sys/[email protected] catalog rman/rman
    RMAN>RUN
    SET NEWNAME FOR DATAFILE 1 TO 'D:\oracle\undb\system01.dbf';
    .... (some set newname omitted here)
    SET NEWNAME FOR DATAFILE 15 TO 'D:\oracle\undb\RMAN01.ORA';
    SET NEWNAME FOR TEMPFILE 1 TO 'D:\oracle\undb\TEMP01.ORA';
    # to manually allocate three auxiliary channels for disk issue
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK;
    DUPLICATE TARGET DATABASE TO undb
    LOGFILE
    GROUP 1 ('D:\oracle\undb\redo01.log') SIZE 100M REUSE,
    GROUP 2 ('D:\oracle\undb\redo02.log') SIZE 100M REUSE,
    GROUP 3 ('D:\oracle\undb\redo03.log') SIZE 100M REUSE;
    database duplicated successfully last week.
    Monday, I created another database in boxA (testdb) and used the similiar scripts (just made necessary changed, database name,file names,etc), and the duplication also successful.
    Yesterday, I tried to duplicate PROD, did the exactly same thing as Monday,
    everything was very slow,
    RMAN>report schema; took over 30 minutes,
    RMAN>list backup;took another 30 minutes,
    then I delete testdb in boxA, nothing better.
    I have tried from boxA, also tried from boxB, things were similiar.
    (when test from boxB, I input: rman target sys/[email protected] auxiliary sys/[email protected] catalog rman/[email protected] )
    when I input:
    RMAN> report schema;
    and checked from Enterprise Manager,
    SELECT RECID , STAMP , THREAD# , SEQUENCE# , FIRST_CHANGE# LOW_SCN , FIRST_TIME LOW_TIME , NEXT_CHANGE# NEXT_SCN ,
    RESETLOGS_CHANGE# , RESETLOGS_TIME FROM V$LOG_HISTORY WHERE RECID BETWEEN :1 AND :1 AND RESETLOGS_TIME IS NOT NULL
    AND STAMP >= :1 ORDER BY RECID
    the query is running for a long time, my V$LOG_HISTORY has 18688 rows, select count(*) from V$LOG_HISTORY took less than 1 second.
    I am wondering what is the reason?
    Can anybody give me a clue?
    Thank you very much.

    Thanks Alan,
    Hardware spec:
    duplicate database server CPU: 2x1995 Mhz ,RAM:4G, hard disk 500G
    production server CPU: 2x2993 Mhz ,RAM:5G,hard disk 900G
    the production server is better than the duplicate server. the production only run Oracle 10g server, the duplicate server is brand new and nothing is runing except Windows and Oracle software only.
    I noticed that when in peek hour, RMAN is really slow, no matter which box I run the RMAN, when in non peek hour, it's reasonable.
    Is there anything I can do on the RMAN side?
    Thanks again

  • Recover database to another database -- RMAN duplicate?

    I have a situation where I want to restore our production DB on server 1 (prod1) to test DB on server 2 (test1) to a paticular point in time. I have rman catalog and backup of production database. DB versions our both 10.2..0.3.
    I have been attemtping the following
    rman target sys@prod1 catalog rman@catalog
    connect auxiliary sys@test1
    run{
    set until time "to_date('07-05-2007 07:00', 'DD-MM-YYYY HH24:MI')";
    duplicate target database to test1;
    This fails with RMAN aboritng and then a bunch of RMAN-05001 errors saying that auxiliary filename XXXX conflicts with a file used by the target database...
    I am confused why does it care what the target DB files are or that there is a conflict when it should be restoring to the auxiliary database (test1)? I want to restore my target DB (prod1) to my auxiliary DB (test1)... What am I doing wrong?
    Is there a better way to attempt to use a backup from yesterday to restore into another (non-production) DB? Is the approach I am using correct or workable, and I am just missing something?
    Thanks

    There are a couple of work around for this, the Oracle document has this fully covered.
    13 Creating and Updating Duplicate Databases with RMAN

Maybe you are looking for

  • Iphone 4 keeps telling me it needs to be restored, but says my iPhone hasn't got a sim card installed when the same one is in there as always

    my iPhone 4 said it needed to be restored, so i plugged it in but now it says there is no sim in the device, please insert one, so i thought my sim card was playing up and got a new one today, but turns out it still says the same thing..

  • My iTunes for windows no longer automatically syncs my iPhone when started

    I used to be able to do a daily backup of my iPhone by simply plugging into my computer.  iTunes would automatically start and do the sync.  That suddenly stopped under version 10.6.0.40.  The iPhone is recognized and I can manually sync it, just not

  • Charting a range of numbers

    Hi, I'm hoping for some help with a chart. I want to chart medical test results, showing the normal range, and also the patient's results. For instance, the normal levels of taurine run from 150 to 550. The patient tests low at 65. I would like to ha

  • Vendor Standard Letters - F.66

    Hi Is there a way that I can send the Vendor Standard Letters (Transaction F.66) via fax or email. At the moment we can only print these letters to the local printer. Thanx in advance. Regards, Utian Goliath

  • Jdk1.4 with JBOSS

    Dear Friends I develop one application in which i use servlet/jsp . I develop my application on JBoss-Tomcat and Mysql combination . My application run perfectly on JDK1.3 . Last night i install jdk1.4 and Start my jboss server . i got following erro