On Fri, Oct 15, 2004 at 10:06:03AM -0600, Alan Sparks wrote:
> On Tue, 2004-10-12 at 01:05, Tim Bunce wrote:
> > On Mon, Oct 11, 2004 at 02:16:16PM -0600, Alan Sparks wrote:
> > > I've seen several posting regarding problems people have seen on Linux
> > > with Oracle 9 client libraries and DBD::Oracle, causing an ORA-03113
> > > end-of-file on communication channel error when querying through
> > > database links.  I did not, however find any solutions...
> > > 
> > > So, we have the problem also, with Oracle 9.2.0 and DBD::Oracle 1.15 on
> > > RHEL 3... talking to an Oracle 8.1.7 server.  Trace files show the
> > > server process dumps core and traces out.
> > 
> > The server process dumping core is, by definition, an Oracle bug.
> > 
> > > Anyway, is there anyone out there who has managed to find a workaround
> > > for the problem, either by a DBD::Oracle change or an Oracle patch?
> > 
> > Please open a TAR with Oracle, see what they say, and report back.
> > (Sadly it's probably still best to talk in terms of your "OCI
> > application" rather than mention you're using Perl/DBI/DBD::Oracle.)
> > 
> > Trace level 9 will trace the OCI calls.
> > 
> > Tim.
> 
> Did the trace() calls, that was a good suggestion.  Got a look into
> Metalink, and found an issue with OCI 9.2 clients and 8.1.7 databases. 
> I've reproduced part of the info below.
> 
> Basically seems to be the same problem, a describe operation on a query
> involving a database link.  I guess DBD::Oracle describes the query
> before execution, to get some metadata?

Yeap.

> Doesn't look like Oracle has published a solution :-/  Wondering if
> there's some way to bypass the describe or maybe somehow reorder to get
> past their problem.  Will try to get the DBA to call on the bug and see
> if there's any new info.

Try
        $dbh->prepare($sql, { ora_check_sql => 0 });

> Looks like the obvious solution is to downgrade Oracle libraries.... but
> getting the 8.1.7 installer to run on RHEL 3 seems like it'll be a
> battle in itself (damn glibc symbols problems).
> -Alan
> 
> 
> Bug No.       2548451

Thanks for the info.

Tim.

Reply via email to