RE: Duplicate timestamp(6): How is this possible?

  • From: "Dunbar, Norman (Capgemini)" <norman.dunbar.capgemini@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • To: <michaeljmoore@xxxxxxxxx>, "Stephane Faroult" <sfaroult@xxxxxxxxxxxx>
  • Date: Thu, 20 Jan 2011 08:42:51 -0000

Morning Michael,

>> I believe I may have figured this out. I am using 
>> current_timestamp. I believe that for a given moment in 
>> time, this value could be different depending on the 
>> location of the user. 'believe' because I'm not really sure. 

Current_timestamp is the "session" timestamp (actually, TIMESTAMP WITH
TIME ZONE) and as such can be duplicated due to the same time being hit
in two different timezones.

>> I think that if I change the default to SYSTIMESTAMP, the 
>> local server timestamp will be populated. 

It will, regardless of where the users are located. SYSTIMESTAMP is
always the database server time. Unless you get really "lucky" you
shouldn't have duplicates. SYSTIMESTAMP is also a TIMESTAMP WITH TIME


Norman Dunbar
Contract Senior Oracle DBA
Capgemini Database Team (EA)
Internal : 7 28 2051
External : 0113 231 2051

Information in this message may be confidential and may be legally privileged. 
If you have received this message by mistake, please notify the sender 
immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should 
still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under 
the Freedom of Information Act, Data Protection Act or for litigation.  Email 
messages and attachments sent to or from any Environment Agency address may 
also be accessed by someone other than the sender or recipient, for business 

If we have sent you information and you wish to use it please read our terms 
and conditions which you can get by calling us on 08708 506 506.  Find out more 
about the Environment Agency at

Other related posts: