Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news-FFM2.ecrc.net!newsfeed.vmunix.org!npeer.de.kpn-eurorings.net!newsfeed.kabelfoon.nl!195.129.110.21.MISMATCH!bnewsfeed00.bru.ops.eu.uu.net!bnewsinpeer01.bru.ops.eu.uu.net!lnewspeer01.lnd.ops.eu.uu.net!lnewspost00.lnd.ops.eu.uu.net!emea.uu.net!not-for-mail From: "Niall Litchfield" Newsgroups: comp.databases.oracle.misc References: Subject: Re: ORA-01001 Error Date: Mon, 7 Jul 2003 11:00:31 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Lines: 40 Message-ID: <3f0944c0$0$18491$ed9e5944@reading.news.pipex.net> NNTP-Posting-Host: host9.audit-commission.gov.uk X-Trace: 1057572033 reading.news.pipex.net 18491 193.128.236.219 X-Complaints-To: abuse@uk.uu.net Xref: newssvr20.news.prodigy.com comp.databases.oracle.misc:129087 "Andrew Specterman" wrote in message news:vgidselqosf214@corp.supernews.com... > A couple of our users are getting ORA-01001 error messages when connecting > to our Oracle Database. > > When they get this, they reconnect all is well. > > No other network issues are reported at the time. > > Our developers inform me that it is a connection error between the client > and the database - are they telling the truth or is this error caused by bad > code in the libraries used to connect from the client to the database? well the docs at http://tahiti.oracle.com would seem to suggest that it is code, rather than network specific ORA-01001 invalid cursor Cause: Either a host language program call specified an invalid cursor or the value of the MAXOPENCURSORS option in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF. Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the MAXOPENCURSORS option value before precompiling. -- Niall Litchfield Oracle DBA Audit Commission UK