Troubleshooting VMware vCenter ETLs

This topic provides information to help you investigate and troubleshoot issues in the VMware vCenter and ESX Server History ETLs.

Issue symptoms

The ETLs fail to run and error messages are logged in the ETL logs.

Resolutions for common issues

Symptom	Action	Reference
The log contains the following error: BCO_ETL_FAIL103: Cannot connect to vCenter. Contacting vCenter	This error occurs when the incorrect URL details are provided in the vCenter ETL configuration under VMware server SDK URL. Make sure that the vCenter URL is https://<YourVecnterServerName>/sdk.	KA 000264459 (Support logon ID is required)
The vCenter History ETL fails with the following error: "This operation is restricted by the administrator - 'vpxd.stats.maxQueryMetrics'	In vCenter version 5.5 build 3 and 6.x, some vSphere APIs limit the number of metrics extracted during each API call. Note the following: For daily data collection, make sure to use the vCenter Service ETL. For historical data recovery, ignore the 'vpxd.stats.maxQueryMetrics' message and the failed ETL status.	KA 000224393 (Support logon ID is required)
The following error occurs: "BCO_ETL_WARN301: Service ## has detected a problem in data extraction. Please verify service status."	This issue occurs due to extraction thread timeout. It happens when there is a performance issue to load data in TrueSight Capacity Optimization.To resolve this issue, restart the cpit services on the Scheduler Server or apply the new hotfix in your environment.	KA 000235322 (Support logon ID is required)
The ETL fails to run and the ETL log displays the following message: BCO_ETL_ERR011: Detected an abnormal ETL termination. eason: com.sun.xml.ws.client.ClientTransport Exception: HTTP transport error: javax.net.ssl.SSLHandshakeException: The server selected protocol version TLS10 is not accepted by client preferences TLS13, TLS12]at com.sun.xml.ws.transport.http.client. HttpClientTransport.getOutput (HttpClientTransport.java:102) at com.sun.xml.ws.transport.http.client. HttpTransportPipe. process (HttpTransportPipe.java:193) at com.sun.xml.ws.transport.http.client. HttpTransportPipe. processRequest (HttpTransportPipe.java:115) at com.sun.xml.ws.transport.Deferred TransportPipe. processReques t(DeferredTransportPipe.java:109) at com.sun.xml.ws.api.pipe.Fiber.__doRun (Fiber.java:1106) at com.sun.xml.ws.api.pipe.Fiber._doRun (Fiber.java:1020) at com.sun.xml.ws.api.pipe.Fiber.doRun (Fiber.java:989)	The ETL is using 1.0 version of TLS to connect to the vCenter Server. The VMware - vCenter and ESX Server History ETLs use TLS version 1.1 or 1.2 to connect to the vCenter Server. Hence, Update the vCenter server protocol to TLS 1.1 or 1.2.	VMware documentation (Support logon ID is required)

Frequently asked questions

How to use the blacklist and whitelist import filter in the ETL?

The option to setup the whitelist and blacklist filter is available in the Import filter section of the Advanced properties configuration. This setting accepts a whitelist text file or a blacklist text file. The whitelist file supports regular expression, and the blacklist file only accepts a list of virtual machine names and vCenter UUIDs. F

For details, see VMware-vCenter-ETLs.

How to stop the vCenter ETL execution forcefully from the database

Do the following:

Login to database (BCO_OWN) via the sqlplus or psql command. For details, see KA 000386376 (Support logon ID is required).
Gather the vCenter ETL Task ID as shown:
Run the following query to confirm whether the ETL status is incorrectly shown as running.
select * from task_status where taskid=<TASK_ID>;
Stop the scheduler on the ETL engine.
./cpit stop scheduler
Correct the ETL status and unschedule it using this query:
update task_status set status='STOPPED' where taskid=<TASK_ID>;
update task set enabled=0 where taskid=<TASK_ID>;
commit;
Do a clean restart of the scheduler on the ETL engine and verify whether you can start or stop the vCenter ETL.
./cpit clean scheduler

How to use the VMware - vCenter and ESX Server History Extractor to recover historical data and consolidate it with the data collected by the VMware - vCenter Extractor Service?

Configure the VMware - vCenter and ESX Server History Extractor to recover historical data and consolidate it with the data collected by the VMware - vCenter Extractor Service ETL by performing these steps:

Login to TrueSight Capacity Optimization console.
Navigate to Administrator > ETL & System Tasks > VMware - vCenter and ESX Server History Extractor.
Click Edit Configuration and then click Advanced.
Under Entity Catalog, select Sharing Status > Shared Entity Catalog > Sharing with Entity Catalog > Default Entity Catalog.

Under Existing domain, select the domain of the current vCenter Service Extractor.
To resolve the conflict, select ETL migration.
Select the hierarchy rule for vCenter Service Extractor.
Under VMware ETL configuration, set the extraction period. (Select a short period such as 5 days.)
Save the changes and run the ETL.

For more information, see KA 000210677 (Support logon ID is required).

How to collect the ETL logs at log level 10?

To add detailed activity logs to the log file:

In TrueSight Capacity Optimization console, navigate to Administration > ETL & system tasks > ETL tasks and select the configured VMware vCenter ETLs.
In the Run configurations section click to modify the ETL task.
From the Edit run configuration page, click Advanced.
Note down the current value of the Log level.
Change the value to 10 - Verbose.
Save the changes and run the ETL.
After you run the ETL and the logs are collected, set the log level back to the earlier value to avoid filesystem space issues.