KB Article #68801
LOGGER_OPTIONS - how does this environment variable work?
Problem
-- What are the -R and -D options used for?
-- What information will be logged in the trace, assuming that traces have beem enabled?
-- how to use both options ?
Resolution
* When used, the -R<time> option wil inactivate active entries older than <time>.
* For example, -R3d will result in active entries older than 3 days will become inactive.
* For example, -R30m will inactivate entries older than 30 minutes.
* There are two kinds of indices in the logger.
1. The Main Index (logididx). The only one which is used to process data
2. The User Indices, all other x* and f* files are only used for the message log
* When used, the -D option is used to defines when the task will start and when the loggers will need to be reindexed. The process will run in parallel at the start of the task. Only the active entries will need to be reindexed before the logger work again so that Integrator can process new messages faster. For larger and more active users of Integrator with heavier loads, we would definitely recommend cleaning out old active log entries.
* The active entries are not made inactive when the logger is started or when the archiving is done. Instead they will be made inactive when the next active logger file is created. So in this example, when a0000004 gets created, the active logger entries in a0000002 and a0000003 will be made inactive. When this occurs, the following entries will be seen in the trace (if debug is applied)
WARNING 20090907 15.12.48.80 logger active log entries that are older than 1 minutes do exist
DEBUG 20090907 15.12.50.17 logger successfully inactivated 40 entries from active log entries file a0000000
* to set both options, use the following syntax :
LOGGER_OPTIONS=-DR7d