RE: ORA-07445 immediately after database open
- From: "Hollis, Les" <Les.Hollis@xxxxxx>
- To: <Paula_Stankus@xxxxxxxxxxxxxxx>, <DGoulet@xxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 1 Dec 2004 21:17:07 -0600
I have 2 instances running on this particular server and have the same
numbr of semaphore entries....
s 10 0xc10287a6 --ra-ra-ra- patagt bmc
s 11 0xc10287a7 --ra-ra-ra- patagt bmc
s 12 0xc10287a8 --ra-ra-ra- patagt bmc
s 13 0xc10287a9 --ra-ra-ra- patagt bmc
s 14 0xc10287aa --ra-ra-ra- patagt bmc
s 15 0xc10287ab --ra-ra-ra- patagt bmc
s 16 0xc10287a0 --ra-ra-ra- patagt bmc
s 458769 0x126633e4 --ra-r----- oracle dba
s 65554 0x126633e5 --ra-r----- oracle dba
s 65555 0x126633e6 --ra-r----- oracle dba
s 458772 0x75648d50 --ra-r----- oracle dba
s 65557 0x75648d51 --ra-r----- oracle dba
s 65558 0x75648d52 --ra-r----- oracle dba
I bet you also have listeners running...and possibly agents?
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Paula_Stankus@xxxxxxxxxxxxxxx
Sent: Wednesday, December 01, 2004 8:26 PM
To: Paula_Stankus@xxxxxxxxxxxxxxx; DGoulet@xxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: 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=3D20
Sent: Wednesday, December 01, 2004 9:19 PM
To: 'DGoulet@xxxxxxxx'; 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
--
http://www.freelists.org/webpage/oracle-l
Other related posts: