This error can occur after correcting the DB2® Universal Driver configuration and restarting the server. The error messages are repeated continuously in the adjunct region.
ExtendedMessage: BBOO0222I: [CommonEventInfrastructure_Bus:mdnodea.mdsr01a-CommonEventInfrastructur e_Bus] CWSIS1538I: The messaging engine, ME_UUID=68E9550CE7780888, INC_UUID=5f244052b02f04b4, is attempting to obtain an exclusive lock on the data store. .. .. ExtendedMessage: BBOO0222I: [CommonEventInfrastructure_Bus:mdnodea.mdsr01a-CommonEventInfrastructur e_Bus] CWSIS1546I: The messaging engine, ME_UUID=68E9550CE7780888, INC_UUID=5f244052b02f04b4, has lost an existing lock or failed to gain an initial lock on the database
These error messages indicate that there is a problem accessing the data store. Check that the fixWPSvars.jacl had created (jdbc/MEdatasource) in the datasource. Check that the datasource has an J2C authentication alias associated with it. If there is no J2C authentication alias associated with the datasource the database access defaults to the user ID of the servant region and tries to find tables called MKASRU which do not exist.
This error can occur because the -sibauth option has not been coded when running fixWPSvars.jacl. You can fix this in a number of ways:
The following steps explain how to create a new J2C authentication alias to be used by the SIBs to access DB2:
The following steps explain how to associate the Service Integration Buses with the authentication alias that you have created: