Duplicate target database not working

Hi All,
I want to clone my exisitng DB to other.
I was refering the below link to do the same.
[http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm|http://web.njit.edu/info/limpid/DOC/backup.102/b14191/rcmdupdb006.htm]
OS:Solaris 10
Oracle version:10.2.0.4.0
What I did tilll now:-
1) Created a database MYDB1 in archive mode
2) Created one tablespace, user and 1 table in DB
3) Registered the MYDB1 in RMAN Db.
4)Created a Pfile from MYDB1 database and changed db value and other values of MYDB1 to MYDB2(Database name to be duplicate)
5)Created a password file
6)Startup MYDB2 in NOMOUNT stage.
7) At RMAN prompt I have done below things to but i have getting the error
rman:rman:>rman target sys/mydb1@mydb1 catalog rman/rman auxiliary sys/mydb2@mydb2
Recovery Manager: Release 10.2.0.4.0 - Production on Fri Sep 7 12:20:22 2012
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database: MYDB1 (DBID=3867673817)
connected to recovery catalog database
connected to auxiliary database: MYDB2 (not mounted)
RMAN> DUPLICATE TARGET DATABASE TO mydb2;
Starting Duplicate Db at 07-SEP-12
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=162 devtype=DISK
WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
contents of Memory Script:
   set until scn  911233;
   set newname for datafile  1 to
"+disk2";
   set newname for datafile  2 to
"+disk2";
   set newname for datafile  3 to
"+disk2";
   set newname for datafile  4 to
"+disk2";
   set newname for datafile  5 to
"+disk2";
   restore
   check readonly
   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
Starting restore at 07-SEP-12
using channel ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2012 12:21:01
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 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
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
745933  B  F  A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
745934  B  F  A DISK        07-SEP-12       1       1       NO         FULL_BACKUP
RMAN> list backup of database;
List of Backup Sets
===================
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
745933  Full    549.12M    DISK        00:01:19     07-SEP-12
        BP Key: 745935   Status: AVAILABLE  Compressed: NO  Tag: FULL_BACKUP
        Piece Name: /backup/oracle_backup/test_dir/rman_bkp/mydb1_0gnkjokf_1_1
  List of Datafiles in backup set 745933
  File LV Type Ckp SCN    Ckp Time  Name
  1       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/system.256.793120373
  2       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/undotbs1.258.793120373
  3       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/sysaux.257.793120373
  4       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/users.259.793120373
  5       Full 980599     07-SEP-12 +DISK1/mydb1/datafile/tbs_umesh.266.793207735
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup/oracle_backup/test_dir/rman_bkp/mydb1_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/software/oracle/product/10.2.0/database/dbs/snapcf_mydb1.f'; # default
RMAN> exit
Recovery Manager complete.
@rman:rman:>Please Suggest where i am going wrong..
Regards
Umesh Gupta

WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
You must check DB_FILE_NAME_CONVERT parameter on MYDB2 database
or I think you must add DB_FILE_NAME_CONVERT, LOG_FILE_NAME_CONVERT to DUPLICATE Command.
DUPLICATE TARGET DATABASE TO MYDB2
SPFILE
SET
  "DB_FILE_NAME_CONVERT"="+DATA/MYDB1/","+DATA/MYDB2"
...  Regards
Mahir M. Quluzade
www.mahir-quluzade.com

Similar Messages

  • Database Project Schema Compare Source Control to target database Not working

    I am trying to use the schema compare feature of database project / TFS.  I don't understand why it is trying to DELETE a stored procedure that exists in TFS.
    The Degenerate Dimension

    Hi MM,  
    Thanks for  your post.
    If you open this solution from a local folder(not stored in TFS), and try to compare that same file, what’s the result? We need confirm this issue relate to VS Schema Compare tool or relate to TFS Source Control first.
    http://blogs.msdn.com/b/ssdt/archive/2012/03/23/schema-compare-improvements.aspx
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

    When executing 'duplicate target database for standby from active'  the system tablespace/datafile (datafile 1)  is not cloned.  All other datafiles clone successfully.  The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    Here are the details:
    Primary is 11.2.0.2 RAC database  on an Exadata platform
    Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
    This is an ASM to ASM duplication.
    This is not unique to this database.  We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
    We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
    We even issued an explicit SET NEWNAME command but RMAN ignored it.
    We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
    We also opened up the network firewall to allow permit any,any traffic.
    We increased the max_server_processes
    and added TCP.NODELAY=yes to the sqlnet.ora file.
    There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
    checked all alert files grid, asm,  and dbhome - no abnormal messages.
    We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

    I successfully created the standby database using RMAN backup and recovery.
    I started the managed recovery.  Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
    I get the following messages in the standby alert log...
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:19:58 2013
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    Tue Nov 26 16:20:01 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:11 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:22 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:32 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    I don't see any MRP processes:
    select process,
    status,
        thread#,
        sequence#,
       block#,
      blocks
      7     from v$managed_standby;
    PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
    ARCH      CLOSING               2     154363          1        132
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    RFS       IDLE                  0          0          0          0
    RFS       IDLE                  1     145418        121          1
    RFS       IDLE                  0          0          0          0
    PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
    RFS       IDLE                  0          0          0          0
    12 rows selected.
    SQL>  SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
       THREAD#  SEQUENCE# APPLIED
             2     154356 NO
             2     154357 NO
             1     145411 NO
             2     154358 NO
             2     154360 NO
             2     154361 NO
             1     145414 NO
             1     145415 NO
             2     154362 NO
             2     154363 NO
             1     145416 NO
    11 rows selected.
    I do have the archive logs that cover sequences 154158-154257
    Crosschecked 38 objects
    Crosschecked 62 objects
    Finished implicit crosscheck backup at 26-NOV-13
    Starting implicit crosscheck copy at 26-NOV-13
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Crosschecked 2 objects
    archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
    validation succeeded for archived log
    archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
    Crosschecked 31 objects

  • 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

  • Duplicate target database for standby failing with below error

    Hello All, Need your assistance
    We are creating a physical standby database (standalone) from 2 node RAC database, OS =RHEL5 and DB =11gR2
    What we did: We took RMAN backup of primary DB along with archives and copied to standby server in same location. We have modified necessory prameters on primary as well as standby too.
    The command we used :
    RMAN>connect target sys/pwd@primary auxiliary sys/pwd@stdby
    RMAN> run {
    allocate auxiliary channel ch1 type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel ch1;
    Note we tried : duplicate target database for standby as well as duplicate target database for standby nofilenamecheck methods too....But no luck..we are getting following error.
    channel ch1: reading from backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
    channel ch1: ORA-19870: error while restoring backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
    ORA-19501: read error on file "/u01/BDB/BWFCCPRD_5fmpdvce_1_1", block number 121856 (block size=8192)
    ORA-27072: File I/O error
    Additional information: 4
    Additional information: 121856
    Additional information: 1036288
    failover to previous backup
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/20/2011 09:16:11
    RMAN-05501: aborting duplication of target database
    RMAN-05556: not all datafiles have backups that can be recovered to SCN 41855007833
    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 4 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
    could you pease help to resolve this ....?
    Note : Creating standby using RMAN 11g new feature : duplicate target database for standby from active database is not possible in our environment since the network bandwith is tooooo low, We have tried and not able to succeed because of n/w issue, So we are doing this alternate method...!!!
    Looking for your valuable advises...
    Thanks in Advance....

    Take the fresh backup and also check the space crunch. The below clink may help you
    ORA-27072: File I/O error Additional information: 2
    --neeraj
    Edited by: Vishen on Oct 20, 2011 2:14 PM

  • Duplicate target database for standby backup location.... errors out

    Hi ,
    i am getting below error while executing
    RMAN> duplicate target database for standby backup location '/rman1/perf/brmbkpdg' nofilenamecheck dorecover ;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "backup": expecting one of: "dorecover, db_file_name_convert, from, nofilenamecheck, ;, spfile"
    RMAN-01007: at line 1 column 39 file: standard input
    Can you please suggest a fix or what should be the syntax
    Thanks
    Naveen

    If it helps here are my tested commands: (Oracle 11)
    PRIMARY
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
    release channel d1;
    STANDBY
    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    My how to notes are here :
    http://www.visi.com/~mseberg/duprman.html
    Please note these were written not to create but to recover a standby, you still have to set up forced logging and the net80 in advance.
    Best Regards
    mseberg

  • Duplicate target database for standby failing ...

    hi,
    below is the message reported at the end of rman session log:
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 01:09:50
    failover to previous backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/10/2011 21:01:34
    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 3 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN>
    10.2.0.5/HPUX 11.31.
    running "duplicate target database for standby" ...
    pl. help to understand and troubleshoot..
    regards,
    X

    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 3 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    running "duplicate target database for standby" ...
    pl. help to understand and troubleshoot..refet this metalink note
    *Rman Restore Fails With 'RMAN-06023: no backup ...of datafile .. to restore' Although Backup is Available [ID 793401.1]*

  • RMAN duplicate target database error

    Hello,
    I’m trying to use RMAN ‘duplicate target from active database’ to a remote host however I’m getting a confusing error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 11/19/2009 13:47:23
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on aux13 channel at 11/19/2009 13:47:23
    ORA-19504: failed to create file "+DATA2"
    RMAN-03009: failure of backup command on aux14 channel at 11/19/2009 13:47:23
    ORA-19504: failed to create file "+DATA2"
    Here’s my script:
    connect target sys/<password>@node1;
    connect auxiliary sys/<password>@node2;
    spool log to '/u01/app/oracle/dba/duplicate111909.log'
    run
    allocate auxiliary channel aux11 device type disk;
    allocate auxiliary channel aux12 device type disk;
    allocate channel aux13 device type disk;
    allocate channel aux14 device type disk;
    duplicate target database to node2 from active database DB_FILE_NAME_CONVERT='+DATA1','+DATA2';
    release channel aux14;
    release channel aux13;
    release channel aux12;
    release channel aux11;
    spool log off;
    exit;
    Node1 uses ASM disk group DATA1 and I intend to use ASM disk group DATA2 on node2. Has anyone seen this error before? I have tried various permutations of DB_FILE_NAME_CONVERT clauses but all error with ORA-19504. On a side note I was able to use ASMCMD cp command to copy a datafile from node1 DATA1 to node 2 DATA2. Also, if I use disk group DATA1 on node 2 then the RMAN duplicate command runs successfully, it only errors when using DATA2. And yes +DATA2 is mounted on node2:
    SQL> select name, state from v$asm_diskgroup;
    NAME STATE
    DATA1 MOUNTED
    DATA2 MOUNTED
    Any and all ideas are welcome. I’m running out of things to check.
    Thanks,
    RJL

    For a duplicate you don't need to give the DB_FILE_NAME_CONVERT especially if you go from a asm to asm diskgroup.
    The place where it'll put all the files will be automatically done taking care of the init.ora file parameter db_create_file_dest, (db_create_online_log_dest_1)

  • Duplicate target database - is failed due to missing archive log

    Hi,
    "duplicate target database to " is failed due to required archive log is not found on tape.
    After mounting the right tape, how to proceed , please suggest
    ERROR:-->
    RMAN>
    connect catalog *******
    connect auxiliary /
    connect target ******
    Run {
    set until time '16-NOV-2008 23:50';
    allocate auxiliary channel t1 type 'sbt_tape' parms ....
    duplicate target database to mydb;
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 11/30/2008 10:27:00
    RMAN-03015: error occurred in stored script Memory Script
    ORA-19501: read error on file "orcl_ARCHIVES_BACKUP_0811160110_u0jvq7vt_1
    _1", blockno 1 (blocksize=512)
    ORA-27190: skgfrd: sbtread2 returned error
    ORA-19511: Error received from media manager layer, error text:
    ANS1314E (RC14) File data currently unavailable on server
    Recovery Manager complete.
    Thanks In Advance,

    This is basically not a RMAN problem,but a media management issue,which has to be addressed to the TSM staff:
    ANS1314E
    File data currently unavailable on server
    Explanation:
    The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
    Data was corrupted at the server
    Server found a read error
    File is temporarily involved in a reclaim operation at the server
    Server requested a tape volume that was marked unavailable.
    System action:
    Processing stopped.
    User response:
    Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.
    Werner

  • Duplicate target database for standby failed

    Hi,
    Im trying to uplicate target database for standby and get error message bellow :
    RMAN> DUPLICATE TARGET DATABASE
    2>   FOR STANDBY
    3>   FROM ACTIVE DATABASE
    4>   DORECOVER
    5>   SPFILE
    6>     SET db_unique_name='dgtst' COMMENT 'Is standby'
    7>     SET LOG_ARCHIVE_DEST_2='SERVICE=dgtst ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dgtst'
    8>     SET FAL_SERVER='dgtst' COMMENT 'Is primary'
    9>   NOFILENAMECHECK;
    Starting Duplicate Db at 24-FEB-12
    using target database control file instead of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/24/2012 22:51:21
    RMAN-05501: aborting duplication of target database
    RMAN-03009: failure of allocate command on ORA_AUX_SBT_TAPE_1 channel at 02/24/2012 22:51:21
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 2Please advice
    Thanks

    Hello mseberg,
    Actually you find the problem .....
    Adding the following softlink helped :
    ln -s /opt/omni/lib/libob2oracle8_64bit.so /u01/app/oracle/product/11.2.0/DG11gR2TST/lib/libobk.so
    I run the duplicate command and its look much better:
    $ rman TARGET sys/mysyspass@dgtst AUXILIARY sys/mysyspass@drtst
    Recovery Manager: Release 11.2.0.2.0 - Production on Sat Feb 25 07:43:15 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: DGTST (DBID=244743902)    <<<=== connected
    connected to auxiliary database: DGTST (not mounted)    <<<=== connected
    RMAN> DUPLICATE TARGET DATABASE
    2> FOR STANDBY
    3> FROM ACTIVE DATABASE
    4> DORECOVER
    5> SPFILE
    6> SET db_unique_name='dgtst' COMMENT 'Is standby'
    SET LOG_ARCHIVE_DEST_2='SERVICE=dgtst ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dgtst'
    7> 8> SET FAL_SERVER='dgtst' COMMENT 'Is primary'
    9> NOFILENAMECHECK;
    Starting Duplicate Db at 25-FEB-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_SBT_TAPE_1
    channel ORA_AUX_SBT_TAPE_1: SID=156 device type=SBT_TAPE
    channel ORA_AUX_SBT_TAPE_1: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
    allocated channel: ORA_AUX_SBT_TAPE_2
    channel ORA_AUX_SBT_TAPE_2: SID=189 device type=SBT_TAPE
    channel ORA_AUX_SBT_TAPE_2: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
    allocated channel: ORA_AUX_SBT_TAPE_16
    channel ORA_AUX_SBT_TAPE_16: SID=129 device type=SBT_TAPE
    channel ORA_AUX_SBT_TAPE_16: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=160 device type=DISK
    contents of Memory Script:
       backup as copy reuse
       targetfile  '/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/orapwdgtst' auxiliary format
    '/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/orapwdgtst'   targetfile
    '/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora' auxiliary format
    '/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora'   ;
       sql clone "alter system set spfile= ''/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora''";
    executing Memory Script
    Starting backup at 25-FEB-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=21 device type=DISK
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/25/2012 07:44:02
    ORA-17629: Cannot connect to the remote database server  <<<<<<====
    ORA-17627: ORA-12541: TNS:no listener                    <<<<<<====
    ORA-17629: Cannot connect to the remote database server
    continuing other job steps, job failed will not be re-run
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/25/2012 07:44:03
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/25/2012 07:44:03
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-12541: TNS:no listener
    ORA-17629: Cannot connect to the remote database serverAs you can see above rman successfully connected to the local and remote database.
    It also successfully allocated the DISK channel , but than it failed on :
    ORA-17627: ORA-12541: TNS:no listenerI cant understand why it happen:
    $ tnsping dgtst
    TNS Ping Utility for HPUX: Version 11.2.0.2.0 - Production on 25-FEB-2012 08:54:48
    Copyright (c) 1997, 2010, Oracle.  All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = hercules)(PORT = 1528))) (CONNECT_DATA = (SERVICE_NAME = dgtst)))
    OK (0 msec)
    $ tnsping drtst
    TNS Ping Utility for HPUX: Version 11.2.0.2.0 - Production on 25-FEB-2012 08:54:54
    Copyright (c) 1997, 2010, Oracle.  All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = pulse)(PORT = 1528))) (CONNECT_DATA = (SERVICE_NAME = dgtst)))
    OK (10 msec)And as you i show the rman successfully connect to both rempte and local as SYS user.

  • DUPLICATE TARGET DATABASE FOR STANDBY NOFILENAMECHECK DORECOVER;

    Hi
    Im a setting up one node physiscal standby for 2node 11.2 rac primary, what does DUPLICATE TARGET DATABASE FOR STANDBY NOFILENAMECHECK DORECOVER; do exactly?
    does it do restore controlfile for standby , restore database; recover database?
    I executed the command at about 2pm and the backup of primary was taken 1pm ( primary is on asm, i used this backup device type disk format '/u02/%U' database plus archivelog;
    backup device type disk format '/u02/%U' current controlfile for standby; )
    does this mean I will have to to restore any archivelogs that are generated after 1pm and manually copy them to standby ? or that data guard is smart enough to go and find them ?

    Hi,
    the command will duplicate the target database and create a standby database (including standby controlfile) from the backup you have taken.
    Then it will do the recovery with all archivelogs the standby system has access to.
    When you setup data guard in the next step, it will detect which archivelogs are missing and the "GAP" resolution will kick in, transferring all archivelogs missing to bring the
    standby database to the same timestamp.
    With 11.2 I would recommend to specify "from active database" additionally, since this will not restore from backup, but restore from the primary database directly via. network.
    This does not only save space, but will also recover to a more actual point (hence requiring less "GAP" resolution when you setup dataguard later).
    Regards
    Sebastian

  • Duplicate Target database to clone_db to remote host with diff dir struct

    Hi,
    Below are the steps i m trying to duplicate prod2 database to test1 db in remote host with different directory structure.
    Task 1: Create an Oracle Password File for the Auxiliary Instance(test1)
    orapwd file=/u01/app/oracle/product/10.2.0/db_1/dbs/orapwtest1 password=sys entries=10Task 2: Establish Oracle Net Connectivity to the Auxiliary Instance
    # Added to the listener.ora SID_LIST
    (SID_DESC =
          (GLOBAL_DBNAME = test1)
          (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
          (SID_NAME = test1)
    # Added to the tnsnames.ora
    TEST1 =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.10)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = test1)
    lsnrctl reloadIn Prod2 Server:
    Task 3: Create an Initialization Parameter File for the Auxiliary Instance
    cp initprod2.ora inittest1.ora
    Make changes for db_name,db_file_name_convert and log_file_name_convert
    vi inittest1.ora
         1  *.audit_file_dest='/u01/app/oracle/product/10.2.0/admin/test1/adump'
         2  *.background_dump_dest='/u01/app/oracle/product/10.2.0/admin/test1/bdump'
         3  *.compatible='10.2.0.1.0'
         4  *.control_files='/u01/app/oracle/product/10.2.0/oradata/test1/control01.ctl',
         5  '/u01/app/oracle/product/10.2.0/oradata/test1/control02.ctl','/u01/app/oracle/product/10.2.0/oradata/test1/control03.ctl'
         6  *.core_dump_dest='/u01/app/oracle/product/10.2.0/admin/test1/cdump'
         7  *.db_block_size=8192
         8  *.db_domain=''
         9  *.db_file_multiblock_read_count=16
        10  *.db_name='test1'
        11  *.dispatchers='(PROTOCOL=TCP) (SERVICE=indiaXDB)'
        12  *.job_queue_processes=10
        13  *.log_archive_dest_1='LOCATION=/u01/app/oracle/product/10.2.0/archive/test1'
        14  *.log_archive_format='%t_%s_%r.dbf'
        15  *.open_cursors=300
        16  *.pga_aggregate_target=200278016
        17  *.processes=150
        18  *.remote_login_passwordfile='EXCLUSIVE'
        19  *.sga_target=601882624
        20  *.undo_management='AUTO'
        21  *.undo_tablespace='UNDOTBS'
        22  *.user_dump_dest='/u01/app/oracle/product/10.2.0/admin/test1/udump'
        23  *.db_recovery_file_dest='/u01/app/oracle/product/10.2.0/backup/test1'
        24  *.db_recovery_file_dest_size=2147483648
        25  *.db_file_name_convert= (/u01/app/oracle/oradata/prod2/,/u01/app/oracle/product/10.2.0/oradata/test1/)
        26  *.log_file_name_convert= (/u01/app/oracle/oradata/prod2/,/u01/app/oracle/product/10.2.0/oradata/test1/)Task 4: Take RMAN Backup
    RMAN Target /
    RMAN> startup mount
    RMAN>run{
         allocate channel ch1 device type disk ;
         backup database noexclude format '/u01/app/oracle/product/10.2.0/backup/prod2/%D_RMAN_BACKUP_%U.bak';
    RMAN> exitTransfer the backupset to test1 server to location : /u01/app/oracle/product/10.2.0/backup/test1
    Transfer the pfile inittest1.ora to test1 to location : /u01/app/oracle/product/10.2.0/db_1/dbs
    In test1 Server:
    export ORACLE_SID=test1
    SQL> CONNECT AUXILIARY sys/sys@test1;
    SQL>startup force nomount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/inittest1.ora';
    RMAN> TARGET sys/password@prod2 NOCATALOG AUXILIARY /
    RMAN> catalog start with '/u01/app/oracle/product/10.2.0/backup/test1';
    RMAN> DUPLICATE TARGET DATABASE TO test1 nofilenamecheck;Can anyone please tell me
    1)Which server i need to do task2 ?
    2) Since i have transfered the RMAN datafile backupset to test1 server location , So it is fine to run DUPLICATE TARGET DATABASE TO test1 from test1 server i.e. auxiliary ?
    Edited by: 913410 on 21 Feb, 2012 9:16 AM
    Edited by: 913410 on 21 Feb, 2012 9:20 AM

    OK
    On the new server use
    NOFILENAMECHECK - to avoid an error message.
    Then in the RMAN script rename like this :
    RUN
      SET NEWNAME FOR DATAFILE 1 TO /oracle/data/file2.f; # rename df 1 as file2.f
      SET NEWNAME FOR DATAFILE 2 TO /oracle/data/file1.f; # rename df 2 as file1.f
      DUPLICATE TARGET DATABASE TO newdb;
    } Check "Using RMAN DUPLICATE With SET NEWNAME: Example" in the same document for more examples.
    I add entries to both the Listener and the tnsnames.
    I have an example of this part only here : ( By that I mean just the listener and tnsname )
    http://www.visi.com/~mseberg/standby_creation_from_active_database_using_rman.html
    The document above is for Standby ( Data Guard ), however if you change the RMAN script on the new host for your purpose its very similar.
    The INIT files shown have a few spaces near bottom to separate out the extra parameters for Data Guard.
    I have not had great luck with the file rename so my directory structure is the same.
    Best Regards
    mseberg
    Edited by: mseberg on Feb 21, 2012 12:10 PM

  • Duplicate target database from tag

    Hi guys,
    Wonder if someone has tried something like 'DUPLICATE TARGET DATABASE TO ... FROM TAG ...'?
    10.2.0.4 database, in today's duplication RMAN tried to find monthly cold backup instead of hotbackup that it usually takes. Monthly cold backup was taken after the hotbackup, and duplication starts some time after that. I know, controllfile tried to find the last backup, but after failing to find it (it is unaccessible from the host that performs duplication) it did not try to find the hotbackup (which is accessible by the new host), instead it was searching for previous monthly cold backups. This seems TAG related (these 2 backups have different tags) and I just wonder if I could explicitly set tag from which I could perform duplication, so I can avoid this happening again?
    Thanks

    user2552261 wrote:
    Hi guys,
    Wonder if someone has tried something like 'DUPLICATE TARGET DATABASE TO ... FROM TAG ...'?
    10.2.0.4 database, in today's duplication RMAN tried to find monthly cold backup instead of hotbackup that it usually takes. Monthly cold backup was taken after the hotbackup, and duplication starts some time after that. I know, controllfile tried to find the last backup, but after failing to find it (it is unaccessible from the host that performs duplication) it did not try to find the hotbackup (which is accessible by the new host), instead it was searching for previous monthly cold backups. This seems TAG related (these 2 backups have different tags) and I just wonder if I could explicitly set tag from which I could perform duplication, so I can avoid this happening again?
    ThanksYes, there's no such syntax, but in RMAN Recipes books, there's a way of how to do it
    Check this link: http://tinyurl.com/yax7k4m

  • DUPLICATE TARGET DATABASE to -

    Run RMAN script to restore database from backup made at 16-Jun but have errors:
    ============================================================================
    rman target rman/<pwd>@TARGETDB auxiliary sys/<pwd>@DUPLIKATDB catalog rman/<pwd>@CATALOGDB
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Jun 29 14:03:58 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: TARGETDB (DBID=1234567890)
    connected to recovery catalog database
    connected to auxiliary database: DUPLIKATDB (not mounted)
    RMAN> RUN
    2> { ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE 'SBT_TAPE'
    3> parms 'SBT_LIBRARY=/usr/lib/libnwora.so,ENV=(NSR_SERVER=[BACKUP_SERVER], NSR_DATA_VOLUME_POOL=ORACLE)';
    4> ALLOCATE CHANNEL aux2 DEVICE TYPE 'SBT_TAPE'
    5> parms 'SBT_LIBRARY=/usr/lib/libnwora.so,ENV=(NSR_SERVER=[BACKUP_SERVER], NSR_DATA_VOLUME_POOL=ORACLE)';
    6> SET NEWNAME FOR DATAFILE 1 TO '/DUPLIKATDB/systemDUPLIKATDB.dbf';
    7> SET NEWNAME FOR DATAFILE 2 TO '/DUPLIKATDB/undotbs01DUPLIKATDB.dbf';
    8> SET NEWNAME FOR DATAFILE 3 TO '/DUPLIKATDB/sysauxDUPLIKATDB.dbf';
    9> SET NEWNAME FOR DATAFILE 4 TO '/DUPLIKATDB/dft01DUPLIKATDB1.dbf';
    10> SET NEWNAME FOR DATAFILE 5 TO '/DUPLIKATDB/tls01DUPLIKATDB.dbf';
    11> SET NEWNAME FOR DATAFILE 6 TO '/DUPLIKATDB/userdata01DUPLIKATDB1.dbf';
    12> SET NEWNAME FOR DATAFILE 7 TO '/DUPLIKATDB/userdata01DUPLIKATDB2.dbf';
    13> SET NEWNAME FOR DATAFILE 8 TO '/DUPLIKATDB/userindex01DUPLIKATDB1.dbf';
    14> SET NEWNAME FOR DATAFILE 9 TO '/DUPLIKATDB/undotbs01DUPLIKATDB1.dbf';
    15> SET NEWNAME FOR TEMPFILE 1 TO '/DUPLIKATDB/tsw01DUPLIKATDB1.dbf';
    16> SET NEWNAME FOR TEMPFILE 2 TO '/DUPLIKATDB/tsw01DUPLIKATDB2.dbf';
    17> DUPLICATE TARGET DATABASE to DUPLIKATDB
    18> UNTIL TIME "to_date('2009-06-16 18:00:00', 'YYYY-MM-DD HH24:MI:SS')"
    19> LOGFILE
    20> GROUP 1 ('/DUPLIKATDB/oralog1DUPLIKATDB1.dbf','/DUPLIKATDB/oralog2DUPLIKATDB1.dbf') SIZE 50M REUSE,
    21> GROUP 2 ('/DUPLIKATDB/oralog1DUPLIKATDB2.dbf','/DUPLIKATDB/oralog2DUPLIKATDB2.dbf') SIZE 50M REUSE,
    22> GROUP 3 ('/DUPLIKATDB/oralog1DUPLIKATDB3.dbf','/DUPLIKATDB/oralog2DUPLIKATDB3.dbf') SIZE 50M REUSE,
    23> GROUP 4 ('/DUPLIKATDB/oralog1DUPLIKATDB4.dbf','/DUPLIKATDB/oralog2DUPLIKATDB4.dbf') SIZE 50M REUSE;
    24> RELEASE CHANNEL aux1;
    25> RELEASE CHANNEL aux2;
    26> }
    allocated channel: aux1
    channel aux1: sid=76 devtype=SBT_TAPE
    channel aux1: NMO v4.2.0.0
    allocated channel: aux2
    channel aux2: sid=46 devtype=SBT_TAPE
    channel aux2: NMO v4.2.0.0
    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 29-JUN-09
    contents of Memory Script:
    set until scn 10177305943361;
    set newname for datafile 1 to
    "/DUPLIKATDB/systemDUPLIKATDB.dbf";
    set newname for datafile 2 to
    "/DUPLIKATDB/undotbs01DUPLIKATDB.dbf";
    set newname for datafile 3 to
    "/DUPLIKATDB/sysauxDUPLIKATDB.dbf";
    set newname for datafile 4 to
    "/DUPLIKATDB/dft01DUPLIKATDB1.dbf";
    set newname for datafile 5 to
    "/DUPLIKATDB/tls01DUPLIKATDB.dbf";
    set newname for datafile 6 to
    "/DUPLIKATDB/userdata01DUPLIKATDB1.dbf";
    set newname for datafile 7 to
    "/DUPLIKATDB/userdata01DUPLIKATDB2.dbf";
    set newname for datafile 8 to
    "/DUPLIKATDB/userindex01DUPLIKATDB1.dbf";
    set newname for datafile 9 to
    "/DUPLIKATDB/undotbs01DUPLIKATDB1.dbf";
    restore
    check readonly
    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
    Starting restore at 29-JUN-09
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /DUPLIKATDB/systemDUPLIKATDB.dbf
    restoring datafile 00002 to /DUPLIKATDB/undotbs01DUPLIKATDB.dbf
    restoring datafile 00003 to /DUPLIKATDB/sysauxDUPLIKATDB.dbf
    restoring datafile 00006 to /DUPLIKATDB/userdata01DUPLIKATDB1.dbf
    restoring datafile 00008 to /DUPLIKATDB/userindex01DUPLIKATDB1.dbf
    restoring datafile 00009 to /DUPLIKATDB/undotbs01DUPLIKATDB1.dbf
    channel aux1: reading from backup piece df.TARGETDB.689628013.243.1
    ORA-19870: error reading backup piece df.TARGETDB.689628013.243.1
    ORA-19507: failed to retrieve sequential file, handle="df.TARGETDB.689628013.243.1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Could not locate the LNM save file 'df.TARGETDB.689628013.243.1' on server '[BACKUP_SERVER]'. (2:9:0)
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00004 to /DUPLIKATDB/dft01DUPLIKATDB1.dbf
    restoring datafile 00005 to /DUPLIKATDB/tls01DUPLIKATDB.dbf
    restoring datafile 00007 to /DUPLIKATDB/userdata01DUPLIKATDB2.dbf
    channel aux1: reading from backup piece df.TARGETDB.689630739.244.1
    ORA-19870: error reading backup piece df.TARGETDB.689630739.244.1
    ORA-19507: failed to retrieve sequential file, handle="df.TARGETDB.689630739.244.1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    A backup or restore session is already in progress. (100:17:0)
    failover to previous backup
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /DUPLIKATDB/systemDUPLIKATDB.dbf
    restoring datafile 00002 to /DUPLIKATDB/undotbs01DUPLIKATDB.dbf
    restoring datafile 00003 to /DUPLIKATDB/sysauxDUPLIKATDB.dbf
    restoring datafile 00006 to /DUPLIKATDB/userdata01DUPLIKATDB1.dbf
    restoring datafile 00008 to /DUPLIKATDB/userindex01DUPLIKATDB1.dbf
    restoring datafile 00009 to /DUPLIKATDB/undotbs01DUPLIKATDB1.dbf
    channel aux1: reading from backup piece df.TARGETDB.689540426.237.1
    ORA-19870: error reading backup piece df.TARGETDB.689540426.237.1
    ORA-19507: failed to retrieve sequential file, handle="df.TARGETDB.689540426.237.1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    A backup or restore session is already in progress. (100:17:0)
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00004 to /DUPLIKATDB/dft01DUPLIKATDB1.dbf
    restoring datafile 00005 to /DUPLIKATDB/tls01DUPLIKATDB.dbf
    restoring datafile 00007 to /DUPLIKATDB/userdata01DUPLIKATDB2.dbf
    channel aux1: reading from backup piece df.TARGETDB.689542473.238.1
    ============================================================================
    Have THESE errors:
    ============================================================================
    ORA-19511: Error received from media manager layer, error text:
    Could not locate the LNM save file 'df.TARGETDB.689628013.243.1' on server '[BACKUP_SERVER]'. (2:9:0)
    ORA-19511: Error received from media manager layer, error text:
    A backup or restore session is already in progress. (100:17:0)
    failover to previous backup
    ============================================================================
    Actually information about backup is do exists both at RMAN and backup server:
    ============================================================================
    RMAN> list backuppiece "df.TARGETDB.689628013.243.1";
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    205590 205583 1 1 AVAILABLE SBT_TAPE df.TARGETDB.689628013.243.1
    ============================================================================
    looked at EMC Networker documentation, this backup technology is used:
    ============================================================================
    ERROR MESAGE: Could not locate the LNM save file 'backup_piece_name' on server 'server'.
    DESCRIPTION: NMO could not locate an index record for the backup piece. The index record is probably missing.
    RESOLUTION: Enter the mminfo and nsrinfo commands to verify the status of the index record.
    ============================================================================
    index records' status is valid
    Gurus,
    can you help me on finding the issue?
    regards,
    Gabit

    metalink note 5705762.8: Bug 5705762 Duplicate may fail on RESTORE
    Workaround:
    Perform the duplicate manually as a restore to different host.
    This issue is fixed in     
    * 10.2.0.4 (Server Patch Set)
    What's your version?

  • ORA-00119,ORA-00132 during duplicate target database for standby in 11gR2

    I am running
    duplicate target database for standby from active database
    command from RMAN.
    I went thru step-by-step on how to create a standby database from the textbook i got from my Oracle Univ. 11g Data Guard course. I set up all the listener.ora and tnsnames.ora files using netmgr, but I'm getting local_listener error.
    Here's what I am running in rman:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'kyledb','kylerep'
    set db_unique_name='kylerep'
    set db_file_name_convert='/kyledb/','/kylerep/'
    set log_file_name_convert='/kyledb/','/kylerep/'
    set control_files='/oradata/kylerep/control01.ctl'
    set log_archive_max_processes='4'
    set fal_client='kylerep'
    set fal_server='kyledb'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(kyledb,kylerep)'
    set log_archive_dest_1='service=kyledb ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=kyledb'
    And here's the error i get:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/12/2010 17:33:28
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_KYLEDB'
    result of
    SQL>show parameter local_listener;
    is
    NAME TYPE VALUE
    local_listener string LISTENER_KYLEDB
    entry in my listener.ora is
    SID_LIST_KYLEDB_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = kyledb.kyledev.usms.doj.gov)
    (ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = kyledb)
    ADR_BASE_KYLEDB_LISTENER = /app/oracle
    KYLEDB_LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    and entry in tnsnames.ora file is
    KYLEREP =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledbdev.usms.doj.gov)(PORT = 7898))
    (CONNECT_DATA =
    (SERVICE_NAME = kylerep.kyledbdev.usms.doj.gov)
    KYLEDB =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = kyledb.kyledev.usms.doj.gov)
    LISTENER_KYLEDB =
    (ADDRESS = (PROTOCOL = TCP)(HOST = kyledev.usms.doj.gov)(PORT = 7898))
    Can anyone help me figure out what went wrong?
    Thanks in advance....

    I had the same problem,
    I Define TNS_ADMIN environment on script an resolve my problem.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 10/08/2010 17:21:15
    RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter LOCAL_LISTENER
    ORA-00132: syntax error or unresolved network name 'LISTENER_DESENV2'
    In my shell increase the Environment:
    ## VARIAVEIS
    export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db1
    export PATH=$ORACLE_HOME/bin:$PATH
    export TNS_ADMIN=/u01/app/oracle/product/10.2.0/asm1/network/admin
    export ORACLE_SID=$1
    ## CHAMADA RMAN
    rman target / log=/u02/backup/db$1/bkp_cold-$1.log cmdfile=/home/oracle/script/rman/cold_backup/cold_backup.rcv
    After this:
    RMAN> run{
    2> shutdown immediate;
    3> startup force mount;
    4> backup database include current controlfile tag 'BKP_COLD_FULL';
    5> alter database open;
    6> delete obsolete;
    7> }
    8>
    9>
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    Oracle instance started
    database mounted
    Total System Global Area 1073741824 bytes
    Fixed Size 2089400 bytes
    Variable Size 264244808 bytes
    Database Buffers 801112064 bytes
    Redo Buffers 6295552 bytes
    Hope this helps and sorry for my terrible English! =)

Maybe you are looking for

  • Using another number for an upgrade for a phone online

    Okay, so I'd like to use another phone number in my plan to get an upgrade online. So does anyone know if that is possible and how I could do that. Thanks.

  • How to quite my iMac's opening bell?

    Each time I turn on my iMac, the opening bell is quite loud.  Is there any way to quiet or lessen the sound?

  • Integration of JSR-168 portlet into Portal - Complete Guide

    Hi there, the CE 7.1 is described to be compatible with JSR-168 portlets. Our Company has developed a JSR-168 portlet which comes as a WAR-File which can be easily included in other application server and portals (WebShpere, Apache). But integration

  • MacBook 1.83GHz

    Can the 1.83 GHz Processor MacBook be purchased with a dvd burner rather than the standard combo drive?

  • SR-IOV Uplink Port with NIC Teaming

    Hello, I'm trying to setup my uplink port profile and logical switch with NIC Teaming and SR-IOV support. In Hyper-V this was easy, just had to create the NIC Team (which I configured as Dynamic & LACP) then check the box on the virtual switch. I'm V