Entry cache problems after upgrade of OID clustered nodes to 220.127.116.11
Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The following notification appears in oidmon.log: [OID] [NOTIFICATION:16]  [OIDMON] [host: ldap1-test.kba.de] [pid: 15560] [tid: 6] OIDNotifyWorker: gslsgrnNotifyChanges: Invalid cache type for the notification: 17.
Userpassword changes are not replicated to other nodes.
To confirm if you are facing the issue, you might check:
1.- Try to change the values of some attributes in one node, e.g. userpassword of a user in oid
2.- Check if you get the notifications in oidlogs, OIDNotifyWorker: gslsgrnNotifyChanges: Invalid cache type for the notification: 15
3.- Run and ldapcompare or ldapsearch to check if oid1 and oid2 have the same values
Command-Line Tools for Managing Entries and Attributes (Doc ID 554236.1)
8.1.1 Examples for ldapsearch
9.1.1 Example for ldapcompare
4.- If you get different values, and you have the notifications, you might facing the issue described in Bug 14113217 - CACHE REFRESH DOES NOT REFRESH PASSWORD ON SECOND OID NODE.
The problem can appear in oid 22.214.171.124, when changing some user attributes on one node, e.g. userpassword.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms