Shawn,
When you restore a backup of your Prod DB to a lower enviornment (Dev, Test, Train, etc) you still need to run scripts like you did in the past to update key Maximo Properties and modify user emails and the like. The key to restoring though is likely what you found is the CRYPTO and CRYPTOX keys between your MAS environments don't match. You have 2 choices:
- from the MAXINST Pod from your lower environment after you do a restore, open the terminal tab (if you have access) and run ./resetcryptocryptox.sh followed by ./validatecryptokey.sh then I find it best to restart the MAXINST pod and it will run through an updatedb and make sure the DB you restored is aligned to the version installed on the server your restored to as well as update key system properties like mxe.db.url, mxe.db.user, mxe.db.password, etc. https://www.ibm.com/docs/en/masv-and-l/cd?topic=encryption-resetting-crypto-cryptox-fields-in-database
- Make the CRYPTOX and CRYPTO keys the same in all Environments (Make Dev the same as Prod)
There are some other considerations you also need to think of such as User access in the lower enviornments and Mongo, but focus on getting the DB restored to the lower environment (Dev)
------------------------------
Michael Marsonet
MRM-EAM Consulting Inc.
------------------------------
Original Message:
Sent: 05-29-2025 11:01
From: Karla Foster
Subject: Database refreshes of DEV environment in Maximo Manage 9
Shawn,
We might be having a similar issue in our hosted environments. We had been able to have IBM refresh our Dev environment from Prod in MAS 8, albeit with bumps in the road. Last Thursday, IBM completed the backflow of MAS 9 PROD to MAS 9 Dev at our request. Our last step in ensuring that the remnants of Prod had been removed, was to sync the MAXADMIN account from LDAP back to Manage so that its primary email was a Dev listener email rather than a Prod one. This is where we failed (synchronization error) and have been stuck ever since. The last comment from IBM is that they are concerned about a corrupt API key.
------------------------------
Karla Foster
PotlatchDeltic
Original Message:
Sent: 05-28-2025 08:53
From: Shawn Miller
Subject: Database refreshes of DEV environment in Maximo Manage 9
Has anyone worked out how to refresh Maximo 9 Dev data with Production data? We have historically (in 7.6 and older versions) done database refreshes from PROD backups into DEV and ran a handful of SQL updates afterwards, but this process is not working in MAS 9. We get the following Error 400: No user id found for the apikey xxx when trying to start the pods via api call to https:/dev.*************.com/toolsapi/toolservice/managestart after the database refresh. I am using a valid api key fron the PROD source environment, and I have verified there is a record for the user I am restoring as in table apikeytoken after the restore. This same user does exist in the DEV mongo database with the same password. Is there some orphan issue or ID mismatch to the mongo user maybe?
#Administration
#Infrastructure
#MaximoApplicationSuite
------------------------------
Shawn Miller
Mount Pleasant Waterworks
------------------------------