Troubleshooting Moviri ETLs
Collect the ETL logs at log level 10
To add detailed activity logs to the log file:
- In the TrueSight Capacity Optimization console, navigate to Administration > ETL & system tasks > ETL tasks and select the configured Moviri ETL.
- In the Run configurations section, click
. - Make a note of the current value of the Log level setting.
- Change the log level to 10 - Verbose and save the run configuration.
- After you run the ETL and the collect the logs, set the log level back to the previous value to avoid filesystem space issues.
Record the Moviri ETL package version
- In the TrueSight Capacity Optimization console, navigate to the Administration > System > Maintenance.
- In the Additional Packages tab, search for the Moviri ETL and make a note of the Execution date, Component version, Installed version, and Status.
This information will help you in troubleshooting issues with Moviri ETL.
Common issues
Here are some of the common issues and the resolution to help you diagnose and resolve the issue. For further assistance, contact BMC support.
Issue | Cause | Resolution |
|---|---|---|
The following message is reported in the ETL log: BCO_TASK_FAIL005: Critical error detected during task XX execution: java.lang.OutOfMemoryError: GC overhead limit exceeded for batch ETLS | The Moviri ETL is not collecting data and the execution is interrupted because the ETL Java heap size is insufficient. | Increase the ETL Java heap size. For details, see the following topics: |
The Moviri ETL is not starting and the ETL execution is interrupted immediately. The following message is reported in the ETL log: FAILED;BCO_ETL_FAIL108: Process cannot be started (cannot fork external java/os process) or process fails due to severe errors (no modules in classpath) java.lang.ClassNotFoundException: com.moviri.etlfactory.MovDateUtil | After upgrading the machine or applying a patch, the Moviri class jar files in $CPITBASE/etl/libmodules/$MODULENAME is missing. Example: For Entuity ETL, EntuityME could be missing. | Check for the presence of at least etlFactoryLibrary-1.X.0.jar in the $CPITBASE/etl/libmodules/$MODULENAME folder. Redeploy the ETL package from the maintenance activity page or copy the content of libmodules folder from another working machine. |
Microsoft SCOM ETL fails with the following error in the ETL log: FAILED BCO_ETL_ERR011: Detected an abnormal ETL termination. Reason: java.sql.SQLException: Invalid object name 'dbo.vManagedEntity'. | The Management Pack in System Center is missing. | Enable or disable the metric classes in the ETL configuration. For details, see KA: Microsoft SCOM error with Invalid object name 'dbo.vManagedEntity'. |
The Splunk ETL fails with the following error in the ETL log: Warning: [STDERR] - java.sql.SQLRecoverableException: IO Error: Connection reset | A problem with Java when trying to connect to Oracle 11 via the standard JDBC Oracle library could be a potential problem in communicating to the database server securely. | Create a file named customenv.sh into $CPITBASE folder (i.e. /opt/bmc/BCO) of the ETL engine executing the task and insert a line like this: ETL_JAVA_OPTS="$ETL_JAVA_OPTS -Djava.security.egd=file:/dev/./urandom" export ETL_JAVA_OPTS |
The Splunk ETL fails with the following error in the ETL log: FAILED BCO_ETL_ERR011: Detected an abnormal ETL termination. Reason: java.lang.RuntimeException: Received fatal alert: protocol_version | Incorrect TLS version is selected. | Make sure that the ETL configuration was set to use TLSv1. For detailed instructions, see KA: Splunk ETL failing. |
The HP NNMi ETL fails with the following error in the ETL log: FAILED BCO_ETL_ERR011: Detected an abnormal ETL termination. Reason: jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad password. | Incorrect credentials provided or unreachable Windows share path for the ETL to connect to. | Verify and modify the credentials and permissions on the Windows share directory. |