| Profiler Extension for SQL Developer Change Log |
Profiler Extension 1.5.1 (August 29, 2008)1984: Add ability to call profiler directlyExisting 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.5SQL 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 machineImplemented performance enhancements to the BFILE downloading process. Profiler Extension 1.2 (March 28, 2008)Minor changes for SQL Developer 1.2 compatibilityProfiler Extension 1.1.4 (January 21, 2008)2584: ORA-00904 invalid identifier error in bfile queryWe 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 SIDThe extension will now properly handle trace file naming for lower/upper/mixed case SID. 2603: Add permissions for DBMS_LOBThe 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. Profiler Extension 1.1.2 (November 21, 2007)2237: unable to run Profiler from SQL DeveloperModified 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 automaticallyIn 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" problemModified the trace file identifier (added seconds) to handle multiple profiles generated within one minute.
|