Directory and Resource Administration Server appears to hang during the Incremental Cache refresh. (NETIQKB13510)

fact
Directory and Resource Administrator 6.50

symptom
Directory and Resource Administration Server appears to hang during the Incremental Cache refresh.

cause
The cause of this issue is that there were a very large number of changes in the enviroment. At one customer's site they were renaming Distribution Groups and the total number of changes since the last incremental cache refresh was over 500,000 changes.  Therefore, the incremental cache refresh was taking longer than the 30 minute schedule between ICR.  The customer stopped the service because they thought that the service was hung which made the incremental cache refresh restart again. 

fix

The issue can be resolved by going into the registry and setting the Incremental cache refresh to NEVER and starting a Full Account Cache Refresh. 

• Run Regedit on the DRA server.
• Navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Modules\Accounts\Domains.Dns\domian_nam.com
• In the right pane is a key named IncDomRef, set the value of the key to NEVER
• Generate a manual accounts cache refresh in DRA

note
DRA version 6.6 has implemented a solution for this condition.  If the incremental cache refresh will take to long (this can be configured), it will stop the ICR and schedule a Full Cache refresh to take place in the middle of the night.

Formerly known as NETIQKB13510