RE: lock_sga error

Thanks Kevin. I wanted to get my shared memory to stay resident and I did implement hugtlb. I am not using the indirect_data_buffers since I only have access to a 1.7 GB SGA at this point.  

Magnus

-----Original Message-----

From: Kevin Closson [mailto:kevinc_at_polyserve.com] Sent: Wednesday, August 03, 2005 2:54 PM To: Oracle-L (E-mail)
Subject: RE: lock_sga error

lock_sga is an OSD init.ora param...it only means something at the port level.. for instance lock_sga was implemented on the DYNIX/ptx port, but use_ism was implemented on Sol instead... Either way, the hope is that the OS complements this param with shared page tables and hard-locked SysV SHMEM... neither of which really related to Linux much.  

Are you sure you can boot of that init.ora file even with lock_sga commented out?  

Now, if you want your shared memory to stay resident (novel concept, I know, but it is a bit new to linux) you have to fiddle around with HUGE_TLB and so on. Also, if using indirect_data_buffers, you will need to use ramfs over shmfs because the latter is pageable ...    

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tim Gorman
Sent: Wednesday, August 03, 2005 9:09 AM To: Oracle-L (E-mail)
Subject: Re: lock_sga error

Why do you want to do this?

on 7/25/05 7:43 AM, Magnus Andersen at Magnus.Andersen_at_WalkerFirst.com wrote:

Hi All,  

I'm trying to lock my sga in memory on a RedHat Linux 3 AS server. When I try to start the database with the "lock_sga=true" paramerter in my init file I get the following error:  

SQL> startup nomount;

ORA-27102: out of memory

Linux Error: 12: Cannot allocate memory

SQL> Any ideas?

Thanks,

Magnus Andersen
Systems Administrator / Oracle DBA
Walker & Associates, Inc.  

--

http://www.freelists.org/webpage/oracle-l Received on Wed Aug 03 2005 - 14:31:14 CDT