Timestamp with fractions

I have problems getting "current_timestamp(6)" with microseconds. (System is NT/Windows2000))
Problem:
select to_char(current_timestamp,'yyyy-mm-dd-hh24.mi.ssxff6') from dual;
returns:
2003-01-14-14.00.27,976000
Even with changing the format model I have found no way of receiving the seconds-fractions with a precision of six.
Is this a specific problem with NT/windows2000 or is there some way to get oracle9.2 to return the needed precision?

Your system clock almost certainly doesn't report time to 6 digits of accuracy, so Oracle throws 0's on the end. I'm not aware of any machine that reports the time to more than 3 or 4 digits, but Oracle will be ready when such a machine comes out.
Justin

Similar Messages

Converting timestamp with timezone to milisecs

Hi guys,
How to converting timestamp with timezone to milisecs?
I'm using oracle 10g.

SeánMacGC wrote:
Hello, do you mean:
SQL> select to_char(systimestamp, 'SSSSS') from dual;
TO_CH
58435
'SSSSS' Format Model returns 'Seconds past midnight' not milliseconds. I wonder if OP meant Fractional Seconds?
SQL> SELECT TO_TIMESTAMP_TZ('1999-12-01 11:00:00.00532 -8:00',
2 'YYYY-MM-DD HH:MI:SS.FF TZH:TZM') col_1 FROM DUAL
3 /
COL_1
01-DEC-99 11.00.00.005320000 AM -08:00
SQL> SELECT TO_CHAR(col_1, 'FF') fractional_sec FROM
2 (SELECT TO_TIMESTAMP_TZ('1999-12-01 11:00:00.00532 -8:00',
3 'YYYY-MM-DD HH:MI:SS.FF TZH:TZM') col_1 FROM DUAL)
4 /
FRACTIONA
005320000
SQL>Regards,
Jo
Edited by: Joice John : Added Code Tags

Is it possible to create a timestamp with an accuracy of 1ms?

I want to acquire data with PCI-6023 and write them with a precise timestamp to a file. Is it possible to create a timestamp with an accuracy of 1ms?
Maybe somebody can tell me experiences with logging data over a time periode up to 24 hours (and time-accuracy of 1ms)?

Hi Hans, This forum is related to one of National Instruments' automation products rather than data aquisition. Perhaps you will acheive better results if you post your question to one of the "Measurement Devices" forms instead.

Partitioning on a table on the field TIMESTAMP WITH TIME ZONE

Hi I have a very large size table which has grown to a size that we are not able to query it efficiently. We have decided to partition the table. But the issue is the table has a TIMESTAMP WITH TIME ZONE field and not DATE. I have found some links on the web which state this might cause an error. I am planning to create a temp table with the partition rules and at the same time copy data from the original one.
using CREATE TABLE XYZ PARTITION BY RANGE (ABC) ( ---- Partition rules ------) NOLOGGING AS SELECT * FROM XYZ_ACTUAL where 1 = 2;
Then if it works fine, I would rename the table with partitions to the actual name.
Should all this be fine?
The database is very critical. Hence the dilemma.

Have you tried converting the timestamp with time zone to a character string as a partition key, possibly using an edit mask to control the timestamp components used?
Your plan sounds OK to me - if you can get the partitioned table created - but I would test in a development first o see where the lLw of Unintended Consequences might decide to manifest itself.
Edited by: riedelme on Dec 8, 2009 9:13 AM

Oracle ODBC driver and TIMESTAMP with timezone

Does anyone know if it is possible to return data from a "TIMESTAMP WITH TIMEZONE" column using the Oracle ODBC driver and an ADO Recordset?
I am using the Oracle driver version 10.2.0.2 and TIMESTAMP fields work fine.
I can call Recordset->Open() with a query like "SELECT * FROM TABLE" when the table contains a column of type timestamp with timezone but when I execute a statement to see if there are results as in
if (!(srcRecsetPtr->BOF && srcRecsetPtr->EndOfFile))
my application throws an unhandled exception and exits. The exception is not a COM exception and I'm not sure how to get back additional information if that's possible.
The only information I've been able to find in searching TechNet and MetaLink is that a workaround is to wrap the columns in a TO_CHAR or TO_DATE conversion first but that's not a good solution for my problem since I am executing user specified SQL which may join multiple tables.
I've found one other note that says the documentation should be corrected and that these fields are NOT supported period (Bug #4011640).
I've experimented with the Bind Timestamp as Date option in the ODBC connection and with various ALTER SESSION settings to attempt to change the NLS_TIMESTAMP_TZ_FORMAT but I have been unable to get past the problem.
Any ideas are greatly appreciated.
Thanks,
Troy

Hi Justin
Thanks for your help.
I tried what you mentioned and I could connect myself via SQL*Plus without passing a password and a login, Extern authentification seems to work and my user seems to be right configurated.
But he problem goes on via ODBC. When I test connection in the ODBC Data Source Administrator of Windows XP, test fails and seems to forbid connection without userID and password. When I try to connect via ODBC in my program the same problem appears : "Unable to connect SQLSTATE=28000 [Oracle][ODBC][ORA]Ora-01017: Invalid username/password;logon denied" I could not connect in this way.. What's wrong ?

Unique or primary key on timestamp with timezone

Hi,
I have been experimenting with a date column in a primary key, or actually I tried using a timestamp with time zone in a primary key.
While researching whether there was a way to avoid ORA-02329, I found the following:
K15> create table dumdum
2    (datum date not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> alter table dumdum
2    add constraint d_pk
3        primary key
4          (datum, naamp)
5    using index;
Table altered.
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_PK';
INDEX_TYPE
NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select sysdate - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_pk validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.46.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15> For the last select statement I get the following "explain plan":
SELECT STATEMENT CHOOSE
          Cost: 2 Bytes: 247 Cardinality: 13
     1 INDEX RANGE SCAN UNIQUE D_PK
                Cost: 3 Bytes: 247 Cardinality: 13 This behavior lived up to my expectations.
Then, I tried this:
K15> create table dumdum
2    (datum date not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> alter table dumdum
2    add constraint d_pk
3        primary key
4          (datum, naamp)
5    using index;
Table altered.
K15>
K15> alter table dumdum
2        modify datum timestamp(6) with time zone;
Table altered.
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_PK';
INDEX_TYPE
NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select sysdate - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_pk validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.46.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15> So, at first glance, the alter table statement to change the datatype from DATE to TIMESTAMP seems like a way of fooling Oracle. But the explain plan reveals a different story:
SELECT STATEMENT CHOOSE
          Cost: 4 Bytes: 1,25 Cardinality: 50
     1 TABLE ACCESS FULL DUMDUM
                Cost: 4 Bytes: 1,25 Cardinality: 50 I was only fooling myself. :-0
But I wasn't done with my research:
K15> create table dumdum
2    (datum timestamp(6) with time zone not null
3    ,naamp varchar2( 30 ) not null);
Table created.
K15>
K15> create unique index d_ind
2      on dumdum
3           (datum, naamp);
Index created.
K15>
K15>
K15> select ind.index_type
2 from   user_indexes ind
3 where ind.index_name = 'D_IND';
INDEX_TYPE
FUNCTION-BASED NORMAL
1 row selected.
K15>
K15> insert into dumdum
2    (datum
3    ,naamp )
4 select systimestamp - (level/1440)
5 ,      'nomen nescio'
6 from   dual
7 connect by level < 1000
8 ;
999 rows created.
K15>
K15> analyze index d_ind validate structure;
Index analyzed.
K15> analyze table dumdum compute statistics;
Table analyzed.
K15>
K15> select naamp
2 from   dumdum
3 where datum > to_date('16-06-2011 15.56.16', 'dd-mm-yyyy hh24.mi.ss' )
4
K15>Now, my explain plan looks fine:
SELECT STATEMENT CHOOSE
          Cost: 2 Bytes: 1,25 Cardinality: 50
     1 INDEX RANGE SCAN UNIQUE D_IND
          Cost: 3 Bytes: 1,25 Cardinality: 50 Why is Oracle so adamant about not allowing a timestamp with time zone in a unique key? And, given their position on the matter, where does their tolerance for a unique index come from?
By the way, if I had a say in it, I would not allow anything that even remotely looks like a date to be part of a primary key, but that's another discussion.
Thanks,
Remco
P.S. All this is on Oracle9i Enterprise Edition Release 9.2.0.8.0. Is it different on 10g or 11g?

See if this helps. You can create primary key for TIMESTAMP WITH LOCAL TIME ZONE datatype.
SQL>CREATE TABLE Mytimezone(Localtimezone TIMESTAMP WITH LOCAL TIME ZONE primary key, Location varchar2(20) );
Table created.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch4datetime.htm#i1006169
TIMESTAMP WITH LOCAL TIME ZONE Datatype
TIMESTAMP WITH LOCAL TIME ZONE is another variant of TIMESTAMP. It differs from TIMESTAMP WITH TIME ZONE as follows: data stored in the database is normalized to the database time zone, and the time zone offset is not stored as part of the column data. When users retrieve the data, Oracle returns it in the users' local session time zone. The time zone offset is the difference (in hours and minutes) between local time and UTC (Coordinated Universal Time, formerly Greenwich Mean Time).
Thanks
http://swervedba.wordpress.com/

Create table interval partition on a column timestamp with local time zone

Hi
Does anyone have an example for 11g on how to create a table with interval partitioning on a column defined as timestamp with local time zone. I know it's possible. the following does not work.
CREATE TABLE KOMODO_EXPIRED_RESULTS
TEST_EVENT_KEY NUMBER NOT NULL,
HPS_DEVICE_KEY NUMBER NOT NULL,
RCS_DEVICE_KEY NUMBER,
EVENT_START_TIMESTAMP TIMESTAMP(6) with local time zone NOT NULL,
BOOTROMVERSION NUMBER,
CHANNELNUMBER NUMBER,
CLIENTVERSION VARCHAR2(4000 BYTE),
ETHERNET_CRC_ERROR_COUNT NUMBER,
ETHERNET_DROPPED_PACKETS NUMBER,
ETHERNET_THROUGHPUT NUMBER,
ETHERNET_TRAFFIC_IN NUMBER,
ETHERNET_TRAFFIC_OUT NUMBER,
IPADDRESS VARCHAR2(4000 BYTE),
KOMODO_ID VARCHAR2(4000 BYTE),
LASTREBOOTTIME VARCHAR2(4000 BYTE),
OSVERSION VARCHAR2(4000 BYTE),
RECEIVER_AUDIOACCESSCONTROLER NUMBER,
RECEIVER_AUDIOBUFFEROVERFLOWS NUMBER,
RECEIVER_AUDIOBUFFERUNDERRUNS NUMBER,
RECEIVER_AUDIOCODEC VARCHAR2(4000 BYTE),
RECEIVER_AUDIODATADROPPED NUMBER,
RECEIVER_AUDIODATATHROUGHPUT NUMBER,
RECEIVER_AUDIODECODERERRORS NUMBER,
RECEIVER_AUDIODESCBUFFERUNDER NUMBER,
RECEIVER_AUDIODESCCRYPTOERROR NUMBER,
RECEIVER_AUDIODESCDATADROPPED NUMBER,
RECEIVER_AUDIODESCDATATHROUGH NUMBER,
RECEIVER_AUDIODESCDECODERERRO NUMBER,
RECEIVER_AUDIODESCDRMERRORS NUMBER,
RECEIVER_AUDIODESCPTSDELTA NUMBER,
RECEIVER_AUDIODESCPTSDELTAHAL NUMBER,
RECEIVER_AUDIODESCSAMPLESDROP NUMBER,
RECEIVER_AUDIODSPCRASHES VARCHAR2(4000 BYTE),
RECEIVER_AUDIOPTSDELTAHAL NUMBER,
RECEIVER_AUDIOSAMPLESDECODED NUMBER,
RECEIVER_AUDIOSAMPLESDROPPED NUMBER,
RECEIVER_AUDIOUNDERRUN NUMBER,
RECEIVER_BITRATE NUMBER,
RECEIVER_BUFFEROVERRUN NUMBER,
RECEIVER_BYTESCCRECEIVED NUMBER,
RECEIVER_BYTESRECEIVED NUMBER,
RECEIVER_CHANNEL NUMBER,
RECEIVER_DECODERSTALL NUMBER,
RECEIVER_DISCONTINUITIES NUMBER,
RECEIVER_DISCONTINUITIESPACKE NUMBER,
RECEIVER_DRIFT NUMBER,
RECEIVER_DROPPEDPACKETSUNTILR NUMBER,
RECEIVER_ECMLOOKUPERROR NUMBER,
RECEIVER_ECMPARSEERRORS NUMBER,
RECEIVER_PMTCHANGED NUMBER,
RECEIVER_REBUFFER NUMBER,
RECEIVER_SELECTCOMPONENTAUDIO NUMBER,
RECEIVER_TIMELINEDISCONTINUIT NUMBER,
RECEIVER_VIDEOACCESSCONTROLER NUMBER,
RECEIVER_VIDEOACCESSCONTROLUN NUMBER,
RECEIVER_VIDEOBUFFEROVERFLOWS NUMBER,
RECEIVER_VIDEOBUFFERUNDERRUNS NUMBER,
RECEIVER_VIDEOCODEC VARCHAR2(4000 BYTE),
RECEIVER_VIDEOCRYPTOERROR NUMBER,
RECEIVER_VIDEODATADROPPED NUMBER,
RECEIVER_VIDEODATATHROUGHPUT NUMBER,
RECEIVER_VIDEODECODERERRORS NUMBER,
RECEIVER_VIDEODRMERRORS NUMBER,
RECEIVER_VIDEODSPCRASHES VARCHAR2(4000 BYTE),
RECEIVER_VIDEOFIFORD NUMBER,
RECEIVER_VIDEOFIFOSIZE NUMBER,
RECEIVER_VIDEOFRAMESDECODED NUMBER,
RECEIVER_VIDEOFRAMESDROPPED NUMBER,
RECEIVER_VIDEOPTSDELTA NUMBER,
RECEIVER_VIDEOPTSDELTAHAL NUMBER,
RECEIVER_VIDEOUNDERRUN NUMBER,
SUBNETMASK VARCHAR2(4000 BYTE),
TUNER_BITRATE NUMBER,
TUNER_BUFFERFAILURE NUMBER,
TUNER_CCPACKETSRECEIVED NUMBER,
TUNER_CHANNEL NUMBER,
TUNER_DATATIMEOUTS NUMBER,
TUNER_DELIVERYMODE VARCHAR2(4000 BYTE),
TUNER_DROPPAST NUMBER,
TUNER_FILL NUMBER,
TUNER_HOLE NUMBER,
TUNER_HOLEDURINGBURST NUMBER,
TUNER_HOLEDURINGBURSTPACKETS NUMBER,
TUNER_HOLETOOLARGEPACKETS NUMBER,
TUNER_MAXIMUMHOLESIZE NUMBER,
TUNER_MULTICASTADDRESS VARCHAR2(4000 BYTE),
TUNER_MULTICASTJOINDELAY NUMBER,
TUNER_OUTOFORDER NUMBER,
TUNER_OVERFLOWRESET NUMBER,
TUNER_OVERFLOWRESETTIMES NUMBER,
TUNER_PACKETSEXPIRED NUMBER,
TUNER_PACKETSPROCESSED NUMBER,
TUNER_PACKETSRECEIVED NUMBER,
TUNER_PACKETSWITHOUTSESSION NUMBER,
TUNER_PARSEERRORS NUMBER,
TUNER_SRCUNAVAILABLERECEIVED NUMBER,
TUNER_TOTALHOLEPACKETS NUMBER,
TUNER_TOTALPACKETSEXPIRED NUMBER,
TUNER_TOTALPACKETSRECEIVED NUMBER,
TUNER_UNICASTADDRESS VARCHAR2(4000 BYTE),
RECEIVER_TUNEDFOR NUMBER,
MACADDRESS VARCHAR2(4000 BYTE),
RECEIVER_TOTALAVUNDERRUNS NUMBER,
RECEIVER_TOTALDISCONTINUITIES NUMBER,
SERVICEID VARCHAR2(4000 BYTE),
DRIVEPRESENT VARCHAR2(4000 BYTE),
STB_STATE VARCHAR2(32 BYTE),
PREV_EXPIRED NUMBER,
PREV_HOLES NUMBER,
PREV_RECEIVED NUMBER,
PREV_TIMESTAMP TIMESTAMP(6),
PREV_REBOOT VARCHAR2(4000 BYTE),
TOTALPACKETSEXPIRED_RATE NUMBER,
TOTALHOLEPACKETS_RATE NUMBER,
TOTALPACKETSRECEIVED_RATE NUMBER,
CONSTRAINT KOMODO_EXPIRED_RESULTS_PK
PRIMARY KEY
(HPS_DEVICE_KEY, EVENT_START_TIMESTAMP)
USING INDEX
TABLESPACE HPS_SUMMARY_INDEX
TABLESPACE HPS_SUMMARY_DATA
PARTITION BY RANGE (EVENT_START_TIMESTAMP)
INTERVAL( NUMTODSINTERVAL(1,'DAY'))
PARTITION DEFAULT_TIME_PART_01 VALUES LESS THAN (TIMESTAMP' 2010-08-01 00:00:00.000000000 +00:00')
LOGGING
COMPRESS FOR ALL OPERATIONS
TABLESPACE HPS_SUMMARY_DATA
NOCACHE
PARALLEL ( DEGREE DEFAULT INSTANCES DEFAULT )
MONITORING
/

I am not sure it can be done.
SQL> create table sales
2 (
3 sales_id number,
4 sales_dt TIMESTAMP(6) with local time zone NOT NULL
5 )
6 partition by range (sales_dt)
7 interval (numtoyminterval(1,'MONTH'))
8 ( partition p0901 values less than (to_date('2009-02-01','yyyy-mm-dd')) );
create table sales
ERROR at line 1:
ORA-14751: Invalid data type for partitioning column of an interval partitioned
table
SQL> ed
Wrote file afiedt.buf
1 create table sales
2 (
3 sales_id number,
4 sales_dt TIMESTAMP(6)
5 )
6 partition by range (sales_dt)
7 interval (numtoyminterval(1,'MONTH'))
8* ( partition p0901 values less than (to_date('2009-02-01','yyyy-mm-dd')) )
SQL> /
Table created.

Usage of java.sql.Timestamp with classes12.zip and ojdbc14.jar ?

Hi all,
If i'm using java.sql.Timestamp with classes12 it is functioning perfectly,
if i'm using ojdbc14 and java.sql.Timestamp it is functioning in different way and failing to do the action..
Example : update set xxx=yy where time = my Timestamp object set in Prepared statement
Hope to see the answer

http://forum.java.sun.com/thread.jspa?threadID=460615&messageID=2116517
Timestamp insert problem
Using the "classes12.zip" file that comes with the distribution for Oracle versions 8.1.6.x and 8.1.7.x, Oracle's DATE datatype is mapped to the "java.sql.Timestamp" class. However, the "ojdbc14.jar" driver maps DATE to "java.sql.Date", and "java.sql.Date" only holds a date (without a time), whereas "java.sql.Timestamp" holds both a date and a time.

Create a timestamp with current_timestamp but keeping the seconds as 00

Hi Everyone,
I was wondering if there is an easier/better way to use the current_timestamp as my base timestamp and display another timestamp with current time and the seconds as 00. E.g., 4:30:00. The below is working but I am thinking it is overly complex.
CAST('timestamp' || ' ' || char(39) || TRIM(CAST(YEAR(CURRENT_DATE) AS CHAR)) || '-' ||
CASE WHEN MONTH(CURRENT_DATE) = '1' THEN '01'
WHEN MONTH(CURRENT_DATE) = '2' THEN '02'
WHEN MONTH(CURRENT_DATE) = '3' THEN '03'
WHEN MONTH(CURRENT_DATE) = '4' THEN '04'
WHEN MONTH(CURRENT_DATE) = '5' THEN '05'
WHEN MONTH(CURRENT_DATE) = '6' THEN '06'
WHEN MONTH(CURRENT_DATE) = '7' THEN '07'
WHEN MONTH(CURRENT_DATE) = '8' THEN '08'
WHEN MONTH(CURRENT_DATE) = '9' THEN '09'
ELSE CAST(MONTH(CURRENT_DATE) AS CHAR) END || '-' ||
CASE WHEN DAYOFMONTH(CURRENT_DATE) = '1' THEN '01'
WHEN DAYOFMONTH(CURRENT_DATE) = '2' THEN '02'
WHEN DAYOFMONTH(CURRENT_DATE) = '3' THEN '03'
WHEN DAYOFMONTH(CURRENT_DATE) = '4' THEN '04'
WHEN DAYOFMONTH(CURRENT_DATE) = '5' THEN '05'
WHEN DAYOFMONTH(CURRENT_DATE) = '6' THEN '06'
WHEN DAYOFMONTH(CURRENT_DATE) = '7' THEN '07'
WHEN DAYOFMONTH(CURRENT_DATE) = '8' THEN '08'
WHEN DAYOFMONTH(CURRENT_DATE) = '9' THEN '09'
ELSE CAST(DAYOFMONTH(CURRENT_DATE) AS CHAR) END || ' ' ||
TRIM(CASE WHEN HOUR(CURRENT_TIMESTAMP) = '1' THEN '01'
WHEN HOUR(CURRENT_TIMESTAMP) = '2' THEN '02'
WHEN HOUR(CURRENT_TIMESTAMP) = '3' THEN '03'
WHEN HOUR(CURRENT_TIMESTAMP) = '4' THEN '04'
WHEN HOUR(CURRENT_TIMESTAMP) = '5' THEN '05'
WHEN HOUR(CURRENT_TIMESTAMP) = '6' THEN '06'
WHEN HOUR(CURRENT_TIMESTAMP) = '7' THEN '07'
WHEN HOUR(CURRENT_TIMESTAMP) = '8' THEN '08'
WHEN HOUR(CURRENT_TIMESTAMP) = '9' THEN '09'
ELSE CAST(HOUR(CURRENT_TIMESTAMP) AS CHAR) END) || ':' ||
TRIM(CASE WHEN MINUTE(CURRENT_TIMESTAMP) = '1' THEN '01'
WHEN MINUTE(CURRENT_TIMESTAMP) = '2' THEN '02'
WHEN MINUTE(CURRENT_TIMESTAMP) = '3' THEN '03'
WHEN MINUTE(CURRENT_TIMESTAMP) = '4' THEN '04'
WHEN MINUTE(CURRENT_TIMESTAMP) = '5' THEN '05'
WHEN MINUTE(CURRENT_TIMESTAMP) = '6' THEN '06'
WHEN MINUTE(CURRENT_TIMESTAMP) = '7' THEN '07'
WHEN MINUTE(CURRENT_TIMESTAMP) = '8' THEN '08'
WHEN MINUTE(CURRENT_TIMESTAMP) = '9' THEN '09'
ELSE CAST(MINUTE(CURRENT_TIMESTAMP) AS CHAR) END) || ':00' ||
char(39) AS TIMESTAMP)
Thanks in advance for any comments
Edited by: user10930658 on Mar 25, 2009 2:05 PM

timestampadd(SQL_TSI_SECOND, -second(current_timestamp ), current_timestamp )

Regarding timestamp with timezone

Hi,
I have the following timestamp with timezone issue.
From java program I am passing the datetime with timezone value to database (INTERVALTIME (column name)).
PrepareStatemenet statement;
java.util.Date dt = ISODateUtil.parse("2006-06-21T18:00:00+00:00");
SimpleTimeZone zone = new SimpleTimeZone(0,"IST");
Calendar cal = converting the dt to calendar;
cal.setTimeZone(zone);
statement.setTimestamp(col, new Timestamp(cal.getTimeInMillis()),cal);
In database INTERVALTIME (column name) coulmn type is TiMESTAMP WITH TIMEZONE.Database is in PDT (GMT-8) timezone.
Now the problem is :
Even if i send the datetime of IST timezone, it is displaying in PDT (GMT-8) timezone.
How can i resolve this issue?

Reo wrote:
The query you provided doesn't run. If I want to convert to a different timezone, I need the from_tz.Is column update_time a TIMESTAMP WITH TIME ZONE? If so, then no casting is needed:
SQL> create table test(id number,update_time timestamp with time zone)
2 /
Table created.
SQL> insert into test values(1,systimestamp)
2 /
1 row created.
SQL> insert into test values(2,systimestamp at time zone 'UTC')
2 /
1 row created.
SQL> select id,
2          update_time,
3          update_time at time zone 'US/Pacific'
4    from test
5 /
        ID
UPDATE_TIME
UPDATE_TIMEATTIMEZONE'US/PACIFIC'
         1
18-NOV-09 04.23.03.241000 PM -05:00
18-NOV-09 01.23.03.241000 PM US/PACIFIC
         2
18-NOV-09 09.23.29.346000 PM UTC
18-NOV-09 01.23.29.346000 PM US/PACIFIC
        ID
UPDATE_TIME
UPDATE_TIMEATTIMEZONE'US/PACIFIC'
SQL> SY.

TimeStamp with time zone vs java Date

In the developer's preview release notes, I read about the extended support on Oracle TimeStamp. We are currently planning to migrate current TIMESTAMP columns to TIMESTAMP WITH TIMEZONE to keep the user time zone with the typed date. Here is my question: Which time zone is persisted using a direct to field mapping between a java.util.Date and a TIMESTAMPTZ column? As the java.util.Date contains no time zone (in opposition to java.util.Calendar), does TopLink uses the JVM time zone? WHat is the best to data structure to keep date/time & time zone in our entities? Thanks, Yannick.

I believe it would be the local timezone of the session. If you map a Date to the TIMESTAMP TZ then the SQL written out will not include a TZ value.
Typically if you wish to map to a TIMESTAMPTZ field you would want to use an object in the model that can hold both the Timestamp and TZ values. This is most commonly a Calendar.
Doug

Oracle timestamp with timezone

Does CR support column of type "timestamp with timezone" column. I am getting error message "Failed to retrive data from database. Details:Not implemented". Thanks

Since this is the Crystal Reports Java forum, you need to specify the explicit Java java.sql Type that the Oracle JDBC driver exposes the database type as.
I'm not familiar with that data type, so don't know if it's mapped to the Timestamp type or not.
Note that CR4E 2.0 supports up to JDBC 4.0 types.
Sincerely,
Ted Ueda

Why have I lost the info of timezone (Timestamps with Timezone )

I have been trying to get timestamps with timezones working in my Java application, but I don't seem to get the data I expect back from the JDBC driver
my field type is Timestamps with Timezone ,in the database,I saw the info of (12-DEC-06 01.12.12.123000 PM -06:00),but I don't know How to get it from Java
I've use the Timestamp aa =rs.getTimestamp("FIELDVALUE");but the timezone is lost, what can I do?
thanks

Timestamps are always GMT based (or could be thought of as timezone neutral) so what you should get back is a timestamp representing a GMT equivalent of the time you see that has a 6 hour offset from GMT. In other words, if the time were 1 PM Central Standard you would get a GMT time of 7 PM.
You should then be able to display that time in any time zone you wish using SimpleDateFormat and specifying the time zone you want to display it in. So if you then display it with Central Standard, the 7 PM GMT would then display as 1 PM again. In other words, 7 PM GMT and 1 PM Central Standard are the same timestamp
If you just display the timestamp using a toString(), you will get the time in the default time zone of the JVM..
Whether the driver actually does this correctly with the Oracle database I can't say. I've made several posts in a variety of places complaining that the driver does not work correctly with timestamps but my experience is limited to regular timestamp fields, not the new Oracle type of timestamp with timezone.
Based on my experience, what you are more likely getting back in the 1 PM- 7 PM example is 7 PM in the default timezone of the JVM.
You should look at the getTimestamp with Calendar options to see if they work better for you.
The main thing to keep in mind is that timestamps are really timezone neutral.

Compare 2 'timestamp with timezone' columns

Hi All,
I'm trying to compare 2 'timestamp with timezone' columns,
comparision works fine as long as there is difference of at least seconds between them.
But when the difference between them is in milliseconds, comparison is failing.
I'm using oracle 10g.
Pls advice.

Works just fine:
SQL> DECLARE
2      t1 TIMESTAMP WITH TIME ZONE := TIMESTAMP '2008-01-10 10:25:17.123456 US/EASTERN';
3      t2 TIMESTAMP WITH TIME ZONE := TIMESTAMP '2008-01-10 10:25:17.323456 US/EASTERN';
4 BEGIN
5      IF t1 <= t2
6        THEN
7          DBMS_OUTPUT.PUT_LINE('t1 <= t2');
8      END IF;
9 END;
10 /
t1 <= t2
PL/SQL procedure successfully completed.
SQL> DECLARE
2      t1 TIMESTAMP WITH TIME ZONE := TIMESTAMP '2008-01-10 10:25:16.123456 US/EASTERN';
3      t2 TIMESTAMP WITH TIME ZONE := TIMESTAMP '2008-01-10 10:25:17.323456 US/EASTERN';
4 BEGIN
5      IF t1 <= t2
6        THEN
7          DBMS_OUTPUT.PUT_LINE('t1 <= t2');
8      END IF;
9 END;
10 /
t1 <= t2
PL/SQL procedure successfully completed.
SQL> Based on your:
But when the difference between them is in milliseconds, comparison is failing. Most likely your code does implicit/explicit timestamp conversion to date. Post your code.
SY.

TIMESTAMP with Microseconds

Hi all,
How can we get the Current System time in TIMESTAMP format which contains microseconds ?
(Sample format 2002-11-15 14:10:13.123456)
My requirement is we want to port our application which is using DB2 CLI to OCCI. In DB2 getting TIMESTAMP with microsecons is not a problem.
Does oracle 9i support TIMESTAMP with microseconds ? or Is there any other procedure to get the TIMESTAMP with microseconds in OCCI applications ?
Reference :- http://otn.oracle.com/products/oracle9i/daily/aug29.html
regards,
Raghavendra.Masineni

Hi all,
How can we get the Current System time in TIMESTAMP format which contains microseconds ?select systimestamp from dual (assuming 9i)
For pre-9i solutions, there are a few askTom articles of interest.
<http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:653903409743>
Justin

Timestamp with fractions

Similar Messages

Maybe you are looking for