I've got Agent 10.2.0.5.0. It was warking fine some time ago. Now I unable to start it. Checked logs and:
In emagent.nohup:
----- Wed Jun 9 08:51:43 2010::tzOffset for +02:00 is 120(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Jun 9 08:51:43 2010::trying again after waiting for 1 sec to account for daylight transition
-----
----- Wed Jun 9 08:51:43 2010::tzOffset for +02:00 is 120(min), but agent is runnning with tzOffset 180(min)
-----
----- Wed Jun 9 08:51:43 2010::Mismatch detected between timezone in env (UTC) and in /oracle/agent10g/sysman/config/emd.properties (+02:00). Forcing value to latter.. -----
Quantifier follows nothing in regex; marked by <-- HERE in m/+ <-- HERE 02:00=UTC/ at /oracle/agent10g/bin/EmctlCommon.pm line 541, <FH2> line 1.
In emdctl.trc:
2010-06-09 08:51:42,274 Thread-1 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =180,and testTZoffset for +02:00:120 do not match
2010-06-09 08:51:43,276 Thread-1 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =180,and testTZoffset for +02:00:120 do not match
So, i think it seems it is so called 'timezone issue'. I read in one of the posts here (
4220180 that it is possible to resolve using emdctl validateTZ agent command. But since I quite new to linux/unix I need your advise.
I run:
[oracle@xxxxx_tp4]$ grep agentTZ emd.properties
And received:
agentTZRegion=+02:00
So, my questions are:
1. Is it correct command to fix timezone in my case: emdctl validateTZ agent +02:00
2. Should I execute these commands before validateTZ with oracle user or root:
$ EMDROOT=$ORACLE_HOME
$ EMSTATE=$ORACLE_HOME
$ export EMDROOT EMSTATE
Waiting for any responce
Nikolajus