aka Oracle 10g agent
Today we received a sev2 ticket regarding an agent that was down. Don’t know why, seeing as the daylight savings time issue occurred on the 29th of March. Below the transcript of starting the agent:
W2ZZXJFF02(agent):/ora/product/agent/10203/agent10g/sysman/log>emctl start agent Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0. Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. Starting agent ....... failed. The agentTZRegion value in /ora/product/agent/10203/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(, ) to get the value propagated to repository. Consult the log files in: /ora/product/agent/10203/agent10g/sysman/log W2ZZXJFF02(agent):/ora/product/agent/10203/agent10g/sysman/log>emctl config agent getTZ Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0. Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. GMT+01:00
What now, you ask ? Of course, i googled and the first hit was a direct hit. Below my attempt:
2ZZXJFF02(agent):/ora/product/agent/10203/agent10g/sysman/log>emctl resetTZ agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Updating /ora/product/agent/10203/agent10g/sysman/config/emd.properties...
----- Thu Apr 2 12:03:51 2009::tzOffset for +01:00 is 60(min), but agent is runnning with tzOffset 120(min)
-----
----- Thu Apr 2 12:03:51 2009::trying again after waiting for 1 sec to account for daylight transition
-----
----- Thu Apr 2 12:03:51 2009::tzOffset for +01:00 is 60(min), but agent is runnning with tzOffset 120(min)
-----
resetTZ failed.
The agentTZRegion in:
/ora/product/agent/10203/agent10g/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:
/ora/product/agent/10203/agent10g/sysman/admin/supportedtzs.lst
W2ZZXJFF02(grid04):/export/home/oracle>sqlplus "/as sysdba"
SQL> alter session set current_schema = SYSMAN;
Session altered.
SQL> select SYS_CONTEXT('USERENV','CURRENT_SCHEMA') as current_schema from dual;
CURRENT_SCHEMA
--------------
SYSMAN
SQL> exec mgmt_target.set_agent_tzrgn('W2ZZXJFF02.ah.nl:3872','Europe/Amsterdam');
That’s it, you’re done.