原因：
- Operating system date has been changed by mistake to future date.
- Rman backup was taken at that future date and the operating system was brought back to Original date.
处理方法：
- Run the following query to find the backuppiece having completion date greater than sysdate
1. Catalog is being used Connect Connect to atalog database an run the following query:
SQL> alter session set nls_date_format='DD-MM-YYYY:HH:MI:SS';
SQL> select piece#,handle, bp_key, start_time, completion_time from rc_backup_piece where completion_time > sysdate;
2. catalog database is not used
Connect to target database and run the following query:
SQL> alter session set nls_date_format='DD-MM-YYYY:HH:MI:SS';
SQL> select piece#, handle, start_time, completion_time from v$backup_piece where completion_time > sysdate;
- The above queries will indicates the filename of the backup piece having issue
- We can explore two options to resolve the issue:
Option A
-----------
This option a is applicable to both cases if rman catalog is used or no rman catalog is used:
Rename all the backuppiece at OS level which are having backuppiece information with Completion date > sysdate
Once renamed
In Rman run the following
Rman > crosscheck backup
Rman> delete noprompt force expired backup
Option B
-----------
If catalog database is not used:
This option would be to recreate the controlfile after the Problematic backuppiece has been renamed.
Ensure you keep a Copy of the existing controlfile before recreating the controlfile.
Also do
Rman> Spool log to '/<path>/rman.log'
Rman> list backup ;
This would ensure you have the list of all the backuppiece (good and bad)