Four ways for Oracle to release flash recovery area

In the morning, you receive an alert email from a Linux server disk and an email from the monitoring Alert Log program. After the check, it is found that there is no space for a partition in the Linux server. The main reason is that the programmer generated a large number of archived logs during the upgrade last night, leading to the failure to archive online redo logs. the following error occurs:

363 | Wed Mar 19 02:33:16 2014 | ORA-00312: online log 2 thread 1: '/u01/app/Oracle/oradata/mes/redo02.log'

369 | Wed Mar 19 02:34:16 2014 | ORA-16014: log 2 sequence #75999 not archived, no available destinations

370 | Wed Mar 19 02:34:16 2014 | ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/mes/redo02.log'

373 | Wed Mar 19 02:34:16 2014 | ORA-16014: log 2 sequence #75999 not archived, no available destinations

374 | Wed Mar 19 02:34:16 2014 | ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/mes/redo02.log'

383 | Wed Mar 19 02:39:16 2014 | ORA-19502: write error on file "/u03/flash_recovery_area/mes/archivelog/2014_03_19/o1_mf_000075999_9lk4pngn _. arc", blockno 108545 (blocksize = 512)

384 | Wed Mar 19 02:39:16 2014 | ORA-27072: File I/O error

Due to the urgency at that time, the archived logs of yesterday were manually deleted and a large amount of space was released. The following error was found in the alarm log:

ORA-19815: WARNING: db_recovery_file_dest_size of 42949672960 bytes is 100.00% used, and has 7684830208 remaining bytes available.

Wed Mar 19 08:48:48 2014

**************************************** ********************************

You have following choices to free up space from flash recovery area:

1. Consider changing rman retention policy. If you are using Data Guard,

Then consider changing rman archivelog deletion policy.

2. Back up files to tertiary device such as tape using RMAN

Backup recovery area command.

3. Add disk space and increase db_recovery_file_dest_size parameter

Reflect the new space.

4. Delete unnecessary files using rman delete command. If an operating

System command was used to delete files, then use rman crosscheck and

Delete expired commands.

**************************************** ********************************

Wed Mar 19 08:48:54 2014

Thread 1 advanced to log sequence 76076 (LGWR switch)

This error occurs because, after the archived logs are manually deleted, the Rman backup will detect the missing logs and thus cannot be further executed. Therefore, you need to manually execute the crosscheck process, and then the Rman backup can be restored to normal.

As shown above, Oracle provides 4 methods to solve this problem:

You have following choices to free up space from flash recovery area:

1. Consider changing rman retention policy. If you are using Data Guard,

Then consider changing rman archivelog deletion policy.

2. Back up files to tertiary device such as tape using RMAN

Backup recovery area command.

3. Add disk space and increase db_recovery_file_dest_size parameter

Reflect the new space.

4. Delete unnecessary files using rman delete command. If an operating

System command was used to delete files, then use rman crosscheck and

Delete expired commands.

Translation:

You can use the following options to release the space in the Flash recovery zone:

1: consider modifying the RMAN backup retention policy. If you use Data Guard, you should consider modifying the RMAN archive log deletion policy.

2: Use the rman backup recovery area command to back up data to a third-party device (such as tape)

3: increase disk space and db_recovery_file_dest_size.

 

   1: