Solved

Oracle rman archivelog backups failing after dataguard switchover

Posted on 2010-11-16
8
1,390 Views
Last Modified: 2012-05-10
We did a dataguard switchover this past weekend for several of our databases.  We then began running the rman backups from the new primary server.  The archive log backups are failing on some of the switched databases.  The problem seems to involve the archive logs created on the original primary between the time of the last archivelog backup on that server and the swtichover. Here's what happens:

The first archive log backup reported success, and included the interim-period archive logs described above
.
The next couple of backups failed with a message saying it can't find the first of the interim-period archive logs:
RMAN-03002: failure of backup command at 11/14/2010 08:36:18
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/app/oracle/admin/webp23/arch/webp23_1_561633885_118314.arc
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
So I copied them over from the original server.  The next backup was happy, and included the interiim-period archive logs.
The next one failed with the same message above.  So I copied them over again.  Went through this cycle a couple of times before I realized the log files it was missing were the same ones over and over.  (It was a hectic morning).
So I copied them over one more time and ran the RMAN CATALOG command:  catalog archivelog 'blah1','blah2'...
Same results:  the first archive log backup was happy, the next failed with the same problem.  I'm running a crosscheck now, but I don't see how that's going to fix it.
Here, finally, is my question:  How can I make future archive log backups succeed?

If anyone has had the patience to read through this rambling tale, I could sure use some help.  Thanks.
0
Comment
Question by:cholman
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
8 Comments
 

Author Comment

by:cholman
ID: 34149490
Anybody?  
0
 

Author Comment

by:cholman
ID: 34150380
I just needed to folllow the 'catalog' with:


crosscheck copy of archivelog all;

Everything is  OK now.
0
 

Author Comment

by:cholman
ID: 34157433
Thanks.

The above solution fixed the archive log backup problems with our two 10.2.0.3 databases, but we're still having the problem with tthe two 10.2.0.4 db's.  I don't know if the version makes a difference or not, just thought I'd toss it out there.  

0
Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

 
LVL 48

Expert Comment

by:schwertner
ID: 34158109
I think this means that you have to check the Oracle parameters pointing to the archivelog destinations.
They are in  LOG_ARCHIVE_DEST parameters. Check also the name convention, name convention and all other parameters in regard to archive log process.
Check also the names of the files, directories, read writes.
0
 

Accepted Solution

by:
cholman earned 0 total points
ID: 34158172
Thanks, schwertner.  I"ve checked all that and it looks good.  I think I have the solution:  I was putting a copy of the "missing" archive logs in place (copying over from the original primary/current standby), then running 'catalog archivelog', then doing the 'crosscheck copy of archivelog all;'.  

Instead of doing all that, if I just follow the failed archivelog backup with a "crosscheck copy of archivelog all;", the backups begin to succeed.

At least that's what I think is happening.  I'll post again when I'm sure of it.
0
 

Author Comment

by:cholman
ID: 34158857

It worked!  We've had two successive successful archivelog backups without manual intervention.

The key was to "crosscheck copy of archivelog all;" with the interim-period logs NOT present on the server hosting the now-primary databases.  

0
 

Author Closing Comment

by:cholman
ID: 34186429
After a lot of fumbling around, I finally solved my own problem.  I gave the solution a 'c' because it documents a lot of that fumbling.  It's not straightforward.  But by reading the entire thread, the answer is there.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configuring and using Oracle Database Gateway for ODBC Introduction First, a brief summary of what a Database Gateway is.  A Gateway is a set of driver agents and configurations that allow an Oracle database to communicate with other platforms…
This post first appeared at Oracleinaction  (http://oracleinaction.com/undo-and-redo-in-oracle/)by Anju Garg (Myself). I  will demonstrate that undo for DML’s is stored both in undo tablespace and online redo logs. Then, we will analyze the reaso…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This video shows how to recover a database from a user managed backup

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question