Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: ORA-01001 Error

Re: ORA-01001 Error

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Mon, 7 Jul 2003 11:00:31 +0100
Message-ID: <3f0944c0$0$18491$ed9e5944@reading.news.pipex.net>


"Andrew Specterman" <aspecterman_at_unlimited.com> wrote in message news:vgidselqosf214_at_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
Received on Mon Jul 07 2003 - 05:00:31 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US