Init parameterBackup & recovery

CONTROL_FILE_RECORD_KEEP_TIME

What it controls

Days that reusable backup and archived log records stay in the control file.

Know this before you change it

Without a recovery catalog, keep it longer than your RMAN recovery window or older backups become unknown to RMAN.

Default: 7

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'control_file_record_keep_time';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'control_file_record_keep_time' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET control_file_record_keep_time = 30 SCOPE = BOTH SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET control_file_record_keep_time SCOPE = SPFILE SID = '*';

Related scripts

• RMAN configuration (non-default settings)The persistent CONFIGURE settings stored in the control file, the same list SHOW ALL marks as changed. Check retention and control file autobackup…

Open in the parameter referenceOracle's reference

More in Backup & recovery

• DB_RECOVERY_FILE_DESTLocation of the Fast Recovery Area, for archived logs, backups and flashback logs.
• DB_RECOVERY_FILE_DEST_SIZEThe most space the Fast Recovery Area may use.
• DB_FLASHBACK_RETENTION_TARGETMinutes of flashback logs to keep for Flashback Database.
• DB_BLOCK_CHECKSUMWhether blocks carry a checksum that's verified on read.
• DB_BLOCK_CHECKINGLogical consistency checks on blocks when they change.
• DB_LOST_WRITE_PROTECTRecords block versions in redo so lost writes can be detected.