ETL Step 16 is taking longer than expected and is causing excessive transaction logging (NETIQKB72238)

  • 7772238
  • 19-Apr-2010
  • 08-Dec-2010


NetIQ Analysis Center 2.6
NetIQ Analysis Center 2.7
NetIQ Analysis Center 2.7.5


SQL ETL Job Step 16 is takes longer than expected and is causes excessive transaction logging.
ETL Step 16 taking longer than expected to complete
ETL causing transaction logs to grow excessively
ETL down for long period of time


To recover from this problem there are two options:

  1. Remove problem data source from Analysis Center.  After removing the problem data source you will loose all existing historical data in Analysis Center for that data source.  Then re-add the data source back to Analysis Center.  All available data in the QDB repository will be imported into the new data source.  The amount of historical data available is dependent upon the data retention policy configured in the AppManager repository.
  2. SQL queries can be run against the affected data source data mart database to purge the backlog of data & the ETL last load date rolled forward to the current day.


This problem is typically caused by a high volume of data that needs to be processed by the Analysis Center ETL SQL job.  This may take an inordinate amount of time to process & will generate exponentially large transaction logs that may consume all available disk space.

Additional Information

Formerly known as NETIQKB72238

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