Oracle Timestamp

Error:

When I try to pull back a timestamp from an oracle database, I get back the value oracle.sql.TIMESTAMP@1e2e861b, when I try to pull back the value as TO_CHAR, TO_DATE or TO_TIMESTAMP (in the query), I get back no results from the query at all.

 

Cause:

The response from oracle is incompatible with the JDBC driver connection

 

Solution:

Enable J2EE (Java/JDBC) compliance

1) Stop Adeptia Services
2) Navigate to the installation directory of Adeptia (\AdeptiaServer\ServerKernel\etc)
3) Take a backup of the launcher.properties file and place it on your desktop
4) Open the launcher.properties file and add this argument (-Doracle.jdbc.J2EE13Compliant=true) to the Kernel and Webrunner JVM parameters as below

#Kernel JVM parameters
KN:JVM: -Xms512M -Xmx1024M -Xrs -XX:PermSize=64M -XX:MaxPermSize=256M -Doracle.jdbc.J2EE13Compliant=true

#Webrunner JVM parameters
WB:JVM: -Xms256M -Xmx512M -Xrs -XX:PermSize=64M -XX:MaxPermSize=256M -Doracle.jdbc.J2EE13Compliant=true

5) Save the file
6) Start Adeptia Services

 

Note: This is a global change to all connections to Oracle databases, so it is recommended to deploy the change in a development environment and perform regression testing on the existing Oracle queries.

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.