Re: Solaris Unix Shared Memory Semaphores - 3113 Problem

This works for me. I needed it after a shutdown was aborted and I had to clean up the semaphores and ipc's.

ps -ef | grep DB_NAME

to find out what processes are running. Next do a

ipcs -a

to look at all the sempaphore and ipc's running. Now to find out what semaphores and things are attached to your database, set your sid first then do a

sysresv

This will give you the ID's of the processes that you need to kill. Kill them with this command.

ipcrm -m ID

ipcrm -s ID

"JustAnotherDBA" <jadba_at_bellsouth.net> wrote in message news:6UP5a.13220$A27.2303_at_fe03.atl2.webusenet.com...
> I had to do a ipcrm to zap the shared memory and semaphores for 1 database
.
> I did this based on documents in Metalink and I am sure it was needed.
>
> But, I am wondering if anyone knows how to tell which shared memory and
> semaphores go with which database.
>
> I couldn't find a way, so I shutdown all of the databases. Then, I did the
> ipcrm command to remove the 1 remaining .
>
> No problems after that with the 1 database that I was getting a 3113 on it
> (just by running svrmgrl).
>
> Some more info...
>
> Solaris 8
> Oracle8i 8.1.6.2.0
> 5 databases
>
> Fyi... below is the output of ipcs before running ipcrm, but after
shutting
> down 1 database...
>
> % ==> ipcs
> IPC status from <running system> as of Sat Feb 22 12:08:52 CST 2003
> T ID KEY MODE OWNER GROUP
> Message Queues:
> Shared Memory:
> m 0 0x66ac8bec --rw-r----- or02sup sccdba
> m 2 0xbf400f48 --rw-r----- or02sup sccdba
> m 403 0xf2ff35a4 --rw------- or02sup sccdba
> m 404 0x717ed15c --rw------- or02sup sccdba
> Semaphores:
> s 196608 0x5857945 --ra-r----- or02sup sccdba
> s 196610 0x509aa45 --ra-r----- or02sup sccdba
> s 458755 0x387a875 --ra------- or02sup sccdba
> s 458756 0x51782c5 --ra------- or02sup sccdba
>
>
>
Received on Sun Feb 23 2003 - 18:16:40 CST