RMAN-05501: abandonment of duplicate target database

Similar Questions

• Duplicate target database - until the time?

  Dear Experts,
  
  RDBMS - 10.2.0.4
  
  I am trying to update the backup "ORCL2" using a cold of 'ORCL1', the two databases are on different servers. under the safeguard of stamp ORCL1 time is over:
  

  Finished Control File and SPFILE Autobackup at 12/27/2012 09:28:58

  I was wondering if the clone will run without any problems with command below, please share your ideas...
  

  run{
  ---channel allocation commands---
  duplicate target database to ORCL2
   until time "to_date('12/27/2012 09:28:58','mm/dd/yyyy hh24:mi:ss')";
  ---channel release commands---
  }

  Published by: DBA112 on December 28, 2012 14:10

  Hello;

  In theory, it should work.

  "DUPLICATE recovers by default until the last archived redo log generated at the time the command was executed, or until one hour set with a SET clause up to THAT."

  Source - database backup and recovery reference 10g Release 2 (10.2) part number B14194-03

  Example of doc

  DUPLICATE TARGET DATABASE TO newdb
      DB_FILE_NAME_CONVERT=('/h1/oracle/dbs/trgt/','/h2/oracle/oradata/newdb/')
      UNTIL TIME 'SYSDATE-1'  # specifies incomplete recovery
  ...
  

  Another example

  http://blog.dbauniversity.com/2012/06/RMAN-duplicate-until-time.html

  Best regards

  mseberg

• Duplicate target database failed with the newspaper missing in the CCR

  Hi all

  I'm duplicating a database of node 2 CARS to the test environment.

  I took archivelog and pending full database backup in the database. dB Dimensions 950 g.

  I restored it to test the environment but get error during recovery

  operating system: aix 7.1

  version of DB: oracle 10g

  I ran the following command to launch two copies

  RMAN > run

  2 > {}

  3 > allocate auxiliary channel ch1 type disk;

  4 > allocate auxiliary channel ch2 type disk;

  5 > allocate auxiliary channel ch3 type disk;

  6 > allocate auxiliary channel ch4 type disk;

  7 > target database duplicate testing up to THAT TIME "2013-12 - 25:10:47:00';"

  {8 >}

  and get below error

  content of Script memory:

  {

  until ' 2013-12 - 25:10:47:00 ";

  recover

  clone database

  delete archivelog

  ;

  }

  execution of Script memory

  executing command: SET until clause

  From pick up to 2013-12 - 27:18:12:49

  starting media recovery

  Oracle error:

  ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

  ORA-01194: file 1 needs a recovery more match

  ORA-01110: data file 1: '+ DATA/test/datafile/system.390.835293413 '.

  output channel: ch1

  output channel: ch2

  output channel: ch3

  output channel: ch4

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of Db in dual at 27/12/2013 18:14:10

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

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

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291696 lowscn 74780879027

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153927 lowscn 74780427224

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291691 lowscn 74763859437

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291690 lowscn 74763843501

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291689 lowscn 74762972560

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153920 lowscn 74761443419

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291688 lowscn 74758111689

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153919 lowscn 74758103358

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291687 lowscn 74758088445

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153918 lowscn 74758078214

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291686 lowscn 74758067675

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153917 lowscn 74758049415

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291685 lowscn 74758046873

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291684 lowscn 74758026214

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153916 lowscn 74757674479

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291683 lowscn 74757658342

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153915 lowscn 74757643881

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291682 lowscn 74757641006

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291681 lowscn 74757621180

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153914 lowscn 74757618464

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291680 lowscn 74757599470

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153913 lowscn 74757584128

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291679 lowscn 74757584121

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291678 lowscn 74757567231

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291677 lowscn 74757550865

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153912 lowscn 74757547289

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291676 lowscn 74757533624

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153911 lowscn 74757513739

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291675 lowscn 74757513659

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291674 lowscn 74757498265

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291673 lowscn 74757483667

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153910 lowscn 74757469005

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291672 lowscn 74757468526

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291671 lowscn 74757453293

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291670 lowscn 74757440237

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153909 lowscn 74757426220

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291669 lowscn 74757422172

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291668 lowscn 74757407202

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153908 lowscn 74757389651

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291667 lowscn 74757386560

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291666 lowscn 74757369955

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153907 lowscn 74757352175

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291665 lowscn 74757351898

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291664 lowscn 74757335274

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291663 lowscn 74757319172

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153906 lowscn 74757314019

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291662 lowscn 74756304245

  MAN-06102: no restaurant chain

  RMAN >

  RMAN >

  well let me know what command should I use to do the archivelog backup if it is not present in our existing backup, restore and recover up to what sequence and thread

  Can you restore your backup to tape archivelogs and apply them manually to the restoration of the database?

  list backup of archivelog from the logseq in the error message to check if they are available. And what type of device. You may find that they are available on the device of type TAPE (SBT) but you specified the device DISC type in the command duplicate.

  As long as you have the archivelogs need supported somewhere, you can restore it and apply then having the OPEN RESETLOGS command completed successfully

• Error in the target database duplicate for standby

  Hi all
  I had a problem trying to rebuild the database pending. This is my environment: Oracle 10g RAC with 2 node on window 2003 Server R2, 32-bit. Main database and backup are 2 RAC node that is located on a different server with the location of this material/ASM configuration and directory structures.
  Here is my scenario:
  After custody of data works, I deleted the eve of database, say sbdb, using dbca. so I recreated the Oracle service using oradim on standby node, Setup the correct file pfile and spfile from the primaries. Create the primary db backup using the following command on primary and copy the files to the backup servers:
  DEVICE TYPE DISK FORMAT 'E:\DATA_GUARD\DB_%U' DATABASE MORE ARCHIVELOG;
  BACKUP DEVICE TYPE DISK FORMAT 'E:\DATA_GUARD\CTL_%U' CURRENT CONTROLFILE TO SLEEP;
  
  After that I ran the command DUPLICATE TARGET DATABASE in standby mode STANDBY, he gave me the following errors:
  From duplicate Db 2 October 08
  using the ORA_AUX_DISK_1 channel
  
  content of Script memory:
  {
  Restore controlfile Eve clone;
  SQL clone 'alter database sleep mounting database';
  }
  execution of Script memory
  
  From restoration to 2 October 08
  
  channel ORA_AUX_DISK_1: from datafile backupset restoration
  channel ORA_AUX_DISK_1: restore the control file
  channel ORA_AUX_DISK_1: reading from the backup E:\DATA_GUARD\CTL_10JS4L22_1_1 piece
  channel ORA_AUX_DISK_1: restored the backup part 1
  piece handle = V:\BACKUP\DATA_GUARD\CTL_10JS4L22_1_1 tag = TAG20081002T104938
  channel ORA_AUX_DISK_1: restoration complete, duration: 00:00:09
  output filename=+DATA/sbdb/controlfile/current.269.667045957
  output filename=+RECOVERY/sbdb/controlfile/current.403.667045957
  Finished restore to 2 October 08
  
  SQL statement: alter database mount rescue
  output channel: ORA_AUX_DISK_1
  WARNING: DB_FILE_NAME_CONVERT gave rise to incorrect ASM names; names have been changed to diskgroup only.
  
  content of Script memory:
  {
  the value of newname for tempfile 1 to
  '+ data ';
  clone tempfile switch all;
  the value of newname for datafile 1 to
  '+ data ';
  the value of newname for datafile 2 to
  '+ data ';
  the value of newname for datafile 3 to
  '+ data ';
  the value of newname for datafile 4 to
  '+ data ';
  the value of newname for datafile 5 to
  '+ data ';
  restoration
  see readonly
  clone database
  ;
  }
  execution of Script memory
  
  executing command: SET NEWNAME
  
  Rename the temporary file 1 + data in the control file
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  executing command: SET NEWNAME
  
  From restoration to 2 October 08
  allocated channel: ORA_AUX_DISK_1
  channel ORA_AUX_DISK_1: sid = instance 176 = sbdb2 devtype = DISK
  
  creation of data fno = 1 name = file & DATA
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Db in dual at 2008-10-02 11:02:04
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-06136: the auxiliary database ORACLE error: ORA-01180: cannot create the data file 1
  ORA-01110: data file 1: '+ DATA/sbdb/datafile/system.347.666704609 '.
  
  I used the same procedure to create database pending several times before. They were all successful. This time, the only difference is that I also recreated primary db in the past and this time I do not rebuild primary db. I think that it is bound to the control file. But the message, it seems to pick the right command file for sleep. Any suggestion?
  
  Thank you very much in advance.

  Error stack

  ' RMAN-06136: ORACLE auxiliary database error: ORA-01180: cannot create the data file 1.
  "ORA-01110: data file 1:"+ DATA/sbdb/datafile/system.347.666704609 '"

  occurs, if RMAN "think" there is no backup data file. In such a case, RMAN attempts to recreate the data files and subsequently applies all necessary for these new files archivelogs created. Which is never possible for datafile 1, which still belongs to the space of SYSTEM tables. Basically, I think you're right, that there is something wrong with the controlfile used during the duplication process. Check if the controlfile maintains valid backups for the current incarnation (incarnation of list + list of backup). The next note of metalink can give more advice:

  THERE ARE AVAILABLE BUT BACKUP RESTORE FAILS WITH RMAN - 03002:ORA - 01180: CANNOT CREATE THE DATA 1 FILE
  NOTE: 727655.1

  Werner

• Duplicate target for RAC database

  Oracle Database 11g Enterprise Edition
  Red Hat Linux
  
  
  Hello
  
  I'm a RAC database cloning using the command duplicate target database. First of all, we need create an auxiliary Instance using the source RAC database init file.
  
  I see the following in the init file,
  
  Mdb1.undo_tablespace = "UNDOTBS1.
  MDB2.undo_tablespace = "UNDOTBS2".
  
  
  What should I enter in the file init auxiliary instance for these Undo tablespace? I'll put CLUSTER_DATABASE false since the duplicate database is a single instance one. Only the Source database is RAC.
  
  
  I'm cloning only SYSTEM, SYSAUX tablespace user and tablespaces Cancel two to 14 days sometime back. I'm ignoring all other storage spaces.

  You only need a cancellation single tablespace... you can also create one afterwards if you want.

• RMAN-03002: failure of duplicate Db

  I tried to reproduce the target database without connecting to the target and the catalog. Under steps have been used, but I'm getting ' RMAN-06023: "for data files

  That RMAN is able to restore controlfile from specified backup location.

  Oracle version: 11.2.0.1.0

  OS version: release of Red Hat Enterprise Linux Server 6.4 (Santiago)

  $ rman auxiliary.

  Recovery Manager: release 11.2.0.1.0 - Production on Thu Nov 20 17:29:32 2014

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

  connected to the auxiliary database: CLONEDB (unassembled)

  RMAN > duplicate target database to the location of backup clonedb ' / backup_database / ';

  From Db double-20_NOV_2014_17:46:18

  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

  Instance Oracle to close

  connected to the auxiliary database (not started)

  Oracle instance started

  Total System Global Area 154484736 bytes

  Bytes of size 2211408 fixed

  100663728 variable size bytes

  46137344 of database buffers bytes

  Redo buffers 5472256 bytes

  content of Script memory:

  {

  clone of SQL 'alter system set = db_name

  "TDB" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone of SQL 'alter system set db_unique_name =

  "CLONEDB" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone to stop immediately;

  Start clone force nomount

  Restore controlfile primary clone of ' / backup_database/backup_TDB_set33_piece1_20141120_11po3oqn_1_1.bkp ';

  change the clone database mount;

  }

  execution of Script memory

  SQL statement: change the system db_name set = comment "TDB" = "modified by RMAN duplicate" scope = spfile

  SQL statement: alter system set db_unique_name = comment "CLONEDB" = "modified by RMAN duplicate" scope = spfile

  Instance Oracle to close

  Oracle instance started

  Total System Global Area 154484736 bytes

  Bytes of size 2211408 fixed

  100663728 variable size bytes

  46137344 of database buffers bytes

  Redo buffers 5472256 bytes

  From restoration to 20_NOV_2014_17:46:27

  allocated channel: ORA_AUX_DISK_1

  channel ORA_AUX_DISK_1: SID = 18 type of device = DISK

  channel ORA_AUX_DISK_1: restore the control file

  channel ORA_AUX_DISK_1: restoration complete, duration: 00:00:01

  output file name=/oracle/oradata/clonedb/control01.ctl

  output file name=/oracle/oradata/clonedb/control02.ctl

  Finished restore at 20_NOV_2014_17:46:29

  mounted database

  output channel: ORA_AUX_DISK_1

  allocated channel: ORA_AUX_DISK_1

  channel ORA_AUX_DISK_1: SID = 18 type of device = DISK

  content of Script memory:

  {

  until the SNA 1268283.

  the value of newname for datafile 1 to

  "/ oracle/oradata/clonedb/system01.dbf";

  the value of newname for datafile 2 to

  "/ oracle/oradata/clonedb/sysaux01.dbf";

  the value of newname for datafile 3 to

  "/ oracle/oradata/clonedb/undotbs01.dbf";

  the value of newname for datafile 4 to

  "/ oracle/oradata/clonedb/users01.dbf";

  the value of newname for datafile 5 to

  "/ oracle/oradata/clonedb/example01.dbf";

  the value of newname for datafile 6 to

  "/ oracle/oradata/clonedb/work1_1.dbf";

  the value of newname for datafile 7 to

  "/ oracle/oradata/clonedb/work2_1.dbf";

  restoration

  clone database

  ;

  }

  execution of Script memory

  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

  From restoration to 20_NOV_2014_17:46:34

  using the ORA_AUX_DISK_1 channel

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of the command duplicate Db at 20/11/2014-17:46:34

  RMAN-05556: not all data files have backups can be recovered on SNA 1268283

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

  RMAN-06026: some targets not found - abandonment of restoration

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

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

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

  RMAN-06023: no backup or copy of the file 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

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  backup was performed with script below

  =======================================

  run

  {

  allocate channels c1 device type disk format'/backup_database/backup_%d_set%s_piece%p_%T_%U.bkp';

  backup of database archivelog all;

  }

  [oracle@vm backup_database] $ ls - ltr *.bkp

  -rw - r-. 1 oracle oinstall 1096220672 20 Nov 17:45 backup_TDB_set31_piece1_20141120_0vpo3oou_1_1.bkp

  -rw - r-. 1 oracle oinstall 26722304 20 Nov 17:45 backup_TDB_set32_piece1_20141120_10po3oql_1_1.bkp

  -rw - r-. 1 oracle oinstall 10158080 20 Nov 17:46 backup_TDB_set33_piece1_20141120_11po3oqn_1_1.bkp

  [oracle@vm backup_database] $

  Please help me find the problem.

  Hi all

  Problem has been resolved.

  He had no problem with the command "duplicate target database to the backup location 'clonedb' ' / backup_database / '; '

  This command will also work.

  Resolution:-at first I was using backup for cloning. This time I used 'INCREMENTAL level 0' backup and it worked.

• RMAN-04005: target database error: ORA-01031: insufficient privileges

  Try to duplicate db
  I checked the orapwd file looks ok.
  
  Oracle: tulpcorpadb03$ rman TARGET sys/***@wcmp AUXILIARY.
  
  Release of Recovery Manager: 9.2.0.8.0 - 64 bit Production
  
  Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04005: target database error:
  ORA-01031: insufficient privileges
  
  I findout, this is prod db and not allowed to bounce to change, any other solution do rman duplicate work without changing it?
  
  SQL > show parameter password
  
  VALUE OF TYPE NAME
  -----------
  Remote_login_passwordfile string NONE
  
  SQL > connect virtue sysdba;
  Connected.
  SQL > select * from v$ pwfile_users;
  
  no selected line

  The auxiliary node must always have access to the backupset.

• Firewall rules RMAN target database and RMAN catalog database

  Hi, we are on Oracle 11.2.0.4 and we just build a new environment, in which case the RMAN catalog is located on a seprate from the target database server. I'm trying to figure if the firewall between these two rules should be two-way, so that the target database and RMAN catalog database can ping each other. If bi-directional rules in place, so what's the reason for this? I understand that during RMAN backup entries are made in the RMAN catalog database, but do not know if the RMAN catalog database must always meet target db. Thank you!

  If you run the rman command on the target database server, it acts as a client to the catalog database server by connecting on sqlnet to the catalog database.

  If you run the rman command on the catalog database server, it's a sqlnet connection join the target database server.

  In both cases, rman is simply a client that connects to the two databases.

  Hemant K Collette

• RMAN-06429: TARGET database is not compatible with this version of RMAN

  He Hi,.
  How can I solve this problem. How I will modernize the Rman. My database of production details are below
  ----------------------------------------------------------------
  Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
  PL/SQL Release 10.2.0.1.0 - Production
  CORE 10.2.0.1.0 Production
  AMT for 32-bit Windows: Version 10.2.0.1.0 - Production
  NLSRTL Version 10.2.0.1.0 - Production
  
  while I'm setting up rman I get below error. Please help me.
  
  C:\Documents and Settings\vj.dcruz > target rman / catalog rman01/rman01@upp
  
  Recovery Manager: release 11.2.0.1.0 - Production Wed Sep 14 08:18:02 2011
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  Recovery Manager incompatible with the TARGET database: required 8.0.4.0 to 10.2.0.0 RMAN
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-06429: TARGET database is not compatible with this version of RMAN
  
  Rgds,
  John

  Johnvd wrote:
  Hi Hemant,

  I do the same database connection 10.2.0.0 thing and configure the rman but while connect target its saying that my Recovery Manager: version 11.2.0.1.0 - Production the sea Sep 14 09:04:59 2011

  How its happens is there anywhere that I need to change the path.

  Kind regards
  John

  John, you should use the binary RMAN that is located in the bin folder of Oracle database (IE u01/oracle/product/10.2/db1/bin). You should not use "rman which comes with Oracle 11g client".

  If you are using windows, run the following commands at the command prompt, and then copy / paste the output:

  echo % 5ORACLE_HOME
  echo %path%

  If you use unix, run the following commands in the terminal and then copy / paste the output:

  echo $ORACLE_HOME
  echo $PATH

  Concerning

  Grosbois

• Duplication duplicate a database with RMAN, different host database different withou

  Hello
  
  I want to duplicate a database with RMAN, different host, a different database without RMAN Duplicate Technic.
  
  I HOST1 with a database DB1 and
  HOST2 with a DB2 database
  
  I have a complete backup of the DB1 in host HOST2. How can I use this backup to clone the database?
  
  Thank you

  see the links: -.
  http://kamranagayev.WordPress.com/2010/03/29/RMAN-video-tutorial-series-performing-disaster-recovery-with-RMAN/ (Video Tutorial)
  http://oracleinstance.blogspot.com/2010/08/disaster-recovery-using-RMAN-demo.html
  http://gavinsoorma.com/recovery-scenarios/

• RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target

  Hello
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2009-03-31 21:59:24
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-06004: error ORACLE recovery catalog database: RMAN-20001: target not found in the recovery catalog database
  
  
  I get the above error while taking backup RMAN Level0. I am able to connect to the database of the catalogue without any problem.
  
  I already have this registry database command in RMAN prompt. Now I am able to see backup list but I don't know how that DB asking to sign up for today. Until yesterday, the backups were running fine btu today his application to enter the catalog DB.
  
  Here we manually to connect the catalogue in this way
  rman target $ /.
  RMAN > catalog connection rmanuser/password @ < globalcatalogDB >
  connected.
  
  After that if I give this command means...
  
  RMAN > backup from the list of database;
  I get the error I pasted at the earliest.
  
  Thanks in advance.

  If you do not have a catalog, you need not to save the database. Rely you only on the target database controlfile. If you use a catalog, you must save the target database, but only once. If you sometimes use a catalog - and sometimes not--the appropriate command is RESYNC (although in many cases RMAN automatically done).

  Werner

• duplicate/clone database recovery failed, but backup total available (ORA-19505, ORA-17503)

  Hello

  I'm 11 GR 2. I ran a duplicate of RMAN database ABCD01P with the simple script:

  DUPLICATE THE TARGET DATABASE TO "TESTBKP' OF THE ACTIVE DATABASE.

  It ran fine for about 3 hours and ended in failure, after all my 175 data files

  have been copied to the destination host, when you start to recover. The log shows:

  ...

  content of Script memory:

  {

  until the SNA 607608188039.

  retrieve the archivelog deletion of database clone;

  }

  ...

  destination for the restoration of the data file 00009: +DATAF/testbkp/datafile/ab11_lob.435.847475901

  aux1 channel: reading of the element of backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

  aux2 channel: from additional data file from the restore backup set

  aux2 channel: specifying datafile (s) to restore from backup set

  ...

  and then failed with:

  ORA-19870: error while restoring the backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021 piece

  ORA-19505: impossible to identify the file "+ FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021".

  ORA-17503: ksfdopn:2 could not open the file +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

  I do not understand because this file it says it could not identify or open exists and is present in my FRA...

  (this backup from an incremental backup, updated full and the first one I did on the source DB one hour before

  -INCREMENTAL LEVEL BACKUP 1 TO RETRIEVE THE COPY WITH THE TAG... DATABASE PLUS ARCHIVELOG...-)

  Any idea?

  Thank you very much...

  SEB

  Hi Seb,

  I've seen similar error reported when there is simultaneous backup running operation.

  Make sure to run twice at a time when there is no alternative transaction.

  Thank you

  Renu

• Database SID and SID of target database catalog is be

  Hello
  
  my database of catalog SID is PROD @ rmandb
  and target database is SID PROD @ test8
  
  How do I configure the tnsnames and connect to the database to record the catalog
  RMAN target sys/sys@PROD rcvcat rman/rman@PROD
  Save the database;
  
  
  Verification through tnsping on RMANDB
  tnsping PROD
  
  AMT Ping Utility for IBM/AIX RISC System/6000: Version 9.2.0.3.0 - Production on 24 February 2013 21:32:33
  
  Copyright (c) 1997 Oracle Corporation. All rights reserved.
  
  Use settings files:
  
  
  TNSNAMES adapter used to resolve the alias
  Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rmandb) (PORT = 1524)) (CONNECT_DATA = (SID = PROD)))
  OK (0 msec)
  
  
  
  1. is it necessary to have different SIDs?
  
  2. for the two database DBID is different.
  
  
  Thank you.

  981553 wrote:
  Hello

  my database of catalog SID is PROD @ rmandb
  and target database is SID PROD @ test8

  How do I configure the tnsnames and connect to the database to record the catalog
  RMAN target sys/sys@PROD rcvcat rman/rman@PROD
  Save the database;

  Verification through tnsping on RMANDB
  tnsping PROD

  AMT Ping Utility for IBM/AIX RISC System/6000: Version 9.2.0.3.0 - Production on 24 February 2013 21:32:33

  Copyright (c) 1997 Oracle Corporation. All rights reserved.

  Use settings files:

  TNSNAMES adapter used to resolve the alias
  Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rmandb) (PORT = 1524)) (CONNECT_DATA = (SID = PROD)))
  OK (0 msec)

  1. is it necessary to have different SIDs?

  2. for the two database DBID is different.

  Thank you.

  Name two different databases, the same is a very stupid thing to do. I correct that if I could. However, assuming that 'rmandb' and 'test8' are the names of two different servers, your tnsnames would look like this

  prod_rmandb =
         (DESCRIPTION =
           (ADDRESS_LIST =
             (ADDRESS = (PROTOCOL = TCP)(HOST = rmandb)(PORT = 1521))
               )
           (CONNECT_DATA =
             (SERVICE_NAME = prod)
           )
         )
  
  prod_tes8 =
         (DESCRIPTION =
           (ADDRESS_LIST =
             (ADDRESS = (PROTOCOL = TCP)(HOST = test8)(PORT = 1521))
               )
           (CONNECT_DATA =
             (SERVICE_NAME = prod)
           )
         )
  

  And your connection string would be

  rman target sys/sys@prod_test8 rcvcat rman/rman@prod_rmandb
  

• Block level of SUPPLY of RMAN catalog DB version and target DBs

  DB catalog version: 11.2.0.2.3
  Target the DBs: 11.2.0.2.3
  
  Currently our catalog DB and target DBs (15 of them) are at the same level of power supply.
  Let's apply PSU 5 (11.2.0.2.3) on some of the target DBs. should it apply PSU 5 (11.2.0.2.3) on the DB catalog first before we apply this power on the target of DBs?

  Hi TeslaMan,
  Probably, you mean that the RDBMS of the catalogue is version 11.2.0.2.3.
  If you are upgrading a CPU target databases, you may need to upgrade the catalog to an equal or higher level schema.
  Please check the version of the current catalog with the following sql schema.

  Select * from RCVER;

  Maybe you can create a catalog schema dummy with the task until RDBMS rman cli (perhaps you have tested the processor already?) and check the new version with the same sql.
  Kind regards
  Tycho

• Unable to connect to my target database

  I am trying to create a clone of my database named proddb using my backup RMNA production,
  so, when I export ORACLE_SID = proddb
  and then try to connect to my use of rman
  RMAN target /.
  
  its projection connected to database clonedb target
  
  I checked the servicxes and there is no service not named clonedb and there is no entry in my tnsnames or listner file like clonedb...

  user9038728 wrote:
  [Oracle@localhost ~] $ export ORACLE_SID = proddb
  [oracle@localhost ~] $ export ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1/

  [oracle@localhost ~] $ rman target sys/password

  Recovery Manager: release 11.2.0.1.0 - Production on Fri Jan 6 11:27:13 2012

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

  connected to target database: CLONEDB (unassembled)

  RMAN >

  This is the output that I am getting...

  Your Production/source/target database must be in an OPEN state & your new/clone/auxiliary instance must be started/no mounted State.

  You need to connect you as below

  $rman auxiliary sys/***@prod target.

  Then the target will be production, you must export the auxiliaries SIDS and test connectivity TNS at the elementary level.