Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: shared memory identification

Re: shared memory identification

From: <mike_st0ne_at_my-deja.com>
Date: Tue, 06 Feb 2001 14:50:22 GMT
Message-ID: <95p2va$4vg$1@nnrp1.deja.com>

In article <954j26$d8a$1_at_nnrp1.deja.com>,   ian_goldstein_at_my-deja.com wrote:
> greetings all,
>
> I am running a Solaris 2.7 operating environment. My dba had a
 problem
> in which he had 2 oracle (8.1.6) instances running. One instance died
> but the shared memory segment was never removed. When I view the
> shared memory through ipcs the "CPID" field is that of a non-existant
> process. As it turns out the SVRMGRL forks off a process that starts
> the oracle instance and then exits, so now I have no way to determine
> which shared memory segment belongs to the remaining Oracle Instance.
>
> The only way I thought to procede in the future was to set up a
> separate user id for each oracle instance.
>
> Does anybody have any other suggestions.
>
> Thanks in advance,
> Ian
>
> Sent via Deja.com
> http://www.deja.com/
>

Ian,

    For any instance, you can identify its shared memory segments by connecting via a SVRMGRL session and issuing "oradebug ipc". Depending on which Oracle release you're working with, you'll either get screen output or a trace file in UDUMP - look for "shmid". So you can identify any "rogue" segments by cross-referencing this info with your "ipcs" output.

Hth

Mike S

Sent via Deja.com
http://www.deja.com/ Received on Tue Feb 06 2001 - 08:50:22 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US