Comments on: Little oradebug enhancement in Oracle 11g

By: niccisweden

niccisweden — Tue, 18 Aug 2009 15:07:24 +0000

informative for me, like that

injectable filler

By: Tanel Poder

Tanel Poder — Wed, 12 Nov 2008 23:10:49 +0000

Hi Chen,

I have such a script which accepds SID as parameter as attaches to its corresponding process like this:

SQL> @odsid 170
Oracle pid: 2, Windows thread id: 2920, image: ORACLE.EXE (PMON)

The script contents are following:

—————————-

SET TERMOUT OFF
COL spid NEW_VALUE odsid_spid
SELECT spid FROM v$process WHERE addr = (SELECT /*+ NO_UNNEST */ paddr FROM v$session WHERE sid = &1);
COL spid CLEAR
SET TERMOUT ON

ORADEBUG SETOSPID &odsid_spid

—————————-

Also you could write an “init” script which intializes sqlplus variables like lgwr, dbw0 etc.

so you could just run “@odsid &lgwr” when doing the demo

By: prodlife

prodlife — Wed, 12 Nov 2008 05:03:09 +0000

Is there a way to name the shadow process from within a session? (In a dedicated connection environment, of course). That could really make life easier when doing demos, research, etc.

By: Ben Prusinski

Ben Prusinski — Mon, 10 Nov 2008 20:54:34 +0000

Tanel-

Nice find with oradebug. I enjoy your blog since we both have a passion for database internals.

Cheers,
Ben

By: Miladin

Miladin — Thu, 06 Nov 2008 21:29:19 +0000

In the past I have to wakeup SMON:

SQL> oradebug setorapname smon
Oracle pid: 19, Unix process pid: 12777, image: oracle@demo01 (SMON)
SQL> oradebug wakeup 19
Statement processed.

Save me time running this query:

SQL> select pid
from v$process p, v$bgprocess b
where b.paddr = p.addr
and name=’SMON’; 2 3 4

PID
———-
19

By: A reader

A reader — Tue, 04 Nov 2008 06:43:49 +0000

Thank You;-)
Nice improvement to oradebug.