CA DataMinder Tuesday Tip: Event Import best practice

Discussion created by devan05 Employee on Jan 29, 2013
Latest reply on Feb 6, 2013 by Chris_Hackett
Event Import best pratcice Published by Andrew Devine on 29 January 2012

CA (DLP) DataMinder can run an import process either as a named import service or via the command line. When an Import process is executed, it creates an associated, perfmon counter instance.

Specifically, when wgnimp is executed from a command line as an unnamed instance, it creates a new set of associated perfmon counters, however on occassion the perfmon counters may fail to clear down correctly and release memory when wgnimp terminates.

In an isolated instance this is unlikely to cause any significant problems, however where multiple starts/restarts are executed (for example, where batch files are used to start/restart multiple continuous import jobs) that results in these orphaned perfmon instances the wgnimp import service may fail to start.

To avoid this situation you should create a named instance of wgnimp. Naming the wgnimpsv service ensures that a single named instance of perfmon counter is created and re-used, so the problem is avoided.

For example; start wgnimp with the syntax

wgnimp -i <instancename> -f <import initialisation file>

For more information on this topic please refer to the CA (DLP) DataMinder r14.1 Archive Integration Guide (DLP_Archive_Int_ENU.pdf) which is available to download from the CA DataMinder 14.1 Bookshelf.