BMXAA3456E - Failed To Perform Reorder Due To Exclusive Access By User

August 16, 2016 AliceDegawa

BMXAA3456E error is displayed while trying to run reorder manually or via crontask.

 

Diagnosing the problem:

Run the following query, replacing the XXXX by the Storeroom in question:

SELECT * FROM REORDERMUTEX WHERE LOCATION='XXXX';

 

Resolving the problem:

If that query returns any row, then delete the row by running:

DELETE FROM REORDERMUTEX WHERE LOCATION='XXXX';
 
The REORDERMUTEX table is a locking mechanism to make sure no two users are running a MR, Direct Issue or Storeroom Reorder at the same time.

 

The records could be left in the REORDERMUTEX table due to an unplanned power outage or any other abnormal server termination.

 

We can have Maximo automatically clear our reorder locks.

 

This can be done by configuring the MXE.REORDER.PREVIEWTIMEOUT property using System Properties application.

 

We can configure this setting to clear locks for a specified number of minutes after one has been recorded by the database. The default for this setting is 30 minutes.

Previous Article
REVOLUCION COGNITIVA EN UNIVERSIDADES MERCOSUR (RECITIC)
REVOLUCION COGNITIVA EN UNIVERSIDADES MERCOSUR (RECITIC)

      REVOLUCION COGNITIVA   El pasado 17 y 18 de agosto, IBM participó del segundo WorkShop sobre herramie...

Next Article
Java Security Warning Continues After Applying Maximo Interim Fix

Java Security warning can continue even after applying Maximo Interim Fix containing newly signed applets a...

×

Want our latest news? Subscribe to our blog!

Last Name
First Name
Thank you!
Error - something went wrong!