Hey Mike, The OCI-21500 is definitely an Oracle problem. It's like the dreaded ORA-600 error in that it should never happen. The main difference is that OCI-21500 is a client problem.
Are you running an unpatched client (9.0.1.0.0)? If so, you'll want the 183MB 9.0.1.4.0 Linux patch from Oracle. There is mention of a fix to one particular OCI-21500 error in the readme, but I don't know if it's applicable to your situation or not. If you're not able to get the patch, consider upgrading/migrating to v9.2. The same fix is in there. HTH! GL! Rich Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA > -----Original Message----- > From: Mike McCauley [mailto:mikem@;open.com.au] > Sent: Wednesday, October 23, 2002 6:06 AM > To: Tim Bunce > Cc: [EMAIL PROTECTED] > Subject: Re: timeout, disconnect on DBD Oracle 9i causes ORA internal > error > > > Hi Tim and all, > > > On Wed, 23 Oct 2002 20:40, Tim Bunce wrote: > > Try doing the disconnect inside the signal handler. > > Interesting thought, but alas it didnt work. > Still get the same internal error and core dump when > disconnect is called. > > I couldnt really see anything relevant in the Oracle API > other than OCIBreak, > which is what $sth->cancel() calls. > > Oracle seems to still think its inside some low level code, > even though we > signalled out of it and then called OCIBreak. I wonder if > there is any code > or API for resetting the comms stack in Oracle after a signal? > > Sigh.
