i shutdown my databas.
add lock_sga=true to init.ora
startup
it gives me error
SQL> startup
ORA-27126: unable to lock shared memory segment in core
SVR4 Error: 1: Not owner
why?
Printable View
i shutdown my databas.
add lock_sga=true to init.ora
startup
it gives me error
SQL> startup
ORA-27126: unable to lock shared memory segment in core
SVR4 Error: 1: Not owner
why?
Check to make sure that your platform supports this, and you have the appropirate privileges, to lock the segment in the memory....
Sam
my system is solaris 2.7
how to check if i have the appropriate privileges to lock the
segment in the memory?
You need root privileges on Solaris to be able to use the lock_sga parameter.
Anybody using this parameter out there ?? :)
-amar
What does lock_sga do and why would you do that??
Thanks ST
It would lock the sga to the memory at boot time and would hold that for ever. But be aware of that if you were to use the virtual memory, then you would endup going to the disk too to process your SGA.
Sam
Checkout the following links for details...
http://otn.oracle.com/docs/products/...h178.htm#37877
http://otn.oracle.com/docs/products/...emor.htm#11453
http://otn.oracle.com/docs/products/...memor.htm#8837
I know on HP-UX you use this solution
You need to give the oracle Unix user memory locking privileges at the OS level.
Do the following:
1) Login as root:
%su root
2) Create the file "/etc/privgroup":
$vi /etc/privgroup
3) Add line "dba MLOCK" to file.
Note: The group dba is assuming the oracle owner's ID is part of the dba
group.
4) As root, run the command "/etc/setprivgrp -f /etc/privgroup":
$/etc/setprivgrp -f /etc/privgroup
I am sure the procedure should be simler on solaris as they are both California Berkly systems