No space in the Flash Recovery Area (FRA)
Monday, August 2, 2010
Membership Price At La Boxing
As part of the back of a database 10g on RHEL 4, I have to run a Level 0 (Full) every Sunday, incremental Monday, Tuesday, Wednesday, Friday and Saturday and cumulative incremental on Thursday, all with RMAN, however, I encounter the following message logged in the execution of the back log level 0: 
[oracle @ testserver ~] $ tail piece rman/logs/Level0-1008021002.log handle = / opt/oracle/flash_recovery_area/ORCL/backupset/2010_08_02/o1_mf_nnnd0_WEEKLY_BACKUP_65fqjdjj_.bkp tag=WEEKLY_BACKUP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:56
RMAN-00571: ===========================================================
[oracle @ testserver oracle] $ du-sk flash_recovery_area
1835880 flash_recovery_area
has occupied little more than 1.8 Gb and revising the settings at Oracle:
SQL> show parameter NAME db_recovery_file_dest_size
; TYPE VALUE
------------------------------------ ----------- - ----------------------------
using RMAN.
Change RMAN retention policy. Change the policy
Starting Control File and SPFILE Autobackup at 02-AUG-10
piece handle = / opt/oracle/flash_recovery_area/ORCL/autobackup/2010_08_02 / comment = NONE
If space for the FRA was set equal to the size of the disk or filesystem and had no extra space, would then have to use some of the other 4 options involving getting rid of files to free space in the FRA. Before deleting any files managed by RMAN sure there is a backing away from the FRA, for example tape or other storage medium, with this ensures that in an eventuality in the production database, you will have the means to restore .
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/02/2010 10:05:46
ORA-19809: limit exceeded for recovery
files ORA-19804: can not reclaim 52428800 bytes disk space from 2147483648 limit
Recovery Manager complete.
see that it's actually three messages. The first (RMAN-03002) indicates that RMAN failed to support implementation including archivelogs. The second (ORA-19809) that there is more space to store backups and finally (ORA-19804) that failed to release about 52 Mb of space in the FRA. Reviewing directory size designed to FRA operating system level, we see that: RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/02/2010 10:05:46
ORA-19809: limit exceeded for recovery
files ORA-19804: can not reclaim 52428800 bytes disk space from 2147483648 limit
Recovery Manager complete.
[oracle @ testserver oracle] $ du-sk flash_recovery_area
1835880 flash_recovery_area
has occupied little more than 1.8 Gb and revising the settings at Oracle:
SQL> show parameter NAME db_recovery_file_dest_size
; TYPE VALUE
------------------------------------ ----------- - ----------------------------
db_recovery_file_dest_size ; big integer 2G
FRA size is 2 GB
workaround, Oracle intends to implement any of the following 5 options: Support the FRA
FRA size is 2 GB
workaround, Oracle intends to implement any of the following 5 options: Support the FRA
using RMAN.
Change RMAN retention policy. Change the policy
- deletion of archive logs.
- Add disk space and increase the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
- Delete Files RMAN using FRA.
- The FRA can be configured to occupy only a portion of the disk-February 2 GB by default, so in this case the most convenient option is to increase its size.
- SQL> alter system set db_recovery_file_dest_size = 3G scope = both;
done this, just throw back your backup.
[oracle @ testserver ~] $ tail rman/logs/Level0-1008021027.log
[oracle @ testserver ~] $ tail rman/logs/Level0-1008021027.log
Starting Control File and SPFILE Autobackup at 02-AUG-10
piece handle = / opt/oracle/flash_recovery_area/ORCL/autobackup/2010_08_02 / comment = NONE
o1_mf_s_725970724_65fs7ooy_.bkp Finished Control File and SPFILE Autobackup at 02-AUG-10
using channel ORA_DISK_1 using channel ORA_DISK_2
no obsolete backups found
Recovery Manager complete. Reviewing
execution log, we see that this time did not return any error messages. And we see the difference of space occupied in the FRA that went from 1.8 Gb to just over 2.6, ie, it took just over 800 MB of free space in the FRA for the backup could run without problems.
[oracle @ testserver oracle] $ du-sk flash_recovery_area
2635256 flash_recovery_area using channel ORA_DISK_1 using channel ORA_DISK_2
no obsolete backups found
Recovery Manager complete. Reviewing
execution log, we see that this time did not return any error messages. And we see the difference of space occupied in the FRA that went from 1.8 Gb to just over 2.6, ie, it took just over 800 MB of free space in the FRA for the backup could run without problems.
[oracle @ testserver oracle] $ du-sk flash_recovery_area
If space for the FRA was set equal to the size of the disk or filesystem and had no extra space, would then have to use some of the other 4 options involving getting rid of files to free space in the FRA. Before deleting any files managed by RMAN sure there is a backing away from the FRA, for example tape or other storage medium, with this ensures that in an eventuality in the production database, you will have the means to restore .
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment