Error: Catastrophic failure on RecordSet.Open

Error: Catastrophic failure on RecordSet.Open

am 27.09.2005 18:33:01 von a_taranov

Hello,

I've got an ASP page which accesses data via Oracle ODBC driver. After
serveral (sometimes, lots of) successful requests, the page returns the
following error to the browser:

Provider error '8000ffff'
Catastrophic failure
/cior1/scripts/financ.asp, line 37

The line in question contains a RecordSet.Open. A simplified code extract
looks like this:

set RS = CreateObject("ADODB.Recordset")
Qry = "some select query"
RS.Open Qry, "driver={Oracle in OraHome920}; DBQ=xxx; DSN=xxx; UID=xxx;
PWD=xx;}

After this error, the ASP application no longer works. It appears hung, for
no error messages are returned to the browser (or to the server logs, either)
and subsequent HTTP requests do not get a reply from the server.

Re: Error: Catastrophic failure on RecordSet.Open

am 27.09.2005 19:49:15 von Steven Burn

http://aspfaq.com/show.asp?id=2323

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

"Andrew Taranov" wrote in message
news:23BC77CD-F0B3-4A3E-A4B5-94B6E278FFAE@microsoft.com...
> Hello,
>
> I've got an ASP page which accesses data via Oracle ODBC driver. After
> serveral (sometimes, lots of) successful requests, the page returns the
> following error to the browser:
>
> Provider error '8000ffff'
> Catastrophic failure
> /cior1/scripts/financ.asp, line 37
>
> The line in question contains a RecordSet.Open. A simplified code extract
> looks like this:
>
> set RS = CreateObject("ADODB.Recordset")
> Qry = "some select query"
> RS.Open Qry, "driver={Oracle in OraHome920}; DBQ=xxx; DSN=xxx; UID=xxx;
> PWD=xx;}
>
> After this error, the ASP application no longer works. It appears hung,
for
> no error messages are returned to the browser (or to the server logs,
either)
> and subsequent HTTP requests do not get a reply from the server.

Re: Error: Catastrophic failure on RecordSet.Open

am 27.09.2005 20:00:39 von reb01501

Andrew Taranov wrote:
> Hello,
>
> I've got an ASP page which accesses data via Oracle ODBC driver. After
> serveral (sometimes, lots of) successful requests, the page returns
> the following error to the browser:
>
> Provider error '8000ffff'
> Catastrophic failure
> /cior1/scripts/financ.asp, line 37
>
> The line in question contains a RecordSet.Open. A simplified code
> extract looks like this:
>
> set RS = CreateObject("ADODB.Recordset")
> Qry = "some select query"
> RS.Open Qry, "driver={Oracle in OraHome920}; DBQ=xxx; DSN=xxx;
> UID=xxx; PWD=xx;}
>

It is a bad idea to use implicit connections, the use of which can disable
connection pooling, as well as creating one of the situations leading to
memory leaks from ADO. It is much better to:

set cn=createobject("adodb.connection")
cn.open "driver={Oracle in OraHome920}; DBQ=xxx; " & _
"DSN=xxx; UID=xxx; PWD=xx;}
set rs=cn.execute(Qry ,,1)
'process the recordset, then
rs.close: set rs=nothing
cn.close:set cn=nothing


I'm not familiar with Oracle, but, if possible, try using a native OLE DB
provider for Oracle instead of the ODBC driver .. one less layer of software
between you and your data.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"