My Oracle Support Banner

EM 12c: emctl start agent Fails With Error 'OMS decided to shutdown the agent because of the following reason sent from OMS: AGENT_TZ_MISMATCH' Reported in emagent.nohup (Doc ID 1519859.1)

Last updated on APRIL 05, 2018

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.3.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Enterprise Manager (EM) 12c Cloud Control Agent start fails with this timezone error:

$/AGENT_INST/bin/emctl start agent

fails with following error

Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Starting agent .................................................................Consult the log files in: <Agent_Instance_Home>/sysman/log

 

$/AGENT_INST/sysman/log/gcagent.log  reports following error

2013-01-08 14:04:14,412 [1:3305B9] INFO - The job system is using the "UTF-8" character set for converting streamed text IO.
2013-01-08 14:04:14,431 [1:3305B9] INFO - fetching the "magic" incident exit code
2013-01-08 14:04:15,784 [1:3305B9] INFO - the "magic" incident exit code is 42
2013-01-08 14:04:18,619 [167:BD2151AA:GC.Executor.6 (oracle_database:SID:audit_failed_logins_historical) (oracle_database:SID:audit_failed_logins_historical:audit_failed_logins_historical)] WARN - Found a row with more columns than declared for the metric for TargetID = SID, Metric = audit_failed_logins_historical
Row = 2013-01-08 20:04:17 GMT,2012-11-30 06:00:00 GMT,1,30
2013-01-08 14:04:21,864 [1:3305B9] INFO - Agent is up and running.
2013-01-08 14:04:24,778 [38:3F09CD9D:pool-1-thread-3] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: SHUTDOWN AGENT_TZ_MISMATCH)
2013-01-08 14:04:25,162 [249:FC52DDBF:GC.SysExecutor.0 (ShutdownFromPing)] INFO - OMS decided to shutdown the agent because of the following reason sent from OMS:  AGENT_TZ_MISMATCH

 

$/AGENT_INST/sysman/log/emagent.nohup reports following error

 --- EMState agent
----- Tue Jan  8 14:03:35 2013::7892::Auto tuning the agent at time Wed Dec 31 18:00:00 1969 -----
UploadMaxBytesXML=50
_SchedulePersistTimer=30
MaxThreads=10
agentJavaDefines=-Xmx128M -XX:MaxPermSize=96M
SchedulerRandomSpreadMins=30
UploadMaxNumberXML=5000
Auto tuning was successful
----- Tue Jan  8 14:03:46 2013::7892::Finished auto tuning the agent at time Wed Dec 31 18:00:00 1969 -----
----- Tue Jan  8 14:03:46 2013::7892::Launching the JVM with following options: -Xmx128M -XX:MaxPermSize=96M -server -d64 -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-DoEscapeAnalysis -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- Tue Jan  8 14:03:46 2013::7892::Agent Launched with PID 7898 at time Tue Jan  8 14:03:46 2013 -----
----- Tue Jan  8 14:03:46 2013::7898::Time elapsed between Launch of Watchdog process and execing EMAgent is 12 secs -----
log4j:ERROR Could not find value for key log4j.appender.QA
log4j:ERROR Could not instantiate appender named "QA".
OMS decided to shutdown the agent because of the following reason sent from OMS:  AGENT_TZ_MISMATCH

Changes

 

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
 It is recommended to upgrade the EM 12c Cloud Control system to 12.1.0.4
 Alternatively, apply <Patch 17328776> to EM 12.1.0.2.2 OMS Oracle Home.
 Workarounds
 If the timezone information on the Agent host is correct and but it is incorrect in the Repository
 If the timezone is incorrect on the Agent host
References


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