- Written by Cary Millsap
- Created: 23 June 2011
New Release! Announcing MR Tools (Method R Tools) version 2.0, our new production version of the trace file tools that we use every time we analyze an Oracle trace file. MR Tools is the perfect companion for the Method R Profiler. If you use tkprof, MR Tools will show you what you’ve been missing. Priced beginning at us$397 per userid.
No other tools (free or commercial) come close to the precision and trustworthiness of Method R software.
Alex Gorbachev / Pythian / Ottawa, Canada
Just in time for ODTUG Kscope11, today we have released the MR Tools (Method R Tools) version 2.0, our new production version, after an 8-week beta test. MR Tools is a suite of software tools that we use every time we analyze an Oracle trace file. The improvements we’ve made are all motivated by changes we’ve needed to become more effective optimizers in our field work. The differences between version 2 and version 1 are enormous. Here are some of the highlights.
First, there are three new tools in the bundle:
- Method R Profiler users among you realize the very difficult problem of Oracle trace files that include lines that you really don’t want the Profiler to see. You can’t simply delete those lines, because the Profiler interprets unexplained tim value changes as unaccounted-for time. mrcallrm removes calls on lines that you want to ignore, and it ripples the appropriate clock value changes throughout the trace file. The result is a trace file with perfect time scope.
- You can see in your trace file that a disk read concluded at tim=1278093618299357. What time is that? With mrtim, you can know that it was 2011-06-22T13:37:45.138542-0500. Now you can correlate your trace data back to your Oracle Active Session History data or your SAN management software. mrtim even knows about the Oracle Database’s nasty little habit on some platforms of calling 1,024 nanoseconds a “microsecond.”
- The Oracle 11.1 era has not been kind to trace file users. Oracle Database bug 7522002 causes database call time values and OS call time values to run off clocks with different resolutions. This causes the sequence of calls in a trace file to zigzag back and forth in time. It makes Oracle trace data incomprehensible, and it renders profiling tools useless. mrtimfix fixes all that. It can also convert all your 1,024-ns-per-ms time values to true microsecond values if you want.
We’ve also added loads of new features into the existing tools. Most of the new features are in the flagship tool of the suite, mrskew. mrskew version 2 has significantly more profiling capabilities. By default, mrskew now produces a profile of where your Oracle Database subroutine call response time (dbcalls and syscalls) has gone. mrskew gives you over a dozen new group and filter expression variables describing attributes like service, module, action, Oracle version, and even SQL text. Now, at last, you write a simple query that groups response time for a directory full of trace files directly by the text of your SQL. If you’re already a tkprof user, the richness of mrskew will make you feel like you have your very own jetpack.
There are lots more new features in our other tools like 11gR2 support, timezone awareness, broader support for Oracle versions and host Oracle platforms, cascading .rc files, and more. Visit the MR Tools Change Log for a complete list.