Re: A really strange one..
- From: "Best, David" <David.Best@xxxxxxxxxx>
- To: <Jon.Crisler@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 26 Sep 2007 15:38:28 -0400
There is a script in oracle_home/bin. Its called sysresv and will list the
shared memory and semaphores for a Sid. Useful for tracking down what is used
for a particular Sid if your are running multiple databases out of the same
home. See note 153961.1 for details if interested.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx>
To: oracle-l <oracle-l@xxxxxxxxxxxxx>
Sent: Wed Sep 26 14:43:00 2007
Subject: RE: A really strange one..
I have seen it many times, mostly on Linux, sometimes on AIX, rarely on
Solaris. Looking for shared memory segments that were not released, and
freeing them (or rebooting) is the normal fix. I believe there is a lock file
in $OH/dbs by default that might need to be removed, but the name of the file
escapes me.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Andrew Kerber
Sent: Wednesday, September 26, 2007 11:36 AM
To: oracle-l
Subject: A really strange one..
Ok, I just ran into a strange one this morning. US central time that is.
We are moving our clustered databases to new servers, and we put one database
onto the new hardware for initial testing. We restored from a backup, and got
both instances running. Today when I did a
ps -ef | grep pmon
I saw two pmon processes going for the single instance. I have no idea what
could have caused that. So I set my oracle_sid, path, oracle_Home and shutdown
the instance. What do you know, there was still one pmon process running. I
did a kill -9 on that one.
Then I go to start the instance again. And I get this error: ORA 01081
"cannot start already-running ORACLE - shut it down first"
I did a ps -ef | grep oracle, didnt get anything (except my user process of
course).
I finally googled and found one possibility, a locked shared memory segment.
Sure enough
ipcs -a | grep dba
returned a large segment of memory that was still locked. So I ran this (found
on the same site) and released it:
ipcs -a | grep dba | perl -ane 'system "ipcrm -$F[0] $F[1]"'
My question is, has anyone seen this before, or know what causes it?
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
This message may contain privileged and/or confidential information. If
you have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any attachments,
delete it immediately from your system and notify the sender promptly by e-mail
that you have done so. Thank you.
Other related posts:
