Removing the Configuration Manager database tables after migration

This topic describes one of the tasks that you might want to complete after migration.

Before you start

Before you start this task, make sure that the migration was successful and that 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 contain development data that the Configuration Manager no longer requires after migration. When you are sure that the migration has been successful, delete the data by performing this task.

To clean up the Configuration Manager DB2 database tables, drop the following database tables by using the DB2 DROP TABLE command. If the Configuration Manager tables are in a DB2 database by themselves, drop the whole database by using the DB2 DROP DATABASE command.
  • CBROKER
  • CBROKERCEG
  • CCOLLECTIVE
  • CCOLLECTIVECBROKER
  • CDELETE
  • CEG
  • CEGCMSGFLOW
  • CEGCMSGPROJECT
  • CLOG
  • CMSGFLOW
  • CMSGPROJECT
  • CNEIGHBOURS
  • COUTSTANDING
  • CSUBSCRIBE
  • CTOPIC
  • CTOPICCTOPIC
  • CTOPOLOGY
  • CTRACE
  • CUUIDLOCKS
Related concepts
Configuration Manager
Related tasks
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Message Broker Version 6.0
Migrating from WebSphere MQ Integrator Version 2.1 to WebSphere Message Broker Version 6.0
Related reference
mqsimigratecomponents command