标题: 【solaris】关于intimate shared memory的问题 [打印本页] 作者: chao_ping 时间: 2002-04-23 18:32 标题: 【solaris】关于intimate shared memory的问题 究竟怎么判定是否已经使用了这种特性？
环境
Solaris 7 64bit.
Oracle 8172 64bit
bash-2.03$ ps -ef|grep oraclebiddb|wc -l
303
bash-2.03$ ipcs -Am
IPC status from <running system> as of 2002年04月23日 星期二 17时25分44秒 CST
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME ISMATTCH
Shared Memory:
m 0 0x500483d0 --rw-r--r-- root root root root 1 68 309 309 2:43:28 2:43:28 2:43:28 1
m 301 0x41180c94 --rw-rw---- oracle oinstall oracle oinstall 318 2648899584 588 9168 17:25:42 17:25:42 14:11:524294261899
bash-2.03$ ps -ef|grep oraclebiddb|wc -l
298
bash-2.03$ ipcs -Am
IPC status from <running system> as of 2002年04月23日 星期二 17时26分16秒 CST
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME ISMATTCH
Shared Memory:
m 0 0x500483d0 --rw-r--r-- root root root root 1 68 309 309 2:43:28 2:43:28 2:43:28 1
m 301 0x41180c94 --rw-rw---- oracle oinstall oracle oinstall 313 2648899584 588 9215 17:26:14 17:26:14 14:11:524294261888 作者: oramind 时间: 2002-04-24 01:15
i think so. by default ISM is enabled in solaris and oracle, unless it\'s explicitly disabled in /etc/system and init.ora, respectively. sometimes, if SGA is too large and doesn\'t fit in one contigious share memory segment, oracle won\'t be able to use ism. the ISMATTCH # on your ipcs output looks strange. i don\'t believe it\'s the actual number of processes attached to ism. i think there is a bug in solaris 2.7 on this. you should check with sunsolve. if i had to guess, i think it\'s a bug in ipcs program, probably conversion between signed and unsigned number, ...
again, just a guess.