If the database logger is started, but no transfer information is being logged to the database
The database tables used by the WebSphere® MQ File Transfer Edition version 7.0.3 or later database 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 you are using the Java™ Platform,
Enterprise Edition database logger, you might see the following message
in the WebSphere Application
Server system out log; if you 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 database 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 database logger uses and their columns, see 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 your 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.
- If the database is on a production system and contains data, you must migrate the data to the 7.0.3 tables. For information about how to increase the page size and migrate your data to version 7.0.3 tables, see Increasing the page size of the log database on Db2 on Windows, UNIX or Linux or Migrating the database tables on Db2 on z/OS.