IJ29181: VMMSYNC SPURIOUS ERRORS BMXAA6695E BMXAA4129E

APAR status

• Closed as program error.

Error description

• VMMSync Cron Task generates a large number of spurious errors
  when data are correct in VMM and in Maximo
  
  Example: [11/7/20
  11:13:20:698 EST] 000009b7 SystemOut O 07 Nov 2020 11:13:20:698
  [ERROR] [CNNCRON01] [CID-CRON-31282] BMXAA6695E - The MBO could
  not be batch validated for object PHONE. The error is TYPE.
  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=ADAMSJQ,
  Phone=1-202-555-1222, Type=MOBILE already exists. Ensure that
  the key value for the given record is unique.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * VMMSYNC SPURIOUS ERRORS BMXAA6695E BMXAA4129E                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  	 release\fix pack for Release 7.6.1.3 Product
  

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