Home » RDBMS Server » Backup & Recovery » RMAN backup problem-UNUSUAL (Oracle 9i, WIN2003 server)
RMAN backup problem-UNUSUAL [message #382294] Wed, 21 January 2009 16:26 Go to next message
dbanukesh
Messages: 96
Registered: November 2008
Location: London
Member

Dear all,

I am facing an unusual problem. I had accidently deleted one archivelog file due to which my RMAN hot backup and archivelog backup was failing. today i have taken RMAN full cold backup and try to run archive job but it is failing as it is still asking the old archivelog before cold backup. As par my understanding if i have taken full cold backup, it has all changes applied. Please correct me if i am wrong here.

Quick response will be highly appreciated.

Thanks in advance!
Nukesh
Re: RMAN backup problem-UNUSUAL [message #382295 is a reply to message #382294] Wed, 21 January 2009 16:28 Go to previous messageGo to next message
dbanukesh
Messages: 96
Registered: November 2008
Location: London
Member

This is archive log failure log..

-----------------------------------------------------------------
released channel: ch01
released channel: ch02
released channel: ch03
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/21/2009 22:15:49
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file H:\ORACLE\ORADATA\SIEB7PRD\ARCHIVE\ARC55775.001
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.

RMAN>

Recovery Manager complete.
#
--------------------------------------------------------
ARC55775.001 log is older log before cold backup.

what are the other solution to rectify this problem?

Cheers
Nukesh
Re: RMAN backup problem-UNUSUAL [message #382300 is a reply to message #382295] Wed, 21 January 2009 17:56 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10672
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
Nothing unusual. How will RMAN know that you messed with the archived log?
Always please search the forum before posting. THis is been frequently asked.
try this
RMAN> crosscheck archivelog all;


You can either manually uncatalog the file
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint008.htm#i1006545
or
catalog it again.

catalog archivelog 'full_path_tofile';



Re: RMAN backup problem-UNUSUAL [message #382303 is a reply to message #382295] Wed, 21 January 2009 19:04 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
In addition to what Mahesh indicated, after you run the crosscheck, you should run the following:

RMAN> delete noprompt expired archivelog all;
Re: RMAN backup problem [message #382441 is a reply to message #382294] Thu, 22 January 2009 05:41 Go to previous messageGo to next message
dbanukesh
Messages: 96
Registered: November 2008
Location: London
Member

Thanks Ebrian and Mahesh for your help. I crosschecked all archivelogs and ran 'delete noprompt expired archivelog all;' command. Backup is now running smoothly. I recently started working on RMAN and improving on this area.

If we take cold backup, it has all previous changes applied on database.It should ask archivelog after cold backup as recovery catalog has information.

But for my understanding, can u tell me why we manually do above solution. In some previous cases i took cold backup and ran archive backup and it ran successfully. so bit sceptical about this.

Thanks Again!!
Nukesh
Re: RMAN backup problem [message #382471 is a reply to message #382441] Thu, 22 January 2009 07:59 Go to previous message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
As Mahesh indicated, it would appear that someone/something manually deleted the archivelogs from the filesystem. The archivelogs should not be deleted with an O/S command, however they should be managed by RMAN DELETE.
Previous Topic: How to Recover the Drop table in 9i
Next Topic: Backup Policy
Goto Forum:
  


Current Time: Sun Dec 11 08:13:30 CST 2016

Total time taken to generate the page: 0.10904 seconds