Inconsistent datatypes: expected NUMBER got TIMESTAMP

[Vishal69_]

Hi Friends,

Is there any way to resolve the above mentioned Subject.

While executing following query on Oracle DB in TD 3.0, it throws this error.

Select * from <table Name>

This happens only when there is a column having TimeStamp data type. When I use To_Char(TimeStampColumn) it gives proper Out Put.

Please help to resolve the above error.

Thanks & Regards,

Vishal SHAH
Sr. Software Developer.

[jmcnamara]

TD and Oracle Timespamp values sometimes don't play together nicely. Using 'select *' can be problematic because TD sometimes can't transalate the inbound data type. If you explicitly bind it to a date variable, it will usually work. The Oracle database version and client version might also be part of the issue. If you are using the Oracle 10g or 11g database & clients, make sure that the client side is higher than release 1 as there were issues with both R1 routers.

[Vishal69_]

even bind variable also dose not work some times...

yes, I am using Oracle 11g R2

Dose TD has new router for Oracle 11g ver ???

[Jeff Luther]

Does TD has new router for Oracle 11g ver ???

For TD v3.0. No, and there will not be. That is not a product suppored in development (for fixes, new releases, etc.)

Is I am sure you have read in other forum threads, a small test case can always be helpful from our side. This would allow checking with with newer TD releases to see if this is still an issue, since for one thing TD v3.0 from the Gupta days never supported Oracle 11g. See the chart here for what it did suspport:
http://www.guptatechnologies.com/Produc ... atrix.aspx