search cancel

Scheduler was hung when the Oracle RDS database failed over to a different region.

book

Article ID: 254668

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

The scheduler was hung when the  Oracle RDS database failed over to a different region. It needed a restart of the scheduler to fix the issue. Need to verify the configuration to prevent such occuerences

Environment

Release : 12.0

Resolution

Log analysis

We detect the problem

[10/13/2022 10:38:39]      CAUAJM_E_18412 The database client has been interrupted while query execution is in progress.
[10/13/2022 10:38:39]      CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.

We check the connection and make an attempt to reconnect

[10/13/2022 10:40:05]      CAUAJM_W_10631 Error with database <autosys>.  Checking connection.
[10/13/2022 10:40:05]      CAUAJM_W_10632 Attempting to reconnect to database <autosys>.  Attempt number [1].

At this point the Oracle client hung. Autosys was not aware.

Though we cannot solve this issue from autosys side. We can setup an alert for client hang from autosys 12.0 SP1 cum1.

With this fix, a new configuration variable

WaitTriesForBlockedOracleClientBeforeAbort

needs to be added to $AUTOUSER/config.$AUTOSERV file. Default value will be 3.

It will abort after three attempts forcing the shadow to take over. Please refer to the following product documentation for more details

ALERT ON POSSIBLE ORACLE CLIENT HANG