My Oracle Support Banner

10g / 11g Grid Agent Startup Fails Due to DST Change in 2013 for Israel Timezone Asia/Jerusalem (Doc ID 1590852.1)

Last updated on NOVEMBER 08, 2019

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.5 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Symptoms

10g / 11g Agent fails to startup.

<AGENT_HOME>/sysman/log/emagent.nohup shows the below error:

----- Sun Sep  8 08:52:02 2013::The agentTZRegion value in C:\Oracle\OEM\agent10g/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 -----
--- Standalone agent
----- Sun Sep  8 12:13:50 2013::tzOffset for Asia/Jerusalem is 120(min), but agent is runnning with tzOffset 180(min)
-----
----- Sun Sep  8 12:13:50 2013::trying again after waiting for 1 sec to account for daylight transition
-----
----- Sun Sep  8 12:13:50 2013::tzOffset for Asia/Jerusalem is 120(min), but agent is runnning with tzOffset 180(min)
-----
----- Sun Sep  8 12:13:50 2013::Mismatch detected between timezone in env (Asia/Jerusalem) and in C:\Oracle\OEM\agent10g/sysman/config/emd.properties (Asia/Jerusalem). Forcing value to latter.. -----
----- Sun Sep  8 12:13:50 2013::The agentTZRegion value in C:\Oracle\OEM\agent10g/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 -----

-  Running the 'emctl resetTZ agent' command returns the below output:

$ emctl resetTZ agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Updating /ema/agent11g/betadb01.il.teva.corp/sysman/config/emd.properties...
----- Sun Sep 8 10:26:11 2013::tzOffset for Israel is 120(min), but agent is runnning with tzOffset 180(min)
-----
----- Sun Sep 8 10:26:11 2013::trying again after waiting for 1 sec to account for daylight transition
-----
----- Sun Sep 8 10:26:11 2013::tzOffset for Israel is 120(min), but agent is runnning with tzOffset 180(min)
-----
resetTZ failed.
The agentTZRegion in:
/ema/agent11g/betadb01.il.teva.corp/sysman/config/emd.properties
is not in agreement with what the agent thinks it should be.
Fix your environment.
Pick a TZ value that corresponds to time zone settings listed in:
/ema/agent11g/sysman/admin/supportedtzs.lst

-  Issue is not specific to any OS and may occur on any OS.

-  Timezone on the OS is set to Asia/Jerusalem.

-  Agent can startup fine if the OS TZ and the Agent TZ is set to some other value with the same offset for example: Europe/Athens.

Changes

From <Note 412160.1> - Updated DST transitions and new Time Zones in Oracle Time Zone File patches:

Israel decided on 9 July to change the end of DST to 02:00 on the last Sunday of October (27 oct for 2013). Tthe previous rule defined in  DSTV19 and DSTv20 was (for 2013-2026) that DST ends at 02:00 on the first Sunday after October 1 ( 6 oct for 2013).

If the Agent is using a lower version (DSTv18 or below) of the timezone files, then the "end of DST" will actually be on 8-September-2013.

Note:

To know the timezone file being used by the Agent, check the <AGENT_HOME>/oracore/zoneinfo/readme.txt.

For example, an entry as below at the top of the file:

Current Structure version: 2
Current Content Version  :4

means that the DST version files being used is DSTv4.

Timezones Affected: 

1. Asia/Jerusalem
2. Asia/Tel_Aviv
3. Israel

Also see <Note 1580237.1> - Israel changes DST end date in 2013 - Impact on Oracle RDBMS

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.