How can you setup a SQL trace when running repotools in IBM Rational Team Concert (RTC)?
The upgrade script may have failed, or you need to run additional trace to debug repotools commands. Enabling trace may also be helpful if repotools crashes or hangs when running a command.
To setup a SQL trace when running repotools:
- Copy the following text file into your environment. For example, copy it into C:\Temp.
- Run the repotools command with the following parameters. This example is for the -createTables function, and the log4j file has been copied to C:\Temp:
repotools -createTables logFile=C:\temp\repotools.log log4j.properties=C:\Temp\log4j.properties.repotools.sqltrace.txt
- Running repotools with the above log4j settings will produce a repotools_create.log including tracing details.
NOTE: In RTC 4.0.5, Online migration not logging messages (278570) made the log4j.properties used by repotools easier to find. As of 4.0.5, it is in conf/repotools_log4j.properties. At the time of publishing this article, 4.0.5 has not yet been released. Check the jazz.net Downloads page for 4.0.5 once it has been released.
The Jazz based products have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.
|Software Development||Rational Quality Manager||1.0, 22.214.171.124, 126.96.36.199, 1.0.1, 188.8.131.52, 184.108.40.206, 2.0, 220.127.116.11, 18.104.22.168, 2.0.1, 22.214.171.124, 3.0.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 4.0, 126.96.36.199, 188.8.131.52, 4.0.1, 4.0.2, 4.0.3|
|Software Development||Rational Requirements Composer||1.0, 2.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 3.0.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 4.0, 126.96.36.199, 188.8.131.52, 4.0.1, 4.0.2, 4.0.3|