You are having a database problem with the IBM Business Process Manager products. For example, you might be experiencing a problem when you connect to one of the databases. You would like to know what documentation you must collect (MustGather) so that the IBM Business Process Manager Support team can diagnose your problem. If you gather this documentation before contacting support, it will expedite the troubleshooting process and save you time.
Diagnosing the problem
Note: Before collecting the troubleshooting data, take a look at the knowledge collection for already known database problems in the IBM Business Process Manager product. If that page does not help, provide the following MustGather data:
Setting the trace string
Set the trace string to the following value logs the SQL queries that are run in the background:
Note: Enabling the trace might slow down your system. This delay can lead to transaction time-outs and errors. Disable this trace after collecting the requested information.
To set the tracing and generate a new set of logs and traces, complete the following steps for the servers or cluster that show the issue:
- In the Integrated Solutions Console, under Troubleshooting > Log and Trace, select the server for which you want to change the settings.
- Click Change Log Detail Levels.
- Select the configuration tab to set the tracing. This change takes effect after the next server restart and a completely new set of log files can be collected. Optionally, select the runtime tab to dynamically set the tracing.
- Enter the trace string and click OK.
- If you selected the configuration tab, stop the server.
- Archive and delete the current logs/traces/ffdc from the following directories:
- Start the server and check the trace.log file to make sure that the correct tracing is set.
- Reproduce the problem and note down the timestamp. Check the trace.log file to ensure that the time of the issue is covered in the file. Gather the complete server log files and the ffdc directory.
- Delete the trace string from the Log Detail Level for your server.
Note: Ensure that you have set the Maximum trace file size (recommendation: 20MB) as well as the number of historical trace files (recommendation: 20) to an appropriate value. You can find those values at Servers > Application Servers > server_name > Diagnostic Trace Service.
General diagnostic information
Collect the general troubleshooting information as described in Collect troubleshooting data for the IBM Business Process Manager products.
- Describe the problem in detail
- Can you determine which database or data source has the issue?
- Which database vendor and which version are you running?
- Is the database located on another physical machine?
- Which JDBC driver are you using?
- Is the connection test for your data sources successful? (In the Integrated Solutions Console, click Test Connection under Resources > JDBC > Data sources)
What to do next
1. Review the logs and traces at the time of the problem to try to determine the source of the problem.
2. Use IBM Support Assistant to search for known problems in the information center, forums, and technotes.
3. If you cannot find related problems or cannot solve the problem, send the information you have collected to IBM by following the instructions in Exchanging Information with IBM Technical Support.
|Business Integration||IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server||Databases||Linux Red Hat - xSeries||8.0.1, 8.0|
|Business Integration||IBM Business Process Manager Express||Databases||Linux, Windows||8.5, 8.0.1, 8.0, 7.5.1, 7.5|
|Business Integration||IBM Business Process Manager Standard||Databases||AIX, Linux, Solaris, Windows||8.5, 8.0.1, 8.0, 7.5.1, 7.5|
|Business Integration||IBM Business Process Manager Advanced Pattern on AIX||Databases||AIX||8.0.1|