-1.46782934822 IS NOT A VALID TIMESTAMP

usuarioincorrecto · Post by **usuarioincorrecto** » Wed 26 Sep 2007 12:20

Hi;

Well;
I'm having problems with Oracle 10g through ODAC with Direct Option.
Sometimes, not always, we are having some Delphi Errors, like "1.4659874632 IS NOT A VALID TIMESTAMP". The number changes.

We HAVE NOT ANY field in Oracle of TIMESTAMP TYPE.

With Oracle 8i this didn't happen. I don't know wether it will work with Oracle Client or not in Oracle 10g. I haven't proved it yet.

Do you know about some ORACLE DATA TYPES, or something similar, which have changed since Oracle 8.1.7 (8i) to Oracle 10g?

With Delphi 6, ODAC 4.50.1.18, Oracle 8.1.7 it works OK.
With Delphi 6, ODAC 10.0.1.10, Oracle 10g, it fails sometimes.

How the NLS_TIMESTAMP_FORMAT parameter, in the Session should be defined?.... What is more... should be defined if we don't work with that kind of fields?. We have 'DD/MM/YYYY HH24:MI:SSXFF' defined for the NLS_TIMESTAMP_FORMAT.

Any Idea about this error and how to solve it?
Have you ever reproduced any error like this?

Thank you very much.

Plash · Post by **Plash** » Thu 27 Sep 2007 08:05

This error can occur if the TOraQuery or another ODAC component that you use, has fields created at design time. Try to recreate the fields in Fields editor using a connection to the new server.