Solaris 10, Oracle 10g and ORA-27102 out of memory

Question

After much STFW'ing, RTFM'ing and experimenting I finally got Oracle 10g to start a database on a SunBlade 100 with 512MB of memory and Solaris 10. As most of the replies on the web about error 27102 "out of memory" address solutions in Solaris 8 and 9, I thought I should post a clear description of the solution here.
Unlike earlier releases of Solaris, most of the system parameters needed to run Oracle are already set properly, so the only one you need is the maximum shared memory parameter. In earlier versions this was called SHMMAX and was set by editing the /etc/system file and rebooting. With Solaris 10 you set this by modifying a "Resource Control Value". You can do this temporarily by using prctl, but that is lost at reboot so you will need to add the command to the oracle user's .profile. The other option is to create a default project for the oracle user:
projadd -U oracle -K "project.max-shm-memory=(priv,2048MB,deny)" user.oraclewhat this does:
- makes a project named "user.oracle" with the user oracle as it's only member.
- because the name was of the form "user.username" it becomes the oracle user's default project.
- the value of the maximum shared memory is set to 2gb, you might want to use a larger value here if you have more memory and swap.
- no reboot is needed, the user will get the new value at their next login.

Answer 1

thanks buddy. I was in this same tricky situation. and ur post solved my prblem.
Is this a bug with solaris 10.
Later i discovered.. on Oracle documentation that.. there r sum parameters that needed to be taken care while pre-installation of Oracle binaries.
Here is the excerpts.
The Oracle installer recognizes kernel parameters set using this method, but it is now deprecated in favour of resource control projects, explained below.
As the root user, issue the following command.
projadd oracle
Append the following line to the "/etc/user_attr" file.
oracle::::project=oracle
If you've performed a default installation, it is likely that the only kernel parameter you need to alter is "max-shm-memory". To check the current value issue the following command.
# prctl -n project.max-shm-memory -i project oracle
project: 100: oracle
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
project.max-shm-memory
        privileged       254MB      -   deny
        system          16.0EB    max   deny     
To reset this value, make sure at least one session is logged in as the oracle user, then from the root user issue the following commands.
# prctl -n project.max-shm-memory -v 4gb -r -i project oracle
# projmod -s -K "project.max-shm-memory=(priv,4gb,deny)" oracle
The first dynamically resets the value, while the second makes changes to the "/etc/project" file so the value is persistent between reboots.
# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
oracle:100::::project.max-shm-memory=(priv,4294967296,deny)
The Oracle installer seems incapable of recognising kernel parameter set using resource control projects, but if you ignore the warnings the installation completes successfully.Even this method works.
Regards
Monu Koshy