All right! that's what I'm talking about. I'll give it a shot. thanks.
"Holger Baer" <holger.baer_at_science-computing.de> wrote in message
news:3EDCD65B.40603_at_science-computing.de...
> ed zappulla wrote:
> > Thanks for the help. That's what I call a civil reply. Not like the
rest
> > of the trash talk here. I'm not a DBA and I'm not really responsible
for
> > this. I'm merely trying to help out another developer in the office.
The
> > funny thing is that we are using ORA 9.2.0.1.0 and are trying to connect
to
> > ORA 9.2.0.1.0. There was 8.16 installed previously and the thin driver
used
> > but that has been cleaned and removed completely (even registry entries)
> > with the new version installed into a new folder. We are still using
> > classes12.zip as the driver from the ora92\jdbc\lib folder. So it seems
> > like this is a bit more of an issue then anyone would have expected and
will
> > require escalation on our side. I would never have thought to search
for
> > "[ttcgcshnd-1], [0], [], [], [], [], [], []". Its so much jiberish.
Thanks
> > again for your help. It is noted and appreciated.
> >
> >
> >
>
> I've run into the same problem. No matter what you think, you *DO* use an
> pre 9i client. If you have metalink access, search for ttcgcshnd.
>
> After some reading I found a workaround that might help you as well:
> setting the event '10841 trace name context forever' does the trick.
>
> Note however, that this is an undocumented and unsupported workaround
> (well it's unsupported unless Oracle Support tells you to use it) ;-)
> so you might use it until you updated classes12.zip to the 9i version.
>
> HTH
>
> Holger
>
>
Received on Tue Jun 03 2003 - 14:51:30 CDT
