5.2.2.0 (2010-06-11)

New features

• 3686: Profiler kernel now emits timestamps into the .log file for activity from ignored sessions.
• 3637: You can now edit the Call Definitions and Transform Parameters files with a single click from the Preferences panel.
• 3614: Customization has been improved by moving common environment variables to the config.properties configuration file. For Profiler 5.1.x users, the following variables will be migrated, if the user chooses to migrate settings, at the first execution of 5.2.2: P5_CDEFS, P5_PARAMS, P5_ENCODING, P5_MAXJAVAHEAP, P5_NS_PER_MS
• 3604: Profiler now emits execution count per execution plan into the output, which makes it easier to reconcile the LIO Blocks numbers in the execution plan section(s) with the LIO Blocks numbers in the corresponding profile by database call section.
• 3586: Profiler kernel now renders p5k options into its XML output.
• 3498: You can now drag a file on the user interface from the completed pane (bottom) to the queued pane (top) to re-run it.

Bug fixes

• 3773: Profiler GUI now properly honors multiple command line options in "Use p5prof command line options" widget.
• 3720: Profiler now recognizes that distinct fleets of STAT lines with identical prefixes are distinct.
• 3717: Profiler now uses "java" as the default value whenever the P5_JAVA environment variable is not set, making the explicit setting of P5_JAVA unnecessary in many implementations.
• 3714: Profiler kernel now renders the correct number of input lines when ignoring sessions and there's at least one trailing empty line.
• 3712: Profiler now emits proper min/max values for RPCs.
• 3708: Profiler now renders placeholder values properly for trace files with BINDS sections containing text "No oacdef for this bind."
• 3700: Profiler kernel consumes considerably less memory for some input files, reducing the likelihood of "Out of memory" errors.
• 3678: Profiler GUI now does a better job of determining the proper --trcunit value for the kernel to use.
• 3656: Profiler user interface now complains if you try to add a non-existent file (e.g., incorrectly defined symlink) into the queued files pane.
• 3459: Profiler kernel now reports "unaccounted-for between calls" time that was previously mistaken as "CPU service, unreported call(s)" time.
• 3441: Literal values in SQL text are highlighted correctly in more cases.

Documentation corrections

• 3771: p5k --maxbind option is now obsolete.
• 3753: Documented several previously undocumented Profiler error messages in the User Guide.
• 3740: Integrated the Profiler Installation Guide into the Profiler User Guide, resulting in a much more helpful, unified document.
• 3737: Skew pictograms in User Guide now render correctly.
• 3735: Getting Started section of the User Guide now guides users to use the graphical user interface instead of the command line interface.
• 3703: Linux installation details were corrected in the User Guide.
• 3665: Corrected typographical errors in the User Guide and provided reference to the Oracle 11g diagnostic_dest directory in addition to the user_dump_dest directory used in Oracle 10g and prior versions.
• 3642: The Profiler User Guide now contains a comprehensive new section for troubleshooting Java installation problems.

5.2.1.0 (2009-09-28)

New features

• All-new Profiler user interface greatly improves workflow and overall end-user experience.
• Profiler now runs on Mac OS X (Intel), Linux, and Microsoft Windows XP and Vista.
• 3542: Made Profiler easier to install on older Windows machines.
• 3515: Profiler is now compliant with US Federal Rehabilitation Act Section 508 Technical Standards.
• 3493: Profiler kernel now interprets trace lines with r=-1 values.
• 3420: Improved the backup and migration of Profiler configuration and license files during upgrades.
• 3417: Improved performance of formatting for very long SQL texts from O(n!) to O(n).

Bug fixes

• 3564: Fixed rounding of syscall elapsed durations, which previously caused occasional attribution of durations to incorrect histogram buckets.
• 3497: Profiler kernel now properly processes all syscalls for SQL statements whose text is "commit" or "rollback".
• 3444: Improved rendering of SQL text containing tab characters.

5.1.27.0 (2009-04-24)

New features

• 3408: Profiler kernel is up to 67% faster for many types of trace files, especially large files dominated by database and OS call lines.
• 3404: Profiler recognizes new 11.1.0.7 'plh' and 'sqlid' trace data tokens.
• 3396: Profiler kernel now throws a warning when it produces a reported zero elapsed duration.
• 3357: The default behavior of the Profiler has been changed so that Section 5.1 Environment Variables will no longer display environment variable information. Use the p5prof --env option to display this information.

Bug fixes

• 3393: Profiler kernel now puts negative unaccounted-for call durations -0.000001 and -0.00001 into the proper histogram buckets.
• 3317: Profiler-generated trcsess.bat files now write multiple distinct output .trc files in situations where previously it over-wrote the same file over and over.
• 3291: Profiler no longer requires all parameter values to be defined in prof.xml. In Section 5.2 Input Parameter Listing of the HTML output, Profiler highlights each parameter value that has been set to a non-default value.

Documentation corrections

• 3312: The --progress argument to p5prof has been modified. The --progressinterval argument is deprecated. The file is updated once per second. Instead of one line per interval, the file now contains only one line with the current progress indicated by a percentage, for example, 25%. This behavior actually changed in 5.1.24, but documentation has now been corrected.
• 3313: Eliminated the p5k --ocinames command line option. (Feature moved to the prof.xml file.)

5.1.26.0 (2008-11-04)

Release Notes

• If you receive errors about the new parameters, SHOW-LITERAL-HIGHLIGHTING or SHOW-OCI-NAMES, you need to edit your prof.xml file. Just add the following two lines to your prof.xml file. We put ours right after the definition of SHOW-P5-STATEMENT-ID in the "Feature Activation" section.

  <param name="SHOW-LITERAL-HIGHLIGHTING">true</param>
  <param name="SHOW-OCI-NAMES">false</param>

New features

• 3280: New prof.xml parameter SHOW-LITERAL-HIGHLIGHTING allows user to specify whether to highlight literal values in SQL text.
• 3275: The "Add Files" button how has a filter for "All files" and for compressed files, in addition to the previously existing filters for *.trc and *.xml files.
• 3268: Upgraded Saxon to 9.1.0.2j.
• 3215: New SHOW-OCI-NAMES prof.xml parameter replaces old --ocinames command line argument.

Bug fixes

• 3276: The environment variable P5_COBRAND is no longer being used, and was valid only for the 5.1.25 release.
• 3265: The "trace file version" drop-down box now displays "version 8 or older" and "version 9 or newer" choices to simplify the option and more efficiently handle future versions..
• 3263: Eliminated "Too many nested template or function calls" errors in cases containing SQL statements with long lines when SHOW-LITERAL-HIGHLIGHTING is activated.
• 3257: Corrected User Guide to specify that using p5unzip is no longer necessary for files of type .bz2, .zip, .gz, .lzf, or .lzo.
• 3256: Fixed broken link in User Guide to Saxonica Limited.
• 3253: Eliminated "Too many nested template or function calls" errors in cases where p5skew HTML output has thousands of lines.

5.1.25.0 (2008-09-29)

New features

• None.

Bug fixes

• 3248: When a statement contains more than one comment and a literal appears between the two comments, the highlighter now recognizes that literal.
• 3245: Profiler now handles STAT lines with negative "obj" values.
• 3240: Improved literal value highlighting in SQL text for lines that end with "is null" or "is not null".

5.1.24.0 (2008-08-29)

New features

• 3214: Renamed "unaccounted-for at file conclusion" pseudo-call to "CPU service, unreported call(s)" and improved documentation allowing more Profiler users to understand what to do when it is the dominant contributor to end-user response time.
• 3196: Profiler kernel now understands how to unzip .zip, .gz, .bz2, and .lzf file formats without requiring you to configure p5unzip to do it for you (in etc\config\unzip.xml).
• 3141: Upgraded core to use Perl 5.10.
• 3121: The Profiler log file now shows the Profiler version and all pertinent environment variables in effect.

Bug fixes

• 3201: Profiler now highlights anchor text only if it is a clickable link.
• 3200: Profiler kernel no longer emits information about environment variables when using the --noenv command line argument.
• 3139: Fixed installation issue with the 5.1.23.0-B.exe. The .NET 2.0 framework will now be correctly installed.
• 2901: GUI now honors the setting of the P5_MAXJAVAHEAP environment variable.

5.1.23.0 (not released)

New features

• 3131: User Guide links the concept of multi-session trace files to the --trcsess option that automatically generates Oracle trcsess commands for such files.
• 3086: Profiler no longer requires the P5_JAVA environment variable to contain a fully-qualified path name. Setting P5_JAVA=java.exe (the new default setting) now works as long as your PATH is set to find java.exe version 1.5 or above.
• 3081: Profiler now shows placeholder names only once in the placeholder table. They are listed in alphabetical order for easy reference.
• Logo, copyright and documentation changes to reflect Method R ownership.

Bug fixes

• 3127: Profiler kernel now dies gracefully when run on a non-existent or unreadable compressed file.
• 3125: Profiler now respects the SHOW-CONFIDENTIALITY-LABEL=true parameter setting in prof.xml.
• 3118: Fixed a bug wherein the Profiler kernel put the trcsess batch file in an unexpected directory if you select a cdefs file during a GUI session.
• 3105: "Number of distinct execution plans" is now counted correctly for SQL statements that have no execution plans in the input trace file.
• 3096: Profiler no longer dies and throws "Bit::Vector::_add(): illegal operand type in overloaded '+' operator at p5k.pl line %d" when a SQL statement produces two or more execution plans in the trace data, where one or more plans have statistics and one or more have no statistics.
• 3054: Profiler no longer lists placeholders listed within SELECT INTO clauses in "Placeholder Values" tables (sections 4.*.4). Previously, for example, "select c1 into :b1 from t where c2=:b2" would incorrectly show :b1 bound to :b2's value in a "Placeholder Values" table, and Profiler wouldn't show the :b2 name at all.
• 3063: In SQL statement texts, Profiler now highlights the word "null" in contexts where a placeholder variable could have been used instead.

5.1.22.0 (2008-03-31)

New features

• 2885: Improved documentation about when and how to use byte encodings other than the default UTF-8.
• 2814: Profiler now makes it easy to see substitutable literals in SQL by highlighting them in the SQL text sections (section numbers 4.*.5).
• 2725: Users can now specify a default --maxjavaheap value in the environment variable called P5_MAXJAVAHEAP.
• 2726: HTML files no longer contain irrelevant statement detail sections for trace files featuring many similar DDL statements. In our test case, HTML file size dropped from 12.9MB to 0.5MB with no loss of relevant information.

Bug fixes

• 2755: Profiler now lets the user know that the task begin and end times are unknown when there's no timestamp in the input trace stream (instead of rendering dates relative to midnight 01/01/1970 UTC).
• 2812: In statement section headers (sections 4.*), it was confusing to see re-use information saying, "1 similar but distinct text". Now, when there's only one distinct text, the information rendered says simply, "1 distinct text".
• 2761: Corrected references in User Guide to --ns_per_ms Profiler kernel option.
• 2698: Profiler now handles arbitrarily long tim values.

5.1.21.0 (2008-01-23)

New features

• None.

Bug fixes

• 2697: Fixed a bug in which oddly-formed Oracle trace data caused the Profiler kernel to emit a element with an id="" attribute. This evidenced in the error message "FORG0001: ValidationException: Cannot convert zero-length string to an integer."
• 2716: Fixed p5prof's inability to recognize Java version "numbers" with characters other than numbers, dots, and underscores in them.

5.1.20.0 (2008-01-07)

New features

• 2631: Profiler and skew analyzer now check to ensure that the file referred to by the P5_JAVA environment variable is an executable Java version 1.5 or greater.

Bug fixes

• 2616: Fixed a bug that prevented the creation of a profile in cases where the trace file has only "WAIT" and "*** SESSION ID" lines (that is, where the trace file contains no db call lines).
  
• 2635: Fixed a bug that caused zombie DOS command shells to exist for the browser lifespan when viewing Profile reports.

5.1.19.0 (2007-12-21)

New features

• 2466: New --trcsess option generates a runnable script containing Oracle trcsess commands that correspond to Profiler log lines of the form, "p5k: ignoring trace data from session (%d.%d) on input lines %d..%d". New --script, --s_ext, and --s_rem options provide user control over the script generation.
• 2258: Now we render the time of the XML file creation, the duration of the Profiler kernel run, and the kernel's MB/sec performance into the Profiler HTML report.
• 2290: Added text to histogram sections (2.*) noting the min, max, and average latencies for the call being described.
• 641: Render the total number of database buffer cache accesses into the profile report header information.
  

Bug fixes

• 2109: Fixed "substr outside of string at p5k.pl line %d" error.
• 2118, 2119: Fixed instances where --ocinames command line option was not honored
• 2599: The license file will now be checked in both the installation directory and the etc\license\ subdirectory for compatibility with all Hotsos products.
• 2510: Upgraded Saxon processor to 9.0.0.1J.
• 2506: Fixed mouse-over hint for "stats" links that refer to statements with no Oracle hash value.
• 2586: Corrected a reference in the User Guide to the directory to which older licenses are backed up during upgrades.
• 2505: Corrected the "Support" section in the User Guide to point to our Hotsos discussion group.
• 2388: Fixed a bug that prevented the "stats" link (and the corresponding statement detail section) from rendering for some ancestors of interesting cursors.
• 2107: Matched the labels on the hotsos.com license registration form with those on the license registration dialog in the product.
• 2186: Fixed a bug that caused the kernel to interpret a STAT line group with intermixed recursive dbcalls as separate STAT line groups.
  

5.1.18.0 (2007-09-14)

New features

• 2042: New --ocinames command line option shows developer-friendly dbcall names (e.g., "prepare", "execute") instead of raw trace file names (e.g., "PARSE", "EXEC").
• 1982: New --javascript/--nojavascript command line option allows you to disable JavaScript "View characteristics" section.
• 1914: Hotsos Profiler now processes Oracle Database 11g trace files.
• 1913: Hotsos Profiler now reports on cost, size, and card row source statistics in Oracle Database 11g trace files.
• 960: New Hotsos Profiler kernel argument --ns_per_ms allows you to specify the duration, in nanoseconds, of an Oracle "microsecond."

Bug fixes

• 2097: Changed visited link color to better visually distinguish visited links from unvisited ones.
• 1939: Added reference to SHOW-NEGATIVE-ROW-SOURCE-TIMINGS parameter when suppressing negative row source timings, to better indicate to the user how to see the missing data.
• 1281: Enhanced reporting of lob processing.
• 1248: Enhanced reporting of cursor-close statistics.
• 60, 2003, 2035: Improved attribution policy for between-call network messaging assigned to cursor slot #0.

5.1.17.0 (2007-06-29)

New features

• 1539: New Hotsos installer-managed "Hotsos Pictogram" font eliminates the need to install "Arial Unicode MS" font to see properly rendered pictograms.

Bug fixes

• 1788: Fixed the problem causing the error "SXXP0003: Error reported by XML parser: Invalid byte 2 of 3-byte UTF-8 sequence."
• 1358: Fixed skew analyzer defect which concealed obj# of calls when using --group=$obj.
• 1328: Profiler now highlights row source operations only when it is supposed to.
• 1218: Accurized text in execution plan sections with negative row source timing data.

5.1.16.0 (2007-04-03)

New features

• None.

Bug fixes

• 1159: Fixed fatal error "XTTE0570: An empty sequence is not allowed as the value of parameter $value" when Oracle kernel emits row source statistics on some STAT lines in a plan but not all of them.
• 1141: Fixed SQL formatter which truncated any string of one or more '0' characters from the tail-end of SQL statements.

5.1.15.0 (2007-03-16)

New features

• None.

Bug fixes

• 1025: Windows 2000 Launch Condition error.
• 947: oci.dll error dialog.

5.1.14.0 (2007-03-02)

New features

• 887: New Profile by SQL Statement section, which highlights SQL statements that consume significant response time but whose contributions would appear in diluted form in the Profile by Cursor section.
• 719: New SHOW-NEGATIVE-ROW-SOURCE-TIMINGS parameter.

Bug fixes

• 711: Pictogram characters now display properly in IE7.

5.1.13.0 (2006-08-25)

New features

• None.

Bug fixes

Note that from this release forward, case numbers shown here are from our new Hotsos Technical Support system, and the text shown here is no longer the bug text, but the release note explaining the post-repair state of the product.

• 126: Profiler kernel honors --xsd command line option.
• 91, 149: Profiler more accurately displays placeholder (bind variable) values.
• 80, 116: Profiler now processes invalid XML characters by translating nonprinting control characters found in Oracle trace files to a visible format; for example, character 0x00 renders in Profiler output as .
• 59: Profiler User Guide explains how it selects which placeholder values to display for a given execution plan.

5.1.12.0 (2006-07-27)

New features

• None.

Bug fixes

• 1436: Critical error in packaging that occurred in 5.1.11.0.

5.1.11.0 (2006-07-21)

New features

• None.

Bug fixes

• 1430: Profiler truncates rowid values in bind data
• 1423: Profiler 5.1.10 allocates time to unaccounted for at file conclusion
• 1330: Warning about negative time for row source operations
• 1376: Begin Prepare Stmt shows incorrect CPU Time

5.1.10.0 (2006-06-02)

New features

• None.

Bug fixes

• 1373: Profiler Output Truncated

5.1.9.0 (2006-05-26)

New features

• None.

Bug fixes

• 1296: Timing Calculation of Profiler
• 1295: Another strange-looking execution plan
• 1294: Strange-looking execution plan
• 1170: Profiler execution plan not showing the last four STAT lines.
• 1096: Plans Not Displaying Correctly

5.1.8.0 (2006-04-21)

New features

• None.

Bug fixes

• 1274: Highlight when Errors and/or Warnings Occur
• 1269: Identify Max Dump File Limit in Profiler

5.1.7.0 (2006-03-24)

New features

• None.

Bug fixes

• 1262: Profiler output should render trace file Oracle release
• 1258: The Profiler output doesn't display the detected Oracle release
• 1254: Ambiguous "Skew Data" titles for "SQL*Net message from client" and "SQL*Net message from client [think time]"
• 1224: Profiler output has cursor grove with cursors that have empty statement reference
• 1223: Profile by Cursor section "Total" row has wrong line number
• 1209: Profiler and Laredo coexistence isn't what it should be

5.1.6.0 (2006-02-24)

New features

• Each synthetic commit and rollback statement now references the Oracle hash value of the statement that it follows.

Bug fixes

• 1228: p5prof: command failed (2304)
• 1226: Trace File Does not Process
• 1222: Question regarding control of P5 with Large Trace Files
• 1218: Profiler output shows too much elapsed time
• 1211: Profiler kernel, p5k, emits too many synthetic commit or rollback statements
• 1207: P5140 GUI hangs between parsing trc file and building xml file
• 1175: Profiler - "Task identification" not being displayed (reopened)

5.1.5.0 (2006-01-20)

New features

• Attribute "unaccounted-for between dbcalls" time to application SQL instead of the synthetic catch-all "not accounted for within other statements".
• Accurately process trace files with multiple Oracle sessions represented in them.

Bug fixes

• 1208: Subtyping qualifier-label doesn't render when there's no qualifier attribute
• 1204: Incorrect Execution Plan Displayed
• 1196: Not Displaying Bind Variable Info
• 1180: Minor grammatical errors in Hotsos Profiler User Guide 5.1.4.0
• 1175: Profiler - "Task identification" not being displayed
• 1171: Profiler Misspelling of "CHARACTER" in 5.1.4.0
• 1140: Does Profiler still require .NET beta version?
• 1130: Bind variables missing from Profiler output?

5.1.4.0 (2005-12-16)

New features

• None.

Bug fixes

• 1166: P5 Profiler uninstall doesn't remove Hotsos folder from start menu
• 1164: Toggle 'Show Top n' combo box
• 1158: Profiler doesn't show placeholder values when there's no plan
• 1144: What is "commit (synthetic)"?
• 1139: Need to display commit and rollback counts in HTML output
• 1135: Upgrade should leave unzip.xml alone
• 1134: Skew Analyzer "Show top n" default value should be "All", not "0"

5.1.3.0 (2005-12-02)

New features

• New SHOW-CONFIDENTIALITY-LABEL profiler parameter allows users to label their profile documents as confidential company property.

Bug fixes

• 1127: Profiler 5.1.2.0 abnormally terminates on Windows 2000
• 1125: Sections 5.3.4.* display incorrectly as 5.3.3.*
• 1123: Error in Hotsos Profiler User Guide - Release 5.1.2.0
• 1119: Profiler dies with SXXP0003..."event" must not contain the '<' character
• 1118: Profiler ignores boolean option specifications
• 1028: FORG0001: Invalid dateTime value. Non-existent date

5.1.2.0 (2005-11-08)

New features

• Compute Oracle trace file timing unit automatically. This allows users to use the Profiler more easily with trace files from instances running different versions of Oracle.
• Elide the Profile by Cursor in the same manner as we elide other sections within the profile report, governed by the CONTRIBUTIONS-MAXIMUM-LIST-LENGTH parameter. This yields a significant performance improvement for trace files containing many distinct SQL texts.

Bug fixes

• 1114: ERROR lines in trace file not reported in HTML output
• 1099: P5 Console passing wrong value for --trcunit to P5PROF
• 1066: P5 java.lang.OutOfMemoryError on Large Trace Files - Similar to ticket 1053
• 1053: XSLT processor crashes with Java out of memory error on large files
• 1050: Files with two periods in name crash console
• 1048: Profiler v5.1.0.11 attributing RPC Call unlike newer v4.1.4 and higher
• 1046: P5 Console application crashes when using file names with multiple '.' separators
• 1038: Subroutine and Cursor Profile totals don't match

5.1.1.0 (2005-10-07)

New features

• None.

Bug fixes

• 1085: No Java at install time
• 1080: Transformation Failed error when running profiler
• 1040: Error in Skew Analyzer output?
• 1037: Use of uninitialized value ...at p5k.pl line 2000/2007
• 1024: Use of uninitialized value in concatenation (.) or string at p5k.pl line 2172
• 1023: Can't spawn "cmd.exe": No such file or directory at p5prof.pl line 135
• 1022: p5skew: can't open '| "C:\...\java.exe" -jar ... >....html' (Bad file descriptor) at p5skew.pl 251
• 1018: FORG0001: Invalid dateTime value. Day is out of range
• 1014: Getting invalid license when installing P5 Profiler
• 1011: p5k throws uninitialized variable warnings to STDERR
• 1008: Strange characters in P5 output
• 1007: FORG0001: Invalid dateTime value on line 88 of task.xsl

5.1.0.0 (2005-09-16)

New features

• All new user interface
• All new report format

Contents

1. Select Help > Check for Updates...
   
2. If the Welcome dialog appears, click Next.
3. If you are updating a prior installation of Profiler Extension, make sure the Method R Extension box is checked and skip to step 8. If you are installing for the first time, continue with the next step.
4. Click Add. The Update Center dialog appears.
5. In the Name field, enter: Method R Extension.
6. In the Location field, enter: http://www.method-r.com/extension/
7. Click OK. The 'Source' dialog appears.
8. Click Next. The 'Updates' dialog appears.
9. Click the checkbox next to the Method R Extension you want to install, then click Next. The 'Download' dialog will appear that will display progress status. Once the download completes the 'Summary' dialog appears.
10. Click Finish. The Preferences dialog appears.
11. Click OK. The Confirm Restart dialog appears.
12. Click Yes to restart SQL Developer.

• Select Method R Profiler > Profile Statements. A check mark next to Profile Statements indicates the Profiler Extension is enabled.
  
• Click the Method R icon in the toolbar. The icon appears in color when the Extension is enabled and is gray when it disabled.

1. Enter the statements you want to profile in a SQL Worksheet.
2. Click the Run Script icon. The Profiler Extension will begin processing and the log panel will display any status or error messages.
3. If the Profiler completes successfully, the following actions will occur:
   • An HTML document opens in your default web browser, if you have selected that option in your preferences.
   • An entry appears in the Profiler History panel.
   • The HTML output will be stored in the trace files directory as specified in the preferences panel.

When this dialog appears:

1. Select one of the following options:

   DBA has executed script manually.

   Select this option if your DBA has already granted the required access.

   Grant access to PUBLIC (all accounts).

   Select this option if you want to grant the required access to all accounts.

   Grant access to account only.

   Select this option if you want to grant the required access only to the specified user.

2. Enter the password for the SYS account if you have selected one of the Grant access options.
3. Click OK.

DECLARE
  v_schema VARCHAR2(40) := '"PUBLIC"';
  v_user_dump_dest VARCHAR2(2000);
BEGIN
  select value into v_user_dump_dest
  from v$parameter
  where name = 'user_dump_dest';

  EXECUTE IMMEDIATE 'CREATE OR REPLACE DIRECTORY "METHODR_UDUMP_DEST" AS ''' || v_user_dump_dest || '''' ;
  IF v_schema != '"SYS"' THEN
    EXECUTE IMMEDIATE 'GRANT READ ON DIRECTORY METHODR_UDUMP_DEST TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT ALTER SESSION TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT SELECT ON SYS.V_$INSTANCE TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT SELECT ON SYS.V_$SESSION TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT SELECT ON SYS.V_$PROCESS TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT SELECT ON SYS.V_$MYSTAT TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT EXECUTE ON DBMS_UTILITY TO ' || v_schema ;
    EXECUTE IMMEDIATE 'GRANT EXECUTE ON DBMS_LOB TO ' || v_schema ;
  END IF;
END;

To open one or more Profile output files from the history, select the desired files in the History panel, then click Open. The files will open in your default browser.

To clear files from the history, click Clear in the History panel. All history records will be cleared from the table. This does not delete the files from the drive.

1. Select Tools > Preferences. The Preferences dialog appears.
2. Select the Method R Profiler tree item. The Method R Profiler preferences appear displaying a panel with 2 tabbed pages. The first tabbed pane contain the Extension Preferences and the second contain the Profiler Parameters.

Extension Preferences

Enable Profiler on startup

Check this box if you want the Profiler Extension to be enabled when you start SQL Developer.

Directory to save trace files

Enter a directory path or click Browse to find a directory. All trace files generated with the Method R Profiler Extension will be stored in the specified directory.

Maximum trace file size (MB)

Enter or select the maximum trace file size you want to automatically download when you profile code. If the trace file that is generated exceeds this size, you will be asked to confirm the download, or the download will be skipped without confirmation, depending on the setting for Confirm if limit is exceeded.

Confirm if limit is exceeded

If this box is checked, you will be asked to confirm the trace file download if the file exceeds the value specified in Maximum trace file size (MB). If this box is not checked, the download will be skipped without a confirmation if the limit is exceeded.

Logging Level

This is the Java logging level that controls the type of messages that displayed for the Method R Profiler extension. Each log message is associated with a level to indicate the importance and urgency of the message. Changing this setting will result in increasing or decreasing the amount of messages that are displayed to the logging window.

Profiler Parameters

Automatically open HTML output in default web browser

Check this box if you want the Profiler output to automatically open in your default web browser when you profile code.

Call definitions

Enter a call definitions file location or click Browse to find a call definitions file. The Profiler User Guide contains more information about specifying call definitions. To see the Profiler User Guide, select Start > All Programs > Method R > Profiler > User Guide.

Transform parameters

Enter a transform parameters file location or click Browse to find a transform parameters file. The Profiler User Guide contains more information about specifying transform parameters. To see the Profiler User Guide, select Start > All Programs > Method R > Profiler > User Guide.

Maximum Java heap size (MB)

Select a maximum size for the Java heap during execution of the Method R Profiler.

Nanoseconds per 'microsecond'

Set the number of nanoseconds per Oracle “microsecond.”

Property Files

Setting Up Logging

Saving Log Messages to a File

1. Select Tools > Preferences. The Preference dialog appears.
2. Select the Environment > Log tree items. The Environment:Log dialog opens.
3. Check Save Logs to File, then enter a Log Directory or click Browse to find a directory.
4. Select any other desired options, then click OK.

1. Select Method R > Profile Input File...
   
2. A form will appear as shown below:
   

Select a file to profile

The first parameters is the input file that can selected by clicking the Browse button next to the text field. This can be a Trace file or a Zip file containing trace files.

Profiler Parameters

The other fields are exactly the Profiler Parameter as described in the Preferences section.

Results

The Results text area is the location where the logging data will be collected about the execution of the Profiler status.

Profiler Extension 1.5.1 (August 29, 2008)

1984: Add ability to call profiler directly

Existing trace files may now be Profiled directly from the SQL Developer interface, in addition to the Zero Click Profiles generated from the SQL Worksheet.

2829: Profiler extension should function with SQL Developer 1.5

SQL Developer 1.5 significantly modified their internal architecture, so the Profiler Extension 1.5.1 is required for correct functionality. If SQL Developer 1.2.x must be used, please use Profiler Extension 1.2.x to match.

2114: Trace file download locking up machine

Implemented performance enhancements to the BFILE downloading process.

Profiler Extension 1.2 (March 28, 2008)

Minor changes for SQL Developer 1.2 compatibility

Profiler Extension 1.1.4 (January 21, 2008)

2584: ORA-00904 invalid identifier error in bfile query

We now handle the case where a trace file header extends beyond 1024 bytes because of bind variable lines before the expected preamble.

Profiler Extension 1.1.3 (January 11, 2008)

2445: Check for trace file with all cases for SID

The extension will now properly handle trace file naming for lower/upper/mixed case SID.

2603: Add permissions for DBMS_LOB

The extension requires execute permission on the DBMS_LOB package. The permissions dialog will now correctly grant these permissions for database connections without former access to the HOTSOS_UDUMP_DEST directory.

For existing installations in which the DBA revoked permissions on DBMS_LOB, these permissions will need to be granted explicitly by the DBA to allow access for the extension.

Profiler Extension 1.1.2 (November 21, 2007)

2237: unable to run Profiler from SQL Developer

Modified the query which is used to locate the trace file on the server to handle platforms where instance name is not reported correctly in V$INSTANCE.

2356: HTML output not opening automatically

In some cases, the HTML output would not open automatically as expected. We moved the call from the Profiler core to the Extension to resolve this issue.

2417: "unaccounted-for between dbcalls" problem

Modified the trace file identifier (added seconds) to handle multiple profiles generated within one minute.

The automated licensing engine is temporarily offline. Please obtain your license by writing to This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Thank you for your purchase of Method R Profiler.