Welcome Guest ( Log In | Register )


 
 
 
 
 
 

 
 
Oracle 

Performance Tuning Reference poster
 
Oracle training in Linux 

commands
 
Oracle training Weblogic Book
 
Easy Oracle Jumpstart
 
Oracle training & performance tuning books
 
Burleson Consulting Remote DB Administration
 
 
 
Reply to this topicStart new topic
> Oracle Enterprise Manager - Timezone mismatch
Douglas
post Oct 31 2008, 12:31 PM
Post #1


Newbie
*

Group: Possible Spammers
Posts: 1
Joined: 31-October 08
Member No.: 38,632



Hello,

I installed Oracle 10.2 on Redhat Linux and the database can be queried through sqlplus with no problem.
However, when I start the Enterprise Manage Database Control I get the following Timezone mismatch error.
My TZ environment value is set to US/Eastern, which also equals the agentTZRegion value of US/Eastern.
Can anyone help? Thanks.

Here is the listing from my console:

[oracle@haran emd]$ emctl start dbconsole
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright © 1996, 2005 Oracle Corporation. All rights reserved.
http://haran.seagull.org:1158/em/console/aboutApplication

Timezone mismatch: The agentTZRegion value (US/Eastern) in
/u01/app/oracle/product/10.2.0/db_1/haran.seagull.org_seagull/sysman/config/emd.properties
does not match the current environment TZ setting(US/Eastern).
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.

[oracle@haran emd]$ echo $TZ
US/Eastern
[oracle@haran emd]$
[oracle@haran emd]$
[oracle@haran emd]$ tail -20 /u01/app/oracle/product/10.2.0/db_1/haran.seagull.org_seagull/sysman/config/emd.properties
tracelevel.fetchlets.propEcho=WARN
tracelevel.fetchlets.readFromFile=WARN
tracelevel.fetchlets.readMultFromFile=WARN
tracelevel.fetchlets.throwable=WARN
tracelevel.fetchlets.resourceGrab=WARN
tracelevel.fetchlets.emSDK=WARN

# The following three properties are for HTTP timeout
# Timeout value for reading Http primary header, default is 30 seconds.
httpTimeoutPrimaryHeader=30

# Timeout value for reading http secondary headers, default is 30 seconds
httpTimeoutSecondaryHeaders=30

# Timeout value for reading http body, default is 60 seconds.
httpTimeoutBody=60
omsRecvDir=/u01/app/oracle/product/10.2.0/db_1/haran.seagull.org_seagull/sysman/recv
##agentTZRegion=US/Eastern
#
agentTZRegion=US/Eastern
[oracle@haran emd]$

Go to the top of the page
 
+Quote Post
andrew kerber
post Oct 31 2008, 02:53 PM
Post #2


Advanced Member
***

Group: Banned
Posts: 489
Joined: 16-November 07
Member No.: 14,089



I ran into this on my home cluster. I think, but have not been able to verify, that it has to do with the latest DST patch for the OS and/or Oracle, and the fact that we are between the normal date for going off DST and the date that was implemented most recently by congress. I suspect that there is some sort of mismatch there.
Go to the top of the page
 
+Quote Post
burleson
post Oct 31 2008, 03:12 PM
Post #3


Advanced Member
***

Group: Members
Posts: 11,623
Joined: 26-January 04
Member No.: 13



Like Andy sez, apply the DST patch first. Please check the metalink note 413327.1.

Also, try unseting the TZ environment variable and the dbconsole may start:

CODE
root$ unset TZ
root$ echo $TZ


--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 24th October 2014 - 04:15 PM