Maximo Open Forum

Hi,

I am trying to create a new appender to log the automation script messages in a separate log file. The system is giving me the record is in use error - 'BMXAA8229W - Record MAXPROPVALUE : Property Name=mxe.logging.rootfolder Server=COMMON Server Host= has been updated by another user.' 

Is there a way to figure out the user name who is updating the record and how to resolve it? I have been receiving the same error for the last couple of days and I am the only person with admin access to our system so not sure why I am getting this error.
#EverythingMaximo

------------------------------
Devendra Verma
SenecaGlobal
------------------------------

The way Maximo works is it tries to execute the update statement using a where clause made up of the primary key from Maxattribute + rowstamp.  And, rowstamp is changed via trigger on each update.  So, the issue occurs when any of that changes between record retrieval and record update causing 0 records to be modified.  This can sometime be caused by the same process stepping on itself.  I suggest starting by turning on SQL logging and searching the log for the update statement that is "failing".  See if there was an earlier statement to do the same and troubleshoot a bit from there.  If you cannot resolve, I suggest opening a Salesforce Case to have this looked into further.

------------------------------
Steven Hauptman
IBM
------------------------------

Hi,

I am with Steven. Please perform the below steps.
1. Turn the SQL logger to INFO in logging application (if you have access to do that). 
2. Reproduce the issue.
3. Open the logs(Maximo logs, sysout, syserr) and search with "BMXAA8229W - Record MAXPROPVALUE".
4. If the error message is found in logs, please go through the previous stack trace of the same log.
5. You will get two SQL update statement trying to update the same maxprop record. 
6. Assume one update is by your action, then you need to troubleshoot from where the other update is coming.
7. Once you get the culprit/process which causes the other update statement, you need to check whether you can suppress it.
8. Once you suppress it, the error won't come.

This is the way to track and fix the all record refetch (mxrowstampupdate) issue in Maximo. Although you may need to turn on the loggers based on the occurrence of the record refetch error.


------------------------------
Subhransu Sekhar Sahoo
Tata Consultancy Services
------------------------------

Thanks for the suggestions!
I was checking the sysout and syserr logs but the sysout log was huge to pinpoint the exact statements causing the error. I didn't think of logging the SQL statements earlier. I will try out this option and see if it gives any clue.

------------------------------
Devendra Verma
SenecaGlobal
------------------------------

Original Message:
Sent: 03-30-2022 02:13
From: Subhransu Sekhar Sahoo
Subject: Unable to create new appender in the logging application

Hi,

I am with Steven. Please perform the below steps.
1. Turn the SQL logger to INFO in logging application (if you have access to do that). 
2. Reproduce the issue.
3. Open the logs(Maximo logs, sysout, syserr) and search with "BMXAA8229W - Record MAXPROPVALUE".
4. If the error message is found in logs, please go through the previous stack trace of the same log.
5. You will get two SQL update statement trying to update the same maxprop record. 
6. Assume one update is by your action, then you need to troubleshoot from where the other update is coming.
7. Once you get the culprit/process which causes the other update statement, you need to check whether you can suppress it.
8. Once you suppress it, the error won't come.

This is the way to track and fix the all record refetch (mxrowstampupdate) issue in Maximo. Although you may need to turn on the loggers based on the occurrence of the record refetch error.


------------------------------
Subhransu Sekhar Sahoo
Tata Consultancy Services
------------------------------

If the log is big and/or logging needs to be set, consider thread logging.  Go to the Logging app.  Find the action for custom logging.  On the second tab set up a row to log UI transactions for the user you are using.  You can enable SQL logging from there.  After reproducing the issue you can view the log in line via the view session log action in the Logging app or you can find the file in the same folder as the rest of the logs.  Be sure to disable or delete the row when you are done.#

------------------------------
Steven Hauptman
IBM
------------------------------

Original Message:
Sent: 03-31-2022 00:00
From: Devendra Verma
Subject: Unable to create new appender in the logging application

Thanks for the suggestions!
I was checking the sysout and syserr logs but the sysout log was huge to pinpoint the exact statements causing the error. I didn't think of logging the SQL statements earlier. I will try out this option and see if it gives any clue.

------------------------------
Devendra Verma
SenecaGlobal
------------------------------


Original Message:
Sent: 03-30-2022 02:13
From: Subhransu Sekhar Sahoo
Subject: Unable to create new appender in the logging application

Hi,

I am with Steven. Please perform the below steps.
1. Turn the SQL logger to INFO in logging application (if you have access to do that). 
2. Reproduce the issue.
3. Open the logs(Maximo logs, sysout, syserr) and search with "BMXAA8229W - Record MAXPROPVALUE".
4. If the error message is found in logs, please go through the previous stack trace of the same log.
5. You will get two SQL update statement trying to update the same maxprop record. 
6. Assume one update is by your action, then you need to troubleshoot from where the other update is coming.
7. Once you get the culprit/process which causes the other update statement, you need to check whether you can suppress it.
8. Once you suppress it, the error won't come.

This is the way to track and fix the all record refetch (mxrowstampupdate) issue in Maximo. Although you may need to turn on the loggers based on the occurrence of the record refetch error.


------------------------------
Subhransu Sekhar Sahoo
Tata Consultancy Services

Hi! I have seen a similar issue show up if the logging root folder is mismanaged. If this seems appropriate, you could change the root logging folder to something benign (like c:\smp\maxlog). Note that the application will build a folder structure off of the path you provide...

------------------------------
keith simmons
Aquitas Solutions
------------------------------

I think Keith is spot on. If there's a discrepancy even with the case of the system property mxe.logging.rootfolder and what we think it should be you'll get the updated by another user error. In the logging application, try to set the logging root folder via the "Set Logging Root Folder" action to something like C:\Logging (just make sure you can write to that directory). What happens is we then append on \maximo\logs to that directory (so it should become C:\Logging\maximo\logs after you close the dialog and open it again). Then from there you shouldn't get the issue anymore.

------------------------------
Steven Shull
IBM
------------------------------

Original Message:
Sent: 03-31-2022 01:36
From: keith simmons
Subject: Unable to create new appender in the logging application

Hi! I have seen a similar issue show up if the logging root folder is mismanaged. If this seems appropriate, you could change the root logging folder to something benign (like c:\smp\maxlog). Note that the application will build a folder structure off of the path you provide...

------------------------------
keith simmons
Aquitas Solutions
------------------------------