RMAN Duplicate

Similar Questions

• 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

• 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

• 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

• db RMAN duplicates problem

  Hi all
  
  10gr2p4 on solaris 10
  
  
  Am in the treatment of the creation of a database with rman duplicate... When restore get the error below:
  
  
  ORA-19504: cannot create the file ' / medtx/data/data/tbss_data01.dbf '.
  ORA-27040: create file error, cannot create the file
  SVR4 error: 2: no such file or directory
  
  
  
  DB_FILE_NAME_CONVERT=(/oracle/u01/medt/,/medtx/data/,/oracle/u02/medt/,/medtx/data/,/oracle/u03/medt/,/medtx/data/,/oracle/u04/medt/,/medtx/data/,/oracle/u05/medt/,/medtx/data/,/oracle/u06/medt/,/medtx/data/)
  
  No idea what I'm missing?
  
  
  Kai

  / Medtx/data/data/really exist and has the appropriate permissions?

  publish the evidence via CUT & PASTE

  ls-la/medtx/data/data /.

• 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.

• RMAN duplicate grave crashes when I'm trying to change the paths of the destination

  Hello community,

  I am trying to duplicate a database of PROD for a test environment using the basic backup technique. I test the script in double and everything works fine when the paths of the database "auxiliary" (the database that I am creating) have the same paths as the basis of the 'target' (the database of production). If I change the paths, the double has failed because it does not find a backup of controlfile:

  channel ch1: from the restore backup set data file

  channel ch1: restore the control file

  channel ch1: reading of the backup piece PROD_cf_c-2175092736-20151204-0 c

  channel ch1: ORA-19870: error when restoring backup piece PROD_cf_c-2175092736-20151204-0 c

  «"ORA-19507: failed to retrieve the sequential file, handle ="PROD_cf_c-2175092736-20151204-0 c", parms ="»

  ORA-27029: skgfrtrv: sbtrestore returned error

  ORA-19511: error received from layer media manager, error text:

  < PROD_cf_c-2175092736-20151204-0 c > backup file not found in the NetBackup catalog

  This is the script that works, but if I have the same structure of directories in PROD and TEST (but this isn't a real scenario):

  run

  {

  allocate auxiliary channel ch1 device type sbt;

  Send "NB_ORA_CLIENT = xxx NB_ORA_POLICY = xxx, NB_ORA_SCHED = Full_Diario';"

  duplicate database for TEST PROD

  until 'sysdate-2/24.

  NOFILENAMECHECK;

  output channel ch1.

  }

  
  

  And this is the script that it does not work because I have the PROD and TEST different directory structure
  

  run

  {

  allocate auxiliary channel ch1 device type sbt;

  Send "NB_ORA_CLIENT = xxx NB_ORA_POLICY = xxx, NB_ORA_SCHED = Full_Diario';"

  duplicate database for TEST PROD

  until 'sysdate-2/24.

  SPFile

  control_files value ' / TEST/orabd1/ctl/control_PROD_01.ctl','/TEST/oralog1/ctl/control_PROD_02.ctl','/TEST/oralog2/ctl/control_PROD_03.ctl '

  db_file_name_convert value "/ PROD /", "/ TEST / '.

  the value log_file_name_convert "/ PROD /", "/ TEST / '.

  core_dump_dest value "/ TEST/oralog1/cdump".

  the value 'TEST' db_name

  Set diagnostic_dest ' /TEST/oralog2'

  instance_name must bring 'TEST'.

  all local_listener 'LISTENER_TEST '.

  Set log_archive_dest_1 ' LOCATION = / TEST/arch.

  the value of log_archive_dest_2 'LOCATION = NULL'

  ;

  output channel ch1.

  }
  
  

  I tried to restore a Netbackup file and it works. I try to duplicate a database when the structures of directories are identical and it works. Why it's a failure when I change the destination paths?

  Thank you!

  Marina.

  Hello

  We had a similar problem in our shop. In our case, that we never knew if she was related to Oracle or NetBackup, but we found a Bug of Oracle, so we think it was a problem with the Oracle.

  Bug 11783792  RMAN SEND command does not hold the value of the variable

  DOC - ID 11783792.8

  
  

  Rather than send 'NB_ORA_CLIENT = DCLI, NB_ORA_POLICY is BD_DC_2, NB_ORA_SCHED = Full_Diario';.

  try something like this:

  Run {}

  allocate channels ch01 type 'sbt_tape' PARMS 'ENV =(NB_ORA_CLIENT=DCLI) ";

  Send "NB_ORA_SERV =';"

  Restore settings

  output channel ch01.

  }

  Let me know if it helps.

  Kind regards

  Ferran

• RMAN duplicate for standby the active database and the missing data files

  We have a car of 2 node ASM 11 GR 2 and 11.1 of database and a standby with ASM also. Our database is relatively low (300 GB)

  and in one recent event the day before was such a departure from the primary that we decided to "repopulate" the data using duplicate RMAN.

  I deleted the data files of the previous day and followed the Oracle documentation to duplicate a database. In the waiting

  I created a static listener and a pfile containing only the essential information (db_unique_name). I started the day before with nomount using the 'empty' pfile.

  I run RMAN, connected to the target and ancillary catalogues and run this command:

  run {
  allocate channel prmy1 type disk;
  allocate channel prmy2 type disk;
  allocate channel prmy3 type disk;
  allocate channel prmy4 type disk;
  allocate channel prmy5 type disk;
  allocate auxiliary channel stby1 type disk;
  duplicate target database for standby from active database nofilenamecheck;
  }
  

  RMAN duplication completed without errors, so I started the rescue database and got

  an error saying that datafile XXX is missing. I checked XXX datafile at the primary level

  and it is in a DISCONNECTED state. In the standby database the same data file is in the online state.

  So I think the problem is that during the duplication, RMAN (as documentation States) does not work

  Copy the files of data in offline mode, but the standby control file seem to think that these data files

  are online and should be present.

  Can someone please help me solve this problem? From my understanding, I could just copy the missing persons

  data files (there are many however) and in the standby go offline, but I don't think it's

  the right solution, edit this file for control of the standby? I would add another option

  in the RMAN script?

  Take the data file in offline mode on the site of the previous day.

  I don't think that two COPIES try to manage separately offline files.

  Hemant K Collette

• RMAN Duplicate - ORA-01092: ORACLE terminated instance. Disconnection forced

  Source DB - 11.2.0.2.0

  Target DB - 11.2.0.2.0

  OS - SunOS 5.11

  Hello guys I'm trying to restore a database by using a duplicate order. Here are the scripts that I use.

  This is the script in which the restore.cmd is called.

  -----------------------------restore.sh--------------------------------------------------------------

  #! / usr/bin/ksh

  #PATH $PATH = "" / usr/ccs/bin: / usr/bin: / usr/sbin: / usr/sbin/nsr: / usr/ucb: / usr/ucb: / etc: / usr/local/bin ""

  #LD_LIBRARY_PATH = / usr/openwin/lib: / usr/ccs/lib

  #export PATH LD_LIBRARY_PATH

  GET_DATE = 'date "+ %y %d hour %M %s %m" '

  CHK_DATE = "date"+ %y %m %d"'"

  GET_YEAR = "date" + %y' "

  GET_DAY = "date"+ %d"'"

  Etiquettemois = "date"+ %p"'"

  GET_MONTH = "date" + %m' "

  ORAENV_ASK = NO

  #. / usr/local/bin/oraenv

  . $HOME/.profile

  echo ${ORACLE_SID}

  ################################################################################################################

  echo $ORACLE_HOME $DB_NAME $ORACLE_BASE

  Export ORACLE_HOME, ORACLE_BASE DB_NAME

  EXPHOME = / export/home/oracle

  CLN_Home = / export/home/oracle

  job_log_file = "${EXPHOME}" / rman_restore.log ' "

  Add $(ORACLE_HOME) / bin/rman trace = / export/home/oracle/monsuivi msglog ${EXPHOME} / rman_restore_msg_log.log < <!

  auxiliary connection.

  Set the dbid = 5798365608

  echo setting

  @${CLN_Home} / restore.cmd

  output

  !

  Shortly after the spfile is restore, I get the following error.

  DOUBLE RMAN ERROR-

  connected to the auxiliary database (not started)

  Oracle instance started

  Total System Global Area 8554127360 bytes

  Bytes of size 2175440 fixed

  5117054512 variable size bytes

  3170893824 of database buffers bytes

  Redo buffers 264003584 bytes

  Call krmmmai krmmpem

  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 Db in dual at 27/12/2013 12:18:10

  RMAN-05501: abandonment of duplicate target database

  RMAN-03015: an error has occurred in the script stored memory Script

  ORA-03113: end of file on communication channel

  -TRYING to solve the error-

  When I checked google, said some, it could be undo tablespace issue, so I put the undo_tablespace parameter in the same as source target. Here again, I was getting the same error.

  The source database has not being upgraded, if this isn't a problem with the upgrade.

  can give any output as to how this problem can be solved?

  Thank you

  First: DUPLICATE is NOT restore!

  Second: If a database hits ORA-1092.

  There will be errors in the alerts log.

  Before even this announcement, you should examine the error online and browsed the alert.

  Troubleshooting is any dumping using ctrl-c/ctrl-v and sitting with your shoes on your desk and your hands behind your head to whistle and wait for replies to come.

  -----------

  Sybrand Bakker

  Senior Oracle DBA