ETL SQL processing job is taking longer than expected to complete (NETIQKB72209)

  • 7772209
  • 13-Apr-2010
  • 08-Dec-2010


NetIQ Analysis Center 2.7
NetIQ Analysis Center 2.7.5


ETL SQL processing job is taking longer than expected to complete


This issue has been resolved in Hotfix 72012 and in NetIQ Analysis Center 2.7.5. However, the fix does not cleanup any of the duplicate objects that may have been created as a result of this defect.  If you are using NetIQ Analysis Center 2.7 you may obtain a copy of Hotfix 72012 via the following link:

The ETL SQL processing job picks objects & data based on their updated modification times recorded in the QDB.  Once the ETL has detected that an object in the QDB object table has been modified the ETL loads the updated object into the Object_M table in the data mart database for the associated data source.


During ETL processing, if an older version of the object is still in the Object_M table, it changes the IsCurrent status of the table entry to 0 and places a new entry with a status of 1.  The ETL and OLAP SQL jobs will only process the associated data for objects that have an IsCurrent status of 1.


A large volume of objects in the Object_M table with the IsCurrent=0  flag can significantly increase the processing time & degrade the performance of the ETL as it will need to parse through the outdated entries in the table.  In this case, the outdated entries can be removed using standard SQL queries provided in the steps below, and return the ETL to expected processing durations.


The ETL SQL job is processing outdated duplicate objects stored in the Object_M table of the affected data mart database. 

Additional Information

Formerly known as NETIQKB72209

Contact NetIQ Technical Support and refer to KB Article Number NETIQKB72209 to obtain the queries & assistance to execute them.