Shadow scheduler is not showing on chk_auto_up

book

Article ID: 128042

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent

Issue/Introduction

Output of chk_auto_up is missing the Shadow Scheduler information.


CAUAJM_I_50054 Attempting (1) to Connect with Database: AUTOAEDB
CAUAJM_I_50055 *** Have Connected successfully with Database: AUTOAEDB. *** 
______________________________________________________________________________ 

CAUAJM_I_50128 Connected with Event Server: AUTOAEDB 
_____________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Application Server on Machine: primary-hostname.domain.com
CAUAJM_I_50243 CA WAAE Application Server is RUNNING on machine: primary-hostname.domain.com
______________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Application Server on Machine: shadow-hostname.domain.com
CAUAJM_I_50243 CA WAAE Application Server is RUNNING on machine: shadow-hostname.domain.com
______________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Primary Scheduler on Machine: primary-hostname.domain.com
CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: primary-hostname.domain.com 
______________________________________________________________________________ 


Upon checking on shadow all seems to be fine: 

CA Services Status Report 

Component Name Pid Status 
------------------------------------ ------- -------------- 
WAAE Agent (WA_AGENT) 6356 running 
WAAE Scheduler (ACE) 1542134 running 
WAAE Application Server (ACE) 3187608 running 

Monitoring shadow event schedular output file: 
/opt/CA/WorkloadAutomationAE/autouser.ILD/out/event_demon.shadow.ACE

*** To break out type control-c (^c) *** 

[12/12/2018 10:13:00] ---------------------------------------- 
[12/12/2018 10:14:00] ---------------------------------------- 
[12/12/2018 10:15:00] ---------------------------------------- 
[12/12/2018 10:16:00] ---------------------------------------- 
[12/12/2018 10:17:00] ---------------------------------------- 
[12/12/2018 10:18:00] ---------------------------------------- 
[12/12/2018 10:19:00] ---------------------------------------- 
[12/12/2018 10:20:00] ---------------------------------------- 
[12/12/2018 10:21:00] ---------------------------------------- 
[12/12/2018 10:22:00] ---------------------------------------- 
[12/12/2018 10:23:00] ---------------------------------------- 

After scheduler restart it went back to usual: 

CAUAJM_I_50054 Attempting (1) to Connect with Database: AUTOAEDB
CAUAJM_I_50055 *** Have Connected successfully with Database: AUTOAEDB. *** 
______________________________________________________________________________ 

CAUAJM_I_50128 Connected with Event Server: AUTOAEDB 
_____________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Application Server on Machine: primary-hostname.domain.com
CAUAJM_I_50243 CA WAAE Application Server is RUNNING on machine: primary-hostname.domain.com
______________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Application Server on Machine: shadow-hostname.domain.com
CAUAJM_I_50243 CA WAAE Application Server is RUNNING on machine: shadow-hostname.domain.com
______________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Primary Scheduler on Machine: primary-hostname.domain.com
CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: primary-hostname.domain.com 
______________________________________________________________________________ 

CAUAJM_I_50038 Checking CA WAAE Shadow Scheduler on Machine: shadow-hostname.domain.com
CAUAJM_I_50045 Shadow Scheduler is RUNNING on machine: shadow-hostname.domain.com
______________________________________________________________________________ 


 

Cause



 

Environment

Autosys 11.3.6 SP7 on Linux

Resolution

Specify the following 2 parameters in in $ORACLE_HOME/network/admin/sqlnet.ora
SQLNET.OUTBOUND_CONNECT_TIMEOUT=4
SQLNET.RECV_TIMEOUT=5