TM ART Log Analyzer.

You can analyze TM ART log files and answer lots of TM ART questions quickly.


Caption for picture above: The original TM ART Log analyzer, now in a museum curated by Hal DeVore.


Major update: The older version of this blog entry had the bat file named findstr.bat. Bad! That means that the findstr.bat file will call itself instead of calling the built-in findstr utility and that means a vicious hanging loop.  I have corrected this by having you call the bat file findstx.bat instead of findstr.bat.



1. Put a copy of all the TM ART logs involved in one directory. For example C:\tmp\log1

2. Put the attached findstx.bat in that directory

3. Run findstx.bat

4. Findstx.bat will read in the *.log files and create .txt files.

5. List the *.txt files.

6. All .txt files that are greater than 0 bytes are interesting.

7. Use the text in the .txt files to search the BMC support knowledge base.


You can re-run this as many times as you like. It does not alter the .log files and it overlays the .txt files.


After working on TM ART for a while I noticed that I was always looking at the log files for the same text.  And after TM ART started supporting the use of Oracle as the TM ART repository with TM ART 3.0 in January 2007 I noticed I searched the logs for the text "ORA" quite a bit. So I created a .bat file to do the most common log file searches.


Here is an example. After you run findstx.bat and it displays "dir *.txt" you get this:



So since rollback.txt contains more than 0 bytes it may be interesting. So we search the knowledge base at the BMC support site and we find knowledge article KA366959. And that tells me I need to tune my database that is being used as the TM ART repository.


That is just one example.  In general you look at E.txt first and W.txt second since they contain Error s and Warnings.


Here is bit of information about each file produced:

AppServershutdown.txt - Helps establish a timeline

AppServerstartup.txt - Helps establish a timeline

complete.txt - Helps establish a timeline

DataDelete.txt - Shows internal DataDelete information

DeleteMonitorDataOrder.txt - Shows internal DataDelete information

E.txt - Shows errors. Look at this file first.

finished.txt - Tells when internal DataDelete sections finish

LowOnMemory.txt - Helps with tuning.

Memorylimitexceeded.txt - Helps with tuning.

ORA-00600.txt - Oracle error from TM ART database.

ORA-01653.txt - Oracle error from TM ART database.

ORA-01654.txt - Oracle error from TM ART database.

ORAdash.txt - Oracle error from TM ART database.

rollback.txt - Oracle rollbacks indicate database tuning is needed.

Rule37.txt - We had an issue with Rule 37 for a while.

shut.txt - Helps establish a timeline

start.txt -  Helps establish a timeline

StartAndShut.txt - Helps establish a timeline

UpdateException.txt - Specialized problem from the past.

UpdateExceptionFailed.txt - Specialized problem from the past.

W.txt - Shows warnings. Look at this file second.

writtenWithin.txt - Shows how long it takes to write results, used for tuning.


Note on the attached file - rename findstxbat.txt to findstx.bat. I did not want to have a .bat file just to avoid someone running it accidentally.


I would love to hear comments on whether you find this useful or how to possibly make it more useful.


Update August 23, 2015: I attached an updated bat file.  See comments in the file. (You will have to rename it to findstx.bat or whatever.)

Update October 5, 2915. I attached an updated bat file and deleted the old one from August 2015. See comments in the file. (You will have to rename it to findstx.bat or whatever.)