Customer's scheduler rolled over because of an error in the logs
[09/27/2022 10:18:06] CAUAJM_E_18402 ORA-00257: Archiver error. Connect AS SYSDBA only until resolved.
[09/27/2022 10:18:06] CAUAJM_E_10656 The database <ABC12345> has encountered a critical error. Please contact the database administrator.
[09/27/2022 10:18:06] CAUAJM_W_10635 Rolling over to single server mode. Using database <ABC12345>.
[09/27/2022 10:18:06] CAUAJM_W_10648 The database: ABC12345 is unavailable. Attempting to rollover to single server mode.
ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=1] [si_int=-311474860] [si_ptr=0xed6f4554] [si_addr=0x20]
kpedbg_dmp_stack()+299<-kpeDbgCrash()+75<-kpeDbgSignalHandler()+107<-skgesig_sigactionHandler()+219<-00000020<-_ZN12CmProxyQuery5getDbEv()+288<-_ZN12DbProxyQuery7executeEv()+596<-_ZN9SngThread7executeEv()+8043<-_ZN9SngThread7IterateEv()+255<-ThreadTE()+71<-start_thread()+204<-clone()+94
Release : 11.3.6
Component :
Work with DBA to clear up the archive log problem. Once that is done, Autosys scheduler needs to be stopped. Databases need to be resyncned next (autobcp/autobcpdp), and then scheduler can be restarted back in dual database mode.