Workaround for Bug 9251136 INSTANCE WILL NOT USE HUGEPAGE IF STARTED BY SRVCTL
- From: Yong Huang <yong321@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 22 Mar 2010 10:20:47 -0700 (PDT)
On 11gR2 Linux, due to Bug 9251136, when you use srvctl to start
instance, or after reboot, even if you don't use AMM (not using
memory_target), HugePages cannot be used. I believe the root cause
is ohasd not honoring ulimit settings. You can verify this by
cat /proc/<any instance process pid>/limits
and compare with your shell `ulimit -a'. The specific limit relevant
to this problem is max locked memory.
To work around the bug, you can set the limit in $GRID_HOME/bin/ohasd
or /etc/init.d/ohasd, but not /etc/profile or /etc/init.d/init.ohasd,
to allow Oracle to use HugePages when srvctl starts instance.
$ diff /u01/app/11.2.0/grid/bin/ohasd /u01/app/11.2.0/grid/bin/ohasd.bak
5,7d4
< #20100319 Increase process max locked memory to allow huge pages as
workaround for Bug 9251136
< ulimit -l 8590000
<
$ grep ^Huge /proc/meminfo
HugePages_Total: 2100
HugePages_Free: 1278
HugePages_Rsvd: 1227
Hugepagesize: 2048 kB
Yong Huang
--
//www.freelists.org/webpage/oracle-l
Other related posts:
- » Workaround for Bug 9251136 INSTANCE WILL NOT USE HUGEPAGE IF STARTED BY SRVCTL - Yong Huang
