Accidently Deleted Archive Logs

Hi all,
I'm no expert and have a poor knowledge in Oracle 9i and I look forward for a possible solution from all of you.
Previously, we had our Oracle 9.0.2 database running in NOARCHIVELOG mode. Last week, we have changed it to ARCHIVELOG mode and we haven't done any backup since we're still waiting for our vendors to set up the backup software.
As of today, we've noticed that the archive logs were increasing, and resulted in a low disk space. We have moved the archive logs to another location as a backup option, in order to free up the disk space. While doing so, we have accidently deleted a few portion of the archive logs. Following are the archive logs (both available and missing) since the DB was switched to ARCHIVELOG mode :
ARCH05507.LOG ~ ARCH05915.LOG <-- AVAILABLE
ARCH05916.LOG ~ ARCH05926.LOG <-- MISSING!!!
ARCH05915.LOG ~ onwards <- AVAILABLE
We would like to re-locate the database to a different server. My questions are as follows :
1. Is it possible to recover the database although there are a few missing archive log files?
2. I've heard about incomplete recovery, can i use this option to do so?
3. What is the worst case scenario, or possible option that we could use?
4. Is there any way to disregard the missing archive logs, and apply to the database using only the available archive logs?
Please help. Thank You
Sathyan Ram

Ivan,
As you mentioned, to perform a cold backup, you will need to shutdown the database, and that the same concept can be applied when changing from archivelog to noarchivelog. But I would like to know what are the consequences I will be facing if I do so? Will there be data consistency issues? Will the database fail to open during the next clean restart?
As for your second question, we assumed that changing no noarchivelog will make it easier for us to re-locate the database to another server, i.e. the process of setting up the database will be much easier. Then we can switch the DB back to archivelog.
The actual problem I'm facing at the moment is that, after we encountered the missing archive logs (i.e. Monday), we're not in a situation to perform a COLD backup because of our corporate restrictions. Either way, I'm not confident performing a HOT backup, because I haven't got any experience, neither do I have any test database to perform such tasks. The only possible time we could perform a COLD backup is on this weekend (Saturday/Sunday), but I believe this will be lead to a total of 5 days of data loss. (The missing log files started on Monday, and production ends on every Friday)
I've came across an article (Terry Sutton, Database Sepcialists, Inc.) regarding on how to recover an Oracle Database with Missing Archived Logs. But this method is totally not supported/recommended by Oracle, and will lead to database inconsistency issues. Considering my situation, will I be able to use this method instead?
Thank You.
Sathyan Ram

Similar Messages

How to delete archive log files from ASM through Grid Control

Hi
Anybody suggest me how to delete archive log files from ASM through Grid Control.
Thanks

It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
~ Madrid
http://hrivera99.blogspot.com/

How to delete archive log on standby site

hi
i configured dataguard on 10g. could anyone suggest how to delete archived log on standby site..

Hi,
There is no automatic feature out-of-the-box but you have the following views:
1) Shows archive logs transfered:
select sequence#, first_time, next_time from v$archived_log order by sequence#;
2) Shows archive logs applied:
select sequence#, archived, applied from v$archived_log order by sequence#;
If you see your archivelogs applied you can safely remove archive log files from your disk. It is your decision if you keep or delete them completely.

How to delete archive logs on the standby database....in 9i

Hello,
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
thanks,
C.

We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.From 10g there is option to purge on deletion policy when archives were applied. Check this note.
*Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]*
Still it is on 9i, So you need to schedule RMAN job or Shell script file to delete archives.
Before deleting archives
1) you need to check is all the archives are applied or not
2) then you can remove all the archives completed before 'sysdate-2';
RMAN> delete archvielog all completed before 'sysdate-2';
As per your requirement.

Manual delete archived log files

Because we don't have RMAN in our development server, I need to use manual operation to delete all archived logs. Is my procedure correct and safe?
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE NOARCHIVELOG;
EXITRun OS command to manually delete archived log files:
rm /oradata/arch/*
Login to sqlplus
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE ARCHIVELOG;
STARTUP OPENThanks!

linuxos wrote:
Oh I suppose RMAN need to be configured somthing before use. I tried it, and find no pre-requisite is required. Thanks!
If the archives are deleted manually in open mode, how can Oracle match the archived logs' retention policy? Does Oracle store the archived logs in data dictionary?While you can delete archivelogs manually any time you want, you should let rman manage them with appropriate rman commands, preferably in a script that you schedule for regular execution.
Some of your questions lead me to question if you understand that archivelogs are not actively open by the database, and they technically are not part of the database. They are simply a series of "offline" copies of the online redo logs. They are written to once, when an online redo is being archived, then they just sit there until needed for a recovery.

Is RMAN only way to take backup and delete Archive Logs?

On primary db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
On Physical standby db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
Thanks

No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
RMAN make this very simple :
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
Best Regards
mseberg

How can we delete archive log files from OEM

Hi,
I took backup of the archive log file and deleted it at OS level but in it is not reflecting in the EM can any one tell me how to delete archive log files from OEM.
any help will be appreciated.
Regards,
Ashraf

This link?
http://download-west.oracle.com/docs/cd/B10501_01/em.920/a96670/ch_backp.htm#26936

Unable to delete archive log.

Hi,
Our database server's archive log destination is full,but after running
backup archivelog all delete input;
it's taking archive log backup,but not deleting archivelogs.
Could you suggest me what is the reason.

RMAN> backup archivelog all delete input;
Starting backup at 17-DEC-10
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=155 recid=422 stamp=737092752
input archive log thread=1 sequence=156 recid=425 stamp=737156432
input archive log thread=1 sequence=157 recid=428 stamp=737257293
input archive log thread=1 sequence=158 recid=431 stamp=737322402
input archive log thread=1 sequence=159 recid=434 stamp=737389991
input archive log thread=1 sequence=160 recid=437 stamp=737408597
input archive log thread=1 sequence=161 recid=440 stamp=737476660
input archive log thread=1 sequence=162 recid=443 stamp=737542384
input archive log thread=1 sequence=163 recid=446 stamp=737634615
input archive log thread=1 sequence=164 recid=449 stamp=737658567
input archive log thread=1 sequence=165 recid=452 stamp=737726432
input archive log thread=1 sequence=166 recid=455 stamp=737827094
input archive log thread=1 sequence=167 recid=456 stamp=737860748
input archive log thread=1 sequence=168 recid=464 stamp=737980097
input archive log thread=1 sequence=169 recid=461 stamp=737980094
input archive log thread=1 sequence=170 recid=467 stamp=737980099
input archive log thread=1 sequence=171 recid=470 stamp=737980425
input archive log thread=1 sequence=172 recid=472 stamp=737981508
input archive log thread=1 sequence=173 recid=474 stamp=737985385
channel ORA_DISK_1: starting piece 1 at 17-DEC-10
channel ORA_DISK_1: finished piece 1 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_1_1 comment=NONE
channel ORA_DISK_1: starting piece 2 at 17-DEC-10
channel ORA_DISK_1: finished piece 2 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_2_1 comment=NONE
channel ORA_DISK_1: starting piece 3 at 17-DEC-10
channel ORA_DISK_1: finished piece 3 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_3_1 comment=NONE
channel ORA_DISK_1: starting piece 4 at 17-DEC-10
channel ORA_DISK_1: finished piece 4 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_4_1 comment=NONE
channel ORA_DISK_1: starting piece 5 at 17-DEC-10
channel ORA_DISK_1: finished piece 5 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_5_1 comment=NONE
channel ORA_DISK_1: starting piece 6 at 17-DEC-10
channel ORA_DISK_1: finished piece 6 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_6_1 comment=NONE
channel ORA_DISK_1: starting piece 7 at 17-DEC-10
channel ORA_DISK_1: finished piece 7 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_7_1 comment=NONE
channel ORA_DISK_1: starting piece 8 at 17-DEC-10
channel ORA_DISK_1: finished piece 8 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_8_1 comment=NONE
channel ORA_DISK_1: starting piece 9 at 17-DEC-10
channel ORA_DISK_1: finished piece 9 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_9_1 comment=NONE
channel ORA_DISK_1: starting piece 10 at 17-DEC-10
channel ORA_DISK_1: finished piece 10 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_10_1 comment=NONE
channel ORA_DISK_1: starting piece 11 at 17-DEC-10
channel ORA_DISK_1: finished piece 11 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_11_1 comment=NONE
channel ORA_DISK_1: starting piece 12 at 17-DEC-10
channel ORA_DISK_1: finished piece 12 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_12_1 comment=NONE
channel ORA_DISK_1: starting piece 13 at 17-DEC-10
channel ORA_DISK_1: finished piece 13 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_13_1 comment=NONE
channel ORA_DISK_1: starting piece 14 at 17-DEC-10
channel ORA_DISK_1: finished piece 14 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_14_1 comment=NONE
channel ORA_DISK_1: starting piece 15 at 17-DEC-10
channel ORA_DISK_1: finished piece 15 at 17-DEC-10
piece handle=D:\RMAN\BACKUP\0MLVPGRB_15_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:03:41
channel ORA_DISK_1: deleting archive log(s)
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00155.001 recid=422 stamp=737
092752
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00156.001 recid=425 stamp=737
156432
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00157.001 recid=428 stamp=737
257293
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00158.001 recid=431 stamp=737
322402
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00159.001 recid=434 stamp=737
389991
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00160.001 recid=437 stamp=737
408597
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00161.001 recid=440 stamp=737
476660
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00162.001 recid=443 stamp=737
542384
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00163.001 recid=446 stamp=737
634615
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00164.001 recid=449 stamp=737
658567
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00165.001 recid=452 stamp=737
726432
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00166.001 recid=455 stamp=737
827094
archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00167.001 recid=456 stamp=737
860748
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00168.001 recid=464 stamp=737
980097
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00169.001 recid=461 stamp=737
980094
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00170.001 recid=467 stamp=737
980099
archive log filename=D:\ORANT\ARCLOG3\REDO03.LOGARC00171.001 recid=470 stamp=737
980425
archive log filename=D:\ORANT\ARCLOG2\REDO02.LOGARC00172.001 recid=472 stamp=737
981508
archive log filename=D:\ORANT\ARCLOG1\REDO01.LOGARC00173.001 recid=474 stamp=737
985385
Finished backup at 17-DEC-10
Starting Control File and SPFILE Autobackup at 17-DEC-10
piece handle=D:\RMAN\BACKUP\C-1738882432-20101217-02 comment=NONE
Finished Control File and SPFILE Autobackup at 17-DEC-10

When to delete Archive Log files ? and is safe to delete ?

Hi all,
I have a question, my DB is running in Archive Log mode and is growing day by day, so should I delete archive log files and where i find that my which files are old and how to delete theses files, for info I also take full RMAN and export backup regularly .
abbas

Well, if you're not comfortable with Backup and Recovery principles, i'd advise you to first read TFM: Backup and Recovery Concept(click) for you data safety's sake.
Anyway, just to give you a glance at what could happen, immagine suche a situation where your database is made of 5 different datafiles (whatever they are - SYSTEM, SYSAUX, UNDO, ...), controlfiles and online redo logs. If, for example your backup is done in a timeline such as:T0 : Backup datafile F1 and F2
T1 : Backup datafile F2 and controlfile
T2 : Backup datafile F3, F4
T3 : Backup datafile F5
T0' : Backup datafile F1 and F2
T1' : Backup datafile F2 and controlfile
T2' : Backup datafile F3, F4
T3' : Backup datafile F5
...If your server crashes (for example is thrown though the 5th floor window..) in order to make a full recovery, you could proceed multiple ways.
. Restore files from Tx' backups. Then you'd need every archived redo logs created from T0' to now in order to be able to do a full recovery.
. Restore files from backups; T3, T0', T2' and rectreate controlfile. Then you'd need every archived redo log created from T3 (inclusive).
. Restore Tx backup, ...
. Restore ...
and so on.
What's important is that you're at least able to resynch a full-set backup. What I mean is: if you restored "T3, T0', T2' and rectreate controlfile", in order to open the database you'll absolutely need every archived redo log created between T3 and T2' inclusive. If one is missions, you won't be able to open it.
That is the principle. Read the concept book I linked to get more infos.
Regards,
Yoann.

How to delete archive log by RMAN.

Hi All,
How to delete archive log by RMAN and what is the difference between
delete all input & all delete input in RMAN backup.

plus archivelog all delete inputYou get an error on the syntax.
"PLUS ARCHIVELOG" does not allow the "ALL" keyword.
(See "backupSpecOperand" in the RMAN Documentation of the BACKUP command syntax).
However, "DELETE INPUT" allows the optional "ALL" keyword as in "DELETE ALL INPUT" to delete from all archivelog destinations.
I guess that you have confused the "ALL" keyword in "BACKUP ARCHIVELOG" as being possible in "BACKUP .. PLUS ARCHIVELOG".
"ALL" is allowed in "BACKUP ARCHIVELOG" but not in "BACKUP .. PLUS ARCHIVELOG".
Hemant K Chitale

Delete archive log file

hello,
I am using oracle 10g on linux i want to delete archive log file automaticaly there is any way to do this.or anyone can tell me scripts for do this.ur help regarding this is highly appreciated
Regard,s
Umair Iqbal

Hi,
Can you please let us know why you want to delete the archive log file?
BTW, you can use RMAN to achieve this by taking the backup of archive log and delete the original file using the following command:
Backup archivelog all delete input;Regards

How to delete archive log file

hii,
presently i am working on oracle 10gR2 on windows server 2003.
hard disk drive is almost full.
when i execute this command
"DELETE EXPIRED ARCHIVE LOG ALL";
it give message
"specifies does not match any archive log in the recovery catalog"
how can i delete archive log files ??
Regards
Vaibhav Dixit

these are the list
RMAN> list archivelog all;
List of Archived Log Copies
Key Thrd Seq S Low Time Name
696 1 341 A 25-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_341_758982530.ARC
698 1 342 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_342_758982530.ARC
700 1 343 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_343_758982530.ARC
702 1 344 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_344_758982530.ARC
704 1 345 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_345_758982530.ARC
705 1 346 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_346_758982530.ARC
708 1 347 A 26-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_347_758982530.ARC
710 1 348 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_348_758982530.ARC
712 1 349 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_349_758982530.ARC
714 1 350 A 27-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_350_758982530.ARC
716 1 351 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_351_758982530.ARC
719 1 352 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_352_758982530.ARC
720 1 353 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_353_758982530.ARC
721 1 354 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_354_758982530.ARC
722 1 355 A 28-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_355_758982530.ARC
727 1 356 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_356_758982530.ARC
728 1 357 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_357_758982530.ARC
730 1 358 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_358_758982530.ARC
732 1 359 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_359_758982530.ARC
734 1 360 A 29-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_360_758982530.ARC
736 1 361 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_361_758982530.ARC
738 1 362 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_362_758982530.ARC
740 1 363 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_363_758982530.ARC
741 1 364 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_364_758982530.ARC
742 1 365 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_365_758982530.ARC
743 1 366 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_366_758982530.ARC
744 1 367 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_367_758982530.ARC
745 1 368 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_368_758982530.ARC
746 1 369 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_369_758982530.ARC
753 1 370 A 30-NOV-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_370_758982530.ARC
756 1 371 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_371_758982530.ARC
758 1 372 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_372_758982530.ARC
759 1 373 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_373_758982530.ARC
763 1 374 A 01-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_374_758982530.ARC
764 1 375 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_375_758982530.ARC
767 1 376 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_376_758982530.ARC
768 1 377 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_377_758982530.ARC
770 1 378 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_378_758982530.ARC
772 1 379 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_379_758982530.ARC
774 1 380 A 02-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_380_758982530.ARC
776 1 381 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_381_758982530.ARC
778 1 382 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_382_758982530.ARC
780 1 383 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_383_758982530.ARC
782 1 384 A 03-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_384_758982530.ARC
784 1 385 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_385_758982530.ARC
785 1 386 A 04-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_386_758982530.ARC
788 1 387 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_387_758982530.ARC
790 1 388 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_388_758982530.ARC
791 1 389 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_389_758982530.ARC
792 1 390 A 05-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_390_758982530.ARC
793 1 391 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_391_758982530.ARC
794 1 392 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_392_758982530.ARC
795 1 393 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_393_758982530.ARC
796 1 394 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_394_758982530.ARC
797 1 395 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_395_758982530.ARC
798 1 396 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_396_758982530.ARC
799 1 397 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_397_758982530.ARC
800 1 398 A 06-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_398_758982530.ARC
801 1 399 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_399_758982530.ARC
802 1 400 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_400_758982530.ARC
803 1 401 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_401_758982530.ARC
804 1 402 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_402_758982530.ARC
805 1 403 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_403_758982530.ARC
806 1 404 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_404_758982530.ARC
808 1 405 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_405_758982530.ARC
814 1 406 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_406_758982530.ARC
816 1 407 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_407_758982530.ARC
817 1 408 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_408_758982530.ARC
822 1 409 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_409_758982530.ARC
823 1 410 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_410_758982530.ARC
824 1 411 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_411_758982530.ARC
826 1 412 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_412_758982530.ARC
829 1 413 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_413_758982530.ARC
831 1 414 A 07-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_414_758982530.ARC
839 1 415 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_415_758982530.ARC
841 1 416 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_416_758982530.ARC
843 1 417 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_417_758982530.ARC
844 1 418 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_418_758982530.ARC
848 1 419 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_419_758982530.ARC
849 1 420 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_420_758982530.ARC
850 1 421 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_421_758982530.ARC
851 1 422 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_422_758982530.ARC
852 1 423 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_423_758982530.ARC
853 1 424 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_424_758982530.ARC
854 1 425 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_425_758982530.ARC
856 1 426 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_426_758982530.ARC
862 1 427 A 08-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_427_758982530.ARC
870 1 428 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_428_758982530.ARC
872 1 429 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_429_758982530.ARC
874 1 430 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_430_758982530.ARC
875 1 431 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_431_758982530.ARC
878 1 432 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_432_758982530.ARC
880 1 433 A 09-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_433_758982530.ARC
882 1 434 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_434_758982530.ARC
884 1 435 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_435_758982530.ARC
886 1 436 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_436_758982530.ARC
888 1 437 A 10-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_437_758982530.ARC
890 1 438 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_438_758982530.ARC
891 1 439 A 11-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_439_758982530.ARC
893 1 440 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_440_758982530.ARC
896 1 441 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_441_758982530.ARC
898 1 442 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_442_758982530.ARC
900 1 443 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_443_758982530.ARC
901 1 444 A 12-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_444_758982530.ARC
902 1 445 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_445_758982530.ARC
903 1 446 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_446_758982530.ARC
904 1 447 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_447_758982530.ARC
910 1 448 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_448_758982530.ARC
912 1 449 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_449_758982530.ARC
914 1 450 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_450_758982530.ARC
916 1 451 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_451_758982530.ARC
918 1 452 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_452_758982530.ARC
920 1 453 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_453_758982530.ARC
922 1 454 A 13-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_454_758982530.ARC
924 1 455 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_455_758982530.ARC
926 1 456 A 14-DEC-11 E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ES
PL\1_456_758982530.ARC
RMAN> delete noprompt expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=77 devtype=DISK
specification does not match any archive log in the recovery catalog

Recovery window retention policy deletes archive logs before a backup?

Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.

Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
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 '%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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           1392   15-JAN-14
Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set           1393   15-JAN-14
Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set           1397   16-JAN-14
Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set           1400   17-JAN-14
Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects

Will RMAN delete archive log files on a Standby server?

Environment:
Oracle 11.2.0.3 EE on Solaris 10.5
I am currently NOT using an RMAN repository (coming soon).
I have a Primary database sending log files to a Standby.
My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
Couldn't find the answer in the docs.
Thanks very much!!
-gary

Hello again Gary;
Sorry for the delay.
Why is what you suggested better?
No, its not better, but I prefer to manage the archive. This method works, period.
Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
No. The policy is important.
Having the Primary set to :
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
For Data Guard I would consider getting a copy of
"Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
Also Data Guard forum here :
Data Guard
Best Regards
mseberg
Edited by: mseberg on Apr 10, 2012 4:39 PM

RMAN never deletes archive log backups

Hi all,
I have same problem as some of you have already faced.
I have some instances 10.2.0.4 running un archive log mode.
I take full hot backup daily.
I setup a rman script to backup and delete obsolete backups according to the following policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
and then:
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
CROSSCHECK ARCHIVELOG ALL;
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
crosscheck archivelog all;
delete noprompt archivelog all completed before 'sysdate -2';
DB full backups are being deleted, however archive logs backups are not deleted.
There are no tablespaces in backup or offline mode.
How can I know the reason why some archive log backups are kept ?
Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
Thanks in advance.

Hi Fernando,
This are the ouputpus of the commands:
RMAN> REPORT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
1090 69.65M DISK 00:00:16 23-FEB-11
BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
List of Archived Logs in backup set 1090
Thrd Seq Low SCN Low Time Next SCN Next Time
1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1411 125.43M DISK 00:00:28 24-FEB-11
BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
List of Archived Logs in backup set 1411
Thrd Seq Low SCN Low Time Next SCN Next Time
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1600 164.40M DISK 00:00:37 25-FEB-11
BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
List of Archived Logs in backup set 1600
Thrd Seq Low SCN Low Time Next SCN Next Time
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1829 132.24M DISK 00:00:30 26-FEB-11
BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
List of Archived Logs in backup set 1829
Thrd Seq Low SCN Low Time Next SCN Next Time
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2058 218.03M DISK 00:00:48 27-FEB-11
BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
List of Archived Logs in backup set 2058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2298 205.39M DISK 00:00:45 28-FEB-11
BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
List of Archived Logs in backup set 2298
Thrd Seq Low SCN Low Time Next SCN Next Time
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2546 180.29M DISK 00:00:39 01-MAR-11
BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
List of Archived Logs in backup set 2546
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
2801 85.40M DISK 00:00:19 02-MAR-11
BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
List of Archived Logs in backup set 2801
Thrd Seq Low SCN Low Time Next SCN Next Time
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3058 137.93M DISK 00:00:30 03-MAR-11
BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
List of Archived Logs in backup set 3058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3324 138.96M DISK 00:00:31 04-MAR-11
BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
List of Archived Logs in backup set 3324
Thrd Seq Low SCN Low Time Next SCN Next Time
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3597 178.07M DISK 00:00:39 05-MAR-11
BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
List of Archived Logs in backup set 3597
Thrd Seq Low SCN Low Time Next SCN Next Time
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3835 198.44M DISK 00:00:43 06-MAR-11
BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
List of Archived Logs in backup set 3835
Thrd Seq Low SCN Low Time Next SCN Next Time
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4131 185.94M DISK 00:00:40 07-MAR-11
BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
List of Archived Logs in backup set 4131
Thrd Seq Low SCN Low Time Next SCN Next Time
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4435 161.37M DISK 00:00:35 08-MAR-11
BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
List of Archived Logs in backup set 4435
Thrd Seq Low SCN Low Time Next SCN Next Time
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4745 79.24M DISK 00:00:18 09-MAR-11
BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
List of Archived Logs in backup set 4745
Thrd Seq Low SCN Low Time Next SCN Next Time
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
5270 135.13M DISK 00:00:31 10-MAR-11
BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
List of Archived Logs in backup set 5270
Thrd Seq Low SCN Low Time Next SCN Next Time
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
RMAN>
For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
I'd like to understand why it happens :-)
Thanks a lot,
Regards,
Diego.

Accidently Deleted Archive Logs

Similar Messages

Maybe you are looking for