Troubleshooting Cloudera ETL

This topic describes the steps to troubleshoot the Moviri Integrator for Helix Capacity Optimization -  Cloudera ETL.

To collect ETL logs at log level 10

To add detailed activity logs to the log file:

  1. In the BMC Helix Capacity Optimization console, navigate to Administration > ETL & system tasks > ETL tasks and select the configured Cloudera ETL.
  2. In the Run configurations section, click .
  3. Make a note of the current value of the Log level setting. 
  4. Change the log level to 10 - Verbose and save the run configuration.
  5. After you run the ETL and the logs are collected, set the log level back to the previous value to avoid filesystem space issues.

To determine the Cloudera ETL package version

  1. In the BMC Helix Capacity Optimization console, navigate to the Administration > System > Maintenance.
  2. In the Additional Packages tab, search for the Cloudera ETL and make a note of the Execution dateComponent versionInstalled version, and Status.
    This information will help you in troubleshooting issues with Cloudera ETL.

Resolutions for common issues


The Cloudera ETL is not collecting data. The following message is reported in the Cloudera ETL log for each entity in the environment:

[2017-09-07 00:00:22] INFO Cloudera Extractor: Extracting HOST_PERF data for host
[2017-09-07 00:00:22] INFO Cloudera Extractor: Extracting data for [] since YYYYMM-
[2017-09-07 00:00:22] INFO Cloudera Extractor: empty time period, skipping query.

The Default Last Counter value is not correctly set in the ETL configuration

The setting might have a value of "YYYY-MM-DD HH24:MI:SS Z" when it should be set to an actual timestamp value, such as "2017-09-11 00:00:00".

The Cloudera ETL fails with BCO_ETL_ERR011 error or an error similar to the following:

[2019-11-20 10:08:58] INFO [SQLite Wrapper] Database file /opt/cpit/BCO/etl/temp/237-data/TO1LWWJ1.db
correctly deleted
[2019-11-20 10:08:58] WARNING [SQLite Wrapper] Database file delete failed since there is no such file or directory

This is a known issue with Cloudera ETL.Deploy the latest version of the Cloudera ETL from the Products Download section of the BMC Support portal.

Was this page helpful? Yes No Submitting... Thank you