On Thu, Sep 02, 2004 at 04:40:21PM -0500, Rafael Caceres wrote: > I've been running a small number of scripts under mod_perl, for months > now without change, and in the last few days my log files are full of > ORA-01001: invalid cursor errors. > > Oracle's doc for that error seem to call for fixes outside perl / DBI / > DBD::Oracle.
- What's the _full_ error message that includes the name of the function being called. - Give sample code or description of what the relevant code is doing. - Check for any recent db config changes. - Check if restarting the httpd fixes the problem (even if only for a while). - http://www.catb.org/~esr/faqs/smart-questions.html Tim. > >From Oracle's docs: > ORA-01001: invalid cursor > Cause: Either a host language program call specified an invalid cursor > or the values of the AREASIZE and MAXOPENCURSORS options 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 AREASIZE and MAXOPENCURSORS options > before precompiling. > > Anyone seen this before? > > Rafael Caceres >
