Oracle Backup
Incident Resolution 
1. Detailed Description of the Issue 
The last successful database backup was outdated. The scheduled backup did not complete as expected, resulting in an increased age of the most recent successful backup. 
2. GxP Impact 
Not required at the moment. 
3. Actions Taken 
Triggered an ad?hoc Full Database Backup. 
Triggered the Incremental Backup after the full backup initiation. 
4. Root Cause 
The system was running in on?demand mode, and the scheduled backup job was cancelled due to the start/stop schedule conflict configured in Control?M. 
5. Workaround 
An ad?hoc full backup was manually triggered, and the backup completed successfully. 
6. Permanent Solution 
The Control?M backup schedule needs to be adjusted to align with the system start/stop schedule to prevent future backup cancellations.