What to do if the MFT logger is started, but no transfer information is being logged to the database

The database tables used by the Managed File Transfer logger require the database to have a page size of 8 KB or larger. If the page size of the database is not large enough, the tables are not created properly and you see the error SQLSTATE=42704.

If we are using the Java Platform, Enterprise Edition database logger, you might see the following message in the WebSphere Application Server system out log; if we are using the stand-alone database logger, you might see the following error in the output0.log file:

DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704
SQLERRMC=FTELOG.TRANSFER_EVENT, DRIVER=3.40.152

The SQLSTATE value of 42704 indicates that a table that the logger expected to exist, in this case FTELOG.TRANSFER_EVENT, does not exist. To fix this problem perform the following steps:

Check that the table exists and is complete. For information about the tables that the logger uses and their columns, see MFT database logger tables.
If the table does not exist or is incomplete, check the page size of the database.
If the database size is less than 8 KB, increase the page size of our database.
- If your database is on a test system or has no data in it, you can drop the tables and re-create the database with a page size greater than 8 KB.
- For information about how to increase the page size, see Migrating MFT: Increasing the log db page size for Db2 on UNIX, Linux, and Windows or Migrating the database tables on Db2 on z/OS to MQ V8.0 or later.

Parent topic: MFT general troubleshooting