Rman won't delete archivelogs

Hello,
I have an oracle 11.2.0 database which i backup nightly using rman.  This database used to have a standby database, which recently was removed from the system.  I have deferred log shipping to this destination.  

When i run an rman backup though i get the following message:

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

Open in new window


I was wondering how i can get RMAN to delete archive logs, and stop saving them for my non-existent standby database.


Thank You
LVL 4
Alex MatzingerDatabase AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

johanntagleCommented:
Encountered something similar before, where I just used the FORCE option to delete the archive logs.  But I would also like to know the permanent fix for this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Geert GOracle dbaCommented:
in rman run
show all;
to see all the parameters
0
Geert GOracle dbaCommented:
the script for deletion may also include a option
what command do you give rman to delete archivelogs ?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Richard OlutolaConsultantCommented:
Check your persistent RMAN configuration and look for
CONFIGURE ARCHIVELOG DELETION POLICY and ensure it is set to NONE.

So it should look like:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

R.
0
Alex MatzingerDatabase AdministratorAuthor Commented:
i've checked the show all command, and it shows this:

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

The command i use to delete the logs is this:

  backup
     as compressed backupset
     skip inaccessible
     archivelog until time 'sysdate-2'
     format '/u07/oraflash/ORATEST/ORATEST.arc_%U.rman'
    delete input;

Open in new window

0
Richard OlutolaConsultantCommented:
Have you manually deleted any archivelogs? If so, you'll need to run crossckeck archivelog all;
Subsequently, try the backup command again and see if it deletes the appropriate copies.

R.
0
Alex MatzingerDatabase AdministratorAuthor Commented:
Yes, i have deleted the archive logs by hand.  I also have been running a crossckeck archivelog all; whenever i do this.  Even after crosschecking the logs, they still not being deleted by rman.
0
Richard OlutolaConsultantCommented:
Have you tried running things on the command line rather than in a run block?

Try the following:

Now that you've run the crosscheck command then try this:
delete noprompt expired archivelog all;

BTW, did you get any messages when you ran the crosscheck command?

R.
0
MikeOM_DBACommented:
Better try this:
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
CHANGE ARCHIVELOG ALL CROSSCHECK;

Open in new window

:p
0
Alex MatzingerDatabase AdministratorAuthor Commented:
I've run the cross check, and got the standard, these logs failed, and then the i found these logs that it gives when you crosscheck.

I'm going to try and add in delete force input into my backup script tonight, and hope this solves the issue.  I was able to delete them using delete force from the command line.

I've also opened up an SR with oracle to try and find a true solution for getting rman to forget about a standby database.
0
MikeOM_DBACommented:
Notice I posted:
CHANGE ARCHIVELOG ALL CROSSCHECK;
And not:
CROSSCHECK ARCHIVELOG ALL;
Which are different.
0
Alex MatzingerDatabase AdministratorAuthor Commented:
This problem worked itself out (a mysterious "oh it just started working again issue").  We tried several parameter changes as suggested by oracle, but they didn't seem to work, and we were directed to change them back to default, then it started working, not sure how, thanks to everyone for your suggestions
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.