000028944 - KB-1276 How to resolve timezone errors when starting OEM agent

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028944
Applies ToAffected Versions: All Versions
IssueWhen attempting to start the Oracle OEM console, the user saw this error:
 
$ emctl start dbconsole
Timezone mismatch: The agentTZRegion value (US/Eastern) in
/u01/app/oracle/product/10.2.0/db_1/appliance2900.aveksa.local_AVDB/sysman/config/emd.properties
does not match the current environment TZ setting(US/Central).
The dbconsole cannot run with this mismatch.
If US/Eastern is the correct timezone, set your timezone environment variable to US/Eastern
and repeat the 'emctl start dbconsole' operation.
If US/Eastern is not the correct timezone, make sure that the timezone in your environment
is correct, and then run the following command in your local Oracle Home: 'emctl resetTZ agent'
The output of this command will include detailed instructions to follow, to correct the mismatch.




 
CauseThe user checked the system time and it is correct for their Timezone. They checked the

database instance 'time' (via logfile time stamps) and saw that it did not match the system

timezone.
ResolutionTo correct this, run the following command as the oracle user.





$ emctl resetTZ agent



The output of this will looking something like this:





TZ set to US/Eastern

Oracle Enterprise Manager 10g Database Control Release 10.2.0.2.0

Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.

Updating /u01/app/oracle/product/10.2.0/db_1/vm-support-01.aveksa.local_AVDB/sysman/config/emd.properties...

Time zone set to US/Eastern.

To complete this process, you must either:



connect to the database served by this DBConsole as user 'sysman', and execute:



SQL> exec mgmt_target.set_agent_tzrgn('vm-support-01.aveksa.local:3938','US/Eastern')



-- or --



connect to the database served by this DBConsole as user 'sys', and execute:



SQL> alter session set current_schema = SYSMAN;

SQL> exec mgmt_target.set_agent_tzrgn('vm-support-01.aveksa.local:3938','US/Eastern')







To complete the process, execute the 'bottom' sql commands, logged into Oracle as sysdba, thus:



$ sqlplus "/as sysdba"

SQL> alter session set current_schema = SYSMAN;

SQL> exec mgmt_target.set_agent_tzrgn('vm-support-01.aveksa.local:3938','US/Eastern')

SQL> exit



The OEM agent should now be able to be started, via:



$ emctl start dbconsole
NotesIf the Database Instance has the correct time, and the appliance does not, refer to

KB-1168 How to set timzone and correct time on the appliance

Attachments

    Outcomes