OMS does not understand the timezone region of the agent – solved!

Hi,

I was having problems starting up the management agent (10.2.0.5) in a RedHat 5 Linux, I was constantly getting the following error:

2009-12-15 19:19:47,406 Thread-1317072 WARN  diagnostics.cpu: nmegam_ActivityManager_init: per-thread cpu usage not available for this platform
2009-12-15 19:19:50,251 Thread-1317072 ERROR pingManager: OMS does not understand the timezone region of the agent. Either start the OMS using the extended list of time zones supported by the database or pick a value of time zone from /u01/app/oracle/product/agent10g/sysman/admin/nsupportedtzs.lst , update the property 'agentTZRegion' in the file /u01/app/oracle/product/agent10g/sysman/config/emd.properties and restart the agent.A value which is around an offset of  +00:00 from GMT should be picked.
2009-12-15 19:19:50,251 Thread-1317072 ERROR : Signalled to Exit with status 55. OMS requested shutdown
2009-12-15 19:19:50,251 Thread-1317072 ERROR pingManager: Did not receive valid response to ping "UNK_TZ"

The error suggests to modify the value of agentTZRegion in the emd.properties with any of the values in the nsupportedtzs.lst

I did that, and then I followed the official procedure (Setting the Management Agent Time Zone)

But I was still getting the error until I found the answer in a forum

I just had to remove some files

rm -r $AGENT_HOME/sysman/emd/state/*
rm -r $AGENT_HOME/sysman/emd/collection/*
rm -r $AGENT_HOME/sysman/emd/upload/*
rm $AGENT_HOME/sysman/emd/lastupld.xml
rm $AGENT_HOME/sysman/emd/agntstmp.txt

And then the problem was gone! The monitoring agent started up nice and quickly!

Advertisements
This entry was posted in High-Availability, Linux/Unix, Oracle Server and tagged , , , , , . Bookmark the permalink.

One Response to OMS does not understand the timezone region of the agent – solved!

  1. Mike says:

    I had the same issue but cleaning up files didn’t quite do it. I also had to delete the agent registration in Grid Control and re-secure the agent.

    1. In Grid Control, browse to “All Targets” and find the agent for the server you’re fighting with.

    2. Click Remove.

    3. Now re-secure the agent with

    $AGENT_HOME/bin/emctl secure agent

    4. The agent should hopefully start for you now.

    $AGENT_HOME/bin/emctl start agent

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s