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 -> Monitoring dbwr with oradebug

Monitoring dbwr with oradebug

From: Knut Talman <knut.talman_at_mytoys.de>
Date: Tue, 26 Jun 2001 23:58:15 +0200
Message-ID: <3B390577.42335BC4@mytoys.de>

I would like to measure the I/O throughput of our system (Oracle 8.1.6.1, Solaris Sparc 6) with oradebug. As far as I know, I do the following:

  1. svrmgrl
  2. connect internal
  3. alter system set timed_statistics=true;
  4. oradebug setospid pid(bp) or oradebug setorapid pid(bp)

   orapid:

    SELECT pid "Oracle Process Id",

           name 
           from v$process, v$bgprocess 
           where v$process.addr = v$bgprocess.paddr; 

5. oradebug unlimit
6. oradebug event 10046 trace name context forever, level 10

Disabling:
7. oradebug close_trace

   oradebug event 10046 trace name context off    oradebug tracefile_name
   oradebug flush

After I have a trace file. Parameter p3 should give me the number of blocks written when monitoring dbwr, ie.

WAIT #0: nam='db file parallel write' ela= 0 p1=1 p2=0 p3=0 WAIT #0: nam='rdbms ipc message' ela= 308 p1=300 p2=0 p3=0

Problem: The whole trace file is full with 'db file parallel write' lines
but in every line p3 is 0!?!

Why are there no blocks written? What am I doing wrong? In my testcase I did a lot of INSERTs and UPDATEs during trace enabled.

Any idea?

Thanks in advance,

Knut Received on Tue Jun 26 2001 - 16:58:15 CDT

Original text of this message

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