How to identify which of the dual WAAE event server is the source for the database synchronization using autobcpDB or native database tools after a database rollover occurs?
search cancel

How to identify which of the dual WAAE event server is the source for the database synchronization using autobcpDB or native database tools after a database rollover occurs?

book

Article ID: 13594

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys)

Issue/Introduction

 

If you configured CA Workload Automation AE to run in dual event server mode and one event server goes down, CA Workload Automation AE automatically rolls over to the second event server and continues running in single event server mode. After you recover the event server that failed, you must synchronize the two event servers before configuring CA Workload Automation AE to run in dual event server mode again.

 



 

How to identify which of the two WAAE event server is the source for the database synchronization using autobcpDB (or native database tools) after a database rollover occurs?

Environment

CA Workload Automation AE 11.3 and higher on all supported Operating System and databases with Dual Event Server configuration.

Resolution

 

One should rely on the Scheduler logs to decide which of the two databases went down and which database was used to switch to single server (database) mode:

The messages to watch out for, in the Scheduler logs, are given below:

CAUAJM_W_10635 Rolling over to single server mode. Using database <EventServer2>.
CAUAJM_W_10648 The database: EventServer1 is unavailable. Attempting to rollover to single server mode.
CAUAJM_I_10659 The CA WAAE Shadow Scheduler has rolled over to single server mode.

Is this example, EventServer1 is the Primary DB and EventServer2 is the Secondary DB, and the Scheduler rolled over to EventServer2.

If you want to further validate the databases, then following suggestions might be useful:

Execute the following SQL against both the databases and compare the results

 

1. Check the row count of the ujo_proc_event table which stores all events processed by the Scheduler.

Oracle:- select count(*) from aedbadmin.ujo_proc_event;

Sybase , MS SQL Server:- select count(*) from ujo_proc_event

Decider: The DB with the higher row count is the most recent.

2. Check the date and timestamp of the event processed last, before the AE instance was brought down for DB sync activity.

Oracle: select to_char(max(QUE_STATUS_STAMP),'Month DD, YYYY HH24:MI:SS') from aedbadmin.ujo_proc_event;

Sybase , MS SQL Server: select max(QUE_STATUS_STAMP),'Month DD, YYYY HH24:MI:SS' from ujo_proc_event

Decider: The DB with the most recent date/timestamp is the current.


3. Check which database has the most recent Event OID generated.


Oracle: select oid from aedbadmin.ujo_next_oid where field = 'eoid';

Sybase, MS SQL Server: select oid from ujo_next_oid where field = 'eoid'

Decider: The DB with greater number is the most recent.

 

After the synchronization activity, to see if the databases are equal, then the following SQLs may help:

1. Confirm both the databases have equal number of active jobs defined.

Oracle: select count(*) from aedbadmin.ujo_job where IS_ACTIVE=1 and IS_CURRVER=1;

Sybase, MS SQL Server: select count(*) from ujo_job where IS_ACTIVE=1 and IS_CURRVER=1

 

2. Confirm that the last_eoid_counter table entries match

Oracle: select * from aedbadmin.ujo_last_eoid_counter;

Sybase, MS SQL Server: select * from ujo_last_eoid_counter

Additional Information

 

CA DocOps: Configure CA Workload Automation AE to Run in Dual Event Server Mode