APAR status
Closed as program error.
Error description
Problem Title ============= VMMSYNC throws BMXAA4129E when syncing existing phone records Problem details: ================= When VMM Sync runs, it fails to sync the HOME or MOBILE phone number for users who do not have a work number. System is trying to insert new phone number with type MOBILE, which of course is not possible, but instead it should updating the existing phone record for the user. Error: The Virtual Machine Manager (VMM) user synchronization failed. BMXAA6782E - The Virtual Member Manager (VMM) user data failed to synchronize with the database. See the associated message. userid = YYYY.ZZZZZ BMXAA4129E - The record for Person=YYYY.ZZZZZ, Phone=+XXXXX, Type=MOBILE already exists. This validation error is thrown when an attempt is made to insert a new record with a unique key value that already exists in the database. Ensure that the key value for the given record is unique. Error count = 117 STEPS TO REPRODUCE: ===================== 1. Configure VMM sync to include a PHONE record (see the usermapping.xml). 2. Set SQL logging to INFO. 3. Perform a sync and verify that the statement 'select * from phone where personid='<PERSONID>'' appears. CURRENT ERRONEOUS RESULT =============================== VMMsync tries to insert duplicate phone record and fails to sync EXPECTED RESULT: ========================== Before syncing, VMMsync should validate if record is existing or not ENVIRONMENT (SYSTEM INFO): ======================== Tivoli's process automation engine 7.6.0.9-IFIX20181005-1042 Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-05
Local fix
It needs the same fix from APAR IJ04097 ported over to /applications/maximo/businessobjects/src/psdi/security/vmm/Defau ltVMMSyncAdapter.java, to reset the email and phone mbosets.
Problem summary
**************************************************************** * USERS AFFECTED: * * LDAP VMMSync users. * **************************************************************** * PROBLEM DESCRIPTION: * * In environments using LDAP VMMSync, error messages may * * appear in the logs about duplicate phone or email records. * * For example, * * BMXAA6782E - The Virtual Member Manager (VMM) user data * * failed to synchronize with the database. See the associated * * message. * * BMXAA4129E - The record for Person=YYYY.ZZZZZ, Phone=+XXXXX, * * Type=MOBILE already exists. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The fix for this APAR is included in the following package: | Release 7.6.1.1. of Base Services.
Temporary fix
Comments
APAR Information
APAR number
IJ10577
Reported component name
WORK ORDERS
Reported component ID
5724R46WO
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-22
Closed date
2018-10-25
Last modified date
2018-10-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WORK ORDERS
Fixed component ID
5724R46WO
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPPU","label":"Work Order Tracking"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
25 October 2018