Tuesday, September 27, 2005

OraSRP v2.1

Well, it seems that after OOW (specifically, after presentation of Kyte and Millsap) everyone knows that Oracle enhanced format of 'WAIT' lines in trace files. By the way, OraSRP recognizes new 'WAIT' format starting from v1.8 (released in July).

But in 10.2 Oracle also slightly changed format of 'BINDS' section. Yesterday I added support of this new format of 'BINDS' into OraSRP v2.1

Also improved processing of 'RPC CALL/EXEC' entries (previously, when trace file contained more than one 'RPC EXEC' per one 'RPC CALL' then results were wrong).

Removed irrelevant numbers (for 'Total' row) in 'Statement Resource Profile' section.

Some fixes for preventing OraSRP from crashes when analyzing "inconsistent" traces.

posted by egor at 9/27/2005 05:43:00 AM

2 Comments:

Blogger Rahul said...

Hi Igor,

Great job with orasrp. Even when I am not looking at wait events, I find the orasrp generated report a lot easier to interpret than the tkprof report.

Here is something that I think is an issue in calculating % in the "Statements Recursive Relationship" section:

Statements Recursive Relationship

SQL Statement Id Exclusive Elapsed Time Cumulative Elapsed Time Similar Command Type
---------------------- ----------------------- ----------------------- ------- ----------------
453491060 65.7070s 23.7% 277.1861s 56.7% 0 UPDATE
1850235640 211.3057s 76.2% 211.3195s 43.2% 0 INSERT
3997906522 0.0111s 0.0% 0.0111s 0.0% 0 SELECT
431456802 0.0020s 0.0% 0.0020s 0.0% 0 SELECT
...
...
...

The % are correct in the Exclusive Elapsed Time column. But the Cumulative Elapsed Time should have 100% for the outermost statement and then the breakup for the inner stmts, right ?

12:32 AM  
Blogger Vadim Bobrov said...

Egor

I tried to look at OraSRP but couldn't find it. Am I looking in the right place?

Thank you
Vadim Bobrov
http://www.fourthelephant.com

1:40 PM  

Post a Comment

<< Home