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:STF-IS-ECC-PROD-RZC-SNAP Job: ORACLE-DB-ARCHIVES Folder: 9EUPR33_STF-DATABASE-ECC-SNAPRZC-CS 
BRARCHIVE failed on host AWSDPNIRLL0003 for database RZC at 2026-06-19 01:34:04 CEST with error: 
ORA-01033: ORACLE initialization or shutdown in progress 
During the execution, BRARCHIVE could not establish a connection to the database instance as it was not fully open. 
Alert log analysis indicates that the database was still in the startup/open phase at the time of the BRARCHIVE execution. The first normal database activity was recorded at 2026-06-19 01:34:19 CEST, shortly after the failed connection attempt. 
Post this event, the database operated normally: 
02:00 CEST – BRBACKUP control file backup completed successfully 
02:34 CEST & 03:34 CEST – Archive log switches and archiving completed successfully 
This confirms that archive log generation and archiving resumed normally after database startup. 
2. GxP Impact – Not required at the moment. 
3. Actions Taken: 
Reviewed BRARCHIVE logs and identified ORA-01033 error during execution 
Analyzed Oracle alert log to verify database status during the failure window 
Confirmed that the database was in startup phase during BRARCHIVE execution 
Validated subsequent database operations including BRBACKUP and archive log switches 
Verified that archive log generation and archiving are functioning normally post database startup 
4. Root Cause:BRARCHIVE was triggered while the Oracle database was still in the initialization/startup phase and not yet in OPEN state, leading to connection failure. 
5. Workaround:Manual re-execution of the BRARCHIVE job can be performed after confirming that the database is fully OPEN. 
 
6. Solution:No configuration issue identified with BRARCHIVE Implement scheduling or dependency checks to ensure BRARCHIVE executes only after database reaches OPEN status 
