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.oracle

what 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.

 

 

THANKS VERY MUCH!!

After trawling the 'net for several days now i finally came across your post and it works a treat. I had tried to do this using the SMC instead of the command line and the SMC updates /etc/project with ERRORS - I only realized this when trying both methods. You cannot do this using SMC which stumped me until i saw your post. I'll contact Sun and raise an error with them.

Simon

 

 

You're welcome.

I personally don't use SMC at all, it's far too slow on a the old blade and I usually work from windows through putty so I don't have the 'advantages' of X. If I could install oracle without X I would.

Peter

 

 

I have/had the same problem. I don't know if this is a bug or just how I'm doing something, but if I reboot, login as my oracle user and do an id -p, my projid = 0. If, however, I login as root and su to oracle, I get the correct project id of 101. What could I be missing? Wouldn't/shouldn't they all be the same?

uid=1010(oracle) gid=101(oinstall) projid=0(system)
bash-3.00$ id -p oracle
uid=1010(oracle) gid=101(oinstall) projid=101(user.oracle)
bash-3.00$

 

 

I tried the fix suggested but still get the problem.
Oracle 10g on Solaris 10.
What else do I need to do ?

 

 

Thanks for the greate help. Initially it didn't work with the given value for me (2GB). I increased it more and it worked fine with me.

projmod -U oracle -K "project.max-shm-memory=(priv,4294967295B,deny)" user.oracle

Regards,
Jayantha Dikkumbura

 

 

Any more information along this thread? I have updated all of my variables, however that did not stop my errors. Anyone else have to do other things to solve the 27102,27101,01034 set of errors?

 

 

Question-- anyone running Oracle RAC (cluster) on Solaris 10?

I've got the systems built and configured with a user.oracle project (both locally and in the LDAP) for 12GB shm-max-memory. The dba's can start the database manually as oracle and it's great and fine and dandy. But under RAC control... no!
The stupid RAC process insist on running under the system project even though they are oracle too, and I can't modify the system project to more than 4.89GB (system has 20gb) even if I wanted to (for a test).

What is this? Help!

 

 

Did you get a resolution on the problem starting the instance with srvctl? I'm having the same problem.

 

 

I had the same exact problem on solaris 10 with Oracle 9i, this resolution works for me also, thank you!!!

Funny thing is the problem was not observed on our production server (v480 / 16GB RAM), it only occurred on our test workstation (ultra 45 / 1GB RAM) even though on both machines oracle is using about half physical RAM.

 

 

I just wanted to also pass along a thank you to pkwooster for the tip. It resolved my problem with Oracle 10g on Solaris 10.

Thanks!

 

 

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

 

 

I just posted a new message asking what I am missing that when I assign the projects for Oracle 10g, running on Solaris 10 that the shm-max-memory segments come up under 4 instead of 1 size as before. Not sure what I am missing? Any help greatly appreciated!!

ipcs -a
IPC status from <running system> as of Fri Dec 15 13:34:22 EST 2006
T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME
Message Queues:
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME
Shared Memory:
m 4 0x41d15124 --rw-r----- oracle dba oracle dba 19 16384 2750 9792 13:34:00 13:34:00 13:10:43
m 3 0 --rw-r----- oracle dba oracle dba 19 2130706432 2750 9792 13:34:00 13:34:00 13:10:40
m 2 0 --rw-r----- oracle dba oracle dba 19 2147483648 2750 9792 13:34:00 13:34:00 13:10:36
m 1 0 --rw-r----- oracle dba oracle dba 19 872415232 2750 9792 13:34:00 13:34:00 13:10:34
T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME
Semaphores:
s 6 0xce915dac --ra-r----- oracle dba oracle dba 504 13:34:08 13:10:44
s 2 0x73657276 --ra-ra-ra- root root root root 3 13:10:27 13:10:27
s 1 0x71c30c0f --ra-ra-ra- root root root root 1 13:10:22 13:09:42
s 0 0x53c3022e --ra------- root root root root 1 13:20:01 13:09:25

 

 

Solaris 10 projects don't seem to be well implemented, and you need to go back to using some of the /etc/system settings such as shmmax. If you research this on Oracle MetaLink, the note says to set the appropriate parameters in /etc/system. I've asked Oracle to work with Sun to resolve this, but I don't think resolution is coming in the next few years.

Here's what's happening ... If you defined a project using projadd, then the project settings are stored but don't necessarily go into effect. This is true even if it's the user's default project. The problem can be observed using "prctl $$", which shows current project settings in effect for your session. If you are logged in as oracle and then you do another "su - oracle" the settings go into effect. Then, when you "exit" back to your original session as user oracle the project is deactivated. Thus, even if you are oracle you don't get oracle's default project settings until you do another "su - oracle".

This is well known to Oracle as it prevents utilities like Server Control from starting RAC instances. I've talked to Veritas about it too, since it impacts their Veritas Cluster Server's ability to start instances. Obviously, it has no impact on root's bootup commands starting your databases since such commands always include "su - oracle" and thus activate your project settings.

So, at this point you have two basic options:
1. always do "su - oracle" to enable your project before issuing any commands, or
2. set the /etc/system parameters

-Mark

 

 

This works perfectly.

******
So, at this point you have two basic options:
1. always do "su - oracle" to enable your project before issuing any commands, or
2. set the /etc/system parameters
******
Is there any other resolution, so that we can use the projects and not have to use "su - oracle" ?