From: Bryan Pepin (bpepin@emc.com)
Date: Fri Jul 20 2007 - 14:38:15 EDT
Hello,
Has anyone else noticed the following behavior regarding Oracle's use of
shared memory, specifically around the shmmax (Solaris 8) and
shm-max-memory (Solaris 10). Before we upgraded our servers from Solaris
8, our Oracle 10G databases were grabbing just 1 large shared memory
segment for the database. For example, this is what ipcs said while
running the DB on Solaris 8:
T ID KEY MODE OWNER GROUP CREATOR CGROUP
NATTCH SEGSZ CPID LPID ATIME DTIME CTIME ISMATTCH
Shared Memory:
m 19458 0xcf1bb170 --rw-r----- oracle dba oracle dba 790
31138578432 21097 22653 10:47:09 10:47:09 7:52:43 790
After "Live Upgrading" to Solaris 10, and converting all our old
/etc/system settings to the new /etc/project format, we are noticing that
now Oracle is grabbing the same "total" size shared mem segments, but
instead of just 1, it is being split up into multiple ISM segments?
T ID KEY MODE OWNER GROUP CREATOR CGROUP
NATTCH SEGSZ CPID LPID ATIME DTIME CTIME ISMATTCH
PROJECT
Shared Memory:
m 112 0x8c07a648 --rw-r----- oracle dba oracle dba 1043
65536 23260 15444 14:25:28 14:25:28 16:21:59 1043 Oracle
m 111 0 --rw-r----- oracle dba oracle dba 1043
1811939328 23260 15444 14:25:28 14:25:28 16:21:55 1043
Oracle
m 109 0 --rw-r----- oracle dba oracle dba 1043
1811939328 23260 15444 14:25:28 14:25:28 16:21:51 1043
Oracle
m 107 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:47 1043
Oracle
m 106 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:43 1043
Oracle
m 105 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:40 1043
Oracle
m 104 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:36 1043
Oracle
m 103 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:33 1043
Oracle
m 102 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:29 1043
Oracle
m 101 0 --rw-r----- oracle dba oracle dba 1043
1795162112 23260 15444 14:25:28 14:25:28 16:21:26 1043
Oracle
m 100 0 --rw-r----- oracle dba oracle dba 1043
15015608320 23260 15444 14:25:28 14:25:28 16:20:51 1043
Oracle
Has anyone run into this? We are not sure if this is a Solaris 10
problem, or an Oracle issue? Sun Support is saying that have not seen
this before.
Any solutions out there to get Oracle back to using just 1 large shared
memory segment?
My last thing to test will be to put the old shmmax variable into
/etc/system, and reboot to see if that magically fixes the situation?
Thanks.
-Bryan
-- ************************************************ Bryan Pepin Unix Enterprise Systems EMC Corporation 4400 Computer Drive Westboro, MA 01580 508-898-4776bpepin@emc.com _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:42:08 EDT