Cleaning up the Configuration Manager database tables after migration

Before you start

Before you start this task, make sure that the migration was successful and you no longer need to retain the flexibility to restore the Version 2.1 level of code.

If you preserve the assignments, topology, and topics data in the configuration repository during a migration from WebSphere MQ Integrator Broker Version 2.1 or WebSphere MQ Integrator Version 2.1 and do not delete the Configuration Manager, the Configuration Manager database tables after migration contain development data that the Configuration Manager no longer requires. When you are sure that the migration has been successful, you can delete the data by performing this task.

Do the following on the system where the Configuration Manager is running:
  1. Issue the mqsimigratetables command for the component ConfigMgr using the -d parameter. For information about how to use this command, see mqsimigratetables command.
  2. Delete the message repository.
    The tables that constitute the message repository are listed in the following books:
    • WebSphere MQ Integrator Broker Version 2.1 Administration Guide
    • WebSphere MQ Integrator Version 2.1 Administration Guide

    If the message repository tables are in a DB2 database by themselves, you can drop the whole database by using the DB2 DROP DATABASE command. Otherwise, you must drop each message repository table by using the SQL DROP TABLE command.

Related concepts
Configuration Manager

Related tasks
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Migrating from WebSphere MQ Integrator Version 2.1 to WebSphere Business Integration Message Broker Version 5.0

Related reference
mqsimigratetables command