Environment
Directory & Resource Administrator 7.x
Directory & Resource Administrator 8.x
Directory & Resource Administrator 8.x
Situation
What triggers the creation of a new service log file (nq1) in DRA?
When are new log files created in DRA?
What instigates the creation of a new log file for DRA?
How do I change the size of the service log in DRA?
How do I increase the default size of the service log in DRA?
When are new log files created in DRA?
What instigates the creation of a new log file for DRA?
How do I change the size of the service log in DRA?
How do I increase the default size of the service log in DRA?
Resolution
In DRA versions 8.5 SP1 and prior, a new service log is created each time the NetIQ Administration service is started/restarted. In DRA 8.6 and later, a new log is created when the default maximum size for the log file is reached. This setting can be changed by increasing the value for the 'MaxMegabites' registry keys located in the following locations:
- For DRA service: HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Logging\Service
- For Core service: HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Logging\Core Service
- For DOM files: HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Administration\Logging\DomFiles
To increase the size of the service log, change the decimal value of the registry key, then restart the NetIQ Administration Service.
Note: The default value for the MaxMegabites key is 25 MB.
Additional Information
Formerly known as NETIQKB72871
This change in behavior was implemented to address a problem with circular logging that DRA uses. In large environments when the number of items DRA logs exceeded the default log size, a new log was not being generated until a service restart, thus overwriting previous logged information.
This change in behavior was implemented to address a problem with circular logging that DRA uses. In large environments when the number of items DRA logs exceeded the default log size, a new log was not being generated until a service restart, thus overwriting previous logged information.