Just wanted to share an update on this topic. I had removed the
session_cached_cursors parameter on this instance based on metalink
note 274496.1. Once I did this, I was able to start the database and
it remained up for about a week, only to crash again last Friday
afternoon. Turns out there was a bug involved. (description below)
We are using extensive Java in several 220.127.116.11/18.104.22.168 databases and
have only seen this issue on one database. I've applied the patch and
thus far, it looks good but I haven't made it through Friday yet.
A patch is available for version 22.214.171.124 as well.
3691672 OERI/ OERI / dump (kgllkdl) from JavaVM /
OERI:1100 from PMON
Details: This problem is introduced in 126.96.36.199 by the fix for bug 3253770.ORA-600
 / ORA-600
 and numerous other errors
can occur using Java in the database, especially where there
is a high degree of concurrency. This problem can lead to a
 error in PMON causing an instance
Note: This problem was originally listed as fixed in 188.8.131.52 but the
fix is incomplete and the problem shows internal errors in
On Tue, 15 Mar 2005 16:50:58 -0500, Robyn <robyn.sands@(protected):
> Hello all,
> One of my test/dev instances went belly up yesterday morning with
errors in the alert log. I've the the database back but I
> ran across a doc on metalink (Note:274496.1) that indicates using
> parameter session_cached_cursors should not be used with version
> 184.108.40.206 and up.
> This database is 220.127.116.11 / HP-UX 11.23. I've been selectively using
> session_cached_cursor with other 9.2.0 databases but this is the first
> db that I've seen these errors on. Has anyone else seen this happen
> and/or heard that this param should not be used?
> tia ... Robyn