-
Has anybody experienced the following error messages in Oracle9i?
SMON: following errors trapped and ignored:
ORA-00604: error occurred at recursive SQL level 1
ORA-01001: invalid cursor
ORA-00601: cleanup lock conflict
Oracle Support could not determine the cause of the error messages.
-
This is just a wild idea:
Sure that this is a new bug for a new version release since
Oracle Support can't even identify the cause of this error.
But don't be alarmed immediately. What I usually do when I am
task to handle new version for development(I assume) in such scenario arise:
I won't wait for the Oracle Technical Support to give me
solution immediately. Instead I go backward and trace
where did this error come from? Because I believe this
is usually just a cause of an erronous programming. Then
perhaps we can avoid those alarming errors such as 600's.
Because this means usually that you need to contact Technical
Support. So settle first the very reason why, when and where
did it start. You might be surprise that the error 600's will
vanish after you debug a program or a sql statement. Or maybe you
need to implement different approach. I hope not.
Thus this came from a sql statement issued against the server?
Or in a precompiler program? etc.
I believe in your case it came from a precompiler program.
And if it where so, have you use the Logon Data Area (LDA)
properly?-i.e. defining by using the OLON or OLOGON. This is
important, since you need to define first the LDA before you
can OPEN a cursor.
Have you open the cursor first by using OOPEN call before using another
calls such as SQL, DEFINE, BIND, DESCRIBE, etc.?
If you satisfied it, then maybe the value of the AREASIZE and
MAXOPENCURSORS options in the precompiler command were to small.
Hope this can help.
Keep it cool.
-
Hi,
I get same error in my dev 9.0.1 databases too. I contacted oracle and no response to correct this error so far. As per oracle, This was known bug to 9.0.0 release but got fixed for 9.0.1. I still get this error in 9.0.1 database.
Alert.log
=======
ORA-00604: error occurred at recursive SQL level 1
ORA-01001: invalid cursor
ORA-00601: cleanup lock conflict
+++++++++++++++++
Trace file info:
home1/oracle/app/oracle/admin/lcs901/bdump/lcs901_smon_26070.trc
Oracle9i Enterprise Edition Release 9.0.1.0.0 - Production
With the Partitioning option
JServer Release 9.0.1.0.0 - Production
ORACLE_HOME = /home1/oracle/app/oracle/product/9.0.1
System name: SunOS
Node name: lcdbsol1
Release: 5.7
Version: Generic_106541-12
Machine: sun4u
Instance name: lcs901
Redo thread mounted by this instance: 1
Oracle process number: 6
Unix process pid: 26070, image: oracle@lcdbsol1 (SMON)
*** SESSION ID:(5.1) 2001-10-11 13:04:10.369
*** 2001-10-11 13:04:10.369
SMON: following errors trapped and ignored:
ORA-00604: error occurred at recursive SQL level 1
ORA-01001: invalid cursor
ORA-00601: cleanup lock conflict
~
+++++++++++++++++
By looking into alert.log and trace file it has been generated by SMON process.
Also , few more info:
This database is development database and no body is using this database currently.This database has been created as fresh database. No upgrade from previous version. This is 9.0.1 database.
After further reserch, I have found Lock from SMON username
Mode held: Row Exclusive
Lock Type : TS
No more information about what object(s) is locked.
This error does not occurs frequently but with in a week of time it appears two times in alert.log Also, no one is using this database too. Thease are test/development databases.
Any ideas??
Thanks,
-
I am curious about the motivation to install and use these early versions of 9i which are full of bugs. Why not wait until Oracle improves 9i and use untill then say 8.1.7?
I am talking about production DBs.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|