Collecting information for MFT database logger problems

The troubleshooting information that you need to collect and send to IBM® if you need assistance with a Managed File Transfer (MFT) database logger problem.

1. Initially, review the information in Troubleshooting logger problems to see whether that helps you to resolve the problem.
2. If you still require assistance, collect the following information and send it to IBM Support:
   • The name of the database logger.
   • The name of the coordination queue manager that the database logger is connecting to.
   • The version of Managed File Transfer that the database logger is using.
   • The version of IBM MQ for the coordination queue manager.
   • The type of database that the database logger is using.
   • Details of any error messages that appear in the database logger's event log when the issue occurs.
   • A database logger trace that covers the time of the issue. For more information about how to collect this trace, see Tracing Managed File Transfer standalone loggers on Multiplatforms.
     • If the database logger is experiencing the problem when communicating with the coordination queue manager (for example, the database logger's event log contains error messages that include an IBM MQ reason code such as 2009 – MQRC_CONNECTION_BROKEN), collect the trace using the trace specification =all.
     • For all other issues, collect the trace using the trace specification com.ibm.wmqfte=all.
   • An archive that contains the database logger log files and configuration files. For more information about how to create the archive, see Creating an archive of MFT troubleshooting information.
   • runmqras output for the coordination queue manager. For more information about how to create the output, see Collecting troubleshooting information automatically with runmqras.