Control-M: 33_EUP - Event: JOB NOT OK App: STF-IS-ECC-PROD-RZC-SNAP Job: ORACLE-DB-ARCHIVES Folder: 9EUPR33_STF-DATABASE-ECC-SNAPRZC-CS
1. Detailed Description of the Issue: 
Control-M: 33_EUP - Event: JOB NOT OK App: STF-IS-ECC-PROD-RZC-SNAP Job: ORACLE-DBSTATS Folder: 9EUPR33_STF-DATABASE-ECC-SNAPRZC-CS 
 
2. GxP Impact: 
Not required at the moment. 
 
3. Actions Taken: 
Verified the system status in the AWS Console. 
Confirmed that the BAB system was intentionally powered off as part of cost?optimization measures. 
Reviewed the system operational schedule and monitoring alert timing. 
4. Root Cause: 
The incident was triggered because the monitoring alert fired before the system's scheduled availability window began. The RZCsystem is configured to be available only on friday from 1:30  CET to 23:30 CET, and at the time of alert generation (23:41 CET), the system had not yet been stopped . 
5. Workaround: 
No workaround is required, as the behavior aligns with the defined operational schedule. Monitoring alerts can be expected when the system is powered off outside the availability window. 
6. Solution: 
No corrective action is needed. The system will be started according to business requirements or during scheduled maintenance within the defined availability window. The incident is considered informational and consistent with expected system behavior