What is the behavior of Directory and Resource Administrator (DRA) Server during initialization if s (NETIQKB42314)

goal
What is the behavior of Directory and Resource Administrator (DRA) Server during initialization if set to only use 'Full Account' Cache Refreshes instead of 'Incremental' Cache Refreshes?

fact
Directory and Resource Administrator 6.50

fact
Directory and Resource Administrator 6.60

fact
Directory and Resource Administrator 7.x

fix

If a domain is set to use Full Account Cache Refresh (this includes any trusted domains), the initialization will wait until the Full Account Cache Refresh is complete before fully initializing.  The result is initialization can take a considerable amount of time to complete. 

There are two workarounds:

1. Set Directory and Resource Administrator (DRA) to use Incremental Cache Refresh (ICR) for the trusted domains.   The behavior of the DRA server when using Incremental Cache Refresh is such that the Server loads the previous domfile into memory and continues with the initializaiton.  On completion of the initialization, the server schedules an ICR to run.  The initialization of the server does not wait in the case of an ICR.
2. If using an ICR is not available and you have to restart the DRA Server Service, you could perform the following to get the DRA back on line faster:
   1. Stop the NetIQ Administration Server Service.
   2. Open Regedit on the DRA server.
   3. Go to  HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Modules\Accounts\Domains.Dns (or Domain.flat if NT 4 domain).
   4. Go to each trusted domain that is running the Full Account Cache Refresh and change the Omit flag to "1".
   5. Start the NetIQ Administration Server Service (The omit will tell DRA to not enumerate those domains during start up).
   6. As soon as the DRA server restarts, go into the Delegation and Configuration Console and un-ignore each of the domains in question. 

 

Formerly known as NETIQKB42314