If you have HugePages properly configured, then these parameters aren't required. From note 361468.1: On Linux and some other platforms the Oracle Database initialization > parameters PRE_PAGE_SGA and LOCK_SGA3 can be set to TRUE to pin the SGA > pages into memory. HugePages already makes the SGA pages non-swappable, so > those parameters are not needed to have SGA pages unswappable. But those > parameters still can provide additional performance advantages for the > internal mechanism of Oracle Database memory management. I'd like to see the output of these 4 commands: grep Huge /proc/meminfo grep huge /etc/sysctl.conf grep memlock /etc/security/limits.conf ipcs -m On Mon, Oct 11, 2010 at 3:53 PM, Crisler, Jon <Jon.Crisler@xxxxxxx> wrote: > Jared- both lock_sga and pre_page_sga are set to FALSE. > > > > *From:* Jared Still [mailto:jkstill@xxxxxxxxx] > *Sent:* Monday, October 11, 2010 3:54 PM > *To:* Crisler, Jon > > *Subject:* Re: 11g RedHat 5 and Hugepages? anybody successful ? > > > > Jon, > > > > Do you have the LOCK_SGA and PRE_PAGE_SGA parameters set? > > > Jared > > On Mon, Oct 11, 2010 at 10:59 AM, Crisler, Jon <Jon.Crisler@xxxxxxx> > wrote: > > I have been trying to get hugepages working on 11gR1 without success. > Has anybody been able to get this to work properly? In order to use > hugepages, you have to turn off 11g ASMM which uses the /dev/shm memory > mapping. > > Hugepages are configured properly in OS, /etc/security/limits.conf > updated for hugepages. If I attempt to set memory_target and > memory_max_target to zero (or reset them) then I get ORA-00849 > SGA_TARGET ### cannot be set to more than MEMORY_MAX_TARGET. I am > following technote 749851.1, and even opened a support case with Oracle, > and I am not getting anywhere. > > Any clues as to what I am missing? Thanks- Jon > -- > //www.freelists.org/webpage/oracle-l > > > -- Don Seiler http://seilerwerks.wordpress.com ultimate: http://www.mufc.us