db RMAN duplicates problem

Similar Questions

• RMAN duplicate problem ORA-01547, different, different sid of the box

  Hello!
  
  We have used for a long time in DOUBLES for the daily backup/restore checking our PROD instance on another instance (sid different - different from the box). Our RMAN backup is on daily basis and full (not increment).
  
  Backup starts every day at 02:00 and ends approximately 04:10. Naturally, we use the (CATDB) catalog database on the other server.
  
  We use for version 7.2 archiving system Legato. All databases (10.2.0.2) are on Linux RH EE 4.5 64bits. Catalog db (CATDB) is on XE 2.0 (free version) on Linux RH EE 4.5 32-bit.
  
  Statistics are based on the weekly level on CATDB and PROD (target) according to all books...
  
  All eyes by the book...
  
  For a long time, we have not had any more problems (duplicate sometimes failed, but we thought that no need to worry about 'some' problems). But recently we had more fruitless duplicates in a short period of time.
  
  In the file is a log of these unsuccessful duplicates:
  http://rapidshare.com/files/181623335/duplicate_problem.txt.html
  
  All the time it looks like when recover part should be given, there is no log archived in backup file!
  
  If I try immediately after restore archive only logs:

  RUN {
  
    allocate channel t1 type 'SBT_TAPE';
  
    send 'NSR_ENV=(NSR_SERVER=zzz.hypohr,NSR_CLIENT=xxy)';
  
    SET ARCHIVELOG DESTINATION TO '/u01/lun0/dolly/arch';
  
    RESTORE ARCHIVELOG TIME BETWEEN "TO_DATE('2008-01-09 02:00:00','yyyy-mm-dd hh24:mi:ss')" AND "TO_DATE('2008-01-09 04:40:00','yyyy-mm-dd hh24:mi:ss')";
  
    release channel t1;
  
  }

  I get all archive logs required to manually restore the database (recover using backup controlfile before...).
  
  I was validating backup and perfect look... (you sent the newspaper).
  
  I was researching the problem and find out who is really some errors reported in our catalog database (Journal of the auxiliary looks OK as well target instance alerts).
  
  In RMAN. ISR table I get records that had problems. Attached paper is based on the following sql:

  SELECT 
  
     ROWID, R.RSR_KEY, R.DBINC_KEY, R.RSR_RECID, 
  
     R.RSR_STAMP, R.RSR_PKEY, R.RSR_L0KEY, 
  
     R.RSR_LEVEL, R.RSR_TYPE, R.RSR_OPER, 
  
     R.RSR_CMDID, R.RSR_STATUS, R.RSR_MBYTES, 
  
     R.RSR_START, R.RSR_END, R.RSR_IBYTES, 
  
     R.RSR_OBYTES, R.RSR_OPTIMIZED, R.RSR_OTYPE, 
  
     R.RSR_SRECID, R.RSR_SSTAMP, R.RSR_ODEVTYPE
  
  FROM RMAN.RSR R
  
  Where
  
  RSR_OPER = 'RMAN'
  
   AND RSR_STATUS like '%ERROR%'

  http://rapidshare.com/files/181625271/RMAN_rsr_errors.txt.html
  
  I tried to reproduce by hand (restore files of data through RMAN restore RMAN archived logs, recover by sqlplus) works just like a charm!
  
  Is there a way someone tell me where to start digging to find out why some duplicates completed with errors.
  
  THX

  The log shows duplicate process begins @ 10:19, newspapers from 04:02-10:02 "expected" so on the tape.

  I think that the errors that appear in the newspaper had to be addressed. Something seems to start running at 04:50 & 09:20 and it produces errors?

• RMAN Duplicate

  Hi all
  
  I'm trying to clone the database with rman with on the same server with version 11 GR 2.
  
  I use no catalog mode.
  
  source instance 400 MB and large_pool_size haing is the target of 100 MB is also same.
  
  but it is housed at the execution of scripts from memory only. don't move.
  
  [oracle@localhost ~] $ rman auxiliary.
  
  Recovery Manager: release 11.2.0.1.0 - Production on Fri Feb 22 17:59:52 2013
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  connected to the auxiliary database: ORCL (unassembled)
  
  RMAN > Connect target sys/oracle@orcl
  
  connected to target database: ORCL (DBID = 1314445644)
  
  RMAN > duplicate target database to "prod" nofilenamecheck.
  
  From February 22, 13 Db double
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_AUX_DISK_1
  channel ORA_AUX_DISK_1: SID = 10 type of device = DISK
  
  content of Script memory:
  {
  clone of SQL "create spfile from memory";
  }
  execution of Script memory
  
  SQL statement: create spfile memory
  
  content of Script memory:
  {
  clone to stop immediately;
  startup nomount clone;
  }
  execution of Script memory
  
  
  
  Please suggest to solve this problem.
  
  Thank you

  This forum is the Oracle Forms Development Forum, please ask your question in the General database discussion forum.

  Bravo!

  Published by: Tony Garabedian on February 22, 2013 15:35

• RMAN duplicate: ORA-00283, ORA-0060internal error code, arguments: [kcvhvdf

  This is related to this thread: Re: duplicated to database: ends with error: rman-06136 ora-01110
  
  I supported the newspaper of archive and continues:
  
  RMAN > overview of the database to recover
  2 >.
  
  To go back to November 16, 12
  using channel ORA_DISK_1
  using channel ORA_DISK_1
  
  Archive logs generated after that YVERT 0 not found in the repository
  Start of recovery Media SNA is 0
  Recovery must be beyond SNA 91215577536 to clear the hazy data file
  Finished recover at 16 November 12
  
  RMAN > run {}
  2 > set up what SNA 91215577536.
  3 > restore database;
  4 > sql ' alter database open resetlogs;
  {5 >};
  
  executing command: SET until clause
  
  To go back to November 16, 12
  using channel ORA_DISK_1
  
  starting media recovery
  media recovery failed
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command recover at 11/16/2012 19:45:40
  ORA-00283: cool cancelled due to errors
  RMAN-11003: failure in parsing / execution of the SQL statement: alter database reco worm if necessary
  forward this 91215577536 change using backup controlfile
  ORA-00283: cool cancelled due to errors
  [ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [], [], [], [], []]
  
  In the alerts log, the ora-00600 even raised.
  
  How to get around this problem?
  
  Thank you

  Hello;

  I agree with you. And while I have nothing to correct your error, this document is worth seeing:

  http://gavinsoorma.com/2012/04/RMAN-duplicate-database-RAC-to-RAC/

  If nothing else its useful to add to any collection of notes, you can have.

  Best regards

  mseberg

• RMAN cloning problem

  Hi gurus,
  
  I'm trying to clone the database on the same server in oracle 11 g 2 on oel 5.5.
  When I ran
  RMAN > duplicate target database to 'clone ';
  
  It runs, but after that the execution cursor blinks like that alone. the script does not end.
  
  This is the alert log database clone.
  
  Commissioning:
  Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
  With the options of partitioning, OLAP, Data Mining and Real Application Testing.
  Using parameters in Server pfile /u01/app/oracle/product/11.2.0/db_1/dbs/initclone.ora-side
  Parameters of the system with default values:
  process = 150
  memory_target = 256 M
  control_files = "/ u01/app/oracle/clone/control01.ctl".
  control_files = "/ u01/app/oracle/flash_recovery_area/clone/control02.ctl".
  db_file_name_convert = ' / u01/app/oracle/orcl.
  db_file_name_convert = ' / u01/app/oracle/clone.
  log_file_name_convert = ' / u01/app/oracle/orcl.
  log_file_name_convert = ' / u01/app/oracle/clone.
  DB_BLOCK_SIZE = 8192
  compatible = "11.2.0.0.0."
  log_archive_format = '% t_%s_%r.dbf '.
  db_recovery_file_dest = ' / u01/app/oracle/flash_recovery_area.
  db_recovery_file_dest_size = 3852M
  undo_tablespace = 'UNDOTBS1.
  Remote_login_passwordfile = "EXCLUSIVE."
  db_domain = «»
  dispatchers = "(PROTOCOL=TCP) (SERVICE = cloneXDB)" "
  audit_file_dest = ' / u01/app/oracle/admin/clone/adump.
  AUDIT_TRAIL = 'DB '.
  db_name = 'clone '.
  open_cursors = 300
  diagnostic_dest = ' / u01/app/oracle '.
  Wed Dec 07 04:21:43 2011
  PMON started with pid = 2, OS id = 6533
  Wed Dec 07 04:21:43 2011
  VKTM started with pid = 3, OS id = 6535 high priority
  VKTM clocked at (10) precision of milliseconds with DBRM quantum (100) ms
  Wed Dec 07 04:21:43 2011
  GEN0 started with pid = 4, OS id = 6539
  Wed Dec 07 04:21:43 2011
  DIAG started with pid = 5, OS id = 6541
  Wed Dec 07 04:21:43 2011
  DBRM started with pid = 6, OS id = 6543
  Wed Dec 07 04:21:43 2011
  PSP0 started with pid = 7, OS id = 6545
  Wed Dec 07 04:21:43 2011
  DIA0 started with pid = 8, OS id = 6547
  Wed Dec 07 04:21:43 2011
  MA started with pid = 9, OS id = 6549
  Wed Dec 07 04:21:43 2011
  DBW0 started with pid = 10, OS id = 6551
  Wed Dec 07 04:21:44 2011
  LGWR started with pid = 11, OS id = 6553
  Wed Dec 07 04:21:44 2011
  CKPT started with pid = 12, OS id = 6555
  Wed Dec 07 04:21:44 2011
  SMON started with pid = 13, OS id = 6557
  Wed Dec 07 04:21:44 2011
  RECCE has started with pid = 14, OS id = 6559
  Wed Dec 07 04:21:44 2011
  MMON started with pid = 15, OS id = 6561
  Wed Dec 07 04:21:44 2011
  MMNL started with pid = 16, OS id = 6563
  commissioning 1 dispatcher (s) for '(ADDRESS =(PARTIAL=YES) (PROTOCOL = TCP))' network address...
  commissioning or shared server 1...
  Environment ORACLE_BASE = / u01/app/oracle
  Wed Dec 07 04:23:50 2011
  Closure of proceedings (immediate)
  Closure of proceedings: in addition to logons disabled
  Stop background MMNL process
  MMON background process stop
  The high waters = 4 license
  All dispatchers/dispatchers and shared servers stop
  Wed Dec 07 04:28:54 2011
  STOP: Active processes prevent the functioning of the stop
  
  
  
  Can you please help me solve this problem...
  
  Thank you very much...!

  899329 wrote:
  Thank you gurus, when I increased the large pool, she did it.

  Thank you very much

  Cool!!! Please close the thread as answered. :)

• RMAN Duplicate + incremental backups + upgrade to 12 c

  Hello

  IM thinking the best way migrationg and upgrading database 11.2.0.4 to 12 c with reasonable downtime.

  reasonable downtime: 30 Minutes

  Source: Solaris (Intel)

  11.2.0.4

  DB Dimensions: 800G

  Target: Linux

  12 c

  new name of the comic.

  IM thinking to use RMAN Duplicate with option NoOpen(1) (RMAN catalog is in use). Double will be for sure several of 30 minutes then think if I can combine two copies for the recovery of the archivelogs generated during replication to minimize downtime. But is it possible when I change DB_NAME?

  Thank you.

  Hello

  I guess, you may need to check once this document. 412484.1

  I'm really not sure about your source and target system

  If your source is the 'Platform_id' 20, you can enjoy all your needs in 30 minutes or less. If this isn't the case, it is difficult.

  If your platform_id is 20, you can then create physical standby for your 11.2.0.4 and get the same thing, once the database is recovered, you can convert this logic of sleep (note: your database must be validated for the logical expectation), if you convert your logical database in standby mode, then you can change the name of your database to the new name also you can upgarde to 12 c.

  After upgrade, you can still recover all changes to your primary. Once the logic ensures sync with primary then you can pass.

  If your platform_id not 20, then

  You can opt for Golden Gate...

  Thank you

• Let the RMAN to know the location of the backup during RMAN DUPLICATE item

  RDBMS Version: 11.2.0.3
  Platform: AIX 6.1
  
  I spent a few discussions lately about the creation of standby DB by using the RMAN DUPLICATE method.
  
  Taking an example from a thread by steve74 yesterday.
  
  The commands below are executed after copying the elements of hot backup of the primary DB Backup on the standby server.
  

  --- Will be running the following DUPLICATE command from standby server 
   
  export ORACLE_SID=orcldg
  SQL> startup nomount pfile='/u01/app/oracle/11.2/db_home1/dbs/initorcldg.ora'
   
   
  rman target sys/mypass@PRIMARY_TNS auxiliary / 
   
  run 
  {
       allocate channel C1 device type disk;
       allocate auxiliary channel C2 device type disk;
       duplicate target database for standby nofilenamecheck;
  }

  The auxiliary instance is just in NOMOUNT. Lets say I copied the primary DB Backup items to the
  following in the standby server location
  

  /u04/backup/RMAN

  I don't see all the above commands which allows to RMAN knows about this place where are stored the backup pieces. For regular DB cloning, we are cataloging of backup items using the CATALOG command. But, you need a control file to do cataloging. The auxiliary instance does still not have control file. So, how this work?

  Hello

  simple. duplicate is a faster and simpler, method because you issue a command.
  After configuration, you issue a command, and if the pfile/spfile is properly configured, RMAN takes care of ALL the necessary measures, even for ASM (assuming the switch of data file also). It restores the CF, he set up the db, it restores, it retrieves, it updates the CF with the correct names, it converts file names if necessary, open the DB ETC.
  And, since only a single command is used, it is less prone to errors.
  And allows you to save a lot of trouble.
  Quite simply, you have a few details such as the location of the backuppieces.

  It works very well also for DEV env refreshes (with a few modifications on the pfile/spfile file).

  BR,
  jpinela.

  Published by: Pinela December 21, 2012 16:02

• Configuring the listener pending side before running the RMAN DUPLICATE

  Version: 11.2.0.3
  Platfomrm: Solaris 10
  
  We will create a DB physical standby for our primary database using RMAN Duplicate.
  
  Our primary DB details

  DB_NAME          = ADPTGMS
  DB_UNIQUE_NAME     = ADPTGMS

  Names for standby

  DB_NAME          = ADPTGMS
  DB_UNIQUE_NAME     = ADPTGMSDG

  Question1.
  Next to the day before, before I run the duplicate RMAN, I need so that it starts the empty instance in NOMOUNT State. Right? Can I configure export ORACLE_SID DB_NAME or DB_UNIQUE_NAME?
  
  Question2.
  
  
  I understand that it is a precondition not to have the listener towards the top pending side make the RMAN Duplicate (otherwise how RMAN will connect to the dummy instance in the side standy)
  Next to Eve, there is no DB turns again. But for the RMAN to connect to the Instance of a model, I configured and started a listener as shown below. Is this really?
  

  $ cat listener.ora
  # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
  # Generated by Oracle configuration tools.
  
  LISTENER_DG =
    (DESCRIPTION_LIST =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 10.80.16.179)(PORT = 1524 ))
        (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2012))
      )
    )
  $
  $
  $
  $ lsnrctl start LISTENER_DG
  
  LSNRCTL for Solaris: Version 11.2.0.3.0 - Production on 20-DEC-2012 00:14:19
  
  Copyright (c) 1991, 2011, Oracle.  All rights reserved.
  
  Starting /u01/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...
  
  TNSLSNR for Solaris: Version 11.2.0.3.0 - Production
  System parameter file is /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
  Log messages written to /u01/app/oracle/diag/tnslsnr/tigris179/listener_dg/alert/log.xml
  Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.80.16.179)(PORT=1524)))
  Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2012)))
  
  Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.80.16.179)(PORT=1524)))
  STATUS of the LISTENER
  ------------------------
  Alias                     LISTENER_DG
  Version                   TNSLSNR for Solaris: Version 11.2.0.3.0 - Production
  Start Date                20-DEC-2012 00:14:24
  Uptime                    0 days 0 hr. 0 min. 3 sec
  Trace Level               off
  Security                  ON: Local OS Authentication
  SNMP                      OFF
  Listener Parameter File   /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
  Listener Log File         /u01/app/oracle/diag/tnslsnr/tigris179/listener_dg/alert/log.xml
  Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.80.16.179)(PORT=1524)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2012)))
  The listener supports no services
  The command completed successfully

  Hello

  The link I gave in my previous post features a display of very good example:

  Primary:

  Pfile/Spfile name: initprim.ora/spfileprim.ora
  db_name=prim
  db_unique_name=prim
  

  Standby time:

  Pfile/Spfile name: initstnd.ora/spfilestnd.ora
  db_name=prim
  db_unique_name=stnd
  

  In your case:

  While adding a static entry to the listener of the day before, SID_NAME should be the DB_UNIQUE_NAME of the database pending. Also the pfile/spfile Eve must be associated with the DB_UNIQUE_NAME of the previous day.

  The pending database ORACLE_SID would be the DB_UNIQUE_NAME of the database pending. Hope that's clear!

  Kind regards
  Shivananda

• Create database pending active using the RMAN Duplicate command

  Hello guys,.
  
  I created the database before using the RMAN Duplicate command, but here I am stuck.
  
  Please help me to overcome this >
  
  RMAN > run {}
  2 > allocate channel prmy1 type disk;
  3 > allocate channel prmy2 type disk;
  4 > allocate channel prmy3 type disk;
  5 > allocate channel prmy4 type disk;
  6 > allocate auxiliary channel stby type disk;
  7 > duplicate target database for the eve of the active database
  8 > spfile
  9 > parameter_value_convert "orcl", "orclstd".
  10 > set db_unique_name = "orclstd".
  11 > set db_file_name_convert = "/ orcl / ', ' / orclstd / '.
  12 > set log_file_name_convert = "/ orcl / ', ' / orclstd / '.
  "13 > set control_files="D:\app\employee3\oradata\ORCLSTD\control01.ctl ', 'D:\app\employee3\flash_recovery_area\ORCLSTD\control02.ctl '.
  14 > set log_archive_max_processes = '5'
  15 > set fal_client = "orclstd."
  16 > set fal_server = "orcl".
  17 > set diagnostic_dest =: \app\employee3'
  18 > set db_recovery_file_dest = a: \app\employee3\flash_recovery_area'
  19 > set standby_file_management = 'AUTO '.
  "20 > set log_archive_config ='dg_config = (orcl, orclstd)"
  21 > set log_archive_dest_2 = 'service = orcl ASYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd';
  {22 >}
  
  allocated channel: prmy1
  channel prmy1: SID = 70 type device = DISK
  
  allocated channel: prmy2
  channel prmy2: SID = 135 type device = DISK
  
  allocated channel: prmy3
  channel prmy3: SID = 191 type device = DISK
  
  allocated channel: prmy4
  channel prmy4: SID = 7 type of device = DISK
  
  allocated canal: stby
  channel stby: SID = 129 type device = DISK
  
  From 7 November 12 Db double
  
  content of Script memory:
  {
  backup that copy reuse
  TargetFile "E:\app\RAJKUMAR\product\11.2.0\dbhome_1\DATABASE\PWDorcl.ORA" auxiliary format
  "D:\app\employee3\product\11gr2\DATABASE\PWDorclstd.ORA" targetfile
  ' E:\APP\RAJKUMAR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL. ORA' auxiliary format
  ' D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD. ORA';
  clone of SQL ' alter system set spfile = "D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD." ORA "«;»
  }
  execution of Script memory
  
  From backup 7 November 12
  Backup finished in 7 November 12
  
  SQL statement: alter system set spfile = "D:\APP\EMPLOYEE3\PRODUCT\11GR2\DATABASE\SPFILEORCLSTD. ORA "
  
  content of Script memory:
  {
  clone of SQL 'alter system set audit_file_dest =
  "E:\app\RAJKUMAR\admin\orclstd\adump" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set dispatchers =
  ''(Protocol=TCP) (SERVICE = orclstdXDB) "comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set db_unique_name =
  "Orclstd" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set db_file_name_convert =
  "/orcl/", "/orclstd/" comment is
  ' ' scope = spfile;
  clone of SQL 'alter system set log_file_name_convert =
  "/orcl/", "/orclstd/" comment is
  ' ' scope = spfile;
  clone of SQL 'alter system set control_files =
  "D:\app\employee3\oradata\ORCLSTD\control01.ctl", "D:\app\employee3\flash_recovery_area\ORCLSTD\control02.ctl" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set log_archive_max_processes =
  5 comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set fal_client =
  "Orclstd" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set fal_server =
  "Orcl" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set diagnostic_dest =
  "D:\app\employee3" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set db_recovery_file_dest =
  "D:\app\employee3\flash_recovery_area" comment =
  ' ' scope = spfile;
  clone of SQL 'alter system set standby_file_management =
  Comment by "AUTO" =
  ' ' scope = spfile;
  clone of SQL 'alter system set log_archive_config =
  Comment by "dg_config" (orcl, orclstd) =. =
  ' ' scope = spfile;
  clone of SQL 'alter system set log_archive_dest_2 =
  "service = orcl ASYNC = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd valid_for" comment =
  ' ' scope = spfile;
  clone to stop immediately;
  startup nomount clone;
  }
  execution of Script memory
  
  SQL statement: alter system set audit_file_dest = comment "E:\app\RAJKUMAR\admin\orclstd\adump" = "' scope = spfile
  
  SQL statement: alter system set dispatchers = ''(PROTOCOL=TCP) (SERVICE = orclstdXDB) "comment ="' scope = spfile
  
  SQL statement: alter system set db_unique_name = comment "orclstd" = "' scope = spfile
  
  SQL statement: alter system set db_file_name_convert = "/orcl/", "/orclstd/" comment = "' scope = spfile
  
  SQL statement: alter system set log_file_name_convert = "/orcl/", "/orclstd/" comment = "' scope = spfile
  
  SQL statement: alter system set control_files = "D:\app\employee3\oradata\ORCLSTD\control01.ctl", "D:\app\employee3\flash_recovery_area\ORCLSTD\control
  02.CTL "comment ="' scope = spfile
  
  SQL statement: alter system set log_archive_max_processes = 5 = comment "' scope = spfile
  
  SQL statement: alter system set fal_client = comment "orclstd" = "' scope = spfile
  
  SQL statement: alter system set fal_server = comment "orcl" = "' scope = spfile
  
  SQL statement: alter system set diagnostic_dest = comment "D:\app\employee3" = "' scope = spfile
  
  SQL statement: alter system set db_recovery_file_dest = comment "D:\app\employee3\flash_recovery_area" = "' scope = spfile
  
  SQL statement: alter system set standby_file_management = comment "AUTO" = "' scope = spfile
  
  SQL statement: alter system set log_archive_config = "dg_config = (orcl, orclstd)" comment = "' scope = spfile
  
  SQL statement: alter system set log_archive_dest_2 = "service = orcl ASYNC = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = orclstd valid_for" comment = "'s
  face = spfile
  
  Instance Oracle to close
  
  connected to the auxiliary database (not started)
  Oracle instance started
  
  Total System Global Area 1071333376 bytes
  
  Bytes of size 1375792 fixed
  528482768 variable size bytes
  Buffers data 536870912 bytes
  Redo buffers 4603904 bytes
  allocated canal: stby
  channel stby: SID = 63 type device = DISK
  
  content of Script memory:
  {
  backup current controlfile to standby auxiliary copy format ' D:\APP\EMPLOYEE3\ORADATA\ORCLSTD\CONTROL01. CTL';
  Restore clone controlfile to ' D:\APP\EMPLOYEE3\FLASH_RECOVERY_AREA\ORCLSTD\CONTROL02. CTL' of
  ' D:\APP\EMPLOYEE3\ORADATA\ORCLSTD\CONTROL01. CTL';
  }
  execution of Script memory
  
  From backup 7 November 12
  channel prmy1: from data file copy
  copy of the control file ensures
  name=E:\APP\RAJKUMAR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFORCL output file. ORA tag = RECID = 1 STAMP = 798743550 TAG20121107T171229
  channel prmy1: datafile copy complete, duration: 00:00:03
  Backup finished in 7 November 12
  
  From restoration to November 7, 12
  
  channel stby: copy of copy of control files
  Restoration finished November 7, 12
  
  content of Script memory:
  {
  SQL clone 'alter database sleep mounting database';
  }
  execution of Script memory
  
  SQL statement: alter database mount rescue
  output channel: prmy1
  output channel: prmy2
  output channel: prmy3
  output channel: prmy4
  exit canal: stby
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command duplicate Db at 07/11/2012 17:12:40
  RMAN-05501: abandonment of duplicate target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\MIGRATION_DATA01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_INDX01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_DATA01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\USERS01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\UNDOTBS01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\SYSAUX01 auxiliary file name. DBF conflict with a file used by the target database
  RMAN-05001: E:\APP\RAJKUMAR\ORADATA\ORCL\SYSTEM01 auxiliary file name. DBF conflict with a file used by the target database
  
  RMAN >
  
  Thank you
  Reverchon

  user9192565 wrote:

  11> set db_file_name_convert='/orcl/','/orclstd/'
  12> set log_file_name_convert='/orcl/','/orclstd/'
  

  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\MIGRATION_DATA01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_INDX01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\DEMO_DATA01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\USERS01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\UNDOTBS01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\SYSAUX01.DBF conflicts with a file used by the target database
  RMAN-05001: auxiliary file name E:\APP\RAJKUMAR\ORADATA\ORCL\SYSTEM01.DBF conflicts with a file used by the target database
  

  The strings that you entered in your file name conversion settings does not match where actually your data files. If the string does not match the names of files, there is no names of files to convert. Because you're on windows, how about something like this?

  set db_file_name_convert='\ORCL\','\ORCLSTD\'
  set log_file_name_convert='\ORCL\','\ORCLSTD\'
  

  Hope that helps...

  Patrik

• Why do we use RMAN DUPLICATE to cloning DB on a different server?

  DB version: 11.2.0.2, 10.2.0.5
  
  I want to create a clone of my Production DB in a test server. In the past, I have taken the backup hot of this DB production and restored and retrieved it in another server using simple RMAN commands.
  After restoring the control file, editing of the DB and catalogue items from backup on the test server, I run

  run {
  restore database ;
  recover database until time <time> ;
  alter database open resetlogs ;
  }

  In OTN, I ran into long discussions such as running
  RMAN duplicate database
  
  where they are trying to restore and recover using DOUBLE command, as shown below.

  run
   {
  duplicate target database to RBS
  nofilenamecheck
  pfile=/tmp/aux.ora;
   }
   

  They can't just use plain RMAN restore and retrieve orders I've done? What advantage have RMAN DUPLICATE on orders of Plains?

  RMAN DUPLICATE is designed to give the database clone a new name of the database and the new database identifier:

  >
  If you copy a database with the operating system instead of the command utilities DUPLICATE, then the DBID of the database copied remains identical to the original database. To register for the database of the copy in the same catalog of recovery with the original, you must change the DBID with utility DBNEWID (see the Oracle database utilities). On the other hand, the command DUPLICATE assigns the duplicate DBID different database so that it can be saved in the same catalog of recovery than the source database.

• Question about RMAN DUPLICATE command

  Oracle version: 10.2
  Operating system: Solaris 10
  
  To create a physical standby DB, I'll take full DB more backup archivelog on main site and copy it to the location of the previous day.
  I'm going to standby mode,
  

  startup nomount pfile=/path/init.ora
  rman target sys/password@primDB auxiliary /
  
  RMAN> run {
  allocate channel t1 device type disk;
  allocate auxiliary channel t2 device type disk;
  duplicate target database for standby nofilenamecheck;
  }

  1. is it true that I need to keep the full backup on the main site when you run the RMAN DUPLICATE backup server? In the affirmative. Why? We have already copied the full backup to the backup site. Right?
  
  2. why the command DORECOVER is optional?
  
  3. several archived newspapers may have been generated after that full backups have been copied to the backup site. When you run the backup site COPY command, RMAN will extract the info again newly generated primary and apply automatically in standby mode?

  Hello;

  I keep the RMAN backup on the primary until the copy is complete, so my RMAN catalog know about it. Sound cleaner this way. What magic RMAN can or can not do with it is not very important IMHO.
  Don't forget that the news of the eve doesn't have to be registered with RMAN, because it is the same database as the main. However you can use a tape with the method too, so it's probably more to do with not having to repeat the same backup if you make a mistake.

  I've never had to use a DORECOVER to a double never. Completing this task at least 30 times and I think 'optional' is not a word strong enough. According to the doc DORECOVER specifies that RMAN should recover the database after it is created. I've never had to use it. See this doc for more information:

  http://docs.Oracle.com/CD/B19306_01/backup.102/b14194/rcmsynta028.htm

  On move any what archiving log new expectations before to start the double so the news of the day before can start working immediately, without additional measures. Usually the Data Guard will begin apply immediately and have RMAN does not do anything. None of the notes has any special note for additional archives moving after starting two copies. RMAN duplicates and Data Guard apply struggling upward.

  Here are my notes on this topic: (these works on Oracle 10 or 11 of the Oracle)

  http://www.Visi.com/~mseberg/duprman2.html

  Best regards

  mseberg

  Published by: mseberg on March 17, 2012 13:07

• RMAN duplicate for standby database failed

  Hello
  I have try several times and for one reason, the auxialiary database finished just as it goes up the auxiliary instance.
  Target database in double check to stanby with the following error. Primary and auxiliary bodies
  Run 11.2.0.2 and are on the same platform of Solaris/patches. Everyone ran in that issue and solve it?
  
  RMAN target / catalog user@catalog
  startup nomount
  Run {}
  allocate auxiliary channel tp1 type sbt_tape;
  allocate auxiliary channel tp2 type sbt_tape;
  target database double standby nofilenamecheck;
  }
  :
  :
  :
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00601: fatal error in the Recovery Manager
  RMAN-03004: fatal error when executing command
  RMAN-04006: auxiliary database error: ORA-01092: ORACLE terminated instance. Disconnection forced
  RMAN-03002: failure of the command duplicate Db at the 15:28:52 01/02/2012
  RMAN-05501: abandonment of duplicate target database
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-03009: failure of switch control on channel clone_default at the 15:28:52 01/02/2012
  ORA-03113: end of file on communication channel

  You have error ORA-7445. I would ask allows you to check the MOS document that said Mseberg.

  Also, do not have the DATA01 on the standby database if your wait is a database not ASM. But you must give the path in the db_file_name_convert and log_file_name_convert on the eve pfile/spfile database

  1 question: is your watch set up database to be on ASM or not?

  See document MOS * no not guide to create physical standby on Normal file system for ASM primary with RMAN [838828.1 ID] * If your principal is on ASM and intelligence on the file system

  See document MOS * Step By Step Guide on creating physical standby with RMAN duplicate in ASM Filesystem for primary ASM [837102.1 ID] * If your primary and the day before are on ASM

  Published by: srp on February 3, 2012 03:49

• RMAN Duplicate using a username other than db name/SID

  Hello
  
  I want to duplicate a database with RMAN duplicate. However, I have 2 databases with the same name and I need to be able to specify that one to use as a target.
  
  Makes the target get specified during the rman (using the tns alias) for example connection string
  
  RMAN target sys/xxx@db1 auxiliary rman_cat/xxx@rman_cat catalog / log = rman_clone.log @duplicate_db1.rcv
  
  If so, when I run the command:
  
  DUPLICATE the TARGET DATABASE TO DB1, RMAN will assume that the DB1 is the auxiliary database as opposed to the target?

  The auxiliary database DB1 it must have the same file structure that target the database DB1? If Yes, you need "nofilenamecheck" as part of the command DUPLICATE, otherwise DUPLICATE option will fail. It is even if the target and auxiliary databases are on different hosts.

  Werner

• RMAN DUPLICATE DATABASE RESULT IN A RE - ORG

  Database Version 10.2.0.4
  
  When I perform a duplicate database RMAN is the new database completely reorganized? The new database can be any fragmentation or water marks high if the source database has done?
  
  Thank you

  The answer to your question is no duplicate RMAN does not cause a re - org, RMAN is a block of files of database level backup, RMAN duplicate is a double level of a data block. Therefore, duplicate RMAN is fundamentally a restoration of the source database, because it is in another location and an instance of the database and the database name change.

• DataGuard Setup: RMAN Duplicate active problem

  Experts,
  
  I am trying to set up a standby database single-server to a primary database RAC, using configurations of data Gaurad. In this process, I finished all the configurations, and I was about to run the RMAN script to duplicate primary DB on Standby DB.
  
  When I turn off the RMAN script, he throws under the errors:
  
  ince the backup to December 5, 11
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = instance 901 = iam1 = DISK device type
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Db in dual at 05/12/2011 15:31:42
  RMAN-05501: abandonment of duplicate target database
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 05/12/2011 15:31:42
  ORA-17629: unable to connect to the remote database server
  ORA-17627: ORA-01031: insufficient privileges
  ORA-17629: unable to connect to the remote database server
  
  
  Additional information:
  -----------------------------
  
  -Password is correctly copied the main database and the RAC rescue.
  -Capable to connect to DB primary waiting for database via sqlplus tool.
  -Telnet is conversely works very well.
  -All the pings work correctly.
  
  Please let me know if you have any suggestions. Happy to provide further information if necessary.
  
  Thank you

  Make sure that you should not use the password file that is located under /dbs. There is a folder called "database", where a password file must have been already generated at installation time. Simply copy the file to the same location on the standby node. I hope it should work now.

  Thank you
  GK