Re: could not allocate semaphores.

I think, that the first described error you can eliminate by setting Solaris semaphore parameters to values recommended by Oracle Server installation guide (system reqs.)! It gots well on SGI Irix for me. The second problem is successive to the first one. Try to kill all oracle processes before trying to start instance, or simply restart machine before it!

Karel

Thor Morten Kopaas wrote:

> Hei,
>
> I just installed Oracle 8.04 on Solaris 2.5.
>
> When starting up the database for the first time I got the following error:
>
> SVRMGR> startup nomount pfile=initsid3.ora
> ORA-00600: internal error code, arguments: [SKGMBUSY], [1], [0], [0], [0],
> [], [
> ], []
> ORA-07252: spcre: semget error, could not allocate semaphores.
> SVR4 Error: 28: No space left on device
> Additional information: -268447208
> Additional information: -268447292
>
> I then decreased the value of processes in initsid3.ora down to 10, but then
> I get this error:
>
> SVRMGR> startup nomount pfile=initsid3.ora
> ORA-00600: internal error code, arguments: [SKGMBUSY], [1], [0], [0], [0],
> [], [
> ], []
> ORA-27100: shared memory realm already exists
> SVR4 Error: 17: File exists
>
> Now it seems that whatever I try to do I get this message when trying to
> start up my instance.
>
> Does anyone know what file it is referring to? Does anyone know how I get
> rid of this error?
>
> If I set ORACLE_SID=sid4 instead of ORACLE_SID=sid3, I am able to start up
> the instance fine.
>
> Oracle support told me to install patch 8.0.4.3.0 which I now have done, but
> I still get the same error.
>
> Thanks,
>
> Thor Morten
Received on Tue Jan 12 1999 - 07:30:06 CST