-none- 2005-03-15 - By -not available-
The metalink note makes it clear to me that this is overkill. From this, =
it looks like I 'd revert session_cached_cursors back to 100 and leave =
open_cursors at 255 like I did back in 9.2.0.4.
I do recall having a series of ora-4031 (See ora-4031.ora-code.com) issues for a db after it went =
from 8.1.7 to 10.1.0.3. This could help to explain that. (the system =
state dump run while throwing the 4031s never completed as after 40 min =
we just bounced the db inst).
Paul
On Tue, 15 Mar 2005 16:50:58 -0500, Robyn <robyn.sands@(protected) > wrote:
> Hello all,
>=20
> One of my test/dev instances went belly up yesterday morning with=20
> ORA-07445 (See ORA-07445.ora-code.com) errors in the alert log. I 've the the database back but I=20
> ran across a doc on metalink (Note:274496.1) that indicates using=20
> parameter session_cached_cursors should not be used with version=20
> 9.2.0.5 and up.
>=20
> This database is 9.2.0.6 / HP-UX 11.23. I 've been selectively using=20
> 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=20
> and/or heard that this param should not be used?
>=20
> tia ... Robyn
> --
> http://www.freelists.org/webpage/oracle-l
>=20
--=20
#/etc/init.d/init.cssd stop
# f=3Dma, divide by 1, convert to moles.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
|
|
