IBM AIOps & Management Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
Sometimes we found DB2 DSA connection failure or DB2 table locked, but we can not find the reason, how we can turn on JDBC tracing for Impact 7.1
1. In Impact 7.1, open jvm.options in a text editor.
2. Add the following line:
-Ddb2.jcc.propertiesFile=<JCC trace file>
where <JCC trace file> points at the .properties text file, for example;
Ensure the file is in a location readable
by the Impact server process.
3. Save your changes and create the
new properties file e.g.
4. Add the following properties to
the file, change the directories as needed;
5. Restart Impact server
6. Use the 'Test Connection'
button on the db2 data source in impact UI, confirm it fails, and send us
nci_collect_logs and the jdbc trace files created in the traceDirectories you
coded in the jcc.properties file.
If your application displays JDBC-related exception messages, activate the JDBC trace service. The resulting log text can help you identify the problem.
This method activates JDBC trace for all applications that run in the server you specify. Identify your database type by selecting the trace group WAS.database and typing one of the following trace strings in the console:
Trace string for JDBC drivers of DB2® databases.
See the following DB2 database sample:
Oops, accurately says, this topic is for enabling JDBC JCC trace.