Getting Error In Purging A Sync Record "Searching the directory server failed - Sizelimit exceeded in LoadDBEntrySetSorted()".
(Doc ID 2140708.1)
Last updated on MARCH 08, 2017
Applies to:COREid Access - Version 10.1.4.3.0 and later
Information in this document applies to any platform.
When purging the sync record retunrs the following an error:
- Confirmed that the maxpage setting is set to 20,000.
1. Multiple questions...
a. How can I determine how many sync records on 1 day?
b. Where are the sync records in the DC?
c. Is it the Policy DC or the user DC?
d. Can I run a ldap query to purge the records instead of using the Access Console?
2. The first obSyncRequestNo has the seq number of 100000 and the last number is 291230. This means we have over 190000 sync records created due to the load test. I need to understand the sync records structure before I use a ldap command to delete the etnries ourselves. Please confirm the following:
Is it fine for me to delete all the sync records under PSCMgmt that are greater than 'user/policy cache timeout' ago using a ldapdelete command?
a. Are the sync records only in the dn obSyncRequestNo=xxxxxx,CN=PSCMgmt,obapp=PSC,OU=Oblix,OU=OAM,OU=SSH Services,DC=sshapps,DC=sshci,DC=ssh?
b. Are there other locations that have the sync records?
c. Are there any relationship of the sync records below to other AD entries? When I delete them, I need to make sure there won't be any ophan entry in the policy.
dn: obSyncRequestNo=xxxxxx,CN=PSCMgmt,obapp=PSC,OU=Oblix,OU=OAM,OU=SSH Services,DC=sshapps,DC=sshci,DC=ssh
3. Would like to know what is the impact of disabling the creation of the sync records? My support team remembers having it disabled in the past. How do we disable the creation of the sync records?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!