TIMESTAMP WITH LOCAL TIME ZONE is another variant of TIMESTAMP that includes a time zone offset in its value. It differs from TIMESTAMP WITH TIME ZONE in that 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 a user retrieves the data, Oracle returns it in the user's 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). This datatype is useful for displaying date information in the time zone of the client system in a two-tier application.

I think that the TSLTZ should use the time zone of the session but DST of the data.

I report this has as a bug to Oracle.

- Sometimes, session still hang forever without any reason. You kill them and they stay there.

Talking about 9i features, It took 10 years to become entry level compliant to Sql92 and still... For example (only one on many), Oracle does not support the "Top" in select for the n first records. They only support the awkward "where rownum...". 'Where' is made to applied restiction on records and here it is used to applied restriction on the full select...

You could have silly things like:

select 
  mesure_detail.CODE_CED,
  mesure_detail.sigle,
  mesure_detail.no_ligne,
  mesure_detail.mesure_id,
  mesure_detail.adresse_electrique lclcl,
  mesure_detail.status_mesure_description mes_desc,
  exception_traitement.date_inscription,
  message
from 
  exception_traitement
  inner join srv_calcul_localisation on (exception_traitement.exception_traitement_id = srv_calcul_localisation.exception_traitement_id)
  inner join mesure_detail on srv_calcul_localisation.mesure1_id = mesure_detail.mesure_id
where 
  rownum <= 20
order by
  exception_traitement.exception_traitement_id desc

Here the 'where' is fully weird because it apply restriction on the entire select statement (sort included). It is the world upside-down. Inner restriction on outer data. The regular behavior is you restrict then you apply sort.

select * from (
select 
  mesure_detail.CODE_CED,
  mesure_detail.sigle,
  mesure_detail.no_ligne,
  mesure_detail.mesure_id,
  mesure_detail.adresse_electrique lclcl,
  mesure_detail.status_mesure_description mes_desc,
  exception_traitement.date_inscription,
  message
from 
  exception_traitement
  inner join srv_calcul_localisation on (exception_traitement.exception_traitement_id = srv_calcul_localisation.exception_traitement_id)
  inner join mesure_detail on srv_calcul_localisation.mesure1_id = mesure_detail.mesure_id
order by
  exception_traitement.exception_traitement_id desc)
where 
  rownum <= 20

Talking about 9i features, It took 10 years to become entry level compliant to Sql92 and still...

Here the 'where' is fully weird because it apply restriction on the entire select statement (sort included). It is the world upside-down. Inner restriction on outer data. The regular behavior is you restrict then you apply sort.