Fix Migration Manager skipping Maximo object changes
Resolve a legacy Migration Manager name collision where a publish channel interface table has the same name as a Maximo object.
Series · Page 3 of 6
Maximo problems with a confirmed solution.
45 articles
Resolve a legacy Migration Manager name collision where a publish channel interface table has the same name as a Maximo object.
Audit DB2 Person Group membership data, generate deterministic sequence repairs, and identify groups with missing or duplicate defaults.
Use a Maximo bind variable to evaluate the current MBO attribute instead of making the database evaluate an unbound conditional expression.
Resolve BMXAA7387E with filtering, batching or a narrowly scoped Maximo fetch limit without exposing the whole JVM to unbounded MBO sets.
Find Maximo tables in reorg-pending state and clear DB2 SQLCODE -668, reason code 7 with a reviewed classic table reorganization.
Enable inactive-site access for the administrator who must finish configuring and activating a new Maximo organization.
Raise the supporting GLCOMPONENT and CHARTOFACCOUNTS attribute lengths before configuring a longer Maximo GL account component.
Find invalid Oracle domain indexes after a Maximo database restore and recover them according to their LOADING, FAILED or UNUSABLE state.