Mar 2021 DST Change: Workaround to Grid Agent Restart Problem Due to a Daylight Savings Change in EST/BST TZs
(Doc ID 2764628.1)
Last updated on DECEMBER 01, 2021
Applies to:
Enterprise Manager Base Platform - Version 10.2.0.5 and laterInformation in this document applies to any platform.
Symptoms
Oracle Management Agent does not start.
$ emctl start agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting agent ...... failed.
The agentTZRegion value in /<Agent_HOME>/agent11g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.
Consult the log files in: /<Agent_Home>/agent11g/sysman/log
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting agent ...... failed.
The agentTZRegion value in /<Agent_HOME>/agent11g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.
Consult the log files in: /<Agent_Home>/agent11g/sysman/log
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |