Re: jdbc driver problems
Date: Thu, 01 Feb 2001 18:42:00 GMT
Message-ID: <95call$3hf$1_at_nnrp1.deja.com>
- I used jdbc drivers from 8.0.5 for both 8.0.5 and 8.1.6 ( and also 7.3.4) databases successfully, no problem here. One bit of advice: check all your stuff with thin driver first.
- I think Cindy is right and you should check if all variables are bound properly. 8.1.6 has better (stricter) syntax and execution control, so it can catch some errors which 8.0.5 didn't catch.
In article <3A7928FC.4E2F2EC2_at_lion-ag.de>,
rinaldis_at_lion-ag.de wrote:
> Thanks fro the advice, but the problem is not in the code. As I wrote
I have
> this problem only passing from oracle 8.0.5 to oracle 8.1.6 and
switching
> drivers accordingly.
>
> Ciao,
> Manuel
>
> "C. Ferguson" wrote:
>
> > Hi,
> > double check your code:
> > For each placeholder you specified in the PreparedStatement, you
must
> > bind a value to it before executing...
> >
> > String myupdate = "update table foo set col1 = ?, col2 = ?, col3 =
? where
> > something = ?";
> >
> > (Note 4 placeholders: col1, col2, col3 are varchar2's and
something is a
> > number)
> >
> > PreparedStatement foo = con.prepareStatement(myupdate);
> > foo.setString(1, 'This');
> > foo.setString(2, 'is ');
> > foo.setString(3, 'a test');
> > foo.setInt(4, 5);
> >
> > foo.executeUpdate();
> >
> > (woa, just noticed you cross-posted to everybody and their
dog...please
> > refrain from this type of behavior...a good bet to get answers from
is the
> > server group, although you probably could have gotten this answer
from a
> > java users group...)
> >
> > hth,
> > cindy
> >
> > Emanuele de Rinaldis wrote:
> >
> > > Hi all,
> > >
> > > I've a problem in the upgrading from oracle 8.0.5 to oracle 8.1.6:
> > >
> > > when I use the jdbc drivers for oracle 8.0.5 I don't manage to get
the
> > > connection to oracle 8.1.6 , but when I use the drivers for oracle
8.1.6
> > > I get errors from preparedStatement.executeUpdate() method calls:
> > >
> > > ORA-01008: not all variables bound
> > >
> > > I tried either with jdk 1.2 and jdk 1.3 but the problem still
persist.
> > >
> > > Does anybody know how to solve the problem ? Any help will be
really
> > > apreciated...
> > >
> > > Thanks,
> > >
> > > Manuel de Rinaldis
>
> --
> LION bioscience AG, Waldhofer Str. 98, D-69123 Heidelberg
> Voice +49-(0)6221-4038-273 Fax +49-(0)6221-4038-290
> EMail emanuele.rinaldis_at_lionbioscience.com
>
>
Sent via Deja.com
http://www.deja.com/
Received on Thu Feb 01 2001 - 19:42:00 CET