Backup location during duplicate database

On my production backup is taken in the path /u01/backup.
I have copied the backup pieces to the location /u07/backup on the Auxiliary system.
But how can i tell RMAN to look for the backups in the new location.
I cant change the location of production using catalog command.
ie.., /u07 is not available on PROD and /u01 is not available on dev.
I want only the duplicate command to read the file from /u07/backup path

Hi,
You could make a link on the Auxiliary system (provided /u01/backup does not exists as a true directory).
If it not already exists create a directory /u01 with the right owner and group.
Than as the oracle user < ln -s /u07/backup /u01/backup >.
Regards,
Tycho

Similar Messages

Backup location during Duplicate db

hi,
Is it possible to change the RMAN backup Location for the Auxillary db.
ie., say on my Target the bakup location is /u03/rman/backup
and on Auxillary host i copy the backup to /u01/rman backup
How to tell RMAN to look at different destination during DUPLICATE database.
also, I am NOT using recovery catalog.

OS? Database version? On 10g and higher use 'catalog backuppiece' to move the metadata information about backups to another location.
Werner

Backup location during update iOS5?

Hello community.
What a nightmare. Trying to update iOS5, keeps internal error, can't connect server error. After every time it fails, the long torturing backup starts again. When it gets through and starts to install, error 3004 and then nothing. Restart my iphone, itunes tells me it has to restore my iphone to factory setting before anything else can be done and wipes my iphone out. My music!!!!
Does anybody know, where is that 10 minutes + backup during the iOS update is loacted in a Mac? I want to find it out and do something. Thanks!!!

OS? Database version? On 10g and higher use 'catalog backuppiece' to move the metadata information about backups to another location.
Werner

Error during duplicate database.

Hi All,
db - 9.2.0.8.0
OS - Win 2003 server
I was rying to duplicate db on the same server. Please go through the following massage.
printing stored script: Memory Script
   set until scn 14420521;
   recover
   clone database
    delete archivelog
executing script: Memory Script
Note, at this point my database was apperead to hang for long time. it was around 2 hour and then revert back with the following
executing command: SET until clause
Starting recover at 18-SEP-08
starting media recovery
archive log thread 1 sequence 7 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_7.ARC
archive log thread 1 sequence 8 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_8.ARC
archive log thread 1 sequence 9 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_9.ARC
archive log thread 1 sequence 10 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_10.ARC
archive log thread 1 sequence 11 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_11.ARC
archive log thread 1 sequence 12 is already on disk as file D:\BCKUP\ARCHIVE\ARCH_12.ARC
archive log filename=D:\BCKUP\ARCHIVE\ARCH_7.ARC thread=1 sequence=7
archive log filename=D:\BCKUP\ARCHIVE\ARCH_8.ARC thread=1 sequence=8
archive log filename=D:\BCKUP\ARCHIVE\ARCH_9.ARC thread=1 sequence=9
archive log filename=D:\BCKUP\ARCHIVE\ARCH_10.ARC thread=1 sequence=10
archive log filename=D:\BCKUP\ARCHIVE\ARCH_11.ARC thread=1 sequence=11
archive log filename=D:\BCKUP\ARCHIVE\ARCH_12.ARC thread=1 sequence=12
media recovery complete
Finished recover at 18-SEP-08
printing stored script: Memory Script
   shutdown clone;
   startup clone nomount ;
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/18/2008 20:11:45
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
hare krishna
Alok

Alok do you have user that still active at auxiliary instance ,exit from that auxilairy session after doing database in nomount and then retry the duplicate process.
Khurram

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

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

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

Problems with DUPLICATE DATABASE when datafile was added after full backup

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

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

Multiple Backup Locations for Multiple Lightroom Databases

I currently work with two lightroom databases but when I back up the databases, the backups get stored in the same Lightroom Backups folder. The two backups are stored in separate sub-folders but the actual database files have the same name. Thus, the only way to know which backup is for which database if to note the times that the backups were created and use this to determine which backup applies to which database.
It would seem like the actual backup files could be named as per the associated database or the backup location could be specified for each database so that there is less chance for a mistake if a database needs to be restored.
Thanks in advance,
Dave Mayfield

Thanks for your reply.
I need the have each LOS ( Location of sale or location of delivery) of Business Partner because we will deliver items for the LOS and not for BP.
As we also need to control (serial numbers) items & services ( field management) I also need to have the LOS as BP.
As example:
BP name AAA have 30 LOS.
BP AAA bought 2000 items.
BP AAA ask us to old theses items in warehouse.
BP AAA request to delivery a x quantity in LOS 1, 2,3,4,...
The invoice went to BP AAA, but the deliveries will be to each LOS of BP AAA.
As I said we need to have the field services working side-by-side with serials numbers and services for each LOS of our BP AAA.
So, we have subcustomers from big customer BP AAA.
Do we have any way of having all subcustomers(LOS) as BP, along with the real customer AAA?
Thanks in advance,

Steps to migrate database backup location to another disk ?

As the database is getting bigger and bigger, the existing disk for backup runs out of space.
We intend to replace it with another disk.
Just would like to seek your advice
1) Do we need to stop SQL Server when we change the backup location ? Most likely NO
2) Should we change the backup location in Database Maintenance Plan before copying BAK / TRN files across disks ?
3) Can I use the following command for copying files across disks ?
ECHO OFF
xcopy D:\Mybackup\*.* \\DestServer\D$\backup\ /S /Y /E /Q
Thanks

Have you heard about backup compression.If you have SQL server 2008 enterprise you ca take advanatge of backup compression. I have used it and works well.If you have 2008 R2 standard and enterprise both can use backup compression.
http://technet.microsoft.com/en-us/library/bb964719(v=sql.105).aspx
Below query will set backup compression for ALL backups on your system
sp_configure 'show advanced options',1
go
reconfigure
go
sp_configure 'backup compression default',1
go
reconfigure
go
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

RMAN duplicate Database

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

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

Duplicate database in 11g

Hi all,
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/17/2010 09:18:42
RMAN-03015: error occurred in stored script Memory Script
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
I have got stuck with this error, while iam trying to duplicate database using rman from active database clause, I have checked in backup location for target and the autobackups are still available.
thanks in advance.

Handle:      user12984527
Status Level:      Newbie
Registered:      Apr 15, 2010
Total Posts:      72
Total Questions:      28 (25 unresolved)
so many questions & so few answers,
when all else fails, Read The Fine Manuals
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp.htm#BRADV143

Unable to create a duplicat database through rman

Hi,
Oracle Version:10.2.0.1
Operating System:Linux
Here i am having databae KKK and i need to duplicate that databae to vtldb.I take the backup of the KKK database as
rman target /
RMAN>Backup databsase;after that i copied all the bakup sets to my vtldb database in the location '/u01/app/oracle/oradata/vtldb/'.Then i created a new auxiliary channel as
create auciliary channel as device type disk format '/u01/pp/oracle/oradata/vtldb/%U';Then connecting to my auxiliary databae and getting the following error.
[oracle@vtlsys3-143 ~]$ rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Mar 11 13:30:12 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: KKK (DBID=2526957931)
RMAN> connect aucxiliary sys@vtldb_rmandup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "auxiliary, catalog, clone, rcvcat, target"
RMAN-01008: the bad identifier was: aucxiliary
RMAN-01007: at line 1 column 9 file: standard input
RMAN> connect auxiliary sys@vtldb_rmandup
auxiliary database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04006: error from auxiliary database: ORA-01031: insufficient privilegesI create the passowrd file for VTLDB aslo .
Can any one please help me how to solve my problem.
Thanks & Regars,
Poorna Prasad.

Hi Anil,
Thanks for your replays.Now i was able to connect to the database.But i am facing another problem.
RMAN> list backup;
RMAN> backup database;
Starting backup at 11-MAR-10
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u01/app/oracle/oradata/kkk/system01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 11-MAR-10
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 03/11/2010 16:36:11
ORA-19504: failed to create file "/u02/rman_bkp/kkk/ora_rbk713378170_s"
ORA-27038: created file already exists
Additional information: 1
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378170_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/u01/app/oracle/oradata/kkk/sysaux01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/kkk/undotbs01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378186_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/app/oracle/oradata/kkk/users01.dbf
channel ORA_DISK_1: starting piece 1 at 11-MAR-10
channel ORA_DISK_1: finished piece 1 at 11-MAR-10
piece handle=/u02/rman_bkp/kkk/ora_rbk713378201_s tag=TAG20100311T163610 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 11-MAR-10
Starting Control File Autobackup at 11-MAR-10
piece handle=/u02/rman_bkp/rman_ctlbkp/ora_cfc-2526957931-20100311-03 comment=NONE
Finished Control File Autobackup at 11-MAR-10
RMAN> connect auxiliary sys@vtldb
auxiliary database Password:
connected to auxiliary database: VTLDB (not mounted)
RMAN> duplicate target database to vtldb
2> ;
Starting Duplicate Db at 11-MAR-10
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=159 devtype=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: sid=157 devtype=DISK
contents of Memory Script:
   set until scn 557331;
   set newname for datafile 1 to
"/u01/app/oracle/oradata/vtldb/system01.dbf";
   set newname for datafile 2 to
"/u01/app/oracle/oradata/vtldb/undotbs01.dbf";
   set newname for datafile 3 to
"/u01/app/oracle/oradata/vtldb/sysaux01.dbf";
   set newname for datafile 4 to
"/u01/app/oracle/oradata/vtldb/users01.dbf";
   restore
   check readonly
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 11-MAR-10
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/11/2010 17:07:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 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 restoreRegards,
Poorna Prasad.

How to restore a database from backup taken in standby database

Its our environment standard to run backup in standby database.
Now we have to perform refresh production database to UAT database.
I have performed normal refresh/duplicate. Is there any additional procedures need to be followed to perform refresh from standby database backup

RMAN Restoration to New Server with Different Directory and New Database Name
In this case, I have an existing production database with RMAN Level 0 backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\flash_recovery_area\galaxy\backupsets\autobackup\SAMSUNG-ctl_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\flash_recovery_area\galaxy\backupsets\level0\level0-%d-%T-%U' MAXPIECESIZE 4G;
DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE - 7';
SHOW ALL;
REPORT SCHEMA;
LIST BACKUP OF DATABASE;
REPORT NEED BACKUP;
REPORT UNRECOVERABLE;
LIST EXPIRED BACKUP BY FILE;
LIST ARCHIVELOG ALL;
REPORT OBSOLETE;
CROSSCHECK BACKUP DEVICE TYPE DISK;
CROSSCHECK COPY OF ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
RUN {
sql 'alter system archive log current';
BACKUP INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT;
LIST BACKUP OF DATABASE;
REPORT NEED BACKUP;
REPORT UNRECOVERABLE;
LIST EXPIRED BACKUP BY FILE;
LIST ARCHIVELOG ALL;
REPORT OBSOLETE;
CROSSCHECK BACKUP DEVICE TYPE DISK;
CROSSCHECK COPY OF ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
The backupsets will be restored into a new server with different file structure. The database will also be different. In the new server, I have created a blank database (SID or CUSTOM database with the name DBGRID). This is easier so I won't have to create any directories, user ORADIM or create new PWFile.
This document assumes that a blank (starter) database has been created in the new server. The RDBMS version is the same as the source database.
In this example, the source database name is GALAXY and the target database name is DBGRID.
Let me know if you have any feedback or comments. All I want is to share these steps with you and make it better so we can help other DBA's as well.
Steps start here
-->
ORIGINAL DATABASE: GALAXY
DUPLICATE DATABASE: DBGRID
FROM THE SOURCE DATABASE (GALAXY)
1. Backup the database using RMAN incremental backups.
2. Check the RMAN logs generated and look for the result of the command:
C:\Users\Administrator>set ORACLE_SID=GALAXY
C:\Users\Administrator>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 06:55:08 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: GALAXY (DBID=3578870300)
RMAN> report schema;
using target database control file instead of recovery catalog
Report of database schema for database with db_unique_name GALAXY
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
1    680      SYSTEM *** C:\ORACLE\ORADATA\GALAXY\SYSTEM01.DBF
2    510      SYSAUX *** C:\ORACLE\ORADATA\GALAXY\SYSAUX01.DBF
3    140      UNDOTBS1 *** C:\ORACLE\ORADATA\GALAXY\UNDOTBS01.DBF
4    5        USERS *** C:\ORACLE\ORADATA\GALAXY\USERS01.DBF
5    106      EXAMPLE *** C:\ORACLE\ORADATA\GALAXY\EXAMPLE01.DBF
6    2048     ALLINDEX *** C:\ORACLE\ORADATA\GALAXY\ALLINDEX01.DBF
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
1    29       TEMP 32767 C:\ORACLE\ORADATA\GALAXY\TEMP01.DBF
This command shows all the physical database files that will be backed-up by the current RMAN job.
List the online redolog files:
SQL> select * from v$logfile;
GROUP# STATUS TYPE    MEMBER IS_
3         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG     NO
3         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG     NO
2         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG     NO
2         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG     NO
1         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG     NO
1         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG     NO
6 rows selected.
3. Since the target server has different structure, it is easier to use a pfile to startup the database rather than restoring the spfile from backup.
C:\Users\Administrator>set ORACLE_SID=GALAXY
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 06:56:14 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> create pfile='C:\TEMP\initGALAXYrman.ora' from spfile;
File created.
4. Edit the pfile to have the following parameters:
(These parameters has been edited to fit the target database requirements)
galaxy entries has been changed to dbgrid. Directories has been corrected as well.
dbgrid.__db_cache_size=192937984
dbgrid.__java_pool_size=4194304
dbgrid.__large_pool_size=4194304
dbgrid.__oracle_base='D:\app\Administrator'#ORACLE_BASE set from environment
dbgrid.__pga_aggregate_target=281018368
dbgrid.__sga_target=524288000
dbgrid.__shared_io_pool_size=0
dbgrid.__shared_pool_size=301989888
dbgrid.__streams_pool_size=4194304
*.audit_file_dest='D:\app\Administrator\admin\DBGRID\adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='D:\oradata\DBGRID\control01.ctl','D:\oradata\DBGRID\control02.ctl'
*.db_block_size=8192
*.db_domain=''
Leave as it is for now --> *.db_name='GALAXY'
*.db_recovery_file_dest='D:\fra\backupsets\duplicate'
*.DB_RECOVERY_FILE_DEST_SIZE=4G
*.diagnostic_dest='D:\app\Administrator'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=DBGRIDXDB)'
*.job_queue_processes=1000
*.log_archive_dest_1='location=D:\fra\backupsets\archs'
*.log_buffer=10485760
*.memory_target=805306368
*.open_cursors=300
*.processes=800
*.remote_login_passwordfile='EXCLUSIVE'
*.session_cached_cursors=300
*.sessions=885
*.undo_tablespace='UNDOTBS1'
Make sure that all the directory values in this edited pfile are existing in the target server.
5. Copy all the RMAN backup pieces generated in the source database. Transfer the edited pfile as well. Make sure that all directories presented in the pfile exists in the target server.
In this example, RMAN backupsets are located at:
Backupsets:
Level0 and Level1 = D:\fra\backupsets\duplicate\level0 , D:\fra\backupsets\duplicate\level1
Controlfile and Spfile Autobackup = D:\fra\backupsets\duplicate\autobackup
Edited pfile initGALAXYrman= C:\TEMP\initDBGRIDnew.ora
FROM THE TARGET DATABASE (DBGRID)
6. Connect to RMAN and perform database duplication using RMAN backup restoration
C:\Users\Administrator>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 07:26:45 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> set dbid = 3578870300; --> THIS IS THE DBID OF THE SOURCE DATABASE!
executing command: SET DBID
RMAN> startup nomount pfile='C:\TEMP\initDBGRIDnew.ora'; -->restore the edited pfile
Oracle instance started
Total System Global Area     535662592 bytes
Fixed Size 1375792 bytes
Variable Size 327156176 bytes
Database Buffers 192937984 bytes
Redo Buffers 14192640 bytes
RMAN> restore controlfile from 'D:\fra\backupsets\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00'; -->restore the correct controlfile
Starting restore at 01-AUG-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
output file name=D:\ORADATA\DBGRID\CONTROL01.CTL
output file name=D:\ORADATA\DBGRID\CONTROL02.CTL
Finished restore at 01-AUG-12
RMAN> alter database mount; -->mount the database
database mounted
released channel: ORA_DISK_1
RMAN> catalog start with "D:\fra\backupsets\duplicate";
--> catalog the location of the backup pieces to make it known to the control file
Starting implicit crosscheck backup at 01-AUG-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 01-AUG-12
Starting implicit crosscheck copy at 01-AUG-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 01-AUG-12
searching for all files in the recovery area
cataloging files...
no files cataloged
searching for all files that match the pattern D:\fra\backupsets\duplicate
List of Files Unknown to the Database
=====================================
File Name: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_1_1
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_1_1
RMAN> list backup summary; -->check your backup they are now known
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1 B A A DISK 01-AUG-12       1       2 NO         TAG20120801T011054
2 B 0 A DISK 01-AUG-12       1       2 NO         TAG20120801T011137
3 B A A DISK 01-AUG-12       1       2 NO         TAG20120801T011405
RMAN> list archivelog all; -->list you archivelog for point in time recovery
List of Archived Log Copies for database with db_unique_name GALAXY
=====================================================================
Key Thrd Seq     S Low Time
26 1    29      A 01-AUG-12
Name: D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
Perform database restoration and recovery. The sequence number is Seq+1 for complete recovery, so that will be 29 + 1 = 30. You can also do recovery via SCN or time based recovery.
Remember in the previous step: RMAN> REPORT SCHEMA;
Each datafile has a corresponding datafile number.
Follow the format to convert them into their respective new restoration directory in the target server.
SET NEWNAME has the format:
SET NEWNAME FOR DATAFILE [FILE NUMBER IN THE REPORT SCHEMA COMMAND] TO
‘[NEW LOCATION AND FILENAME OF THE DATAFILES]’;
RMAN> run {
2> SET UNTIL SEQUENCE 30 THREAD 1;
3> set newname for datafile 1 to 'D:\oradbgrid\oradata\SYSTEM01.DBF';
4> set newname for datafile 2 to 'D:\oradbgrid\oradata\SYSAUX01.DBF';
5> set newname for datafile 3 to 'D:\oradbgrid\oradata\UNDOTBS01.DBF';
6> set newname for datafile 4 to 'D:\oradbgrid\oradata\USERS01.DBF';
7> set newname for datafile 5 to 'D:\oradbgrid\oradata\EXAMPLE01.DBF';
8> set newname for datafile 6 to 'D:\oradbgrid\oradata\ALLINDEX01.DBF';
9> restore database;
10> switch datafile all;
11> recover database;
12> }
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
Starting restore at 01-AUG-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to D:\oradbgrid\oradata\SYSTEM01.DBF
channel ORA_DISK_1: restoring datafile 00002 to D:\oradbgrid\oradata\SYSAUX01.DBF
channel ORA_DISK_1: restoring datafile 00003 to D:\oradbgrid\oradata\UNDOTBS01.DBF
channel ORA_DISK_1: restoring datafile 00004 to D:\oradbgrid\oradata\USERS01.DBF
channel ORA_DISK_1: restoring datafile 00005 to D:\oradbgrid\oradata\EXAMPLE01.DBF
channel ORA_DISK_1: restoring datafile 00006 to D:\oradbgrid\oradata\ALLINDEX01.DBF
channel ORA_DISK_1: reading from backup piece D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
channel ORA_DISK_1: piece handle=D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1 tag=TAG20120801T011137
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:06
Finished restore at 01-AUG-12
Starting recover at 01-AUG-12
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 29 is already on disk as file D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
archived log file name=D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001 thread=1 sequence=29
media recovery complete, elapsed time: 00:00:01
Finished recover at 01-AUG-12
Log in to SQL*Plus to recreate the redolog files.
Format:
ALTER DATABASE RENAME FILE ‘[OLD REDOLOG LOCATION]’ TO ‘[NEW REDOLOG LOCATION]’;
C:\Users\Administrator>sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 08:54:27 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
dbgrid MOUNTED
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03B.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02B.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01B.LOG';
Database altered.
Open the database in resetlogs option. Create spfile from the edited pfile then bounce the database.
RMAN> alter database open resetlogs;
database opened
SQL> create spfile from pfile='C:\TEMP\initDBGRIDnew.ora';
File created.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 327156176 bytes
Database Buffers 192937984 bytes
Redo Buffers 14192640 bytes
Database mounted.
Database opened.
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
dbgrid OPEN
Create a new TEMP tablespace, make this as the new default temporary tablespace. Drop the old TEMP tablespace. Restart the database.
SQL> CREATE TEMPORARY TABLESPACE TEMP01 TEMPFILE 'D:\oradbgrid\oradata\TEMP0101.dbf' SIZE 200M;
Tablespace created.
SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP01;
Database altered.
SQL> drop tablespace TEMP including contents and datafiles;
Tablespace dropped.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance sta

Duplicate database command fails with RMAN-06023

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

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

Rman duplicate database from test to production different host

Dear All,
usually i do the rman duplicate (clone) database in different host using same backup location as the source database in target database.
now i am in situation to clone the database with different backup location
source database location:/u01/db/backup
target database location: /tmp_dbbkup
is it possible to create the duplicate database with the command
rman target sys@UAT1 auxiliary /
RMAN>CATALOG BACKUPPIECE '/tmp_dbbkup/UAT_2670198561_44_20110101;
RMAN>duplicate target database to DEV;
is it ok?
we dont have privilege/rights to create a folder/directory in production server.
what i have to do now?
thanks in advance.
my oracle version: 10.2.0.4.0
operating system: AIX

tychos wrote:
Hi rajeysh,
what i have to do now?You could make a sym link on the dev server
So /u01/db/backup on the dev server points to /tmp_dbbkup
Regards,
Tychothank for your reply tychos,
$ ln -s /u01/db/backup/OUAT_2670198561_44_20110101 /oracle/db/backup/UAT_2670198561_44_20110101
$ ls -ltr
total 1475968
-rw-r----- 1 oracle dba 307654656 Jan 7 10:03 db_DEV_20110107_4em1gm3e_1_1_L0
-rw-r----- 1 oracle dba 448030720 Jan 7 10:03 db_DEV_20110107_4dm1gm3e_1_1_L0
lrwxrwxrwx 1 oracle dba 45 Jan 11 20:53 UAT_2670198561_44_20110101 -> /u01/db/backup/OUAT_2670198561_44_20110101
$ ln -s /u01/db/backup/AOUAT_2670198561_46_20110101 /oracle/db/backup/OUAT_2670198561_46_20110101
$ ln -s /u01/db/backup/OUAT_2670198561_47_20110101 /oracle/db/backup/OUAT_2670198561_47_20110101
$ ln -s /u01/db/backup/OUAT_2670198561_45_20110101 /oracle/db/backup/OUAT_2670198561_45_20110101
$
is it ok
will the duplicate gets the information from /oracle/db/backup
if i did anything wrong , please correct me?

Restore controlfile from backup location

Hi All,
I have a RMAN backup and want to recover my data from backup. RMAN backup has taken by someone but during restore to another DB server I am confused at controlfile point. I can see two controlfile in RMAN backup. Do I need to add both controlfile in restore command or any one controlfile would be okay? Please suggest.
I run below command - rman > restore control file from '<backup location>';
Thanks...
Edited by: user12115 on Jun 15, 2012 5:23 AM

I have a RMAN backup and want to recover my data from backup. RMAN backup has taken by someone but during restore to another DB server I am confused at controlfile point. I can see two controlfile in RMAN backup. Do I need to add both controlfile in restore command or any one controlfile would be okay? Please suggest.
I run below command - rman > restore control file from '<backup location>';In you log file one of backup set contains of data files another backup set contains Controlfile + SPFILE(optional)
Or else you can check from source database
RMAN> list backup of controlfile;
Note that backup piece according to date, and you can use that piece name to restore controlfile.

Backup location during duplicate database

Similar Messages

Maybe you are looking for