Cloud Pak for Business Automation

Cloud Pak for Business Automation

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

Messaging engine was not starting On Production BAW New Environment 

Tue November 12, 2024 06:30 AM

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 .

Resolution
If 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 tables
SIB000 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.

Statistics
0 Favorited
4 Views
0 Files
0 Shares
0 Downloads