IJ15890: LDAPSYNC CRONTASK NOT POPULATING PHONE OBJECT WHEN 2 PHONE RECORDS ARE ADDED ON THE USER MAPPING XML.

APAR status

• Closed as program error.

Error description

• Problem:
  Second XML table element for PHONE is overwriting the first
  table element for PHONE. Customer's first PHONE element
  references work phone from Active Directory (telephoneNumber)
  and the second element references mobile from Active Directory
  (mobile). The Mobile phone record seems to be overwriting the
  work phone record.
  
  Performance Issue:
  No
  
  Steps to Reproduce:
  1.Delete all phone records for a user that has mobile and
  telephoneNumber filled out in Active Directory.
  2.Update the UserMapping XML parameter in the LDAPSYNC crontask
  to match what's at the end of this document.
  3.Update the paramvalue to null for highestCommittedUSN on the
  LDAPSYNCPARAMS table to do a full sync with AD. Wait for LDAP
  crontask to sync.
  4.Check phone records for the user they previously deleted phone
  records from. Only 1 phone number will appear in the PHONE table
  for that person, even though 2 should appear.
  
  Results:
  Only 1 phone number will appear in the PHONE table for that
  person, even though 2 should appear.
  LDAPSYNC crontask not populating Phone object when 2 phone
  records are added on the User Mapping XML.
  User do not see any error in the logs that indicates the phone
  number is not being updated. So it looks like it passes in the
  logs, but in reality, the only record that shows is whatever is
  listed last of the phone numbers in the xml. For example, if
  mobile phone is placed first in the xml and telephoneNumber is
  second, user will see the telephoneNumber in the PHONE table but
  not mobile. Same goes for the opposite.
  
  Expected Results:
  Two phone records should appear for individuals in the Maximo
  People application with telephoneNumber and mobile filled out in
  Active Directory. TelephoneNumber (work) should be marked as
  primary and mobile (mobile) should not.
  
  Reported in Version:
  Tivoli's process automation engine 7.6.1 IFIX004
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users in LDAP environments.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Problem:                                                     *
  * Second XML table element for PHONE is overwriting the first  *
  * table element for PHONE. Customer's first PHONE element      *
  * references work phone from Active Directory                  *
  * (telephoneNumber) and the second element references mobile   *
  * from Active Directory (mobile). The Mobile phone record      *
  * seems to be overwriting the work phone record.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is included in the following package:
                           | Release 7.6.1.2 of Base Services.
  

Temporary fix

Comments

APAR Information

• 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