AwE-5016 Master TimeZone doesn't match the Database
search cancel

AwE-5016 Master TimeZone doesn't match the Database

book

Article ID: 89867

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Master can sometimes be seen in  TROUBLE Status with the following errors noted in the RmiServer log

Error MessageDetails:

AwE-5016 Master TimeZone doesn't match the Database 

Details: XX minutes offset

 

When looking at the UI, the timestamp in the lower right may show the correct timezone, but does not show the correct time.  For example, if the database and RMI Server should be CEST and should currently show 16:00, the time in the lower right of the UI may show 10:00 CEST (correct timezone of CEST, but incorrect time - here it is showing EST time).

Environment

CA Automic Applications Manage 9.x

Cause

This error is caused by a mismatch between the Applications Manager Oracle database and the time defined for the Master.

Resolution

- Verify the current time of the database by logging into the Applications Manager database and issuing:

     select to_char(sysdate,'YYYY MM DD HH24:MI:SS') from dual;

- Next verify the Master machine's time by running the following command:

Windows:
     time

Unix/Linux:
     date

- If this matches the database time,  then check to see if the Master and the Applications Manager's Oracle database are in the same timezone by logging into SQL Plus as the Applications Manager's user and run the following SQL:

     select sop.so_oper_name, ats.aw_tz_name, ats.aw_gmt_diff from so_operators sop, aw_timezone_list ats where sop.so_time_zone=ats.aw_tz_seq;

- Also run the following command to get the Master's timezone information from the aw_master_config table:

     select item, value from aw_master_config where item='MASTER_TIMEZONE';

- If the timezone information in these 2 queries doesn't match, please contact Technical Support.

 

If the timezones above all match, but the issue still persists, have a DBA check what the timezone on the listener is as in some cases the listener may have an incorrect timezone and Applications Manager is retrieving the database timezone through this.