Hi,
Below is a description of a JDBC problem that causes Java programs to
fail on T64 4.0F although they worked on T64 4.0D.
Have any of you met this problem ?
Yours,
Lars Bro
-----Original Message-----
From: Lars Bro [mailto:lbr]
Sent: Friday, January 28, 2000 3:16 PM
To: 'support_rdbms_at_dk.oracle.com'
Subject: 122808
Hej, her er lidt dok...
Systemet er Tru64Unix 4.0f
-----Original Message-----
From: Arne Christensen [mailto:ach_at_nettest.dk]
Sent: Friday, January 28, 2000 2:49 PM
To: lbr
Subject: Oracle-fejl
A Java application accessing Oracle via JDBC fails when run on Tru64 Unix
4.0F, but not on earlier versions.
We use Oracle8 Enterprise Edition Release 8.0.5.0.0 and Thin JDBC driver
version 8.0.4.something or 8.0.5.0.0 (does not affect the result). The JDK
in use is version 1.1.7B-2.
The Java application uses placeholders ("?") in SQL queries and the
setInt/setString methods to supply values for these placeholders. It turns
out that on Tru64 Unix 4.0F, the setString method delivers its value to the
wrong placeholder or not at all, whereas on previous version of the
operating system, everything works fine. The same versions of Oracle, JDBC
driver and JDK were used in both configurations.
The attached small Java program was used to pinpoint the problem. Its
results are consistent with the faulty behaviour that our application
exhibits. The Java program simply does a SELECT ?, ?, ? FROM DUAL, supplying
a varying number of string and integer values for the placeholders, and
displays whatever the JDBC driver returns. The results are surprising; a
number of examples are also attached.
- application/octet-stream attachment: tt.java
Received on Mon Jan 31 2000 - 09:05:50 NZDT