Red Hat Bugzilla – Bug 165015
Kernel panic on a system running Oracle with large SGA
Last modified: 2007-11-30 17:07:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050512 Firefox/1.0.4
Description of problem:
We have a system running RHEL 3 (update 4). The system is a database server running Oracle Database Server 22.214.171.124 . On irregular time intervals the systems experiences kernel panic and restarts.
The Oracle server uses large SGA, based on indirect_data_buffers and /dev/shm .
The system has 8GB of RAM, 4 of which are mouted on /dev/shm .
Version-Release number of selected component (if applicable):
Nothing suspisious could be found in the system logs.
The system just panics and restarts
Please include the full console output of the oops/panic messages (using
a serial console line if necessary). Also, please let us know if this
can be reproduced on the latest released kernel, which is the post-U5
security release (kernel version 2.4.21-32.0.1.EL from RHSA-2005:472).
If this is a serious issue for you, you should also register the problem
with Red Hat Customer Support (so that they can open an Issue Tracker ticket)
and let them know that this BZ was already created.
Can't supply the console output of the panic messages, since the system is
managed remotely, the panic occurs on the irregular time interavals and there is
no persistent monitoring of the system via serial console.
Currently, the system is in production and can't be stopped for upgrade to U5.
Don't you have similar complaints according to Oracle on RHEL 3?
No, we don't.
I'm reverting this to NEEDINFO state. Without the additional information,
no progress can be made on this problem.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.