How to Troubleshoot Timezone Issues in Enterprise Manager Agent Setup?
(Doc ID 330737.1)
Last updated on FEBRUARY 19, 2019
Enterprise Manager Base Platform - Version 10.1.0.4 to 18.104.22.168 [Release 10.1 to 11.1] Information in this document applies to any platform.
***Checked for relevance on 20-Feb-2013***
This note provides steps for troubleshooting issues related to Timezone settings in a Grid Agent installation. An incorrect Timezone configuration in the Agent setup will prevent the Agent from starting up. This note can also be used for dbconsole. Be aware that the 10g dbconsole agent component is is built around the 10.1 Grid Control agent, and the 11g dbconsole agent component is built around 10.2 Grid control agent.
The Timezone setting discovered by the Agent is utilized for multiple operations: - The Agent collects metric data using timestamps based on the TZ setting of the Agent/target. The Metric data is uploaded to the repository 'as is' by the Loader into the relevant metric tables. - The Grid Console UI uses the TZ for each target to convert the metric data based on the TZ of the current page internally, etc.
Hence, if the TZ is wrongly configured at the Agent, it can also affect the timestamp related data seen in the Grid Console, for the discovered targets.
<Document 548928.1>: Enterprise Manager Grid Control Agent 10g, Process Control (Start, Stop & Status) Troubleshooting Guide <Document 359524.1>: How To Find Agents with time-skew problems
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!