APAR status
Closed as program error.
Error description
LDAPSYNC throws BMXAA4129E when syncing existing phone records. PROBLEM: When LDAP Sync runs, it fails to sync the HOME phone number for users who do not have a work number. There were times that ldapsync skips validation from phone table before syncing a phone record. This will result to inserting a new row instead of updating the existing phone record for the user. Phone set is needed to be reset to select or validate the existing phone record. Error: BMXAA6695E - The MBO could not be batch validated for object PHONE. The error is PHONENUM. Ensure that the object exists in the maxobject table. Check the log files in the home directory to determine the cause and source of the error. . psdi.util.MXApplicationException: BMXAA4129E - The record for Person=YYYYY, Phone=XXX-XXX-XXX, Type=HOME 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. PERFORMANCE ISSUE: No STEPS TO REPRODUCE: 1) Configure LDAP 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: Ldapsync tries to insert duplicate phone record and fails to sync. EXPECTED RESULT: Ldapsync should validate if record is existing or not before syncing. ADDITIONAL INFO: ENVIRONMENT (SYSTEM INFO): App Server IBM WebSphere Application Server 8.5.5.11 Version Tivoli's process automation engine 7.6.0.8 Build 20170512-0100 DB Build V7608-63 IBM Maximo Asset Management Work Centers 7.6.0.2 Build 20170509-0906 DB Build V7602-57 IBM Maximo Enterprise Adapter for Oracle Applications 7.6.0.0-20161219-1328 Build 20150804-1717 DB Build V7600-05 HFDB Build HF7600-01 IBM TPAE Integration Framework 7.6.0.8 Build 20170510-2330 DB Build V7608-43 IBM Maximo for Utilities 7.6.0.1 Build 20170518-1923 DB Build V7601-08 IBM Maximo Transportation 7.6.2.4 Build 20170221-0604 DB Build V7624-02 IBM Maximo Spatial Asset Management 7.6.0.2 Build 20170518-1103 DB Build V7602-23 IBM Maximo Asset Management 7.6.0.8 Build 20170512-0100 DB Build V7604-01 IBM Maximo for Oil and Gas 7.6.1.0-20170516-1429 Build 20170516-1429 DB Build V7610-139 HFDB Build HF7610-14 Server OS Windows Server 2012 R2 6.3 Server DB Oracle 12.1 (Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options) LOCAL FIX: n/a
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * Users in LDAP environments. * **************************************************************** * PROBLEM DESCRIPTION: * * When LDAP sync runs, instead of fetching and validating * * against existing records in the PHONE table or EMAIL tables * * using the relationships PERSON.PHONE and * * PERSON.PRIMARYEMAIL, Maximo may instead execute an insert * * statement, resulting in an LDAP sync error due to duplicate * * records existing. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The fix for this APAR is included in the following package: | Release 7.6.1.0 of Base Services.
Temporary fix
Comments
APAR Information
APAR number
IJ04097
Reported component name
MAXIMO SYSTEMS
Reported component ID
5724R46AV
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-13
Closed date
2018-02-20
Last modified date
2018-02-20
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
MAXIMO SYSTEMS
Fixed component ID
5724R46AV
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
20 February 2018