Operating System - HP-UX
1748054 Members
4656 Online
108758 Solutions
New Discussion

Re: Oracle db problem; shared mem, not owner

 
Evelyn Daroga
Regular Advisor

Re: Oracle db problem; shared mem, not owner

Ok, I got it working. Turns out there is a parameter in the Oracle init.ora file that turns SGA locking on. It was set to "true" (back in 2000) for the 2 db's I was having trouble with, but not any of the others. I turned it off, and the db's came right up. No idea why suddenly it's a problem.

BTW, the parameter is: LOCK_SGA=TRUE for anyone who is interested. I just commented it out in the init.ora file.

thanks for everyone's help. I appreciate the quick responses (btw - I didn't get any responses for the same question logged at the Oracle site)
Evelyn Daroga
Regular Advisor

Re: Oracle db problem; shared mem, not owner

Alternatively -- just FYI for anyone who runs into this in the future -- here is a more correct solution (haven't actually done it yet) that was recommended to me:

On HP in order for a user to lock memory segments they need specific privs. Try this to set them.

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