Flash recovery area issue

i am trying to start database but getting error;
SQL> startup force;
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - 18446744073
709551614)
Please guide and help

it works!
SQL> startup
ORACLE instance started.
Total System Global Area 671088640 bytes
Fixed Size                  2023248 bytes
Variable Size             180355248 bytes
Database Buffers          482344960 bytes
Redo Buffers                6365184 bytes
Database mounted.
Database opened.
SQL> show parameter DB_RECOVERY_FILE_DEST_SIZE
NAME                                 TYPE        VALUE
db_recovery_file_dest_size           big integer 5G
SQL> Alter system set DB_RECOVERY_FILE_DEST_SIZE=8G scope=both;
System altered.
SQL> show parameter DB_RECOVERY_FILE_DEST_SIZE
NAME                                 TYPE        VALUE
db_recovery_file_dest_size           big integer 8G
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 671088640 bytes
Fixed Size                  2023248 bytes
Variable Size             188743856 bytes
Database Buffers          473956352 bytes
Redo Buffers                6365184 bytes
Database mounted.
Database opened.
SQL> show parameter DB_RECOVERY_FILE_DEST_SIZE
NAME                                 TYPE        VALUE
db_recovery_file_dest_size           big integer 8G
SQL>

Similar Messages

Flash recovery area issue. I can not open the database??

Hi all
I am using oracle 11.2.0 .1.0 on windows
when i tried to start the database I got the following error.
ORA-03113: end-of-file on communication channel
I clear out all information in Trace file. I cleared out all operating system level audit trails. then i deleted archivelog files using operating system level delete. still my database is not opening???
I tried to start this using RMAN but got the same error. now i have deleted the files from flash recovery area how can i let oracle system to know that those are deleted and there is enough space. Rman does not execute crosschek commands at mount state of the database?
Need solution.
Regards
MAlik

malikdba wrote:
the last option which ask to delete the files. i already have deleted the files at operating system level. now the issue is how to let the system that the space is free in flash recovery area? rman is not running crosscheck command at mount stage of the target database. What steps should i follow now?
Thanks
malik
Are you saying you are getting an error while trying to crosscheck at mount? Or you simply don't believe it will work?
oracle:orcl$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jul 11 10:52:48 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> startup mount;
Oracle instance started
database mounted
Total System Global Area     839282688 bytes
Fixed Size                     2231128 bytes
Variable Size                503317672 bytes
Database Buffers             331350016 bytes
Redo Buffers                   2383872 bytes
RMAN> crosscheck archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
specification does not match any archived log in the repository
RMAN>
A perfectly normal crosscheck at the mount stage

Online redo logs in Flash Recovery Area

Hi,
Currently I have redo logs multiplexed on two separate disks. I want to add a new member to each log file group that goes in flash recovery area. What is the easiest way to accomplish this?
It seems to me that I can only do this by dropping the existing groups and recreating them. If I decide to go this route, what parameters do I need to set so that 3 members are created for each group?
Thanks

Simply issue 'alter database add logfile group <n>;', don't specify a location. Assuming 'db_recovery_file_dest' is correctly set this will create an Oracle managed file under <FRA>/onlinelog/<OMF-filename>, something like
4 ONLINE
C:\ORACLE\FLASH_RECOVERY_AREA\ORACLE\ONLINELOG\O1_MF_4_5WRBM1C4_.LOG
GROUP# STATUS TYPE
MEMBER
IS_
YES
Werner

Changing the location of the Flash Recovery Area

My flash recovery area is currently on the same disk as the database. The recovery area also has all out backups for the past month. What's steps should I take to change location of the flash recovery area? Do I have to do anything besides changing db_recovery_file_dest? Would I have to update the control files, spfile and so on?
Thanks in advance,

you can make the change at pfile or spfile level and stop and restart the database. this should work.

Changing the location of archive log from flash recovery area PLZ HELP!!!

Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AM

user10243788 wrote:
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                99.44                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                49.72                         0              57
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                  0                         0               0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
For regular housekeeping, you need to be doing something similar to this in rman:
run {
backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 1 times to device type disk;
run {
delete noprompt obsolete;
crosscheck archivelog all;
delete noprompt expired archivelog all;

Flash recovery area: archivelog file directory modification time

Using Oracle Database 10g Release 10.2.0.3.0 - 64bit (Standard Edition) on Solaris 10, SunOS 5.10 Generic_118833-33, archivelog files in the Flash Recovery Area are still present, after the time that they should have been made redundant and therefore deleted::
bvsmdb01-oracle10g $ date
Thu Jan 24 16:04:46 GMT 2008
bvsmdb01-oracle10g $ ls -lt archivelog
total 20
drwxr-x--- 2 oracle10g oinstall 1024 Jan 24 16:00 2008_01_24
drwxr-x--- 2 oracle10g oinstall 512 Jan 23 23:30 2008_01_19
drwxr-x--- 2 oracle10g oinstall 1536 Jan 23 23:04 2008_01_23
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 23:30 2008_01_18
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 22:53 2008_01_22
drwxr-x--- 2 oracle10g oinstall 1024 Jan 21 23:07 2008_01_21
drwxr-x--- 2 oracle10g oinstall 512 Jan 20 22:20 2008_01_20
bvsmdb01-oracle10g $
The archivelog directory for 2008_01_19 has a modification time of Jan 23 23:30 - this is almost 4 days after it was last written to.
The current redundancy setting in RMAN is shown in the output of show all:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/dbs/snapcf_kierli.f'; # default
So, the current retention policy is three days. It is 24/1 today - the archivelog directory from 19/1 should have been deleted by now, but it has not been.
The modification time for the archivelog directory 2008_01_19 has a modification time of Jan 23 23:30 2008.
Why is this? How can this be investigated? Does anyone have any suggestions?
Thanks
Jerry Mander

From 2 Day DBA:
Even after files in the flash recovery area are obsolete, they are generally not deleted from the flash recovery area until space is needed to store new files. As long as space permits, files recently moved to tape will remain on disk as well, so that they will not have to be retrieved from tape in the event of a recovery.
What is the current space used in the FRA and what is the FRA disk limit ?

Flash recovery area, need help!

Hi! I have some problems with Flash Recovery Area. I use Oracle 10g.
So,
1) I tried to change Flash Recovery Area Size from 10 to 15 GB in Enterprise Manager, see: http://my.jetscreenshot.com/2677/20111129-mxmb-117kb
Applied changes and shutdown DB. After I started DB and see the Flash Recovery Area Size then I can see that it is old one - 10GB and free space is with "-" sign, see: http://my.jetscreenshot.com/2677/20111129-bwlw-101kb
What I am doing wrong?
2) Can You pleas explain, what to do step by step with example, how can I delete Flash Recovery files USING ENTERPRISE MANAGER, what steps I need to do? Because my HDD is almost full.
3) It is possible to delete Flash Recovery files automatic after some time? If Yes, please say how?
Hope for Your help, best regards, Debuger

1) Mybe I can't change recovery area size because there somewhere area size is limited to 10gb, because I do not understand why always after restart there is 10gb... :(You are missing something when you bounce, Make sure you have started with same SPFILE, You have to load the same PFILE/SPFILE when you performed changes.
2) How can I schedule a RMAN job to cleanup? Can You give me all necessary steps to do?You can schedule RMAN archive delete jobs.
check these links
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/advmaint.htm#i1006414
http://docs.oracle.com/cd/B28359_01/server.111/b28301/backrest004.htm

How to disable flash recovery area feature?

Please guide how to disable flash recovery area with commands
Thanks,
Waheed

How about searching for it first,
http://www.oracle.com/pls/db92/db92.federated_search
Adith

Redo logs and Flash recovery area

Hi,
Is it a good practice to place a copy of the (multiplexed) online redo at the flash recovery area? Wouldn't it be better to place a copy of the archived log at the flash recovery area?

user492400 wrote:
Hi,
Is it a good practice to place a copy of the (multiplexed) online redo at the flash recovery area? Wouldn't it be better to place a copy of the archived log at the flash recovery area?Its not only the archvielogs that should be placed in the FRA. FRA is supposed to contain one copy of the archive logs and the rest 9 destinations are given to you for the multiplexing of it. The idea of multiplexing the redo logs and placing them anywhere( not just on the FRA itself) is simply required so that you won't get to a situation where you would lose all the redo log files and thus have to recreate them, losing the data inside them. So aleast one copy of the log files should be there and where you want to put it, that would depend on you.
HTH
Aman....

Disk array configurations with oracle redo logs and flash recovery area.

Dear Oracle users,
We are planning to buy the new server for oracle database 10g standard edition. We put oracle database file, redo logs, and flash recovery area on each of disk array. My question is what is the best disk array configuration for redo logs and flash recovery area? RAID 10 or RAID 1? Is that possible we can duplicate Flash recovery area to the other location (such as net work drive) at the same time? Since we only have single disk array controller to connect to the disk arrays, I am try to avoid the single failure that will lose archive logs and daily backup.
thanks,
Belinda

Thank you so much for the suggestion. Could you please let me know the answer for my question of FRA redundancy?
“Is that possible we can duplicate Flash recovery area to the other location (such as net work drive) at the same time? Since we only have single disk array controller to connect to the disk arrays, I am try to avoid the single failure that will lose archive logs and daily backup.”

Adding new hard drive for Flash recovery area

i am adding new hard drive for flash recovery area. How i can make single directory on that flash recovery area & how i can test that i am accessing that rightly , to that directory & flash back recovery area disk?

Are you on Windows or Unix? And are you using ASM?
I'll assume you are on Windows....So after allocating the drive, you will format it say as F drive. Then you can create a directory T:\Flash. The parameter determining the location of the flash recovery area is db_recovery_file_dest. But you also need to set the size of the flash recovery area as well. After that's done. You can do your backups to Flash and see if the directory is populated.

How to use Flash recovery area only for flashback database feature

I would like to use flash recovery area only for flashback database feature, which means, flash recovery area will store only flashback logs.
I dont want to use that file system for any other files, like archive log files, database backups, control file copies, multiplex redo log, etc
is it possible? I want to use this feature only for flashback database option and hence i dont want to disturb any existing configuration in my database
including backup jobs. Is it required to store archive redo log files also in flash recovery area to use the flashback database feature?
I certainly can't afford to have a copy of entire database in this file system as size of my DB is more than the flash recovery area file system I have.
Thanks
Sarayu

user13312943 wrote:
Aman,
I think i was not clear in my question. Let me try again
My only requirement is to use flashback database feature (or be prepared to use if required). I dont want to create a large file system to use this FRA to store all these files. Out of all the files being stored here copy of data files seems to be consuming more space. I see these files are classified as transient and permanent files. I am okay with permanent files. I fear that this file system may consume more space if i store backup files on disk. I want database backups to go to tapes, not to the FRA disk. Is it possible?
Thanks for your reply
Okay, well in that case you can use RMAN and push the backups to the tape drives. FLB logs would be stored on the FRA.
Aman....

Flash Recovery Area On 11.5.10.2

Hello,
We are running 11.5.10.2 on window 2003 server 32-bit,we save backup on flash_recovery area which size is 91 GB,total file system size on window of flash recovery area is 190GB.When i check the space on file system it show me 84 GB free space,I want to ask then where is 27 GB space,because backupset size is 2.70GB autobackup size is 128 MB and datafile size is 79 GB.
Please help me out.
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
2745    B F A DISK        23-SEP-13       1       1       NO         TAG20130923T233305
2747    B F A DISK        24-SEP-13       1       1       NO         TAG20130924T203609
2749    B F A DISK        26-SEP-13       1       1       NO         TAG20130926T194832
2751    B F A DISK        27-SEP-13       1       1       NO         TAG20130927T214235
2753    B F A DISK        08-OCT-13       1       1       NO         TAG20131008T184055
2754    B 1 A DISK        09-OCT-13       1       1       NO         ORA\$OEM_LEVEL_0
2755    B F A DISK        09-OCT-13       1       1       NO         TAG20131009T225822
Regards,
Merri

Hello,
report obsolete show's
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           2745   23-SEP-13
Backup Piece       2745   23-SEP-13          I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130923-00
Backup Set           2747   24-SEP-13
Backup Piece       2747   24-SEP-13          I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130924-00
Backup Set           2749   26-SEP-13
Backup Piece       2749   26-SEP-13          I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130926-00
Archive Log          135874 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98760_578172119.DBF
Backup Set           2751   27-SEP-13
Backup Piece       2751   27-SEP-13          I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130927-00
Archive Log          135876 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98761_578172119.DBF
Archive Log          135878 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98762_578172119.DBF
Archive Log          135880 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98763_578172119.DBF
Archive Log          135882 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98764_578172119.DBF
Archive Log          135884 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98765_578172119.DBF
Archive Log          135886 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98766_578172119.DBF
Archive Log          135888 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98767_578172119.DBF
Archive Log          135890 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98768_578172119.DBF
Archive Log          135892 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98769_578172119.DBF
Archive Log          135894 03-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98770_578172119.DBF
Archive Log          135896 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98771_578172119.DBF
Archive Log          135898 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98772_578172119.DBF
Archive Log          135900 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98773_578172119.DBF
Archive Log          135902 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98774_578172119.DBF
Archive Log          135904 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98775_578172119.DBF
Archive Log          135906 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98776_578172119.DBF
Archive Log          135908 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98777_578172119.DBF
Archive Log          135910 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98778_578172119.DBF
Archive Log          135912 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98779_578172119.DBF
Archive Log          135914 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98780_578172119.DBF
Archive Log          135916 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98781_578172119.DBF
Archive Log          135918 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98782_578172119.DBF
Archive Log          135920 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98783_578172119.DBF
Archive Log          135922 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98784_578172119.DBF
Archive Log          135924 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98785_578172119.DBF
Archive Log          135926 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98786_578172119.DBF
Archive Log          135928 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98787_578172119.DBF
Archive Log          135930 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98788_578172119.DBF
Archive Log          135932 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98789_578172119.DBF
Archive Log          135934 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98790_578172119.DBF
Archive Log          135936 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98791_578172119.DBF
Archive Log          135938 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98792_578172119.DBF
Archive Log          135940 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98793_578172119.DBF
Archive Log          135942 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98794_578172119.DBF
Archive Log          135944 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98795_578172119.DBF
Archive Log          135946 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98796_578172119.DBF
Archive Log          135948 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98797_578172119.DBF
Archive Log          135950 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98798_578172119.DBF
Archive Log          135952 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98799_578172119.DBF
Archive Log          135954 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98800_578172119.DBF
Archive Log          135956 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98801_578172119.DBF
Archive Log          135958 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98802_578172119.DBF
Archive Log          135960 04-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98803_578172119.DBF
Archive Log          135962 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98804_578172119.DBF
Archive Log          135964 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98805_578172119.DBF
Archive Log          135966 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98806_578172119.DBF
Archive Log          135968 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98807_578172119.DBF
Archive Log          135970 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98808_578172119.DBF
Archive Log          135972 05-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98809_578172119.DBF
Archive Log          135974 06-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98810_578172119.DBF
Archive Log          135976 06-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98811_578172119.DBF
Archive Log          135978 06-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98812_578172119.DBF
Archive Log          135980 06-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98813_578172119.DBF
Archive Log          135982 06-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98814_578172119.DBF
Archive Log          135984 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98815_578172119.DBF
Archive Log          135986 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98816_578172119.DBF
Archive Log          135988 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98817_578172119.DBF
Archive Log          135990 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98818_578172119.DBF
Archive Log          135992 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98819_578172119.DBF
Archive Log          135994 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98820_578172119.DBF
Archive Log          135996 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98821_578172119.DBF
Archive Log          135997 07-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98822_578172119.DBF
Archive Log          136000 07-OCT-13          F:\******\1_98823_578172119.DBF
Archive Log          136002 08-OCT-13          F:\\1_98824_578172119.DBF
Archive Log          136004 08-OCT-13          F:\********\1_98825_578172119.DBF
Archive Log          136006 08-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98826_578172119.DBF
Archive Log          136008 08-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98827_578172119.DBF
Archive Log          136010 08-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98828_578172119.DBF
Archive Log          136012 08-OCT-13          F:\ARCHIVELOGS\APPPROD\1_98829_578172119.DBF
Backup Set           2753   08-OCT-13
Backup Piece       2753   08-OCT-13          I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20131008-00
NAME
SPACE_LIMIT
SPACE_USED
SPACE_RECLAIMABLE
NUMBER_OF_FILES
I:\flash_recovery\
97710505984
83336011776
0
47
Regards,
Merri

Retention policy for archivelogs in the flash recovery area

I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
Thanks.

I am using the flash recovery area for all my backup
files (archive logs, data and control files). I want
to use the redundancy retention policy because it is
easy to calculate the space requirement. However, I
am not clear how the retention policy applies to
archive logs.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM    <DIR>          .
03/17/2008 03:44 PM    <DIR>          ..
03/17/2008 03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
               1 File(s)      9,750,528 bytes
               2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM    <DIR>          .
03/17/2008 03:59 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM    <DIR>          .
03/17/2008 04:09 PM    <DIR>          ..
03/17/2008 04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
               1 File(s)      9,751,552 bytes
               2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           240    17-MAR-08
Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set           241    17-MAR-08
Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

What's Flash Recovery Area's retention policy?

What's Flash Recovery Area's retention policy?
I can't find info about that,
thanks

Anantha R,
I think that parameter is nothing to do with the flash recovery area.
user11402556,
Please read; http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm
Ogan

Flash recovery area issue

Similar Messages

Maybe you are looking for