First page Back Continue Last page Graphics
CFRKT Parameter…
control_file_record_keep_time parameter controls reuse of reusable records
Minimum age in days of a reusable record before it can be overwritten
Reusable records EXPIRE
- Default is 7 days
- Maximum 365 days
- Minimum 0
Overwritten metadata is lost, unless
- Using a recovery catalog and RESYNC catalog prior to overwrite
- More on this later…
Notes:
The control_file_record_keep_time parameter helps control control file size by specifying, in days, how old a reusable record must be before it can be overwritten. So, for example, a value of 7 means that a backup record can not be reused (overwritten) unless it has existed for 7 days.
The default value of the control_file_record_keep_time is 7 days; the minimum is 0 and the maximum is 365 days. Setting to 0 effectively turns off expiration check, i.e. reusable records are reused as necessary (and the control file will not expand). Use with caution and you can lose metadata RMAN needs for recovery
Overwritten metadata is lost - unless you use a recovery catalog and update the catalog with the RESYNC CATALOG command before the record is overwritten. If the control_file_record_keep_time value is 5, you need to resync the catalog every 4 days or less. See more in the “Re-Sync Catalog” section of this chapter.
Note that losing the metadata does not necessarily mean you cannot recover. It simply means that RMAN does not know about it and thus cannot use it in RMAN recovery. If the backup data is still available (the RMAN backup sets and Oracle archived logs), you can still manually apply them to the database.