Re: Oracle JDBC problem

From: dg <dvillalo_at_avega.com>
Date: 23 Jan 2003 12:59:20 -0800
Message-ID: <921a292a.0301231259.4077cc9a_at_posting.google.com>


Had the same problem after upgrading from 8.1.7 to 9.2.0.

Get the latest jdbc driver from technet (free, no metalink account required). This fixed the problem.

Alternately, add the following line to your init.ora file & bounce the database, but this is really just a work-around, not a fix.

"event=10841 trace name context forever"

qwert12345_at_boxfrog.com (Doug Baroter) wrote in message news:<fc254714.0301221149.1ce0b80a_at_posting.google.com>...
> Thanks, bung ho. As I mentioned, SQL*Plus client execution of the SQL
> statement was fine. Would you think download newer jdbc driver and do
> reinstallation might be the best cause of action?
>
> bung_ho_at_hotmail.com (bung ho) wrote in message news:<567a1b1.0301210904.4a804358_at_posting.google.com>...
> > are you executing that SQL from sqlplus or something else? it appears
> > that the most common cause for that error is using pre-9i thin jdbc
> > drivers against a 9i db.
> >
> >
> >
> > qwert12345_at_boxfrog.com (Doug Baroter) wrote in message news:<fc254714.0301201527.be52044_at_posting.google.com>...
> > > SQL: select banner from v$version
> > > against an Oracle9i db resulted in the following error:
> > >
> > > ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [],
> > > [], [], [], []
> > >
> > > I don't have access to Oracle's bug reporting web site, could some one
> > > kindly post it?
> > >
> > > Secondly, is there any alternative to find current server version
> > > other than the above query? Thanks.
Received on Thu Jan 23 2003 - 21:59:20 CET

Original text of this message