RMAN-08137: WARNING: archived log not deleted, needed for standby

Flash recovery area full? Backups fail in delete archives after backup?
with this error

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

The root problem is in standby or oracle streams not working properly
you should check first if you can investigate because the problem not yet rise
a urgent service problem with any outage of resources.

This post isn’t inteded to solve stream or standby problem, is about ways of force
archive log files deletion for solve a urgent issue.
If is a standby you can check in primary v$archived_log if you have
those files with APPLIED=’NO’

Cause: The archive logs seems that it is not yet applied in the standby database.
Select sequence# , applied from v$archived_log;

Action: Check the standby database and apply the logs manually and the start the deletion process.
I can delete the archive logs by force using the below command.

Only if you have a problem for solve fast you can do two things, before take care of have this archives in backup:

1) rman> delete noprompt force archivelog all;

2) delete the files and do a crosscheck and delete expired

crosscheck archivelog all;
DELETE EXPIRED ARCHIVELOG ALL;

Best for not lose archives wich arent applied in standby is change rman configuration that table to delete the archivelogs.
CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters:

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters are successfully stored

RMAN-08591: WARNING: invalid archived log deletion policy
Now you can delete withput problem or eliminate a file not shipped to standby:

RMAN> delete noprompt archivelog all;
RMAN> crosscheck archivelog all;

And next is seting back the old configuration.

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY CLEAR;
RMAN> Show all;

Advertisements

Comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s