EM 12c : emctl start agent Fails with Error 'Oracleagent12c1Agent service could not be started' 'Mismatch detected between timezone' Reported in emagent.nohup
(Doc ID 1950190.1)
Last updated on JUNE 20, 2023
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.1.0 and laterGeneric Windows
Generic Linux
Symptoms
$\AGENT_INST\bin\emctl.bat start agent
fails with following error
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
The Oracleagent12c1Agent service is starting..................
The Oracleagent12c1Agent service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
$\AGENT_INST\bin\emctl.bat start agent
fails with following error
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
The Oracleagent12c1Agent service is starting......
The Oracleagent12c1Agent service could not be started.
A service specific error occurred: 2.
More help is available by typing NET HELPMSG 3547.
OR
$/AGENT_INST/bin/emctl start agent
fails with following error
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Starting agent .... failed.
property 'agentTZregion' in '<Agent Base>/agent_inst/sysman/config/emd.properties' contains an invalid value of '+05:30'.Agent start up can not proceed.This value might have been manually modified to be an incorrect value.This value needs to be set to one of the values listed in '<Agent ORACLE HOME>/sysman/admin/supportedtzs.lst'. Execute 'emctl config agent getTZ' and see if this is an appropriate value.
Consult emctl.log and emagent.nohup in: <Agent Base>/agent_inst/sysman/log
<Agent Base>/agent_inst/sysman/log/emagent.nohup reports the following error
----- Tue Dec 20 23:42:18 2011::2572::Mismatch detected between timezone in env
(America/New_York) and in <Agent Base>\agent_inst/sysman/config/emd.properties (GMT). Forcing value to latter..
----- Tue Dec 20 23:42:18 2011::2572::The agentTZRegion value in <Agent Base>\agent_inst/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_ag
ent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.
<Agent Base>/agent_inst/sysman/log/emctl.log reports the following error
4532 :: Thu Nov 29 10:16:29 2012::Wrote PickedDefaultTZ=true in <Agent Base>/agent_inst\agent_inst/sysman/emd/agntstmp.txt
4532 :: Thu Nov 29 10:16:29 2012::Default timezone for the system is:GMT+05:30 which is not supported. Installing a default timesone of GMT
4532 :: Thu Nov 29 10:16:29 2012::An agentTZregion of 'GMT' is installed in <Agent Base>/agent_inst\agent_inst/sysman/config/emd.properties.
10672 :: Thu Nov 29 10:16:30 2012::<Agent Base>/agent_inst\core\12.1.0.2.0/bin/emdctl set_discovery_root plugin oracle.sysman.oh <Agent Base>\plugins\oracle.sysman.oh.discovery.plugin_12.1.0.2.0 12.1.0.2.0 (isDontRestart=0)
<Agent Base>/agent_inst/sysman/log/emagent.nohup reports the following error
----- Wed Jun 20 10:02:27 2012::6260::Mismatch detected between timezone in env (UTC) and in <Agent Base>\agent_inst/sysman/config/emd.properties (GMT). Forcing value to latter.. -----
----- Wed Jun 20 10:02:27 2012::6260::The agentTZRegion value in <Agent Base>\agent_inst\agent_inst/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 executes '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. -----
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 |