When trying to start a WebSphere Application Server Messaging Engine, it fails to start and in the SystemOut.log you see this error: CWSIS1535E: The messaging engine's unique id does not match that found in the data store.
The symptoms of this problem are that the WebSphere Application Server Messaging Engine will not start and the following messages appear in SystemOut.log:
CWSIS1538I: The messaging engine, ME_UUID=ME2_UUID, INC_UUID=INC1, is attempting to obtain an exclusive lock on the data store.
CWSIS1545I: A single previous owner was found in the messaging engine's data store, ME_UUID=ME1_UUID, INC_UUID=INC1
CWSIS1535E: The messaging engine's unique id does not match that found in the data store. ME_UUID=ME2_UUID,ME_UUID(DB)=ME1_UUID
This problem occurs when the messaging engine detects it does not have exclusive ownership of the data store because the identifiers in the SIBOWNER table do not match those of the messaging engine. Messaging engine ME2 is trying to take exclusive locks on tables that are owned by ME1. This will never succeed.
Diagnosing The Problem
The most likely causes for this problem are failing to clean up the data from a deleted messaging engine or incorrect configuration. One of these conditions is likely occurring:
1) A new messaging engine (ME2) is attempting to use the same tables as a previously deleted messaging engine (ME1), without the data for ME1 being deleted.
2) ME2 is attempting to use the same schema name as ME1 in the same database.
3) ME2 is mistakenly using the data source defined for ME1.
Resolving The Problem
Ensure that data source references the correct database instance and that schemas being used by each messaging engine are unique.
In WebSphere Application Server make sure that you have dropped data store tables after deleting a messaging engine.
WebSphere Application Server WAS SIB SIBUS SI BUS
15 June 2018