Re: Identifying Shared Memory Segments

You can do this for each instance:

% svrmgrl

SVRMGR> connect internal
SVRMGR> oradebug setmypid
SVRMGR> oradebug ipc

That will drop a trace file in the instance's user_dump_dest directory containing the segment IDs of the instance's shared memory.

--
Jeremiah

In article <39cdfef7_at_pink.one.net.au>,
  "Joseph Blazic" <joseph_blazic_at_atu.com.au> wrote:


> Hi All,

>

> I have a UNIX (AIX) box running two oracle instances.

> Both instance's processes (at the moment) have the same owner and

 group.


> Anyone have any suggestions on how to identify shared memory segments

 based


> on SID?

>

> In AIX, ipcs -am lists information about shared memory segments.  As

 far as


> I can tell, this listing does not provide any information which can,

> cross-referencing the oracle alert log, definitively identify the

 instance.


> For example, creation time is listed, but only the clock time, not

 date.


> Further, the creation time does not necessarily match to-the-second

 with any


> instance-up event in the alert log.

>

> Unfortunately I am stuck (for now) with an old version of oracle which

> suffers from space leaks...which requires manually clearing-out shared

> memory segments before re-starting oracle.  The segments must be

> unambiguously identified; I wish to script some automation.



Sent via Deja.com http://www.deja.com/
Before you buy.