Re: Sartup failure due to init parameter: LOCK_SGA

Without even trying to sound cynical...

take the parameter out of init.ora

you seem to know about this parameter though...

why did you put it in (what was your reasoning or who instructed you to do so ? )

one of my NT instances has 512 too and it's not needed at all.

if linux is gonna page oracle out you'd better find out why first rather than locking it into real mem.
"Jetlag" <jetlag11235_at_yahoo.com> wrote in message news:2eeed00e.0210171324.634b47c9_at_posting.google.com...
> I'm running Oracle 9i under Linux (Debian/Woody) and I am unable to
> start Oracle when the LOCK_SGA parameter is set to TRUE.
>
> The system has a total of 512M of RAM. I have tried starting Oracle
> with over 400M free and with the SGA sized smaller than 100M.
>
> Still, I receive the following error ... whether I start Oracle as
> root (from /etc/init.d) or as oracle (from sqlplus /nolog).
>
> The error I receive is shown below. It does not seem to appear in any
> Oracle logs.
>
> SQL> ORA-27126: unable to lock shared memory segment in core
> Linux Error: 1: Operation not permitted
>
> Any suggestions would be appreciated greatly. Thanks.
Received on Fri Oct 18 2002 - 04:36:18 CDT