RE: ORA-07445 immediately after database open

One other note of concern. It appears that the semaphores are too high on this machine:

Shared Memory:

m        700   0x39699788 --rw-r-----   oracle      dba
m        701   0x9d8f0618 --rw-r-----   oracle      dba
Semaphores:
s     983040   0xe6f6fb58 --ra-r-----   oracle      dba
s     131073   0xe6f6fb59 --ra-r-----   oracle      dba
s     131074   0xe6f6fb5a --ra-r-----   oracle      dba
s     983043   0xa4a3ef00 --ra-r-----   oracle      dba
s     196612   0xa4a3ef01 --ra-r-----   oracle      dba
s     196613   0xa4a3ef02 --ra-r-----   oracle      dba

There are only 2 running Oracle databases so I was expected 2 semaphores. I am concerned we will have memory issues.

-----Original Message-----
From: Stankus, Paula G=20
Sent: Wednesday, December 01, 2004 9:19 PM To: 'DGoulet_at_vicr.com'; Oracle DBA List (E-mail) Subject: RE: ORA-07445 immediately after database open

Guys,

Periodically, I see the following type of message in the alert.log usually after a database open. We are running 9.2.0.4 and from what I am seeing on Metalink this may be due to a bug during shutdown/startup that isn't resolved until 10i. It doesn't appear to occur except during shutdown/startup so I am not sure it is a problem. As I have often found opening TAR's to be frustrating I am not too concerned. Anyone encounter this issue??

Errors in file /opt/oracle/admin/leprod/udump/leprod_ora_25892.trc: ORA-07445: exception encountered: core dump [0000000100FAAFF8] [SIGSEGV] [Addres
s not mapped to object] [0x000000004] [] []

Thanks,
Paula

--
http://www.freelists.org/webpage/oracle-l