After an upgrade of DB2 v9.5 to v9.7, you are seeing a very large number of messages like the following in your fmcsys.log file:
02/04/13 10:01:03 FMC12200I The completion of the program for activity
'QTogxPkAAAAAAAAAAAAAAAEAAAACNz5AAAAAAAAAAAAAAAAAAQAAAAJB' was ignored.
02/04/13 10:01:15 FMC12200I The completion of the program for activity
'QTohBNUAAAAAAAAAAAAAAAEAAAABOAoAAAAAAAAAAAAAAAAAAQAAAAFB' was ignored.
With this DB2 version, the default transactional behavior of DB2 has changed and this may impact proper processing of the Websphere MQ Workflow server.
- Sometimes these two errors show up if you have mixed levels of DB2 connect versions on Workflow client and server. They need to be running on the same DB2 version
Diagnosing the problem
If you see FMC00118E after upgrading the DB2 version, you may also need to set the following as shown in the below link for MQ Series v6 even though you are on MQ v7:
Message "FMC12200I ... Internal retry... " should be addressed by using the MQ Series environment setting AMQ_REVERSE_COMMIT_ORDER
Resolving the problem
1. Make sure that the DB2 property CUR_COMMIT is set to 'DISABLED' (default setting is 'ON'). Otherwise you may encounter 'FMC00118E Object does not exist' and the FMC12200I The completion of the program for activity'QTogW5kAAAAAAAAAAAAAAAEAAAAJNxQAAAAAAAAAAAAAAAAAAQAAAAlB'
2. MQ Series property: AMQ_REVERSE_COMMIT_ORDER (see for details; this setting is still valid for later versions of MQ Series)