RMAN Backup Doubt...

Hi all,
I have set up RMAN Backup in my system which takes daily full backup as it is Standara Edition 9i.
My db size is 35GB.
As is see in the backup folder that there are three backup files each of 35GB.
I don't know why there are three peices.
I have given my RMAN Configuration below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'H:\OCTO backup\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'H:\OCTO backup\OCTO_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'H:\OCTO backup\SNCFOCTO.ORA';
Can Anybody explain me how come it take Three 35GB files. and why.
Thanks in Advance....
Elango

Folks,
I have Pasted the LIST BACKUP; output below.
Spooling started in log file: C:\Documents and Settings\dbProfessionals_PM\Desktop\dbpros\listbackp.txt
Recovery Manager: Release 9.2.0.7.0 - Production
RMAN>
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4211 Full 2M DISK 00:00:02 19-SEP-10
BP Key: 4211 Status: EXPIRED Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100919-00
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4212 Full 33G DISK 02:55:10 20-SEP-10
BP Key: 4212 Status: AVAILABLE Tag: TAG20100919T220053
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4JLOAM4M_1_1
List of Datafiles in backup set 4212
File LV Type Ckp SCN Ckp Time Name
1 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4213 Full 2M DISK 00:00:01 20-SEP-10
BP Key: 4213 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100920-00
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4214 Full 33G DISK 01:30:10 20-SEP-10
BP Key: 4214 Status: AVAILABLE Tag: TAG20100920T101831
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4MLOC1BN_1_1
List of Datafiles in backup set 4214
File LV Type Ckp SCN Ckp Time Name
1 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4215 Full 2M DISK 00:00:01 20-SEP-10
BP Key: 4215 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100920-01
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4216 Full 33G DISK 02:33:19 21-SEP-10
BP Key: 4216 Status: AVAILABLE Tag: TAG20100920T220137
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4OLODAI1_1_1
List of Datafiles in backup set 4216
File LV Type Ckp SCN Ckp Time Name
1 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4217 Full 2M DISK 00:00:01 21-SEP-10
BP Key: 4217 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100921-00
SPFILE Included: Modification time: 14-SEP-10
RMAN>
Elango
Elango

Similar Messages

How to verify RMAN backup ?

How to verify and validate the RMAN backups on daily basis?One more doubt at this point - if we can't locate any RMAN script in crontab(crontab -l) but still backup is occuring regularly, how can we see the script behind this?
Thanks in advance.
Edited by: 916438 on May 27, 2012 8:47 PM

916438 wrote:
How to verify and validate the RMAN backups on daily basis?One more doubt at this point - if we can't locate any RMAN script in crontab(crontab -l) but still backup is occuring regularly, how can we see the script behind this?
What you want see? If backup was executed without error or make sure that there is a valid backup on tape or disk.
So, If you want see if backup was executed successfull you must find the logs of backup or query "V$RMAN_OUTPUT" (check it on documentation).
If you want check if Database is Valid on Disk or TAPE as mentioned previously "RESTORE VALIDATE DATABASE" (check it on documentation).
Where we can locate RMAN SCRIPT? It's hard to answer.
It' your env, you should find out. The options are: Crontab / Oracle Enteprise Manager / Third-Party Backup Software / Job Scheduler.
Also you can try : Take a time of backup was executed and check on shell a time of exection of backup " ps -ef |grep rman" you will find from where script was started.
Regards,
Levi Pereira

Configure backup agent to take the RMAN backup

Hi,
We have a Sun Storagetek SL48 tape library with us. we want to take the backup to tape using Rman.
In order to take the RMAN backup, we need a backup agent needs to be installed on the database server.
1. My doubt is If we have Sun Storagetek SL48 tape library, what backup agent needs to be installed on the server?
2. If we know agent name, Could you please share the document to install the agent?
Thanks for your help.
R.Sundaravel

These softwares support the SL48 and they have an agent for RMAN : Symantec NetBackup, Legato Networker.
For Symantec, please check this URL : http://www.symantec.com/business/support/index?page=content&id=HOWTO44847#v15496705
For Legato, this one : https://store.emc.com/Product-Family/DATA-DOMAIN-PRODUCTS/EMC-NetWorker/p/EMC-NetWorker

How can i delete old RMAN backup files

Hi All
We have configured RMAN backup for one of our clients PROD instance[10.2.0.3] in 2010 Dec.
Now my doubt is how can i delte old backup files of Dec and January, only this two months backup files only i need to delte.
kindly suggest me.
The parameters are :
CONFIGURE RETENTION POLICY TO NONE;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/ebiz/backup/PROD-%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ebiz/backup/PROD-%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/ebiz/oracle/proddb/10.2.0/dbs/snapcf_PROD.f'; # default
Regards
Shaik

Hello,
You can use this :
DELETE BACKUP COMPLETED BEFORE TO_DATE('01/31/2011 00:00:00','MM/DD/YY HH24:MI:SS');Regards,
Sylvie

RMAN Backup policy

Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
007

1 What does the documentation of your unknown version of RMAN say? Does it states minutes are possible? If so, why are you asking rhetorical questions? (questions for which you already know the answer)
2 Rman only considers level 0 backups to determine whether a backup is obsolete, as you can't restore from an incremental backup.
Setting up a backup scheme for 4 days with a recovery window of 3 days wouldn't make any backup obsolete.
Sybrand Bakker
Senior Oracle DBA

RMAN : BACKUP OPTIMIZATION ON

Hi All,
I have a doubt about BACKUP OPTIMIZATION ON parameter..
If Any one worked, can u tell me the exact use of this parameter....
Regards,
Prabhu.

Used to enable or disable backup optimization. Backup file optimization can assist in reducing the space used to backup the database. When performing an RMAN backup, a check is done on the file before backup to see if the file already exists in a backupset with the same information: (dbid, checkpoint, and resetlogs data).
For archive logs, the same file means the same dbid, thread, sequence, and resetlogs data. If the DELETE INPUT option is used, RMAN deletes all the files that would have been backed up, even when the file is not included due to file optimization.
The two possible values for backup optimization is ON and OFF as shown in the following example syntax:
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE BACKUP OPTIMIZATION ON;
Use caution when enabling backup optimization if you use a media manager that has an expiration policy. The media manager can expire tapes containing backups (using its media control software), and RMAN will not make new backups because of optimization. One way to protect from this is to run CROSSCHECK periodically to synchronize the repository with the media manager.
Also note that you should consider how backup optimization works with regards to the RETENTION POLICY. RMAN will only work with files within the retention period. For example, consider performing a backup with optimization enabled and a retention period of 3 days. RMAN will only compare the datafile with backup sets within the 3 day period - even if the datafile it is about to backup hasn't changed within that 3 days.
ofcourse the best reference is here

RMAN Backup from windows to Linux

Hi,
I am having Windows 2003 server Oracle 10.2
and I have RHEL5 and Oracle 10.2
I have taken a RMAN Oracle Database Backup from windows..
I have installed oracle software on RHEL5 and now i need to restore this backup to the Linux
it is possible to restore it? if possible can any one let me know the process?
Regards,
Vijayaraghavan K

I have another doubt
I took RMAN full DB Backup - it comes around 2.5 G (performed on time 9.00 A.M morning)
When i perform differential incremental backup it comes around 2.6 G (performed on time 9.45 A.M )
Why it is coming like this.. The backup should happen only for the changed blocks alone?? i.e it should come around 10 Mb or 20 Mb?? Why is like this? or my understanding of differential backup is wrong?
I issued the below commands for Full DB Backup and Incremental Backup...
FULL DB backup at 9.00 A.M
RMAN> BACKUP INCREMENTAL LEVEL 0 DATABASE;
Differentail Backup a 9.45 A.M
RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE;
Regards,
Vijayaraghavan K

Taking RMAN backup of primary and standby databases.

Hi,
I am going to setup a Standby for Primary two node RAC to single node standby.
My doubt is, in standby both primary and standby will have the same db_name. So how can i take the RMAN backup of both primary and standby by using a single catalog.
That is, we can register the primary DB with catalog using it's db_name. But how can we register the standby with catalog using same db_name as it is already registered.
Thanks,
Mahi

Are you using a physical or logical standby?
If its a physical standby why do you need to back up both databases? backup the standby and you are done, the backup from the standby can be recovered to either the live serever or the standby if needed, andt hen the archivelogs used to bring it up to date.
If its a logical standby then change the database name for the standby and you can back both up to the same catalog, or alternativly cretae a new catalog for the standby, either as a new database or a new schema in your existing catalog.

How can i do a RMAN backup of my database from the network ?

i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.

Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus

Can not recover table from rman backup

For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backup

Hi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH

Unable to restore and recover my Database from RMAN Backup

Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
Mahi

All you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

Create a new Database in an other server using a copie of RMAN backup

Hi all,
I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
If some procedure or steps is there, email it to my adresse [email protected]
Hamid.
Thanks

By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
1. Create a password file for the Cloned (GEMINI) instance:
orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
2. Configure tnsnames.ora and listner.ora
Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
2.a Manually register the database against the listener (listener.ora)
(SID_DESC =
(ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
(SID_NAME = GEMINI)
2.b Added the target GEMINI to the tnsnames.ora
GEMINI =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(ORACLE_SID = GEMINI)
2.c Reload the listener
lsnrctl reload
3. Create a new init.ora for the cloned database.
Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
DB_NAME=GEMINI
CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
/u02/oradata/GEMINI/control02.ctl,
/u02/oradata/GEMINI/control03.ctl)
# Convert file names to allow for different directory structure.
DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
# block_size and compatible parameters must match those of the source database
DB_BLOCK_SIZE=8192
COMPATIBLE=9.2.0.0.0
4. Connect to the cloned instance
ORACLE_SID=GEMINI; export ORACLE_SID
sqlplus /nolog
conn / as sysdba
5. Create an SPFILE based on the init.ora
CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
6. Start the database in NOMOUNT mode:
STARTUP FORCE NOMOUNT;
7. Connect to the TARGET, CATALOG and AUXILIARY databases.
By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
ORACLE_SID=GEMINI; export ORACLE_SID
rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
8. Complete or Incomplete clone (recover)
From the rman the database using one of the following commands:
8.a Clone the database by means of a complete recover.
DUPLICATE TARGET DATABASE TO GEMINI;
8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
9. Process finished.
Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
Ref. RMAN Clone a Database
~ Madrid

I am getting below error while taking RMAN backup.

Friends,
I am getting below error while taking RMAN backup.
The issue is related with a lock while trying to backup the controlfile.
The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Is there anyway to solve this issue?Thanks in advance.

Hi,
SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
FROM v$session s, v$enqueue_lock l
WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
no rows selected
Oracle version : 10.2.0.3
I am getting this error once in a month not everyday.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Please suggest me based on this..Thanks in advance..

Creating a new controlfile with datafiles in RMAN backup

Hi,
i am using oracle 10g (10.2.0.1) in RHEL5 server. i am trying to restore a RMAN backup from one server to another new server with new db name. i have taken out the spfile from RMAN autobackup and created pfile from it and edited the pfile with new dbname and directory structure and started the db in nomount with the new pfile. Now i have restored the controfile from the RMAN autobackup tried to put the database in mount state. But it failed due to the below error
RMAN-03002: failure of alter db command at 11/05/2012 21:44:56
ORA-01103: database name 'ORADB' in control file is not 'DEVDB'
Hence i shutdown the database and started the db in nomount with new pfile and tried to create the controlfile with the new db name,but it failed as it is looking for the datafiles.
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
'/u01/app/oracle/oradata/DEVDB/datafile/o1_mf_system_80jq0kfw_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
All my datafiles reside in my RMAN backup. How to get the datafiles from RMAN backup in the above scenario??
Regards,
007

Hello;
The location and filename and DBIS will be different, but you need something like this :
$ORACLE_HOME/bin/rman << EOF
CONNECT TARGET /
STARTUP NOMOUNT;
SET DBID 3754763357; #DBID of PROD database
RUN
   ALLOCATE CHANNEL c1 DEVICE TYPE disk format '/u01/oradata/backups';
   RESTORE CONTROLFILE FROM '/u01/oradata/backups/sb_t790762003_s85_p1';
   ALTER DATABASE MOUNT;
   SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/CLONE/system01.dbf';
    SET NEWNAME FOR TEMPFILE 1 TO '/u01/app/oracle/oradata/CLONE/temp01.dbf';
   RESTORE DATABASE;
   SWITCH DATAFILE ALL;
   RECOVER DATABASE;
   release channel c1;
ALTER DATABASE OPEN RESETLOGS; So you need "SET NEWNAME" for all your files
Full Example
http://www.visi.com/~mseberg/rman/restore_database_without_catalog.html
Best Regards
mseberg

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

Similar Messages

Maybe you are looking for