Troubleshooting
Problem
When running the MASUSERSYNC crontask, the crontask runs but there are some users who are still not synced.
Diagnosing The Problem
There are a few reasons why users may not be synced as expected when running MASUSERSYNC.
MASISSUER
Only users with a NULL MASISSUER column will ever be synced by MASUSERSYNC. When troubleshooting MASUSERSYNC issues, you should always first verify these users you are attempting to sync have this column correctly defined. You can verify which users currently meet the criteria by running this SQL query on your database:
SELECT * FROM maxuser WHERE masissuer is NULL;
If you need to change this value for a specific user, this SQL query can be run:
UPDATE maxuser SET MASISSUER = NULL WHERE userid = (your user)
STATUS
Even if the MASISSUER column is correctly defined, MASUSERSYNC will still only ever sync users who currently have an ACTIVE status. INACTIVE and DELETED users will always be skipped by the synchronization. You should verify the status of the users you are trying to sync:
SELECT * FROM maxuser WHERE masissuer is NULL AND (status = 'INACTIVE' or status = 'DELETED');
RESENDUSERSSEL
When defining the parameters for the MASUSERSYNC crontask, you can choose to define an optional RESENDUSERSSEL parameter to resend specific users back to Maximo Application Suite. The format for this parameter is a WHERE clause which MASUSERSYNC will use to filter for the specific users to synchronize. If you are using this parameter or have used it in the past, you should verify the users you are trying to sync actually meet the criteria you have defined.
This parameter will update MASISSUER to NULL for any users who meet the criteria defined by the WHERE clause, causing all these users to be synchronized the next time the crontask runs. Please ensure the criteria you define specifically only captures the users you desire to sync.
Note: This value still cannot be used to send INACTIVE or DELETED users.
Further Troubleshooting
If all of the above looks to be correct and the users are still not syncing, there may be errors occurring during the crontask execution. You should investigate both the Manage log files as well as the Maximo Application Suite log files to confirm.
The Manage pod log files you should investigate are the {instance_name}-{workspace_name}-cron pod (if you have defined a separate crontask bundle), or the default {instance_name}-{workspace_name}-all pod.
The Maximo Application Suite log file you should investigate is the {instance_name}-internalapi pod.
If you need assistance understanding any error messages you discover, feel free to open a case with IBM Support.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m0z0000001iYjAAI","label":"Crontask"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
10 June 2024
UID
ibm17114817