ORIGINAL QUESTION:
Does anyone have experience with the following error:
oracle error ORA 7279 - spcre:semget error, unable to get first
semphore set; followed by SVR4: Error:28: No space left on device.
We suspect that increasing our kernel semaphore limits might fix this,
but I'd like some other opinions.
RESOLUTION:
It turns out that our original assumption was correct, and we needed to
increase our available semaphores. In our case we ended up needing to
increase shmmax as well, as someone apparently left of the last digit,
leaving us with 10% of what we need. Here are the parameters affected:
shmsys:shminfo_shmmax
semsys:seminfo_semmni
semsys:seminfo_semmsl
semsys:seminfo_semmns
A few people pointed out that the PROCESSES parameter could be set too
high in the init.ora file.
Also, thanks to Julie Fisher, who gave me the method for calculating
some of the values:
semmns needs to be set to at least : (instances processes
{smon,psmon,dbwr,lgrw,arch,any other} * number of instances) + (the
value of
the PROCESSES parameter in the init<sid>.ora file) + (system processes
of
other non-Oracle applications).
semmsl needs to be set to the value of the PROCESSES parameter in the
init<sid>.ora file. If you have more than one instance and the values
of
the PROCESSES parameter are different, make semmsl equal to the lowest
PROCESSES so that you don't allocate semaphores that will not be used.
Additional thanks to:
David Evans
Todd Herr
Terry Parn
Ken Weschler
Fernando Nantes de Souza
Viet Hoang
Jonathon W. Ross
Steve Boronski
Ray Trzaska
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:08 CDT