RMAN time-based backup retention policy adjustment

We know that the backup information of ramn in nocatalog mode is kept in the control file. The retention days of RMAN backup sets in the control file depends on the initialization parameter control.

We know that the backup information of ramn in nocatalog mode is kept in the control file. The retention days of RMAN backup sets in the control file depends on the initialization parameter control.

I recently received an email saying that there is not enough storage space. It seems that the RAMN backup set occupies a large amount of storage space.
Looking at these backup sets, there were actually two months ago. No wonder the storage space was insufficient.

RMAN> show all;
RMAN configuration parameters:
Configure retention policy to recovery window of 60 DAYS;

SQL> show parameter control_file_record_keep_time;

NAME TYPE VALUE
-----------------------------------------------------------------------------
Control_file_record_keep_time integer 16

We know that the backup information of ramn in nocatalog mode is kept in the control file.
The retention days of RMAN backup sets in the control file depend on the initialization parameter control_file_record_keep_time.
If the number of days exceeds the number of days configured for control_file_record_keep_time, the control file may overwrite the records before the retention period.

Therefore, the value of control_file_record_keep_time should be greater than the backup set retention time configured in RAMN.

Based on the above principles, the retention time of the Backup set in RMAN is adjusted.
RMAN> configure retention policy to recovery window of 16 days;

New RMAN configuration parameters:
Configure retention policy to recovery window of 16 DAYS;
The new RMAN configuration parameters are successfully stored.