Oracle timestamp with time zone

Similar Questions

• Error recovery DB TIMESTAMP WITH time ZONE SCHEDULE

  I use Managed Driver version 4.121.1.0 with EF. Trying to extract data from a table that contains a column what data type is TIMESTAMP WITH time ZONE SCHEDULE, I get a "System.InvalidTimeZoneException" in Oracle.ManagedDataAccess.dll.

  This is the statement that I'm executing:

  application of var = db. COORDENADA. Select (x = > new {ID = x.COORDENADAID, CREATED = x.FECHAHORAGPS}). ToList();

  var RES = query. ToList();

  When debugging of I am, I can see the SQL to run:

  SELECT

  "Extent1". "" COORDENADAID "AS"COORDENADAID. "

  "Extent1". "' FECHAHORAGPS ' AS 'FECHAHORAGPS '.

  OF "GEOTRACKER. "" COORDENADA ""Extent1 ".

  which causes no problem in Oracle SQL Developer and get these data:

  COORDENADAID FECHAHORAGPS

  ------------ ----------------------------------

  1 06/03/14 17:10:10, EUROPE 000000000

  / PARIS

  2 02/03/14 00:00:00, 000000000 EUROPE

  / PARIS

  ...

  I think there must be something with the time format returned as name instead of offset, but I can't understand how to check this. Any idea

  This bug has been fixed in Oracle DB 12.1.0.1.6 patch bundle which can be downloaded from My Oracle Support (MOS). After you download the patch bundle, you'll notice that it's a pretty important download. There is no need to install the patch to the entire group on your target computer. Instead, simply extract the managed provider and just install it.

  If you do not have access to MOS, ask your DBA that should, or you can wait for the next version of the ODAC for the fix.

• A question about the insertion of the localTimeStamp returned the value into a timestamp with time zone column

  Hello

  Oracle version: Enterprise Edition Release 12.1.0.1.0 - 64 bit

  OS: CentOS 4.6 X86_64                  

  I have a question about the localTimeStamp function. According to the documentation for this function is
  the same thing as current_TimeStamp except that the returned value does not include the time zone.

  Consider the following example:

  SQL > create table tmptab (colval timestamp with time zone not null);

  Table created.

  SQL > insert into tmptab (colval) values (localTimeStamp);

  1 line of creation.

  SQL > select t1.colval, tmptab from t1;

  COLVAL

  ---------------------------------------------------------------------------

  24 JANUARY 14 09.45.42.253732 H + 01:00

  SQL >

  Why introduce the foregoing did not fail? the data type of the column in my table colval expects a timestamp with time zone

  during each which inserts as I understand (correct me if I'm wrong) is not provided by the localTimeStamp function.

  Could someone kindly tell me what I misunderstood?

  Thanks in advance,

  dariyoosh wrote:

  Hello

  Oracle version: Enterprise Edition Release 12.1.0.1.0 - 64 bit

  OS: CentOS 4.6 X86_64                  

  I have a question about the localTimeStamp function. According to the documentation for this function is
  the same thing as current_TimeStamp except that the returned value does not include the time zone.

  Consider the following example:

  SQL > create table tmptab (colval timestamp with time zone not null);

  Table created.

  SQL > insert into tmptab (colval) values (localTimeStamp);

  1 line of creation.

  SQL > select t1.colval, tmptab from t1;

  COLVAL

  ---------------------------------------------------------------------------

  24 JANUARY 14 09.45.42.253732 H + 01:00

  SQL >

  Why introduce the foregoing did not fail? the data type of the column in my table colval expects a timestamp with time zone

  during each which inserts as I understand (correct me if I'm wrong) is not provided by the localTimeStamp function.

  Could someone kindly tell me what I misunderstood?

  Thanks in advance,

  Then, when you do

  create table t (neck DATE);

  Insert into t (to_date ('1st January 2014', ' mon-dd-yyyy "");)

  Are you surprised that it works? After all a DATE column contains a time component, you do not provide: but he

  works and gives you 00:00:00 as the component "hour".

  Similarly, the timezone component is being developed to automatically with, I think, time zone of your system.

• How get/check out the time portion of timestamp with time zone?

  Using Oracle 10 g, I have a timestamp with time zone.
  
  We have treatment that uses hourly (as a shift of the day of treatment). I want to 'get' the time contained in a timestamp, so that I can compare it to one of our differences for example (pseudocode)
  
  If the time in the timestamp = 0 then
  treatment of midnight
  on the other
  do other hourly treatment
  FI
  
  I thought that "extract" was the right way to get the time portion of the time stamp, but it returns an interval based on UTC - so where I could expect
  
  SELECT extract (time OF THE TIMESTAMP ' 2009-06-08 00:34:56 Europe/London ') FROM dual
  
  to return to 0, it is actually 23 since it's time for the time zone UTC.
  
  Then... How should I be getting time in order to have it make 'sense' in the context of its time zone? I simply use to_char and analyze the time part?
  
  Thoughts?
  
  --
  Andy

  Not the literal timestamp ' 2009-06-08 00:34:56 Europe/London ' specifies TIMESTAMP (9) WITH ZONE TIME, subsequent DISTRIBUTION converts this TIMESTAMP value (6).

• Store and retrieve Date timestamp with time zone in the database

  Hi Experts,
  

  Required Date Format:
  YYYY-MM-DDTHH:MM:SS.[timestamp][timezone] 

  Can anyone suggest then how should I store the date in the database?
  
  
  Thank you
  Dharan V

  You can use the TIMESTAMP WITH TIME ZONE data type:

  SQL> create table tab (mydate timestamp with time zone);
  
  Tabella creata.
  
  SQL> insert into tab values (systimestamp);
  
  Creata 1 riga.
  
  SQL> select to_char(mydate,'yyyy-mm-dd"T"hh24:mi:ss.ff3 TZR')
    2  from tab;
  
  TO_CHAR(MYDATE,'YYYY-MM-DD"T"HH24:MI:SS.FF3TZR')
  --------------------------------------------------------------
  2010-01-30T09:50:53.814 +01:00
  

  Max

• Validation XSD using XS: DateTime with time zone without xdb:SQLType

  I work on code that performs XSD validation on an XML document in an Oracle database. I managed to get the validation running code, but Oracle complains about the way in which an element xs: DateTime is provided with the 'Z' at the end stating that it is the hour UTC. The error I get is;

  ORA-30992: an error has occurred in Xpath [Xpath of the element xs: DateTime]

  ORA-01830: date format picture ends before converting all of the input string

  This has been resolved by removing me the 'Z' of the time, which will make "2013-08 - 06T 12: 29:15Z' in ' 2013 - 08 - 06 T 12: 29:15'." After spending a bit of time to research, I could identify if I included some Oracle XDB namespace and specified the "xdb:SQLType =" TIMESTAMP WITH TIME ZONE "' for this item it will happen the XSD validation correctly, allowing for the marker of the UTC at the end unfortunately for me, it means I should get a XSD which is maintained on the international stage in many organizations changed to include the" specific annotations Oracle, which won't be easy. I was wondering if anyone knows anyway I can specify using code that the timestamp must understand the marker of the UTC, rather than having to get the XSD document changed

  I know I could make these changes only the local copy of the XSD, but I would consider it as a last resort because it would add an additional human step to any update and we know all the error-prone how we fleshy meat bags are.

  Thanks for any help or advice, anyone is able to give to this topic.

  Sam

  I know I could make these changes only the local copy of the XSD, but I would consider it as a last resort because it would add an additional human step to any update and we know all the error-prone how we fleshy meat bags are.

  It does not necessarily require someone (human) make the changes.

  For example, you could imagine including the amendment as part of the standard installation process and use something like this to do the job:

  SQL > declare

  2

  3 my_schema xmltype: = xmltype)

  4'http://www.w3.org/2001/XMLSchema">

  5

  6

  7

  8

  9

  10

  11

  12       '

  13       ) ;

  14

  result 15 clob;

  16

  17 start

  18

  19 dbms_xmlschema_annotate.setTimeStampWithTimeZone (my_schema);

  20

  21 select xmlserialize (document my_schema dash) in the double result;

  22 dbms_output.put_line (result);

  23

  24 end;

  25.

  http://www.w3.org/2001/XMLSchema"xmlns:xdb ="http://xmlns.oracle.com/xdb">."

  PL/SQL procedure successfully completed

  DBMS_XMLSCHEMA_ANNOTATE is part of a separate set of tools must be installed on the db.

  The set is available here: http://download.oracle.com/otn/samplecode/xdb_util.zip

• Working with time zones

  Hey everybody.

  I have a problem, I have some information that I get from an external source, which is a date UTC Epoch.

  I want to see the/Modify on a DateField

  The problem is, if I display it on a DateField, default peripheral lag is added, so I'm on GMT + 2, and the era time I get is 15:00, 17:00 it appears.

  I want it to be displayed at 15:00.

  now, I know that the time zone is registered in the java.util.Date object, you can get away with DateFormat.format)

  is there a way I can set the time zone to GMT dates?

  Thank you very much

  Omri

  Check java.util.Calendar and java.util.Timezone classes

• Oracle Timestamp with the right date

  Hello

  I have a date field, but it must be stated in the report as follows: -.

  day - 2014-08-14, but it should be shown in the report as "2014-08-14 00.00.00.0000'"

  Select TO_CHAR (TO_DATE ('2014-08-11 ',' YYYY-MM-DD'), "YYYY-MM-DD HH24:MI:SSxFF") double - it does not work.

  any help appreciated.

  Select to_char (cast (DATE ' timestamp' 2014-08-11),'YYYY-MM-DD HH24:MI:SS.) FF4') are the result of the double

  RESULT
  2014-08-11 00:00:00.0000

  Concerning

  Etbin

• timestamp with local time zone

  Hello
  I created a table as follows:
  
  create table timetest
  (date of col1,
  timestamp col2,
  COL3 timestamp with time zone,
  COL4 timestamp with local time zone.
  year apart col5 in the month,
  day apart col6 in the second
  )
  
  inserted a line like:
  insert into timetest values (sysdate, sysdate, sysdate, sysdate, 13-11' year to month INTERVAL,
  ('13 2:59:59.111233' INTERVAL DAY (2) second (6))
  
  When I select * from timetest
  I have found no difference between col2 and col4, I mean timestamp and timestamp with local time zone.
  Please tell me the difference between these two.
  
  thnx in advance

  TIMESTAMP WITH LOCAL TIME ZONE:-always displays the date stored in the local time zone setting i.e. According to the session's time zone setting.
  TIMESTAMP WITH time ZONE:-it will always displays the values stored regardless of the settings of the session.

  Instead of insert sysdate insert localtimestamp and systimestamp into your table.
  insert into values tab (SYSTIMESTAMP, SYSTIMESTAMP);

  insert into tab (LOCALTIMESTAMP, LOCALTIMESTAMP) values;

  Then you must define the different session time zone as the time zone database. I have change the zone session affecting different database.

  SQL > alter session set time_zone = "-03: 00 ';"
  Modified session.

  SQL > select dbtimezone, sessiontimezone double;
  DBTIMEZONE SESSIONTIMEZONE
  ---------- ----------------
  -07:00 - 03:00

  To select it and see the difference.

• DataPump with different time zone files

  Hello

  I'm trying to import a schema with datapump to a 12 c in oracle 11.2 instance oracle instance. I got an error cause different time zone files. 11.2 is on version 14 and 12 c is on version 18. So I tried to import a single table, make a new export with that one table (table got no timestamp with time zone column data type) and exported. That has worked well. So I modified my schema export to exclude these tables with columns with data type timestatmp with time zone. When you try to import this new dump, it still does not for the same reason.

  So, to import a table worked, but import a schema failed. Does anyone have a suggestion for me, how can I import this discharge? And no, I can't install a patch with the new zone files.

  sql_coder

  I could solve it myself, had to exclude more tables, not only those with timestamp with time zone, but also excluded arrays with data like AQ types $ _ %.

  sql_coder

• time zone - with unknown time zone

  I am able to run it:
  
  
  Select current_timestamp to the time zone "America/Los Angeles.
  of the double
  
  
  My problem is that the zone, which in this case is ' American/of Los Angeles', does not know until the moment of execution. So I want to replace it with a bind variable or pl/sql. When I do this:
  
  Select current_timestamp to the zone: tz
  of the double
  
  
  I get "Keyword not found". Any ideas?
  
  Thank you.
  
  Published by: usmanwvu on August 2, 2012 13:52
  
  Published by: usmanwvu on August 2, 2012 13:53

  If you do this in PL/SQL, you don't have to select the double at all - you could do something like

  declare
    v_ts   TIMESTAMP WITH TIME ZONE;
    v_tz   VARCHAR2(30);
  begin
    v_tz := 'American/Los_Angeles';
    v_ts := CURRENT_TIMESTAMP AT TIME ZONE v_tz;
  end;
  /
  

  Alternatively, in SQL, if you si vous Enroulez wrap the bind variable in an NVL function you can either give a default zone valid or invalid according to how you want it behaves on no entry:

  select current_timestamp at time zone NVL(:TZ,'American/Los_Angeles') from dual;
  

  Kind regards
  Bob

• convert timestamp timestamp in another time zone

  Hello
  
  I'm trying to convert a TIMESTAMP to a correspondent of value computing in a different time zone. However, I want the result to be another TIMESTAMP, not TIMESTAMP WITH TIMEZONE. How can I do this?
  
  Thank you.

  If you have a timestamp without time zone and you need to convert timestamp in a different zone time, right? Fistr you must throw source timestamp timestamp with time zone time (my example uses the default time zone set for the database) and then convert it in another time zone and cast result back to timestamp without time zone:

  with t as (
             select to_timestamp('10/12/2010 17','mm/dd/yyyy hh24') ts_est from dual
            )
  select  ts_est,
          cast(cast(ts_est as timestamp with time zone) at time zone 'PST' as timestamp) ts_pst
    from  t
  /
  
  TS_EST
  ---------------------------------
  TS_PST
  ---------------------------------
  12-OCT-10 05.00.00.000000000 PM
  12-OCT-10 02.00.00.000000 PM
  
  SQL> 
  

  SY.

• TIMESTAMP and TIMESTAMP WITH TIMEZONE

  Pretty simple scenario. A table with 2 columns, without constraints. Column of TS is the TIMESTAMP data type. Column TS_TZ is the TIMESTAMP WITH TIME ZONE data type. Accuracy for both is 4. I'm studying explicit data type conversions. In order to enhance my understanding, I'm experimenting with the insertion of string literals:

  INSERT INTO TEST_DATA_TYPES (ts, ts_tz)

  VALUES (19-SEPT-14 02:24:14 ', 19-SEP-14 02:24:14 ');

  The attempt above raise 01840. 00000 - 'entry not long enough for the date format value.

  INSERT INTO TEST_DATA_TYPES (ts, ts_tz)

  VALUES (19-SEPT-14 02:24:14 ', 19-SEP-14 02:24:14 ');

  INSERT INTO TEST_DATA_TYPES (ts, ts_tz)

  VALUES (19-SEPT-14 02:24:14 ', 19-SEP-14 02:24:14.0');

  Two inserts above work. Note that I changed was the chain of ts_tz. In one, I added 'AM' and in others I added a fraction of a second. He was the first attempt fail because Oracle needs some sort of explicit indication where precision ends before the name of the region can be added?

  Hello

  2679789 wrote:

  ... In order to enhance my understanding, I'm experimenting with the insertion of string literals:

  INSERT INTO TEST_DATA_TYPES (ts, ts_tz)

  VALUES (19-SEPT-14 02:24:14 ', 19-SEP-14 02:24:14 ');

  ...

  It is very important to understand that you should not use a string where other data type (for example, a TIMESTAMP) is expected; She simply asked in trouble.  Even if make you it work properly today, you can do something next week, as apply a patch, that will not not have to work.  Use the conversion functions explicitly, like TO_TIMESTAMP, iwhen, you must.  Never rely on implicit conversions.

  Learn exactly why a given implicit conversion may not be a good way to invest your time.

• overloading a DATE with time STAMP function to avoid the "too many declarations.

  CREATE OR REPLACE PACKAGE util
  AS
    FUNCTION yn (bool IN BOOLEAN)
      RETURN CHAR;
  
    FUNCTION is_same(a varchar2, b varchar2)
      RETURN BOOLEAN;
  
    FUNCTION is_same(a date, b date)
      RETURN BOOLEAN;
  
    /* Oracle's documentation says that you cannot overload subprograms
     * that have the same type family for the arguments.  But, 
     * apparently timestamp and date are in different type families,
     * even though Oracle's documentation says they are in the same one.
     * If we don't create a specific overloaded function for timestamp,
     * and for timestamp with time zone, we get "too many declarations 
     * of is_same match" when we try to call is_same for timestamps.
     */
    FUNCTION is_same(a timestamp, b timestamp)
      RETURN BOOLEAN;
  
    FUNCTION is_same(a timestamp with time zone, b timestamp with time zone)
      RETURN BOOLEAN;
  
    /* These two do indeed cause problems, although there are no errors when we compile the package.  Why no errors here? */
    FUNCTION is_same(a integer, b integer) return boolean;
  
    FUNCTION is_same(a real, b real) return boolean;
  
  END util;
  /
  
  CREATE OR REPLACE PACKAGE BODY util
  AS
    /********************************************************************************
       NAME: yn
       PURPOSE: pass in a boolean, get back a Y or N
    ********************************************************************************/
    FUNCTION yn (bool IN BOOLEAN)
      RETURN CHAR
    IS
    BEGIN
      IF bool
      THEN
        RETURN 'Y';
      END IF;
  
      RETURN 'N';
    END yn;
  
    /********************************************************************************
       NAME: is_same
       PURPOSE: pass in two values, get back a boolean indicating whether they are
                the same.  Two nulls = true with this function.
    ********************************************************************************/
    FUNCTION is_same(a in varchar2, b in varchar2)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    FUNCTION is_same(a in date, b in date)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
    
    FUNCTION is_same(a in timestamp, b in timestamp)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    FUNCTION is_same(a in timestamp with time zone, b in timestamp with time zone)
      RETURN BOOLEAN
    IS
      bool boolean := false;
    BEGIN
      IF a IS NULL and b IS NULL THEN bool := true;
      -- explicitly set this to false if exactly one arg is null
      ELSIF a is NULL or b IS NULL then bool := false;
      ELSE bool := a = b;
      END IF;
      RETURN bool;
    END is_same;
  
    /* Don't bother to fully implement these two, as they'll just cause errors at run time anyway */
    FUNCTION is_same(a integer, b integer) return boolean is begin return false; end;
    FUNCTION is_same(a real, b real) return boolean is begin return false; end;
    
  END util;
  /
  
  declare
   d1 date := timestamp '2011-02-15 13:14:15';
   d2 date;
   t timestamp := timestamp '2011-02-15 13:14:15';
   t2 timestamp;
   a varchar2(10);
   n real := 1;
   n2 real;
  begin
   dbms_output.put_line('dates');
   dbms_output.put_line(util.yn(util.is_same(d2,d2) ));
   dbms_output.put_line(util.yn(util.is_same(d1,d2) ));
   dbms_output.put_line('timestamps'); -- why don't these throw exception?
   dbms_output.put_line(util.yn(util.is_same(t2,t2) ));
   dbms_output.put_line(util.yn(util.is_same(t,t2) ));
   dbms_output.put_line('varchars');
   dbms_output.put_line(util.yn(util.is_same(a,a)));
   dbms_output.put_line(util.yn(util.is_same(a,'a')));
   dbms_output.put_line('numbers');
   -- dbms_output.put_line(util.yn(util.is_same(n,n2))); -- this would throw an exception
  end;
  /

  Originally, I had just the a function with the arguments of VARCHAR2. It worked not correctly because when the dates were gone, the automatic conversion into VARCHAR2 lowered the timestamp. So, I added a 2nd function with the arguments to DATE. Then I started to get "too many declarations of is_same exist" error during the passage of time stamps. This made no sense to me, so, although documentation Oracle says you can't do this, I created a 3rd version of the function, to manage the TIMESTAMPS explicitly. Surprisingly, it works fine. But then I noticed that he did not work with TIMESTAMP with time zones. Therefore, the fourth version of the function. Docs of the Oracle say that if your arguments are of the same family, you can't create an overloaded function, but in the example above shows, it's very bad.
  
  Finally, just for grins, I created the functions of number two, one number, the other with REAL and even these are allowed - they are compiled. But then, at runtime, it fails. I'm really confused.
  
  Here's the apparently erroneous Oracle documentation on this subject: http://docs.oracle.com/cd/B12037_01/appdev.101/b10807/08_subs.htm (see overload subprogram names) and here are the different types and their families: http://docs.oracle.com/cd/E11882_01/appdev.112/e17126/predefined.htm.
  
  Published by: hot water on 9 January 2013 15:38
  
  Published by: hot water on 9 January 2013 15:46

  >
  So, I added a 2nd function with the arguments to DATE. Then I started to get "too many declarations of is_same exist" error during the passage of time stamps. It makes no sense for me
  >
  This is because when you pass a TIMESTAMP Oracle cannot determine whether to implicitly convert to VARCHAR2 and use your first function or implicitly convert to DATE and use your second function. Where the "too many declarations" error exist.
  >
  , even if said Oracle documentation you can not do, so I created a 3rd version of the function to manage the TIMESTAMPS explicitly. Surprisingly, it works fine. But then I noticed that he did not work with TIMESTAMP with time zones.
  >
  Perhaps due to another error "too many declarations? Because now, there will be THREE possible implicit conversions that might be made.
  >
  Therefore, the fourth version of the function. Docs of the Oracle say that if your arguments are of the same family, you can't create an overloaded function, but in the example above shows, it's very bad.
  >
  I think that the documentation, of the family of 'date', is wrong as you suggest. For WHOLE and REAL, the problem is that those are the ANSI data types and are really the same Oracle data type; they are more like "alias" that different data types.

  See the doc of SQL language
  >
  ANSI SQL/DS and DB2 data types

  The SQL statements that create tables and clusters allows also ANSI data types and products IBM SQL/DS and DB2 data types. Oracle recognizes the ANSI or IBM data type name that differs from the Oracle database data type name. It converts the data type for the equivalent Oracle data type, stores the Oracle data type under the name of the column data type and stores the data in the column in the data type Oracle based on the conversions listed in the following tables.

  INTEGER NUMBER

  INT

  SMALLINT
  NUMBER (38)

  FLOAT (Note b)

  DOUBLE-PRECISION (Note c)

  REAL (Note d)
  FLOAT (126)

  FLOAT (126)

  FLOAT (63)

• Display data DateTime Fields in the local time zone

  I have a table defined as follows:
  
  create table TimeTest
  (
  DATETIME TIMESTAMP (0) WITH TIME ZONE
  )
  
  I insert two lines where the time zone changes to a date given in the spring:
  insert into timetest values (datetime) (to_timestamp_tz (' 08/Mar/2009:01:59:55-0500 ',' DD/my/YYYY:HH24:MI:SS TZHTZM ""));
  insert into timetest values (datetime) (to_timestamp_tz (' 08/Mar/2009:03:00:00-0400 ',' DD/my/YYYY:HH24:MI:SS TZHTZM ""));
  
  How can I select the datetime field in the time zone of my choice? If my session time zone is - 0400, should not 01:59:55-0500 displayed as time 02:59:55?
  
  The session time zone is:
  Select double sessiontimezone;
  -04:00
  
  So why do I get this:
  Select to_char (datetime, ' DD/my/YYYY:HH24:MI:SS TZHTZM "") of timetest;
  08/Mar / 2009:01:59:55-0500
  08/Mar / 2009:03:00:00-0400
  
  I thought I would get this result instead:
  08/Mar / 2009:02:59:55-0400
  08/Mar / 2009:03:00:00-0400
  
  Thank you
  Troy
  
  Published by: cforasun on April 8, 2010 17:36

  It is stored as a timestamp with time zone, so you must cast in the local time zone for your database:

  Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
  Connected as fsitja
  
  SQL>
  SQL> create table TimeTest (DATETIME TIMESTAMP(0) WITH TIME ZONE);
  
  Table created
  SQL> insert into timetest(datetime) values (to_timestamp_tz('08/Mar/2009:01:59:55 -0500', 'DD/Mon/YYYY:HH24:MI:SS TZHTZM'));
  
  1 row inserted
  SQL> insert into timetest(datetime) values (to_timestamp_tz('08/Mar/2009:03:00:00 -0400', 'DD/Mon/YYYY:HH24:MI:SS TZHTZM'));
  
  1 row inserted
  SQL> commit;
  
  Commit complete
  SQL> select datetime, cast(datetime as timestamp(0) with local time zone) from timetest;
  
  DATETIME                                          CAST(DATETIMEASTIMESTAMP(0)WIT
  ------------------------------------------------- --------------------------------
  08/03/09 01:59:55 -05:00                          08/03/09 03:59:55
  08/03/09 03:00:00 -04:00                          08/03/09 04:00:00
  
  SQL>