Why does the datetime field fetched from a database using the Oracle 10g thin driver (classes12.jar) show the timestamp as zero in TIBCO IntegrationManager™ (IM) database tasks ?

Why does the datetime field fetched from a database using the Oracle 10g thin driver (classes12.jar) show the timestamp as zero in TIBCO IntegrationManager™ (IM) database tasks ?

book

Article ID: KB0086550

calendar_today

Updated On:

Products Versions
TIBCO IntegrationManager -
Not Applicable -

Description

Resolution:
A different behavior is seen with Oracle 9i and Oracle 10g thin drivers (classes12.jar) while trying to fetch the date field from a Oracle 10g database task in IM. Prior to Oracle 9.2, Oracle JDBC drivers mapped the DATE Data type to java.sql.Timestamp that contained both date and time information. In Oracle 9.2, the TIMESTAMP data type support was added. In the JDBC drivers of Oracle 9.2 and later, the Oracle DATE datatype is mapped to java.sql.Date and the Oracle TIMESTAMP datatype is mapped to java.sql.Timestamp.

Since java.sql.Date object does not contain time information, if the database DATE column contains the time, that information is lost and the time part of the datetime is displayed as a zero timestamp. To resolve this issue, you can set the system property, oracle.jdbc.V8Compatible, to true in your imse / imed.tra file.

Example: java.extended.properties -Xms128m -Xmx512m -Doracle.jdbc.V8Compatible=true

Issue/Introduction

Why does the datetime field fetched from a database using the Oracle 10g thin driver (classes12.jar) show the timestamp as zero in TIBCO IntegrationManager™ (IM) database tasks ?