Size of backup RMAN cumulative level 1.

Hi all
Sometimes it is the Hiller to ask stupid questions...

Sunday, level 0. -> 50 G
Monday level 1 cumulative 4 GB
Tuesday cumulative level 1 > > 2GB < <

I think we know of the anther, but that is the question...
Is the backup file from Tuesday is smaller in the case of archivelog redolog files?

Thank you * T

August 23, 10 full 11.7893262 GB

24 Aug 10 incrementielle.634921875 GB

25 Aug 10 incremental 1.47552734 GB

Aug 26, 10 incremental 1.50706055 GB

So, your backup using this query size is OK. It is more wider in size in 24, 25 and 26 compared to 23.

23 to the cumulative 24 - sauvegarde.63 GB size

23 to 25 cumulative - size 1.47 GB backup

23 to 26 cumulative - 1.50 GB size of backup

Hope you are clear now.

Concerning
Asif Kabir

-Mark your useful post as correct/helpful and close the debate.

Tags: Database

Similar Questions

Estimate the size of backups rman & time

Hi DBAs,
ENV: 11 GR 2, Windows Server 2008, 64-bit, = 12 GB RAM,
DB size = 370 GB., CMS = 5 GB, EAMA = enabled.
We need to move this database to the 2012 Windows Server that runs on Hyper-V. You guys you will suggest what are the best methods to move with limited downtime?
If we opt for RMAN, is it possible to measure to estimate the size of the backup? (at least, approximate size) and how long it takes to finish?
Please, share your ideas!
Thank you
Hari

IamHariKrishna wrote:

Thank you sb92075. Like size, is it possible to estimate the time as well?

Some, many, most of the professionals actually test before doing it for real & would be able to answer this question by themselves with appeals to foreigners to do their work for them, according to.

How to find the total size of the RMAN backup files?

Hello
env: Oracle 10 g 2, RHEL 64 bit
My customer has a production database where rman backups are taken: level 0 backup every Sunday and level 1, Monday to Saturday.
I have very limited access to this database of production because it is managed by a third party, and they don't give me my required info (don't know why). I don't have access to the rman repository. To connect to the database that I have to connect to a staging server, then connect to the database server. I have no access to Enterprise Manager. So in short, my access is limited. I want to collect information on the total size of the files of rman backup - both for level 1 to level 0 backups separately. I understand that this info can be retrieved from the rman repository. Is there a dictionary views/tables of data where I can get this info?
Best regards

Hello

Have you tried to check forum this:https://forums.oracle.com/thread/1097939

HTH

Cumulative level 1 backup and redundancy of information

My understanding of Cumulative level 1 - backups all the block changed since last level 0 backups and also double level 1 incremental copies, if we missed any level 1 differential before running the level 1 cumulative backup.
Having said that I fell on the underside of documentation in Oracle.
Suppose a case where REDUNDANCY is 1 . You run a backup of level 0 at noon Monday, a level 1 cumulative backup on Tuesday and Wednesday at noon and a backup of level 0 at noon Thursday. Immediately after each daily backup, you run a DELETE OBSOLETE . Wednesday DELETE command does not remove the level 1 of the Tuesday backup because the backup is not redundant: the level 1 of Tuesday backup could be used to recover the level 0 backup Monday for a duration between Tuesday noon and Wednesday noon. However, the DELETE command Thursday removes the previous level 0 and level 1 backups.
Can someone explain to me why killing level 1 backup needed clarification? When we have a backup of the sea element that has backup KILLS (e i, which has backup LUN)
to recover the database so I think that a single backup item is needed Wednesday.
Please correct me if I'm wrong. Sorry for my bad English, if you find any grammatical error
Also put me as what will contain the element of KILLING level 1 cumulative backup
for sample data of level 0 kills more than Monday morning and data MIDI Mar
Thank you

Thank you

2638616 wrote:

My understanding of Cumulative level 1 - backups all the block changed since last level 0 backups and also double level 1 incremental copies, if we missed any level 1 differential before running the level 1 cumulative backup.

Having said that I fell on the underside of documentation in Oracle.

Assume a case in which REDUNDANCY is 1 . You run a backup of level 0 at noon Monday, a level 1 cumulative backup on Tuesday and Wednesday at noon and a backup of level 0 at noon Thursday. Immediately after each daily backup, you run a DELETE OBSOLETE . Wednesday DELETE command does not remove the level 1 of the Tuesday backup because the backup is not redundant: the level 1 of Tuesday backup could be used to recover the level 0 backup Monday for a duration between Tuesday noon and Wednesday noon. However, the DELETE command Thursday removes the previous level 0 and level 1 backups.

Can someone explain to me why killing level 1 backup needed clarification? When we have a backup of the sea element that has backup KILLS (e i, which has backup LUN)

to recover the database so I think that a single backup item is needed Wednesday.

Please correct me if I'm wrong. Sorry for my bad English, if you find any grammatical error

Also put me as what will contain the element of KILLING level 1 cumulative backup

for sample data of level 0 kills more than Monday morning and data MIDI Mar

Thank you

Thank you

Also put me as what will contain the element of KILLING level 1 cumulative backup

for example Monday level 0 data more Tuesday morning as well as MIDI data Mar

No backup of level 1 will contain nothing of the previous level 0 backup. First level 1 (no matter the cumulative or differential) will contain only the data blocks that have changed since the previous level 0. Backups.will all new 1 cumulative level contain only data blocks that have changed since the previous level 0.

And if you think a little about it, which will answer any other questions.

While you take the cumulative incremental backup RMAN. Meanwhile users ke
While you take the cumulative incremental backup RMAN.
During this time users keep be updated, insert the corresponding schema.
But my Client doesn't backup up-to-date. Is it possible to get the up-to-date backup?
(If I have something wrong, sorry about that, that was my interview question)

Thanks for all,
Kind regards
DB
DB wrote:
While you take the cumulative incremental backup RMAN.
During this time users keep be updated, insert the corresponding schema.
But my Client doesn't backup up-to-date. Is it possible to get the up-to-date backup?
(If I have something wrong, sorry about that, that was my interview question)

Thanks for all,
Kind regards
DB

RMAN backup is not compatible and easy to follow on-line transactions. If it's something any purpose of migration suggest taking COLD backup.
If it's no way suggested, then after your entire + cumulative backups, however, that data will be available in archives

How to restore the Rman incremental level 0 backup if the SID is different?
Hi Experts,
I had a little problem with restore rman backup of level 0. I have backup rman for oracle 11.2.0.1.0 - 64 bit and restore the server to Test 11.2.0.1.0 - 64 bit.

Problem:
Sid = prd production server
Sid = prderp test server

Operating system is Oracle linux 5 on both servers.

How to restore Rman if the SID is different?
Hello

Refer to this http://shivanandarao.wordpress.com/2012/04/19/duplicating-primary-database-to-a-new-host-without-connecting-to-the-primary-database-in-oracle-10g11g/

You need to restore it under the same name as you have in the production and later change the dbname using the NEST.

If you don't want to go with this method, then I suggest you to go with the method of double RMAN.

http://www.Oracle-base.com/articles/11g/duplicate-database-using-RMAN-11gr2.php
http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm
```
rman target sys/@prod auxiliary sys/@tst
RMAN>duplicate target database to 'prderp' nofilenamecheck;
```
Please close this Re: how to restore the Rman backup if the SID is different? wire by marking as replied.

RMAN size incremental backups have increased.
In a database of CARS of two nodes, the size of the file incremental RMAN is usually around 400-500 MB and RMAN complete file size takes up approximately 10 GB.
Suddenly, the RMAN incremental file size has increased to about 16-17 GB and there are no extension on the block of data file size data of size/volume/DB etc.

What could be the reason for the sudden increase in the size of the RMAN incremental file?

Thank you

Database:
BANNER
--------------------------------------------------------------------------------
Oracle Database 11 g Release 11.1.0.6.0 - 64 bit Production
PL/SQL release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
AMT for Linux: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production

OPERATING SYSTEM:
Linux 2.6.18 - 92.1.22.el5 #1 SMP node1 kills Dec 16 11:57:43 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux
Have you checked the abnormal generation of redo. East - the number of the generated archivelogs identical or similar to the period you are comparing?
Would it be because you save including archivelogs topic archivelogs.

------------------------------------------
Coskan GUNDOGAR

Oracle DBA
Blog: http://coskan.wordpress.com
Twitter: http://www.twitter.com/coskan
LinkedIn: http://uk.linkedin.com/in/coskan
------------------------------------------

Edited by: coskan on May 27, 2010 22:56

What happened when RMAN 1 level 1 is running and start a 2nd

Hello
I have some doubts on the RMAN backup,
(1) what will happen when the first backup which is cumulative level 1 is running and second level 1 is launched.
Example,
Each work day 4 h level 1 is running and not completed and 9 AM is started before complete 04:00, in this situation, what would happen if 04:00 will be shut down properly and 09:00 will start correctly or any error will be through?
(2) what happens when level 1 is running and not completed when the use of level 0 is the beginning.
(3) is 1 / my dismissal and have only a level 0 and other many cumulative level 1 filled with hard drive backup and it reached assigned size. How I can take more away level 1 and how can I take level 0. If I don't have enough memory.
When my redundancy policy is 1 so I would have 2 valid level 0 then then a level 0 backup will become obsolete and can delete.
Help, please.

(1) 2nd level 1 will take place at the same time.

(2) level 0 will start and operate concurrently.

(3) you need to extend the backup volume. If you can't do that let down backups, then do the 0 level.

Only the unused blocks backup RMAN as well?

DB version: 11.2.0.4
OS: RHEL 6.6
If I remember correctly, RMAN backs up only used blocks. I created a tablespace of 20 GB, as shown below. When I backed up, the backup piece is only 4MB in size, as shown below.
SQL > create tablespace TEST_TS3 datafile '+ DATA_DG' size 20 G
autoextend on
MaxSize 32767 m
Local extended management
single 4 M size
Auto segment space management;
Created tablespace.
SQL >
SQL > select tablespace_name, bytes/1024/1024 of dba_Data_Files where nom_tablespace = 'TEST_TS3 ';
BYTES/1024/1024 NOM_TABLESPACE
------------------------------ ---------------
TEST_TS3 20480
Backup tablespace TEST_TS3 that is not used by all segments (empty)
RMAN > backup tablespace TEST_TS3 format='/u05/RMAN_BKP/TBS_%U_%T.rmbk' tag = TEST_TS3_BKP;
From 18 February 16 backup
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 4941 instance = HMAGPRD2 = DISK device type
channel ORA_DISK_1: starting full datafile from backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
Enter a number of file datafile = name=+DATA_DG/hmagprd2/datafile/test_ts3.413.904152141 00144
channel ORA_DISK_1: starting piece 1-18 February 16
channel ORA_DISK_1: finished piece 1-18 February 16
piece handle=/u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk tag = TEST_TS3_BKP comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup finished on 18 February 16
$
$ ls - lh /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk
-rw - r - 1 oracle oinstall 4.1 M 18 Feb 17:29 /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk
But in the world of real output, size of the RMAN backups seems to be much higher.
The following production DB is 27.5 terabytes in size as evidenced by the physical layer (DBA_DATA_FILES. Column of BYTES)
SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_Data_Files;
BYTESGB
----------
27885.3252
But at the level of the logic layer, the used space is only 16.5 TB as evidenced by DBA_EXTENTS. BYTES column
SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_extents.
BYTESGB
----------
16621.316
But the size of RMAN backup came to 20 terabytes , become almost 4TB that space consumed at the level of the logical layer (DBA_EXTENTS. BYTES).
Why is this?

RMAN jump blocks that have never been used. If a block has been used in the past, it will be included in the same backup if currently is not used:

https://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmcncpt.htm

Compression for backup sets

When you back up the data files of backup sets, RMAN can use unused block compression to skip blocks of data file. RMAN always ignores blocks that have never been used. Under certain conditions, which are listed in the BACKUP AS BACKUPSET entry in reference Oracle database backup and recovery, RMAN also ignores the blocks that are not currently used. Data file backup sets are generally smaller than copies of data file and take less time to write. Compression of the unused block is fundamental to how RMAN writes files of data in backup items and cannot be disabled.

Restore from different database Rman backup RMAN
Hello world

I'm practicing Rman, so I request that the way to restore the rman backup in a different database.

For example:

1. I have backup Rman of DB1 to level 0 and level 1 cumulative data base more archievelog

2. I need to import or restore the backup Rman of DB1 to a different database DB2.

What is the procedure to make the queries above. Please anyone one help out me.

I use oracle 10g r2 running in windows server 2003.

Thanks in advance.
flanged wrote:
Hello world

I'm practicing Rman, so I request that the way to restore the rman backup in a different database.

For example:

1. I have backup Rman of DB1 to level 0 and level 1 cumulative data base more archievelog

2. I need to import or restore the backup Rman of DB1 to a different database DB2.

What is the procedure to make the queries above. Please anyone one help out me.

I use oracle 10g r2 running in windows server 2003.

Thanks in advance.

If you want to restore the database from one node to the node of dfiferent, you can follow below url

http://mohamedazar.WordPress.com/2011/03/13/disaster-recoveryrestore-database-from-one-server-to-another-server-when-different-location/

but you couldnot able to restore the database backup entire rman in another database instance struture.

RMAN cumulative problem
I use a backup strategy incremental cumulative rman.

I thought that each cumulative backup level 1 more level 0 who was caught before it, would be enough to restore the database.

When I run the script that removes the old backupsets (former level1s) and the previous archivelogs. It does not remove
the previous level1, so in the end, the use of the disc of the location of the rman, is growing rapidly.

In this connection, there is an explanation
http://www.ora00600.com/scripts/RMAN/Cumul...al_backups.html.

So I would like to know, if my experience is correct, and if you want to restore a cumulative 1 level, rman will not erase the previous backupsets level1 because they may be needed during recovery.

Thanks in advance for your answer.
That behavior is expected, it is related to the point-in-time recovery. You have 1 redundancy, it must be possible to go back in time to the last backup backups + required level 1 to level 0.
Let's say you make a level 0 backup Sunday, then Monday for cumulative level 1 backups Saturday. Now, you decide, for example, Friday, you will need to go back to Tuesday. To do this, you definitely need archivelogs and the previous incremental backups. You cannot use the last cumulative backup from Thursday. After another level 0 backups, previous level 0 and all backup level 1 next + archivelogs become obsolete - but not before.

Werner

backup rman design database with phsical ensures

Hello
12 c database, after physical expectation is created, I need backup rman configuration,
The goal is: a) backup of database b) remove archivelogs that have been backed up, free up space FRA.
Design as below:
1:
in RMAN (primary and standby):
RMAN >
Configure controlfile autobackup on;
set the type of backup device type disk compressed backupset;
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

2: primary school:
RMAN > CONFIGURE RETENTION POLICY to the 5 DAY RECOVERY WINDOW;
3: in priamry, turn on track changes to block
4: primary, implemented since rman level 0 (full backup) on Sunday.
5: in the primary, the installation program rman level 1 backup from Monday to Saturday.
6: primary, set up since rman "save archive backup delete them all obsolete" every hour;
questions here:
1. as in step 5, for the protection of the o and delete archivelog, the script using:
Run {}
allocate channel d1 type disk;
SQL 'alter system archive log current';
overlap archivelog all;
backup AS COMPRESSED BACKUPSET archivelog all delete them all input;
output channel d1;
}
I wonder if ' archivelog all delete all entries "will delete archivelog which was not taken on the eve of the database and broken standby database
(hanging and out-of-sync with primary)... it is a concern, is that possible?
2. If the primary database crashed, failover to standby mode, then restore/recovery primary, switch back to the primary, this design is just? If you have any good suggestions, please let me know.
(to put it simply, I don't want to full/incremental backup to install standby, primary server CPU is good enough)
Thank you very much!

A few brief notes worth a visit:

Based on Oracle 11 g Data Guard for the backup database and restore

http://www.databasejournal.com/features/Oracle/article.php/3830766/leveraging-Oracle-11g-Data-Guard-for-database-backup-and-recovery.htm

Standby database using RMAN

http://Arup.blogspot.com/2007/07/standby-database-using-RMAN.html

Best regards

mseberg

Help remove backups rman (delete the repository)

Hi all.
I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.

I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.

(1) disable mode archive.

(2) a clean shutdown and take a backup to cold.

(3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).

(4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.

(5) turn on archiving

(6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.

Help is requested on the best way to clean all the backups (3).

I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.

So which is the best way easier and faster? Will delete backup include the archive logs?

Thanks in advance. Luis!

myluism wrote:

Can I still use them?

I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.

Why is backup RMAN 2 TB DB still 2 TB when expdp dump was only 600 MB?

RDBMS version: 11.2.0.3/Oracle Linux 6.2
We took a RMAN of below mentioned DB Backup.

Since DBA_SEGMENTS showed 2 TB, I thought that RMAN backup size will be half of this IE. 1 TB. But the size of the RMAN backups was 1.95 TB!
expdp full DB was only 600 MB!
SQL > select sum (bytes/power (1024,3)) of dba_segments;
SUM (BYTES/POWER (1024,3))
------------------------
2056.27728
SQL > select sum (bytes/power (1024,3)) sumbytesGB, sum (maxbytes/power (1024,3)) sumMaxBytes of dba_data_files;
SUMBYTESGB SUMMAXBYTES
---------- -----------
5451 427.998978

SQL > col file_name format a75
SQL > set 300 pages
SQL > select file_name, bytes/power (1024,3) bytesGB, maxbytes/power (1024,3) from dba_data_files;
FILE_NAME BYTESGB MAXBYTES/POWER (1024,3)
--------------------------------------------------------------------------- ---------- ----------------------
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_01.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_02.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_03.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_04.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_05.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_06.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_07.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_08.dbf 20 0
+CMS_DATA/bcmsprd/datafile/users.271.803502221 6 31.9999847
20 20 +CMS_DATA/bcmsprd/datafile/undotbs1.265.803502221
+CMS_DATA/bcmsprd/datafile/SYSAUX.272.803502221 10 31.9999847
+CMS_DATA/bcmsprd/datafile/system.260.803502221 10 31.9999847
20 20 +CMS_DATA/bcmsprd/datafile/undotbs2.261.803502407
20 20 +CMS_DATA/bcmsprd/datafile/undotbs3.267.803502407
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_09.dbf 20 0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_10.dbf 20 0
< snipped >

RMAN backs up all blocks of formatting - even if the lines have been removed and the blocks are "logically empty." expdp, obviously, do not save deleted rows. Similarly, if you have created a table, and then later he truncated, the blocks are formatted and be candidates for RMAN backups. Truncated tables would be "empty" and would result in 0 rows exported.

So, you will have this problem if you have deleted a large number of lines and/or issued truncates.

Hemant K Collette

The front last backup RMAN delete file even if redundancy on 3 days
Dear Oracle gurus

My environment
Node 2 11g R2 Cluster with ASM
Database 11.2.0.3.0

I got to know that file below is delete by RMAN even if redundancy on 3 days
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed

can you please provide a reason or recommendations to correct the backup configuration

=========Before Backup========================================
917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
* 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
===========================================================================

===================After Backup========================================================
-rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
==================================================================================

Configuration of RMAN
bash-$3.2 rman target /.

Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013

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

connected to target database: ORCL (DBID = 3171721304)

RMAN > show all.

using the control file of the target instead of recovery catalog database
RMAN settings for database with db_unique_name ORCLDR are:
CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default

RMAN > exit
=========================================================================================
RMAN Full Backup Script
RMAN level 0
#! / bin/bash
. /Home/Oracle/.bash_profile
logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
run
{
allocate channels ch1 type disk maxpiecesize = 1024 M;
allocate channel ch2 type disk maxpiecesize = 1024M;
database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
include current controlfile more archivelog delete all entries
tag 'datafile_full ';
}
delete noprompt obsolete;
EXIT;
EXPRESSIONS OF FOLKLORE
=========================================================================================

Backup logs
-bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log

Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013

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

connected to target database: ORCL (DBID = 3171721304)

RMAN >
RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
using the control file of the target instead of recovery catalog database
allocated channel: ch1
channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type

allocated channel: ch2
channel ch2: SID = 5 = device type ORCLdr2 = DISK instance

From backup may 19, 13
Current archived log
archived journal of wire 1 to jump with sequence 84; already saved
skip the journal archived thread 2 with sequence 79; already saved
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from 3 to 19 May 13 piece
channel ch2: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:01:10
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
channel ch1: finished part 3 to 19 May 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:01:25
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
Backup finished on 19 May 13

From backup may 19, 13
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
channel ch1: from room 1 to May 19, 13
channel ch2: start the incremental level 0 datafile backup set
channel ch2: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:22
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
channel ch2: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: complete set of backups, time: 00:00:22
including the current control in the backup set file
channel ch1: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:01
Backup finished on 19 May 13

From backup may 19, 13
Current archived log
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:00:01
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:00:01
channel ch2: archived deletion or newspapers
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
Backup finished on 19 May 13

From control file and SPFILE Autobackup 19 May 13
room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
File control finished and Autobackup SPFILE to 19 May 13
output channel: ch1
output channel: ch2

RMAN >
RMAN >
RMAN retention policy apply to the order
RMAN retention policy is set to 3 redundancy
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
Remove the following obsolete backups and copies:
Making key time filename/handle type
-------------------- ------ ------------------ --------------------
8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
Game save 40 9 May 13
Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Save game 39 may 9, 13
Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Backs up the entire 42 9 May 13
Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
Backs up the entire 43 9 May 13
Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
Save game 46 may 10, 13
Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
Game backup 45 may 10, 13
Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
Save game 47 10 May 13
Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 48 may 10, 13
Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 50 10 May 13
Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
Backs up the entire 51 may 10, 13
Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
Backs up the entire 54 may 11, 13
Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
Save game 53 may 11, 13
Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
Save game 55 may 11, 13
Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 56 may 11, 13
Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 58 may 11, 13
Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
Save game 59 may 11, 13
Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
Backs up the entire 62 12 May 13
Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
Save game 61 12 May 13
Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
Save game 77 14 May 13
Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
Game backup 101 16 May 13
Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
Backs up the entire 114 18 May 13
Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
20 objects deleted

RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
RMAN-06208: status do not match. Use the OVERLAP command to set status
RMAN-06210: list of relevant objects
RMAN-06211: =.
RMAN-06212: filename/Type object Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup

RMAN >
RMAN >

Complete recovery manager.
-bash - $3.2

Concerning
Hitgon

Published by: hitgon on May 20, 2013 02:09

Published by: hitgon on May 20, 2013 02:15
It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.

Hemant K Collette

Size of backup RMAN cumulative level 1.

Similar Questions

Compression for backup sets

Maybe you are looking for