Come for answers. Stay for best practices. All we’re missing is you.
Problem Statement: Messaging engine was not starting.Cause: Each messaging engine have its unique ID which is stored in the messaging engine tables so when we move the database to another environment and try to start the BAW from there it will show the errors related to UUID .
ResolutionIf you also want to move your IBM BAW databases, backup/restore or use the replication technique to move the database in between production and DR sites then we need to drop below SIB* tables from the cmnuser schema.
After switch over and before starting the environment drop below tablesSIB000 SIB001 SIB002 SIBCLASSMAP SIBKEYS SIBLISTING SIBOWNER SIBOWNERO SIBXACTS
This is required because we are using the existing databases, therefore we must need to drop the previous messaging engine tables before starting the new deployment environment. Once the tables are dropped start the dmgr, nodes and clusters and verify that the messaging engine is now started.