current_timestamp, local time zone question/issues
798578Sep 30 2010 — edited Oct 1 2010I'm trying to track down a curious issue.
A package inserts data into a table the column data type is timestamp with local time zone.
The package puts upon insert current_timestamp into this column.
I am getting timestamps in the future put in. But not consistently. (10.2.0.3)
Wondering if anyone else has seen this. I'll be putting a TAR (SR if you prefer) with oracle in but I find
a lot of times the community has a quick answer on these sorts of things.
So basically I see the time going in, and it's the time that would be for the timezone in question but in the wrong time zone.
Let me explain.
Let's say it's 4pm Eastern current time (1pm Pacific). I alter my session to 'US/Pacific' inserting in to the table results in a time of 7pm Eastern going in the table. If my current session is set to US/Pacific it will say 4pm which is the current time for eastern, but is not correct obviously as that time has not arrived yet.
Anyone else seen this sort of behaviour and if so what caused it?
thx