Home » RDBMS Server » Backup & Recovery » archive logs directory (FRA) accidentally deleted (Oracle 10g 10.2.0.5, RHEL 6.2)
archive logs directory (FRA) accidentally deleted [message #668795] Wed, 14 March 2018 22:46 Go to next message
reym21
Messages: 238
Registered: February 2010
Location: Philippines
Senior Member

Gurus,

Good day.

One of our SysAdm accidentally formatted (Mar. 13 6PM) the flash_recovery_area directory of our production database.
According to him, the command (creation/expansion of mountpoints) he accidentally executed will lose all existing archived logs once the database server is restarted.

We immediately implemented an adhoc RMAN full backup (Mar. 14, 4PM, completed on Mar. 15, 12AM - 1.7TB size)
while he (SysAdm) backup continuously all the files in the said FRA to another directory.
We're also scheduling a database restart this afternoon at 5PM, where we will create/point the FRA to another directory.

Are the archived logs generated from 6PM of Mar. 13 up to 5PM today still restorable/recoverable?
Or said archived logs are considered "corrupted" already?

Thank you in advance.
Re: archive logs directory (FRA) accidentally deleted [message #668796 is a reply to message #668795] Wed, 14 March 2018 23:16 Go to previous messageGo to next message
BlackSwan
Messages: 26640
Registered: January 2009
Location: SoCal
Senior Member
reym21 wrote on Wed, 14 March 2018 20:46
Gurus,

Good day.

One of our SysAdm accidentally formatted (Mar. 13 6PM) the flash_recovery_area directory of our production database.
According to him, the command (creation/expansion of mountpoints) he accidentally executed will lose all existing archived logs once the database server is restarted.

We immediately implemented an adhoc RMAN full backup (Mar. 14, 4PM, completed on Mar. 15, 12AM - 1.7TB size)
while he (SysAdm) backup continuously all the files in the said FRA to another directory.
We're also scheduling a database restart this afternoon at 5PM, where we will create/point the FRA to another directory.

Are the archived logs generated from 6PM of Mar. 13 up to 5PM today still restorable/recoverable?
Or said archived logs are considered "corrupted" already?

Thank you in advance.
Archived logs are only useful when they can be applied to previous complete backup.
Without a complete & good backup, archived redo file are incomplete & useless.
Re: archive logs directory (FRA) accidentally deleted [message #668797 is a reply to message #668796] Thu, 15 March 2018 00:34 Go to previous messageGo to next message
reym21
Messages: 238
Registered: February 2010
Location: Philippines
Senior Member

Sir, thank you for your prompt reply.

As I'd list the archived logs using RMAN (LIST BACKUP OF ARCHIVELOG ALL;),
it shows that all archived logs dated from Feb. 2 up to Mar. 14, 10:31PM were already backed-up.
But, when I execute this command: "select sequence#, first_time, next_time, applied, archived from v$archived_log"
there were still 27,840 archived logs (dated Feb. 2 to Mar. 15, 2018) that have not been applied (APPLIED=NO).
What would be our next steps? Can we forcibly apply those still "unapplied" archived logs?

Thanks again.
Re: archive logs directory (FRA) accidentally deleted [message #668798 is a reply to message #668795] Thu, 15 March 2018 01:36 Go to previous messageGo to next message
John Watson
Messages: 8075
Registered: January 2010
Location: Global Village
Senior Member
We are you re-starting the database? There is no need to do that just to change the location of the FRA. This all seems rather a fuss about nothing. All you need do is change your db_recovery_file_dest and then:
{backup database plus archivelog;
crosscheck backip;
crosscheck archivelog all;
delete expired backup;
delete expired archivelog all;}
LAstly, you are misunderstanding what APPLIED means. Better look it up.
Re: archive logs directory (FRA) accidentally deleted [message #668802 is a reply to message #668798] Thu, 15 March 2018 04:07 Go to previous message
reym21
Messages: 238
Registered: February 2010
Location: Philippines
Senior Member

Thank you very much!
All well-noted, Sir.

Regards,
Previous Topic: RMAN pushing same backups again and again to tape causing TSM running out of space
Next Topic: ORA-27072: File I/O error for sysaux.dbf, more logfiles than expected
Goto Forum:
  


Current Time: Sun Dec 08 10:24:44 CST 2019