Release 1.5 Name Change

Due to an inadvertent clash between my TraceMiner name and a registered trade mark from Germany, I have had to change the name of my utility. It is now TraceCollier.

This is the first TraceCollier release under the new name. The version has been upped to 1.5 to cover.

The EXE files are for Windows. The 32 and 64 bit versions are available. The other files are form Linux and again, there are 32 and 64bit versions.

When you have downloaded the version you want, please rename it to get rid of the digits. (If you wish.)

Enjoy.

Release 1.10

Release 1.10 fixes one minor foibles:

• Trace files created with the trcsess utility could not be opened. That has been fixed.

It also adds a few minor "enhancements":

• The project file for CodeBlocks on Windows, has been updated with new targets to build 32 and 64 bit versions. I'm hoping to also have the same targets for Linux builds, also using CodeBlocks.
• The HTML report has a new footer to list the version of TraceMiner2 used, and has links to the Licence, the sources and the binary releases.
• Batch files for Windows users, have been supplied to rebuild (full compile of everything) or recompile (changed files only) using CodeBlocks as a make utility.

Sources work on all platforms. EXE files are for Windows, the others are for Linux.

Enjoy.

Release 1.09

Release 1.09 fixes a couple of minor foibles:

• The EXEC line in an ERROR entry is now listed along with the error line, as in EXEC/ERROR.
• The headings have been changed to suit the above.
• The alignment for the Binds line, for an ERROR, has been fixed. It was left and should have been right aligned.
• The doxygen comments have been corrected to avoid warnings when generating Doxygen documentation. (For developers really)
• The doxygen control file has been updated for the current version of Doxygen.

The binary files are:

• Windows 64bit binaries (TraceMiner2.exe) use REGEXes. Compiled with gcc 5.1.0
• Linux 64bit binaries (TraceMiner2) do not use REGEXes. Compiled with gcc 4.8.5.

Sources work on all platforms.

Release 1.07

Version 1.07 is a bugfix with bonus release.

• Command line option -f was not working but --feedback was. Fixed.
• COMMIT or ROLLBACK lines had incorrect formatting. Fixed.
• Better CSS, thanks Rich, allows table widths etc to be changed without a recompile.

Windows binaries (TraceMiner2.exe) are 32bit and suitable for both 32 and 64bit Windows.
Linux binaries (TraceMiner2) are 32bit and should be suitable for the appropriate platform. 64bit users might need to install the 32 bit support libraries. Check your repository for details.

Sources will compile on all platforms.

Release 1.06

Updated to 1.06 by customer request. (Hi Rich).

If you pre-process a trace file using TraceAdjust and then run it through TraceMiner2, it will report the date and time of each EXEC statement. The date format is always yyyy Mon dd hh24:mi:ss.ffffff and is accurate to micrsecond level - in as much as the Oracle tim value in a trace line is accurate of course.

Windows binaries (TraceMiner2.exe) are 32bit and suitable for both 32 and 64bit Windows.
Linux binaries (TraceMiner2) are 32bit and should be suitable for the appropriate platform. 64bit users might need to install the 32 bit support libraries. Check your repository for details.

Sources will compile on all platforms.

Release 1.05

This release fixed issue #15 which was where it was ignoring binds for a cursor when that cursor had previously been closed. Now that Oracle caches closed cursors, we need to always consider those binds.

I also added a header on the screen and in the debug file (when running --verbose) to display the version and whether REGEXes are in use or not.

• Windows 64bit binaries (TraceMiner2.exe) use REGEXes. Compiled with gcc 5.1.0
• Linux 64bit binaries (TraceMiner2) do not use REGEXes. Compiled with gcc 4.8.5.

Sources work on all platforms.

Release 1.04 - 64bit binary + Sources Windows and Linux

Release 1.04 - 64bit binary + Sources

This release is an experiment. The contents are the sources and compiled versions of TraceMiner 2, version 1.04 for 64 bit Windows and Linux.

Windows 64 bit Version

TraceMiner2.exe has been tested for "stand-alone-ness" in a Windows 7 command session with no %PATH% set up, to ensure that it can be used as is. It worked fine.

Let me know if you have difficulties. It was compiled with this:

C:\Users\hisg494>g++ --version
g++ (tdm64-1) 5.1.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Linux 64bit Version

TraceMiner2 has been compiled with this:

g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

And it requires the following shared libraries:

$ ldd bin/TraceMiner2
        linux-vdso.so.1 =>  (0x00007fff31f0a000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f4012199000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f4011e97000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4011c81000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f40118b4000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f401249d000)

32bit Systems and 'Other' Unix Systems

Sorry folks. You need to download the Release 1.04 source code only and compile for your own system.

Source Only Release 1.04

Source Code Only Release (like all then others actually, but I might be doing binaries soon!)

Testing with older versions of the g++ compiler, specifically 4.8.5, showed that while version 5.1.0 compiled my code ok, the old version had errors. Most amusing, not. These foibles are fixed in this release.

Also fixed was an interesting bug whereby if the trace file was generated on Windows, the ^M aka \r aka carriage return at the end of each line caused an exception when extracting a bind variable, when compiled with an old version of g++, and the last bit of text on the line was the bind name. For example:

SELECT STUFF FROM TABLE WHERE SOMETHING = :BIND_NAME^M;

This is now also fixed. Unfortunately, it slows down the parsing of a trace file as it looks for and removes the ^M characters.

And finally, if a trace file was created without bind variable details, the report displayed the SQL statements with all the binds removed! Not good. Now it simply displays the SQL text unchanged - still with the binds present.

Source Only Release 1.03

Version 1.03
Fixes missing information in the ERROR lines. This is different from the PARSE ERROR lines and was missing details of what line the SQL was found on, where it was parsed and the EXEC line that caused the error.

Release 1.02

A couple of small bugs fixed:

• When a bind was immediately preceded by a '>' (greater than, or PL/SQL parameter passing '=>'), or a '<' (less than), it was not being recognised as a bind variable.
• Double spacing multi-line SQL statements in the report have been fixed.
• Much better debugging information as line numbers are reported for (almost) ever process that works on lines of the trace file.