RE: timestamp resolution
- From: "Ken Naim" <kennaim@xxxxxxxxx>
- To: <valpis@xxxxxxxxx>, "'Oracle Discussion List'" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 27 Sep 2007 09:10:26 -0400
What hardware is this running on. The timestamp function is dependent on
what precision your hardware and OS supports. Windows on dell only support 3
decimal places for example while other support down to 6.
Ken
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Johan Eriksson
Sent: Thursday, September 27, 2007 2:54 AM
To: Oracle Discussion List
Subject: timestamp resolution
Hi all
My environment is Red Hat 4, 64 bit and oracle 10.2.0.2 64bit
A newly created databases gives me some trouble. This query and output
is from another database
select current_timestamp from dual;
CURRENT_TIMESTAMP
---------------------------------------------------------------------------
27-SEP-07 08.41.39.980750 AM +02:00
all fine and dandy, if rerun all the decimals are changed, but running
on the new database gives me
27-SEP-07 08.41.39.980000 AM +02:00
and it is only the 2 first decimals that are changed, the rest is always
zeros.
Anyone who could advice on what could trigger this?
/johan
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
