Installing Method R Workbench

Using Method R Workbench does not require you to install or change anything on your database server. Most people install Method R Workbench on a separate computer and then transport .trc files from the computer running Oracle to the computer running the Workbench application. Occasionally, people will also install Workbench on the database server so that they can filter trace files before transporting them to another computer for analysis.

Workbench Application

To install Method R Workbench:

  1. Confirm that your operating system is one of:
    • Microsoft Windows 64-bit version 7 or newer
    • Linux 64-bit and glibc 2.15 or a compatible GNU C Library
    • macOS 10.9 (Mac OS X Mavericks) or newer
  2. Confirm that you have a 64-bit Java Virtual Machine, Java SE 8 or later (JRE or JDK).
  3. Obtain a license key from our trial license key request form or our online store.
  4. Download the Method R Workbench distribution file for your platform.
  5. Inflate the distribution file in a directory for which you have read+write permission:
    • Windows. Method R Workbench for Windows is distributed as a .zip file. To install it, unzip the distribution file into a new folder. Run the Workbench application by double-clicking mrworkbench.exe.
    • Linux. Method R Workbench for Linux is distributed as a .tar.gz file. To install it, use tar -xzf to inflate the distribution file into /opt/local (for example). Run the Workbench application by executing bin/mrworkbench from a shell or a .desktop file.
    • macOS. Method R Workbench for macOS is distributed as a .dmg file. To install it, open the DMG and drag the application icon to your /Applications folder (for example). Then close and eject the DMG. Run the Workbench application by double-clicking the Workbench icon.
  6. Enter your license key in the application’s Help › License dialog.


Most of the installation problems we see have something to do with installing Java.

  • 64-bit JVM. I have a 32-bit Java Virtual Machine already installed; will that work? No, your JVM must be 64-bit, and it must be Java (JRE or JDK) 1.8 or greater.
  • Testing Java. How can I test Java on my computer? Run the command java -version from a shell prompt. If the command succeeds, then Java is visible from your path. If the command does not succeed, then visit for help.
  • Installing Java. I don’t have Java installed; how can I install it? Follow the instructions at
  • Java Not Found. The application says that I don’t have Java installed, but I do. How can I make Method R Workbench find my Java Virtual Machine?
    • Windows. Workbench for Windows uses the WinRun4J configurable Java launcher. You can control WinRun4J by editing mrworkbench.ini, which is in the same folder as mrworkbench.exe. We’ve left some comments in there to help you along. You can find full WinRun4J documentation at
    • Linux. Put the directory of the Java executable that you want to use at the head of your PATH.
    • macOS. Put the directory of the Java executable that you want to use at the head of your PATH, or set the JAVA_HOME environment variable to the parent of the bin directory containing the Java executable that you want to use. JAVA_HOME takes precedence over PATH.
  • Java Version. How can I change the version of Java that the Workbench application uses? Open a command shell, set your PATH so that java -version reports the Java version you want, and then run either mrworkbench (Linux or macOS) or mrworkbench.cmd (Windows).
  • Execution Script. What can I do if I’ve tried the other troubleshooting tips, and Workbench still doesn’t run properly when I click the application icon? Each Method R Workbench distribution includes a shell script in the bin directory that can help you work around problems you might encounter with running the application. On Linux and macOS, the script is called mrworkbench; on Windows, it is mrworkbench.cmd.


To uninstall Method R Workbench:

  1. Delete the Method R Workbench application folder that you created when you inflated our distribution file.
  2. Delete the $HOME/.method-r folder.