Jobs scheduled in IST timezone run 30 minutes later than scheduled
Article ID: 84616
Updated On:
Products
CA Automic Applications Manager (AM)
Issue/Introduction
Error Message :
N/A
Jobs defined in Applications Manager (AM) that have schedules that use the IST time-zone run 30 minutes later than their scheduled time.
N/A
Jobs defined in Applications Manager (AM) that have schedules that use the IST time-zone run 30 minutes later than their scheduled time.
Cause
Cause type:
Defect
Root Cause: Definition of IST incorrectly set as GMT 5 in the aw_timezone_list table causing jobs which have schedules using IST to run 30 minutes late.
Defect
Root Cause: Definition of IST incorrectly set as GMT 5 in the aw_timezone_list table causing jobs which have schedules using IST to run 30 minutes late.
Environment
OS Version: N/A
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
Applications Manager 9.1.1 - Available
Applications Manager 8.0.17 - Available
Fix Status: Released
Fix Version(s):
Applications Manager 9.1.1 - Available
Applications Manager 8.0.17 - Available
Additional Information
Workaround :
Log into the Application Manager database as the AM Oracle userid and run the following SQL.
SQL>update aw_timezone_list set aw_gmt_diff = 5.5 where aw_tz_name = 'IST'; SQL>commit;
This will adjust the 30 minute time discrepancy with IST schedules.
BEWARE: If awinstall is run using a version that does not contain the fix after running the above update statement, the default value will revert back to GMT5.
Log into the Application Manager database as the AM Oracle userid and run the following SQL.
SQL>update aw_timezone_list set aw_gmt_diff = 5.5 where aw_tz_name = 'IST'; SQL>commit;
This will adjust the 30 minute time discrepancy with IST schedules.
BEWARE: If awinstall is run using a version that does not contain the fix after running the above update statement, the default value will revert back to GMT5.
Feedback
Powered by
