Excellent. Thank you.
-----Original Message-----
From: Andrew Kerber [mailto:andrew.kerber@xxxxxxxxx]
Sent: Friday, December 18, 2015 9:15 AM
To: Terrian, Thomas J DLA CTR INFORMATION OPERATIONS
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: [Non-DoD Source] Re: time stamps with Data Guard
If you set the time zone of the standby server at the os level to match the
time zone of the primary server at the os level, then there wont be a problem.
Also, check the exact data type you are storing. If you are storing time stamp
with time zone, you dont have a problem to begin with.
On Fri, Dec 18, 2015 at 7:15 AM, Terrian, Thomas J DLA CTR INFORMATION
OPERATIONS <Tom.Terrian.ctr@xxxxxxx> wrote:
So, if I change the time zone of the standby, then (when we switchover)
if we look at sysdate if won't be the same as the O/S time? Oracle will
convert it over to whichever time zone I set it to?
-----Original Message-----
From: Andrew Kerber [mailto:andrew.kerber@xxxxxxxxx]
Sent: Friday, December 18, 2015 8:06 AM
To: Terrian, Thomas J DLA CTR INFORMATION OPERATIONS
Cc: oracle-l@xxxxxxxxxxxxx
Subject: [Non-DoD Source] Re: time stamps with Data Guard
You can set the time zone of the standby server to match the primary.
Sent from my iPhone
> On Dec 18, 2015, at 6:29 AM, Terrian, Thomas J DLA CTR INFORMATION
OPERATIONS <Tom.Terrian.ctr@xxxxxxx> wrote:
>
> We have a primary database in one time zone and a Data Guard copy in
another time zone. I know just about nothing about nls parameters, time zones,
etc. If we switch over to the stand-by copy its timestamp will be off by many
hours (records will get inserted based on the local time). When we switch back
any sorting on the timestamp fields will be out of order. Is there a parameter
I can set at the database level to keep the timestamps in order when we switch
back and forth?
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
