Rman backup on tablespace level.

Hi,
I plan to backup at tablespace level instead of whole database. Other than the tablespaces used for the application, do I have to backup system and other tablespaces in 9i to guarantee recovery like the ones we did without rman, alter tablesapce....? The DB is on archivelog mode. Thanks.
Tracy

The SYSTEM tablespace is the most critical and important tablespace. That is good practice to ever have a backup of this tablespace.
If you don't have a backup of the other tablespaces you can recover your database too, but that isn't so easy. BUT YOU MUST HAVE ALL ARCHIVELOG!
This type of backup is suitable only for advanced DBAs. You must know what are you doing and what is your real goal; and that is not only to recover the database!!! that is much more.
I think that the best command for you is backup database.
After that you can evaluate incremental backup.
Bye, Aron

Similar Messages

Rman backup full then level 0 and level 1 Weekly

Please share your thoughts of backups.
Friday -> Take a full rman backup
Saturday -> Take a level 0 rman backup -> If recovery needed restore full and apply level 0 ?
Sunday -> Take a level 1 rman backup -> If recovery needed restore full and apply incremental 1 ?
Monday -> Take a level 2 rman backup -> If recover needed restore full and apply incremental 1 ?
Tuesday -> Take a level 1 rman backup -> If recover needed restore full and apply incremental 2 ?
Wednesday -> Take a level 2 rman backup -> If recovery needed restore full and apply incremental 1 ?
Thursday -> Take a level 1 rman backup -> If recovery need restore full and apply incremental 2 ?
Thanks

Please note that Full and level 0 backs are same...
Sunday -> Take a level 0 rman backup
Monday -> Take a level 1 rman backup
Tuesday -> Take a level 1 rman backup
Wednesday -> Take a level 2 rman backup
Thursday -> Take a level 1 rman backup
Friday-> Take a level 1 rman backup
Saturday -> Take a level 1 rman backup
Taking level 2 in the middle of the week, so that in case of any recovery you need ao apply changes since the last level 0, 1 or 2

Rman backup for tablespaces

Dear,
i want to use rman to backup the tablespaces. I have write a pram file as below.
owner=database
file=c:/backup/database.dmp
log=database.log
buffer=81920
How can i run this file from rman
ManyThanks

It appears that you have created a parfile for the export utility and NOT for RMAN. The basic command to backup a tablespace in RMAN is:
RMAN> BACKUP TABLESPACE USERS;If you are looking to actually export a tablespace, you can save the following to a file called user_parfile.txt
userid=system
file=d:\user_exp.dmp
log=d:\user_exp.log
tablespaces=users
buffer=81920and execute as:
exp parfile=d:\user_parfile.txt

How to find total size of RMAN backup files?

Hi there
env: Oracle 10gR2, RHEL 64bit
My client has a production database where rman backups are taken: Level-0 backup every Sunday and Level-1 Monday thru Saturday.
I have very limited access to this production database because it is being managed by third party and they won't provide me my required info (not sure why). I do not have access to their rman repository. To connect to the database I have to login to an intermediate server and then login to the database server. I have no access to Enterprise Manager. So in short, my access is limited. I want to gather the information on total size of rman backup files - both for a Level-0 and Level-1 backups separately. I understand that this info can be retrieved from rman repository. Are there any data dictionary views/tables where I may get this info?
Best regards

Hi,
Have you searched in forum check this:https://forums.oracle.com/thread/1097939
HTH

RMAN Backup specially for tablespaces

Hi@everybody,
we have a Oracle 11gR2 (11.2.0.3.0) Server, based on RedHat 6, running in our company. For the Backups i'm using RMAN with a script. In that script this code specially creates the backup:
        run {
            allocate channel oem_backup_disk1 type disk;
            backup incremental level ${level} cumulative as COMPRESSED BACKUPSET tag '${tag}' database;
            backup as COMPRESSED BACKUPSET tag '${tag}' archivelog all not backed up;
            release channel oem_backup_disk1;
${level} is for 0 or 1, full backup or incremental backup. ${tag} is the name for the backup. This script is for the hole database. But now i want to change that script to tablespace level. We have some "test" tablespaces, where a backup is not needed. I just found that one:
backup tablespace TEST tag='BACKUP_TEST';
But now i'm not shure how i can implement that into my script.
Can you guys help me?
Thanks and best regards,
David

I've just to ask again to understand it right:
In RMAN - Console i just exclude the tablespaces that should not be backed up with:
CONFIGURE EXCLUDE FOR TABLESPACE Tbs1, tbs2, tbs5;
And then RMAN knows, when he is doing a backup of the database, he will exclude that tablespaces that i've told him? Thats awesome! And easier to handle!
EDIT: I've tested this on my Oracle Test server and it works! Thanks a lot for the answers!

Undo tablespace recovery from RMAN backup

Hi,
Lets's assume we have RMAN backup and archivelog backups, and now
my undo tablespace's disk crashed ,how can i recover?
Can i recover while database is up?
Thanks,
Kumar.

to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
rman target /
RUN
STARTUP MOUNT;
ALLOCATE CHANNEL ch3 TYPE Disk;
RESTORE datafile 'c:\u01\prod3\undo01.dbf';
RECOVER datafile 'c:\u01\prod3\undo01.dbf';
ALTER DATABASE OPEN;
RELEASE CHANNEL ch3;
hope this will help you

Tablespace level backup using data pump

Hi,
Im using 10.2.0.4 on RHEL 4,
I have one doubt, can we take a tablespace level backup using data pump,
bt i dnt wnt to use it for transportable tablespace.
thanks.

Yes, you can only for the tables in that tablespace only.
Use the TABLESPACES option to export list of tablespaces.*here all the tables in that tablespaces will be exported*.
and you must have the EXP_FULL_DATABASE role to use tablespace mode.
Have a look at this,
http://stanford.edu/dept/itss/docs/oracle/10g/server.101/b10825/dp_export.htm#i1007519
Thanks
Edited by: Cj on Dec 12, 2010 11:48 PM

How to identify rman backup level?

Hi,
I am using rman catalog for rman backup. how to identify rman backup level from catalog.
Thanks,

By doing the obvious and consulting the online documentation at http://tahiti.oracle.com
You will notice the list backup command output has a level column and this is also present in rc_backupset and/or rc_backuppiece.
Sybrand Bakker
Senior Oracle DBA

"list backup of tablespace" - Not coming out back to RMAN prompt

Hi All,
We have a script to perform the restore and recover test process.
In that we have given the command "list backup of tablespace <tablespace name > summary" to check if the tablespace is backedup successfully.
Its returning the list of backup pieces, but it hangs in that stage without coming back to RMAN prompt.
I have manually loged in to rman session and typed "list backup of tablespace <tablespace name > summary", after listing the backup it hangs and not coming back to RMAN prompt.
Please advice on this.
Thanks & Regards,
Rakesh

And your version and operating system are?
Is this a production system with other things running or a home machine with minimal resources?
If Windows specifically which edition of the Windows software (don't just say XP).

NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

제품 : RMAN
작성날짜 : 2004-05-20
NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
=======================================================
오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
전략을 세울 수 있다.
1. 백업 화일 최적화 방법 (Backup File Optimization)
백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
된다.
이때 같은 화일이라고 판단하는 기준은 다음과 같다.
* Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
되어야 함.
* Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
SCN 과 time.
* Backup Set: 같은 Backup Set recid 와 stamp.
RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
되어도 화일을 지우게 된다.
RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
않는다.
그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
Note:
자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
예:
CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
2. Backup Optimization에 Retention Policies 적용 하기
Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
REDUNDANCY = 1 이 적용 된다.
a. Recovery Window 를 이용한 Backup Optimization
만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
Window 보다 오래된 데이터 화일을 백업한다.
예를 들면 다음과 같은 조건에서
o Today is February 21.
o The recovery window is 7 days.
o The most recent backup of tablespace tbs2 to tape is January 3.
o Tablespace tbs2 is read-only.
2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
조건을 지키게 된다.
이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
b. Redundancy 를 이용한 Backup Optimization
Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
Redundancy의 갯수를 정한다.
아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
동안 한다고 하자.
Day Action Result Redundant Backup
Monday Take tablespace archive offline clean.
Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
Friday Run BACKUP DATABASE. n/a Tuesday backup.
Saturday Run BACKUP DATABASE. n/a Tuesday backup.
Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
복사하지 않게 된다.
RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
사이클이 진행 된다.
3. RETENTION POLICY NONE vs. DEFAULT
주의 사항:
'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
(REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
제거 하라는 명령이다.
보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
--------------THE END----------------------------------------------

Hi,
Backup optimisation = +- do not copy empty space.
So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
Regards,
Yoann.

Force logging at tablespace level for standby database

Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.

Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale

RMAN Backup Plan

Hello -
I'm running Oracle 8.1.7
I'm developing an online backup strategy using RMAN. I want to backup the tablespaces, then backup the archived logs.
Here is a script that I am using:
rm /backups/old/*
mv /backups/* /backups/old
rman target uname/pwd nocatalog <<EOF
allocate channel for maintenance type disk;
crosscheck backup;
delete expired backupset;
release channel;
run {
allocate channel d1 type disk;
sql 'alter system switch logfile';
backup incremental level = 0
filesperset = 3
format '/backups/indx_%d_%U.bak'
tablespace indx; }
run {
allocate channel d1 type disk;
backup incremental level = 0
filesperset = 3
format '/backups/data_%d_%U.bak'
tablespace data; }
run {
allocate channel d1 type disk;
backup incremental level = 0
filesperset = 3
format '/backups/system_%d_%U.bak'
tablespace system; }
run {
allocate channel d1 type disk;
backup
format '/backups/arch_%d_%U.bak'
(archivelog all delete input);
Does this appear to be a good backup stragegy using RMAN?
Thanks.

I'm taking a backup of the controlfile binary, but what if my datafile paths will be different on the restoration server?
Say if I backup my entire database and I specify like 3 files per set. After I copy all of these backup set files to the restoration server, what are the steps to recovery?
Do I perform the following
1. startup mount pfile = 'initsomedb.ora'
2. startup RMAN as follows:
rman> run {allocate channel d1 type disk;
then I am lost syntactically...
Do I specify:
   restore controlfile to 'some_path'
   from 'path of backup set with controlfile'
Thanks for any insight. I'm just finding it hard finding any documention or example for what I am trying to accomplish with RMAN 8i.

RMAN backup into multiple locations

Hi All,
Our database size is 1.4 TB. I am planning to schedule RMAN full backu. But i do not have mount point of size 1.4 TB. We have mount point /rmanbkp1 of size 1200GB and /rmanbkp2 of size 200GB. How can i distribute RMAN backup to these two filesystems.
Can i take tablespace level backups..?
Please suggest.
Thanks
Sandeep Vadlamudi

Hello;
First of all 1200GB, might be enough since you probably are not using all the blocks in the 1.4 TB and will compress you will also lose less.
Can i take tablespace level backups..?
Yes but the value is limited. You cannot for example recover a dropped tablespace.
Test a backup first and get an idea of how much space you really need.
Also once you have a backup how do you free space for the next backup?
You could use the FORMAT command to backup the database to one location and the Archive to the other. 200 GB is not much space.
RMAN backup into more than one location :
http://www.oracle-class.com/?p=2043
Best Regards
mseberg

RMAN backup Scripts: Please Check and Advice

Dear All
We are now upgrading our database from 9iR2 to 10gR2.
Before this process we want a full database backup with RMAN with the following scrips. I also included our current database configuration.
So, dear all gurus please check this process if any thing goes wrong and give some valuable advice for better performance and other issue.
===========================================================
/data01          400GB
/data02      400GB
/data03          400GB
/idx04          400GB
Current Tablespace Used Size= 1700GB
Total Tablespace=31
Total File=295
Max File Size= 15GB
Avg File Size= 9GB
CPU_COUNT=4
Memory=32GB
sqlplus /nolog
conn /as sysdba
--configured database in archivelog mode. Then
create user rman identified by pass default tablespace INDX tempprary tablespace temp;grant connect,resource,RECOVERY_CATALOG_OWNER to RMAN;
RMAN target rman/rman@dwh nocatalog
RMAN>configure channel device type disk maxpiecesize=64GB;
RMAN>configure channel device type disk maxsetsize=195GB;
RMAN>configure channel device type disk parallelism=4;
RMAN>run {
allocate channel Channel1 type disk format '/data01/oracle/rman_backup/DWH_df_%s_%p_%c';
allocate channel Channel2 type disk format '/data02/oracle/rman_backup/DWH_df_%s_%p_%c';
allocate channel Channel3 type disk format '/data03/oracle/rman_backup/DWH_df_%s_%p_%c';
allocate channel Channel4 type disk format '/idx01/oracle/rman_backup/DWH_df_%s_%p_%c' ;
backup as compressed backupset database plus archivelog;
backup current controlfile format '/idx01/oracle/rman_backup/DWH_cf_%U.f';
backup spfiel format '/idx01/oracle/rman_backup/DWH_spf_%U.f';
release channel Channel1;
release channel Channel2;
release channel Channel3;
release channel Channel4;
===========================================================
Thanks & Regards
Quazi Abdur Rab

Try this ...
RUN {
RECOVER COPY OF DATABASE WITH TAG 'incr_backup' UNTIL TIME 'SYSDATE - 7';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr_backup' DATABASE;
The RECOVER COPY... line will not do anything until the script has been running for more than 7 days. The BACKUP INCREMENTAL line will perform a complete backup (level 0) the first day it is run, with all subsequent backups being level 1 incremental backups. After 7 days, the RECOVER COPY... line will start to take effect, merging all incremental backups older than 7 days into the level 0 backup, effectively moving the level 0 backup forward. The effect of this is that you will permanently have a 7 day recovery window with a 7 day old level 0 backup and 6 level 1 incremental backups. Notice that the tag must be used to identify which incremental backups apply to which image copies

Setting up new dbname/sid while creating oracle db from rman backups in 11g

Hi all,
I have rman backups and need to create another database from rman backups with different name... but it is unsuccessful..
created instance with new db...
running create new db connecting rman auxiliary sys/password@newdb
run {
SET NEWNAME FOR DATAFILE 1 TO 'F:\app\HOME\oradata\clonedb1\SYSTEM01.DBF';
SET NEWNAME FOR DATAFILE 2 TO 'F:\app\HOME\oradata\clonedb1\SYSAUX01.DBF';
SET NEWNAME FOR DATAFILE 3 TO 'F:\app\HOME\oradata\clonedb1\UNDOTBS01.DBF';
SET NEWNAME FOR DATAFILE 4 TO 'F:\app\HOME\oradata\clonedb1\USERS01.DBF';
SET NEWNAME FOR DATAFILE 5 TO 'F:\app\HOME\oradata\clonedb1\EXAMPLE01.DBF';
SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';
DUPLICATE DATABASE TO clonedb
pfile 'D:\TESTDELETE\initclonedb1.ora'
BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'
LOGFILE GROUP 1 ('F:\APP\HOME\ORADATA\ORCL\REDO01.LOG') SIZE 60M REUSE,
GROUP 2 ('F:\APP\HOME\ORADATA\ORCL\REDO02.LOG.rdo') SIZE 60M REUSE,
GROUP 3 ('F:\APP\HOME\ORADATA\ORCL\REDO03.LOG') SIZE 60M REUSE;
Error it shown is in rman backup creation is as follows
<part>>
sql statement: alter system set db_name = ''ORCL'' comment= ''Modified by RMAN
duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 640286720 bytes
Fixed Size 1376492 bytes
Variable Size 314576660 bytes
Database Buffers 318767104 bytes
Redo Buffers 5566464 bytes
Starting restore at 20-DEC-11
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=133 device type=DISK
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
output file name=F:\APP\HOME\ORADATA\CLONEDB1\CONTROL01.CTL
output file name=F:\APP\HOME\FLASH_RECOVERY_AREA\CLONEDB1\CONTROL02.CTL
Finished restore at 20-DEC-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/20/2011 07:07:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01102: cannot mount databa
se in EXCLUSIVE mode
RMAN> EXIT
how can i prevent rman setting db_name=orcl which is already exists in the db.. i need to create db from rman backups with different dbname...
whould someone help me out, how can i create database from another database rman backups with different dbname/sid on same host..
My pfile has new db_name , but while db creation rman setting to db_name to source dbname.. it should be new db name that i want create with new db name...
is there any RMAN command to specify new DB name it should set while running
sql statement: alter system set db_name = newdbname -- as part rman script execution...
it appears to be i should not touch the soruce db.. i have access to only source db rman backups and need to create another db with different dbname/sid.. please do help...

When you performing RMAN duplicate why you making your script so complicated?
Your instance name and DB name can be different, But what is the contents in your pfile "D:\TESTDELETE\initclonedb1.ora" ? please do post
Have you started any other services related to ORACLE? check in start --> run --> services.msc any other active oracles services, Make sure you have clonedb1.
Startup in nomount
check the connectivity to target server.
SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';Why you mentioning SET NEWNAME FOR DATAFILE ? You have option of db_file_name_convert/log_file_name_convert in case if your file system different in Target & auxiliary.
BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'When you have backup in same location why you are mentioning this clause?
First run duplicate from auxiliary server as
rman target sys/*****@prod auxiliary /
RMAN> duplicate target database to "db_name";
Am not sure what you are trying to do. is it 11gR1 or 11gR2?
You have option of duplicate from active database without having backup also..
here some links please check it.
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmdupdb.htm#BGBFDJHB
RMAN 11GR2 : DUPLICATE WITHOUT CONNECTING TO TARGET DATABASE [ID 874352.1]
knowledgespring
     Newbie
Handle:      knowledgespring
Status Level:      Newbie (10)
Registered:      Dec 26, 2007
Total Posts:      243
Total Questions:      77 (75 unresolved)
So sad that forum was able to help only in two answers out of your 77 questions :(
Edited by: CKPT on Dec 21, 2011 5:12 PM

Rman backup on tablespace level.

Similar Messages

Maybe you are looking for