RS03736: LDAP SYNCHRONIZATION IS SOMETIMES BLOCKED AFTER A RESTART

Operational Decision Manager V8.10.5.0: Interim Fix 12 for Decision Center
IBM Operational Decision Manager V8.10.5.1 Fix Pack
Operational Decision Manager V8.10.5.0: Interim Fix 3 for Decision Center
Operational Decision Manager V8.10.5.0: Interim Fix 4 for Decision Center
IBM Operational Decision Manager for z/OS 8.10.5.1 Fix Pack

APAR status

• Closed as program error.

Error description

• After a restart, the LDAP synchronization
  is blocked with an exception: " The specified element of type
  'brm.Lock' was not found".
  
  Exceptions thrown on launching the
  ldap sync:
  { "error": "RuntimeException", "reason":
  "ilog.rules.teamserver.model.IlrObjectNotFoundException: The
  specified element of type 'brm.Lock' was not found", "status":
  "NOT_FOUND", "ref": null, "errorCode": null, "details": [
  "ilog.rules.teamserver.model.IlrObjectNotFoundException: The
  specified element of type 'brm.Lock' was not found", "The
  specified element of type 'brm.Lock' was not found" ]}
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users defined in an LDAP                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After a B/G or a Migrated schema, the LDAP synchronization   *
  * is                                                           *
  * blocked with an exception: " The specified element of type   *
  * 'brm.Lock' was not found".                                   *
  *                                                              *
  * Exceptions thrown on launching the                           *
  * ldap sync:                                                   *
  * { "error": "RuntimeException", "reason":                     *
  * "ilog.rules.teamserver.model.IlrObjectNotFoundException: The *
  * specified element of type 'brm.Lock' was not found",         *
  * "status":                                                    *
  * "NOT_FOUND", "ref": null, "errorCode": null, "details": [    *
  * "ilog.rules.teamserver.model.IlrObjectNotFoundException: The *
  * specified element of type 'brm.Lock' was not found", "The    *
  * specified element of type 'brm.Lock' was not found" ]}       *
  *                                                              *
  *                                                              *
  * We've                                                        *
  * noticed the same error in log regularly (in production as    *
  * well)                                                        *
  * but it did not blocked the LDAP sync.                        *
  * The specified element of                                     *
  * type 'brm.Lock' was not found exception thrown in log        *
  * With                                                         *
  * 8.10.3-IF016 in DC logs we find a lot of exception like this *
  * The specified element of type 'brm.Lock' was not found       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Updated shutdown mechanism to ensure the LDAP synchronization
  lock is not left behind.
  

Temporary fix

• Manually cleanup the lock.
  

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

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R8A0 PSY

     UP