1/27/2024 0 Comments Autosys primary backup scheduler![]() CAUAJM_I_40266 DBMaint is ended with: normal termination, exit status = 0ĬAUAJM_I_85000 Compliance Application runningĬAUAJM_I_85001 Compliance Application terminated successfully ĬAUAJM_I_60013 Number of Events Deleted: 37ĬAUAJM_I_60017 Number of job runs deleted: 9ĬAUAJM_I_60437 Number of Machines Deleted: 0ĬAUAJM_I_60021 Number of Audit Infos Deleted: 0ĬAUAJM_I_60019 dbstatistics: Running dbstatistics at: Tue Sep 15 03:30:13 2020ĬAUAJM_I_60020 dbspace: Running dbspace at : Tue Sep 15 03:30:44 2020ĬAUAJM_I_60031 The AutoSys tables have used 19.0 MB disk space. On the other hand, if youve just finished decommissioning another job scheduling or workload automation tool in favor of this one, you might be pretty. CAUAJM_I_80021 The agent inventory service has evaluated the statuses of 21 machine(s) in 0.102 seconds. CAUAJM_I_20218 Executing Command: exec $AUTOSYS/bin/DBMaint, DBMaint 0. CAUAJM_I_40264 **** Internal Database Maintenance **** How to Schedule Informatica Sessions with Autosys. And the situation with scheduler+em crash was exclusive, now there is no failed processes in unifstat output. I've found, that event management always fails at 03:30am, when DBMaint script starts. On the primary Scheduler, what do you see in event_demon log file, at the same time you see " CAUAJM_W_00144 The CA WAAE shadow scheduler appears to have failed over prematurely" on the Shadow ?ĭoes caiopr stop/crash before or after Scheduler ? Resolution Run autoping from the new Scheduler. So a stop/start of Scheduler can solve this. When the Primary scheduler is shutdown and Shadow is made primary the WA Agents may not respond to current (new) Primary server. You can have a look at Event Management log file:Ĭautil select conlog list conlog > today.txtĭo you see any CAUAJM_I_40245 message or error message in today.txt ?Īn other explanation could be that Event Management was not available few minutes while event_demon process was running and the Scheduler has stopped to send messages to Event Management. As I know, there were no any network or hardware problems ![]() I'd like to understand what reason could lead to event management crash or scheduler and event manager shutdown. I restarted services again and now they seems to be working. CAOP_I_DAEMONTERM Daemon terminated by signal 63583,caioprCAOPLinux-x Schedule and execute regular system management activities, including system reboot, backup, recovery, archiving, and restoration. Consider a higher value for the HAPollInterval setting. I restarted all services and then event management started to work.īut few hours later WAAE Scheduler and CA-Event Manager fell down without any reason.ĬAUAJM_W_00144 The CA WAAE shadow scheduler appears to have failed over prematurely. Autosys is a multi-platform automated job management system which provides scheduling monitoring and reporting of Autosys jobs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |