Title: RE: Oracle Bug Report


> Date: Sat, 04 Sep 2004 18:07:44 +0200
> To: [EMAIL PROTECTED]
> From: Andrea Gabellini <[EMAIL PROTECTED]>
> Subject: Re: Oracle bug report
> Reply-To: [EMAIL PROTECTED]
>
> Hi,
>
> looking at the code, the server return SQL_DOWN if there is
> any type of error.
>
> Errors like "ORA-01401: inserted value too large for column"
> are set by the
> Oracle server, so the server is up and running.
>
> In this situation it's not a good idea to reconnect the socket.
>
> Performing some tests, I found two specific errors that mean
> "database
> down": ORA-03113 and ORA-03114.
>
> So I wrote a new function, sql_check_error (like the mysql one), that
> checks the error code and return SQL_DOWN or -1.
>
> I don't know if this solve the bug, but surely it manages
> better the query.
>
> In this patch I set the "commit on success".
>
I am of the belief that this is an Oracle 8 (8.1.7.0.0) problem. The machine I'm running on, was upgraded to Oracle 9.2 last week. The problem still occurred if I used the the Oracle 8 Shared Libs. However, it disappears when using the 9.2 versions of those libs.

Perhaps, there is a patch for Oracle 8 that addresses this issue.

Regards,
Omar El-Hassan

Reply via email to