Re: Oracle Client showing time an hour behind

From: Saad Khan <saad4u_at_gmail.com>
Date: Tue, 11 May 2010 15:37:18 -0400
Message-ID: <AANLkTimyD4wMOpeRNJZ6PhuHwAHk9Zk_5GWKP3PKELpZ_at_mail.gmail.com>



Ok, I restarted the listener and that FIXED the problem..

wow, thanks Harel.

I tested it first in non-prod and then prod. It worked fine in both environments.

But only thing which bothers me a lil is that, on the non-prod environment, the dbtimezone is -04:00, while on prod, the dbtimezone is -05:00, earlier clients connecting to both environments were showing wrong time, now after listener restart, both are getting right time. So is it all about listener only?? The dbtimezone doesnt matter?

On Tue, May 11, 2010 at 2:40 PM, Saad Khan <saad4u_at_gmail.com> wrote:

> I'm testing it in non-prod right now.
>
> One more thing, the dbtimezone , I changed it to -05:00 But the
> sessiontimezone is still showing -04:00.
>
> How can I change the sessiontimezone now?
>
>
> On Tue, May 11, 2010 at 12:16 PM, Harel Safra <harel.safra_at_gmail.com>wrote:
>
>> Clients that connect through the listener inherit it's TZ settings. If you
>> did the change to DST by changing the TZ in your database server the
>> listener (an therefore the clients) won't detect the change until it's
>> restarted.
>> I've seen it happen several times.
>>
>> btw, restarting the listener isn't a traumatic event. Clients that are
>> connected will stay connected, the only influence is that during the restart
>> new clients can't connect to the database.
>>
>> Harel Safra
>>
>>
>> On 11/05/2010 18:56, Saad Khan wrote:
>>
>>>
>>> Harel, I'm not sure how listener start can help! I remember doing it in
>>> my previous change orders but I can try in non-prod env first.
>>>
>>>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue May 11 2010 - 14:37:18 CDT

Original text of this message