Oracle Solaris System Administration (MOSC)

MOSC Banner

Unexplained shared memory segment

edited Mar 31, 2011 7:09PM in Oracle Solaris System Administration (MOSC) 1 commentAnswered
We have a T6320 blade with an 8 core 1.4 Ghz T2 processor that has 128 GiB of RAM.  The system runs one non-global zone named Boston that contains an Oracle 11g database with an SGA set to 30GiB.  After upgrading the server from 64GiB to 128GiB of RAM, we noticed 30GiB of RAM was "missing" so to speak.  prstat -mZ reports the zone containing 36GiB of RAM while mdb -k ::memstat reports Anon is using nearly 70GiB of RAM. 

The Oracle database is only supposed to have 1 shared memory segment even though icps -mbop is reporting there are two. One of the memory segments has an NATTCH value of 0. We are unsure what is causing the creation of second shared memory segment.  Overtime, the LPID of the second memory segment changes to the same LPID value as the 1st shared memory segment.  My question is, is it possible the Oracle database orphaned a shared memory segment and can I remove it with ipcrm?  Or are the two shared memory segments referencing each other and I'm on a

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center