Hi

I am trying to get 2 listeners working on the same machine, each using
a different timezone. I know this can be done on Linux/Unix boxes but
I can't seem to get it to stick on a Win2003 machine. I want my
original listener (port 1521) to use EST time and my other listener
(port 1525) to use PST.

If I set my windows timezone to PST and start my second listener, it
gives me the right time (in PST) when connecting from my client
machine. When I go to switch the timezone back to EST on my server,
the listener seems to pick up the new timezone and when I query again
(in the same sql session), I get the time on EST again.

Is this a limitation of Oracle Server on Windows or is there some
trick?

Thanks,
Dave

Dave wrote:
> Hi
>
> I am trying to get 2 listeners working on the same machine, each using
> a different timezone. I know this can be done on Linux/Unix boxes but
> I can't seem to get it to stick on a Win2003 machine. I want my
> original listener (port 1521) to use EST time and my other listener
> (port 1525) to use PST.
>
> If I set my windows timezone to PST and start my second listener, it
> gives me the right time (in PST) when connecting from my client
> machine. When I go to switch the timezone back to EST on my server,
> the listener seems to pick up the new timezone and when I query again
> (in the same sql session), I get the time on EST again.
>
> Is this a limitation of Oracle Server on Windows or is there some
> trick?

Hm, might be related to Windows as such settings are managed differently
than on *nix boxes.

What are you trying to achieve with this? I've never heard that someone
sets up two listeners to switch timezones, but then again I may be just
ignorant. Did you consider using SESSION_TIMEZONE to switch timezones
of sessions?

Kind regards

robert

Thanks... Well the situation is this.... "Hypothically" I outsouce
data for 2 customers on 1 instance. One is in CA and one MA. Each
wants to see data in their timezone.

IN *nix system, you can set the timezone variable and start the
listener. The listener then keeps that timezone while it runs. You
can then open another "session", set the timezone to something
different and then start the other listener. Each listener keeps the
timezone reference in which it was started.

In a production outsource environment, you would, of course, have a
Linus/Unix db server. But for the lowly developer, you take what you
can get....

How about storing the data with timezoen information? Depending on the
version, timezone is supported