Validate RMAN backupset

Hello,
Two nodes RAC system. Database version 11gR2
I have two scripts - one script backups a database to ASM FRA (local backup) and other script use the command "backup backupset" as shown below to the remote NFS mount.
run {
allocate channel d2 device type disk format '/cloudfs/oracle/temp/%U';
backup backupset completed between 'sysdate-1' and 'sysdate';
release channel d2;
First question - What happens if the ASM FRA is not completed on time and still running. And the second script that backup the ASM FRA to the NFS will start execute at the same time??
I think the backup to NFS will be corrupted. I have setup two scripts running two hours apart from each others. But I think this is not a good way to do it, because what if the first backup is running longer than two hours?
Second question - Can the command "backup backupset ..." automatically waits for the first backup to complete before it continues so it can backup everything from ASM backupset??
Thank you in advance.
Edited by: feverlove on Oct 21, 2012 3:43 PM
Edited by: feverlove on Oct 21, 2012 3:46 PM

Hello;
First question - What happens if the ASM FRA is not completed on time and still running. And the second script that backup to the NFS will start execute at the same time??I'm thinking it would work since the backup locations are different. But I have no way to test. Maybe backup a tablespace as a short test.
Second question - Can the command "backup backupset ..." automatically waits for the first backup to complete before it continues so it can backup everything from ASM backupset??backup backupset is used to make copies of backup sets so no.
Example
RMAN>backup device type disk
backupset
completed before 'sysdate-10'Best Regards
mseberg

Similar Messages

What are the caveats of using ASM as storage for RMAN backupsets?

Hello all,
We are currently evaluating RAC as our standard database platform. Until now we have been using 10g single instance with ASM for datafiles and local filesystems for RMAN backupsets and archivelogs. We chose to use local fileystems for backup components so that we can utilize a Tivoli filesystem backup in order to secure the backup pieces to tape.
With RAC, we are looking into a shared location for backupsets and archivelogs. OCFS2 is out of the picture due to it not functioning on top of linux LVM. It appears that our only "shared" option is to use ASM for backupsets and archivelogs.
My concern is that while the data diskgroups and rman diskgroups will be separate, they are both running on ASM and therefore if ASM fails or is corrupted, we have nothing. My current plan is to utilize the Tivoli RMAN MML (TDPO) to backup the backupsets to tape after the ASM backupset has completed.
What experiences have been had with using ASM for RMAN backups?
Any advice on additional protection we can employ to ensure that the database remains recoverable?
Thanks in advance,
David

I've personally haven't implemented RMAN with ASM, but you may want to review Faster Backup, Faster Recovery which discusses RMAN utilizing ASM.
And although you may not get any of the negative aspects from these presentations, you may want to check out High Availability Customer Case Studies, Presentations, Profiles, Analyst Reports, and Press Releases.
Hope this helps!

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

Can we rename/relocate the RMAN backupset?

Hi All,
Can we rename/relocate the RMAN backupset?
I have the following scenerio:
1.took tha backup on /u99 mountpoint using rman
2.copy the entire backup to tape
3.filesystem /u99 scrapped
4.created new filesystem /u101
5.copy the backup to /u101 from tape.
Now we have to restore the database..but problem is that rman dont know /u101, by default it will search from /u99 filesystem...how to tell rman take the backup from /u101 not from /u99...
Please help me
Regards
Symal

You need to use the RMAN command
SET NEWNAME FOR DATAFILE <datafile_number> TO ‘<path_and_filename>’;
for each datafile you want to restore and recover.

FIles of same RMAN backupset

Hello all gurus,
Sir,
Version : ORACLE 9.2.0.1.0
O/S : Windows XP
I wish to know how can I check which physical files are of same RMAN backupset.
Thanks in Advance

You can do two things.
Issue from the RMAN prompt, list backup;
This will give you the listing of the backupsets and pieces. Check over there in the media that actually those pieces are there or not?
Or you can issue list backup and then issue crosscheck backup.This would verify that the backups coming up in the listing are actually available over the physical hard disk or not?
HTH
Aman....

Restoration of 10gR2 RMAN backupset onto 11gR1 database

I am trying to restore my RMAN backupset from 10gR2 RAC database onto 11gR1 RAC database, both on HP Itanium v11.31. I was wondering if anyone has tried this before?
RMAN> alter database open resetlogs;
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 04/17/2012 21:45:48
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 11201
Session ID: 1185 Serial number: 139
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 04/17/2012 21:45:48
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 11201
Session ID: 1185 Serial number: 139
After I had encountered this, I tried to startup with upgrade option and the database could be opened. Am I supposed to do anything after this? I tried logging into the database as another user but I encountered the following error:
ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
Am I supposed to run any utlrp.sql script or something?

user12043880 wrote:
I am trying to restore my RMAN backupset from 10gR2 RAC database onto 11gR1 RAC database, both on HP Itanium v11.31. I was wondering if anyone has tried this before?
RMAN> alter database open resetlogs;
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 04/17/2012 21:45:48
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 11201
Session ID: 1185 Serial number: 139
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 04/17/2012 21:45:48
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 11201
Session ID: 1185 Serial number: 139
After I had encountered this, I tried to startup with upgrade option and the database could be opened. Am I supposed to do anything after this? I tried logging into the database as another user but I encountered the following error:
ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
Am I supposed to run any utlrp.sql script or something?Now you must UPGRADE your Database use DBUA of OH 11gR1 to accomplish it.
Regards,
Levi Pereira

Expired RMAN backupset?

Dear all,
I copied all the RMAN backupset and found this is expired. Is it possible to make this valid, NOT EXPIRED.
backup piece handle=/backup/db/backup/RMAN/backup_PROD_748148532_40523_1_ibm9flpk_1_1.bck recid=40515 stamp=748148534
crosschecked backup piece: found to be 'EXPIRED'
Please advice.

yes... it is in the original location. I can restore the control file successful.
However, I get error when I restore database.
>
RMAN> restore database;
Starting restore at 15-APR-11
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=16 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=17 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 04/15/2011 17:47:48
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 235 found to restore
>
Please advice.

RMAN backupsets to disk - how to parallelize?

Is there any way to utilize Oracle RMAN backup parallel features via BR*Tools when performing backup to disk?
Platform: Windows if it is relevant, Oracle 10.2.0.4.
The only way I found so far is to use exec_parallel parameter in BRTools profile and in this case parallelizing done via starting n processes of RMAN in parallel when each makes backup of separate datafile. The aim is to do something with BRTools parameters to get parallel option 'inside' RMAN (equivalent of "RMAN> CONFIGURE DEVICE TYPE disk PARALLELISM n;").
The other part - how to parallelize offline redo log backups for RMAN backupsets? Even having exec_parallel parameter set to >1 only one process of BRARCHIVE is processing all offline redo logs serially.
BR*Tools parameters which I changed from baseline:
backup_mode = full
backup_type = online
backup_dev_type = disk
archive_function = save_delete
disk_copy_cmd = rman_set
rman_compress = yes
rman_cross_check = arch_force
exec_parallel = 4

Hi Vladimir,
>> Well, BRARCHIVE does support rman backupsets; not directly through command line parameters but via parameter file.
You need to use external backup library in order to use backupset by BRARCHIVE with the parameter "rman_filesperset" in init<DBSID>.sap. Please check the link;
http://help.sap.com/saphelp_sm32/helpdata/de/82/29e03a00281877e10000000a11402f/content.htm
>> Is there a way to create disk RMAN backup via External Backup Library?
Are you asking this for BRBACKUP or BRARCHIVE? First of all, you can the note "1101530 - Support for RMAN savesets for backups on hard disk"
And the the links, below;
Profile Parameters and BRBACKUP Command Options->
http://help.sap.com/saphelp_nw04/helpdata/en/3f/9d800e1aec11d2b42c00609419997a/content.htm
parallel channels used by RMAN with an external backup library-> http://help.sap.com/saphelp_sm32/helpdata/en/57/29e03a00281877e10000000a11402f/content.htm
You can take the detailed information by contacting local vendors.
Best regards,
Orkun Gedik
Edited by: Orkun Gedik on Jun 12, 2011 12:32 AM

Validate RMAN backup

Hi All,
I have database of 3.5 TB. Backup strategy is RMAN hot backup. I need your suggestions " How could I verify/validate RMAN backup ". We don't have that much disk available to abstract RMAN backup and validate database.

Please read the RMAN documentation under 'restore database validate'
Please do not conform to the standards of all other posters from Hyderabad in this forum to never read any manual prior to posting.
Sybrand Bakker
Senior Oracle DBA

Rman command to validate the backupsets are recoverable

Hi,
I'm using 9iR2 rman/controlfile to do the fullbackup. The DB is in archivelog mode. And my fullbackup includes both DB and archivelog file with input delete. What is/are the rman command that I can use to make sure the full backupset are OK in case I need to do recovery? I got no result from following 2 commands. Is it enough? Thanks.
report unrecoverable;
report need backup;

Check the RETENTION POLICY. According to the retention policy RMAN will maintain the backup copy.
REPORT OBSOLETE command will list you which are the backup set we can delete it.
DELETE OBSOLETE
Deletes the backups and copies that are obsolete (that is, "not needed") under the configured retention policy. Alternatively, use REDUNDANCY and RECOVERY WINDOW parameters to specify criteria.

Validate rman backups

Hi,
oracle 9.2.0.1
rman Incremental cumalative backups
HI,
i do incremental cumalative backups. Full Level 0 on friday, level 1 incremental done Mon - Thurs.
i noticed that if i run a RESTORE DATABASE VALIDATE command, it checks/uses all the pieces that are part of the FULL LEVEL 0 only. But this does not tell me if the incremental backup pieces created are good or not.
How (without actually restoring to test server) can i test/validate up-to the latest incremental daily backup?
J

RESTORE VALIDATE will only do full backups, LEVEL 0 backups, controlfiles, spfile, datafile copies and archivelogs. However, you can VALIDATE a LEVEL 1 backupset with simply:
RMAN> VALIDATE BACKUPSET <backupset_#>;

Rman Backupset size is exceeding the database size

Hi
my rman backup size is exceeding the database backup size and occupying the full mountpoint. and finally due to space issue, backup is failing.
Below is the RMAN script
run {
backup
incremental level 0
tag ASCPLVL0
database plus archivelog ;
delete noprompt backupset completed before 'sysdate - 4/24' ;
Please look into this
Regards
M. Satyanvesh

Are you using compression?
Ans: No
The size of an RMAN backup isn't always proportional to the size of the database.
Ans: yeah I know, but it should be somewhere near to database size(lets say 100gb or 150 gb variance)
How many archivelogs are you backing up with your database? This is possibly a factor in the size of your db backup.
Ans: archive log count per day is 18 and size is 34gb
Have you got a retention policy in place and do you regularly delete obsolete backups/archivelogs?
Ans: yes
Are you taking this backup as part of a backup strategy? or is this just a one off for some other purpose which would seem to be the case.
Ans: This is production systesm so its a part of backup strategy

Rman backupset 관련 질문

rman 백업에 관해 질문드립니다.
모하나 해결하면 한도끝도 없이 터지네요. ^^;;;
rman백업할때 backup set을 만들고 나서 백업이 이루어지는걸로 알고 있습니다.
max값이 5이고 이거는 dbf 파일 갯수를 의미하는것 같은데요.
현재 rman 백업 셋팅한 곳이 디비파일이 이미지파일이라 사이즈가 큰 편입니다.
가장 큰 파일은 하나에 20g이지만..다른 사이트는 훨씬 더 큰곳도 많을거라는 생각은 드네요.
백업만 돌면 backup set을 만들면서 오라클 홈쪽이 full이 나버리네요.
백업이 시작되면 약간의 여유공간이 필요한 건 알고 있었는데...
이게 버퍼 사이즈 정도라고만 생각하고 max 2g 라고 생각했는데..(문서찾아보니..그런의미인듯해서요;;)
현재 오라클 홈이 available 공간이 20g 였는데....
backup set을 만들면서 bk_%s_%t 모 어쩌구 라고 시작되는 파일이 생기잖아요..format에 따라.
그 bk로 시작되는 파일이 5~6개가 생겼는데... 공간이 full나니까 더이상 생기지도 못하고..에러가 나버렸네요..
스크립트에 FILERSPERSET = 5 를 "2" 로 바꿨거든요...
그래도 마찬가지네요. ㅠㅠ
궁금한거는... dbf 파일의 용량에 따라서 backupset을 만들때 필요한 여유공간이 어느정도로 잡아야하나요..??
20g 갖고도 백업할때 용량이 모자른다는거는 말이 안되는거같아서요...
왜냐면..기존에 레가토 넷워커로 rman백업이 정상적으로 진행이 되고 있었거든요.
근데 넷백업으로 설정만 하면 이런 에러가 발생을 합니다.
그리고 스크립트중에 ALLOCATE CHANNEL ch00 TYPE DISK; <--부분에 수정이 필요한건 아닌가요??
테잎이 아닌 디스크로 받고 있거든요.
저 DISK 부분에 절대경로로 적어줘야되는건지...
그리고 디스크백업을 받을때에는 무언가 다른 옵션을 더 넣어줘야 하는지...해서요..
답변 부탁드립니다. plz.................... ㅠ.ㅠ
첨가.
아래와 같이 타겟서버의 변수값에 MAXSETSIZE값을 지정해주어서 백업셋을 만들때 제한을 두게끔..
설정을 하는건 아닌지.... 문서 찾다가 아래 찾았네요.
우선은 테스트 중이긴 한데요...결과도 알려드릴께요.
아시는 분은 답변 부탁드립니다.
(참고로 script의 allocate backup type to disk <--- 모 이부분 밑에다가 MAXPIECESIZE = 4g 할당해죠도 넘어버리네요;;)
RMAN> CONFIGURE MAXSETSIZE TO 1500m;
NOTE: Take careful note when setting this parameter. While the size of your database may be small enough for MAXSETSIZE, your database may grow beyond beyond MAXSETSIZE which will cause your database backups to fail.
For some time, there have been some question as to what this parameter limits. While the documentation states that it limits the size of a backup set, it seems to place limits on the datafile sizes - even though I am using backup sets and not image copies. For example, I have set MAXSETSIZE to 500m and attempted to backup a database, only to get the error: <PRE>RMAN-06183: datafile or datafilecopy larger than SETSIZE: file# 1 /u10/app/oradata/TARGDB/users01.dbf</PRE>The file (users01.dbf) is larger than 500MB but the backupset is considerably smaller than that (there is very little data in there at present). The Oracle documentation states that MAXSETSIZE limits the size of the backupsets, NOT the size of the datafiles which can be backed-up. All I can say, is that Oracle states that this is expected behavior, and I think it is a bug in the documentation.

RMAN> list backup of tablespace tools;
BS Key Type LV Size Device Type Elapsed Time Completion Time
65 Full 8.60M DISK 00:00:26 31-MAR-10
BP Key: 65 Status: AVAILABLE Compressed: NO Tag: TAG20100331T165859
Piece Name: D:\DF_ROCK_55_1_715107540.BAK
List of Datafiles in backup set 65
File LV Type Ckp SCN Ckp Time Name
9 Full 654488210 31-MAR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TOOLS01.DBF
RMAN>
-- The BS is 65 returned from above list command whereas its 55 in physical locaction... ? why?
please help..

Restore RMAN backupset on different DB version/Platform/RAC

Hi Oracle Experts,
I have taken a RMAN backup on 10.2.0.1 AIX 64bit.
I have successfully restore the DB using this backupset on another server with same 10.2.0.1 AIX 64 bit.
I have also successfully restore the DB using this backupset on 10.2.0.2 AIX 64 bit.
Is it not possible to use this backupset on 11g Redhat 32bit?
I know there is a RMAN compatilblility metrix, it is in terms of DB version. How about platform?
Thanks in advance.

You can, however you'll have to use Cross-Platform Tranportable Tablespace.

Split RMAN BackupSet

Hi Team,
I am taking backup of Oracle DB using RMAN.
For taking backup I am using following script.
run
CONFIGURE MAXSETSIZE TO 1 G;
ALLOCATE CHANNEL C1 TYPE DISK FORMAT 'C:\BK\DATAFILE_CTL_%d_%T';
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE;
RELEASE CHANNEL C1;
Now my problem is that while specifying the naming format for the backupset I am giving as DATAFILE_CTL_%d_%T
so after 1GB it gives the error as it tries to create same file name which is already exist.
I can able to resolve this issue by specifying it as DATAFILE_CTL_%d_%T_%U , so that it will take each time unique name for file.
But what if I want to give names in sequence as DATAFILE_CTL_%d_%T_01 , DATAFILE_CTL_%d_%T_02 , .......
Can anybody plz suggest some solutions for this?

Hi Daljit,
Its really close to my requirement , but I want the backupsets should starts with my backupset counter , where as here it starts with controlfile backupset counter.
Anyway thanks for the help, it still help me to resolve my issue.
Also plz let me know if u have any other solution.
Thanks,
S.Tiwari

Validate RMAN backupset

Similar Messages

Maybe you are looking for