RMAN-08137: WARNING: archive log not deleted as it is still needed

Admin — Thu, 04 Jun 2009 16:21:16 GMT

Hi,

I'm getting the following error message everytime I do a log backup or even a hot backup along with archive logs.

My configuration is Oracle 10gR2 with a Physical Standby Database.

I appreciate the error message and Oracle states that this is an informational message only, however, our monitoring system picks this up and it sends out alerts unnecessarily. Which annoys me because I have to wake up in the middle of the night.

Sample:

archive log filename=/u01/oradba/admin/PROD/arch_1/PROD_1_178007_647537618.arc recid=425136 stamp=688505501
channel d4: finished piece 1 at 02-JUN-09
piece handle=/u01/oradba/admin/PROD/rman_diskbackups/al_PROD_27273_1_688506356 tag=TAG20090602T194548 comment=NONE
channel d4: backup set complete, elapsed time: 00:00:02
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u01/oradba/admin/PROD/arch_1/PROD_1_178010_647537618.arc thread=1 sequence=178010
Finished backup at 02-JUN-09

This is why my rman backup script is doing :

replace script oracle_prod_log_disk{
allocate channel d1 type DISK;
backup
tag log_backup_PROD
format '/u01/oradba/admin/PROD/rman_logdiskbackups/al_%d_%s_%p_%t'
(archivelog like '/u01/oradba/admin/PROD/arch_1/%' delete input skip inaccessible);
}

To fix this ....after finding out that there is a known bug in 10gR2, I decided to follow what the Data Guard Do***ent says. I hope this helps you guys out. here is what I did:

I changed my script to do the following:

run {
allocate channel d1 type DISK;
backup
tag log_backup_PROD
format '/u01/oradba/admin/PROD/rman_logdiskbackups/al_%d_%s_%p_%t'
(archivelog UNTIL TIME 'sysdate-1/24' not backed up 1 times);
delete noprompt archivelog UNTIL TIME 'sysdate-2/24' backed up 1 times to device type disk;
}

Basically I got rid of the delete input part. That is what was the driver behind that message. Basically I'm backing up all archive logs that are older then 1 hour and deleting those that are backed up and older then 2 hours. I could have changed this to older then 24 hours but there are times where the business decides to do heavy load and fills up my archive log destination. This way I did it like this.

I hope this helps.

Good luck.

Thanks,

FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals / Oracle Forum / RMAN - Error Codes / RMAN-08000-08999 / RMAN-08137: WARNING: archive log not deleted as it is still needed / Latest Posts

RMAN-08137: WARNING: archive log not deleted as it is still needed