Troubleshooting the VMware vCenter ETLs

The VMware vCenter ETLs might fail due to incorrect configurations and other issues. Review the ETL logs to investigate and troubleshoot these issues.

Related topics

VMware-vCenter-Extractor-Service
VMware-vCenter-and-ESX-Server-History-Extractor

Collecting-ETL-logs-at-log-level-10

Resolutions for common issues

The following table explains the common issues for the ETL failures and their resolutions.

Symptom

Cause

Resolution

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.

Make sure that the vCenter URL is https://<YourVecnterServerName>/sdk.

For more information, see Knowledge article 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 5.5 Update 3 and 6.x, some vSphere APIs limit the number of metrics extracted during each API call.

  • 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.

For more information, see  KA 000224393

(Support logon ID is required).

The ETL fails to run and the log displays the following message:

BCO_ETL_ERR011: Detected an abnormal ETL termination.

Reason: 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 version 1.0 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. Therefore, update the vCenter server protocol to TLS 1.1 or 1.2. For more information, see  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 a regular expression, and the blacklist file accepts only a list of virtual machine names and vCenter UUIDs. For more information, see VMware-vCenter-ETLs.

How to stop the vCenter ETL run forcefully from the database?

Do the following steps:

  1. Log in to database (BCO_OWN) using the SQL PLUS or psql command. For details, see Knowledge article 000386376 (Support logon ID is required).

  2. Note the vCenter ETL task ID.

    Task ID 1.jpg

  3. Run the following query to confirm that the ETL status is shown as running.
    select * from task_status where taskid=<TASK_ID>;
  4. Stop the scheduler on the ETL engine.
    ./cpit stop scheduler
  5. Update 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;
  6. Perform a clean restart of the scheduler on the ETL engine, and confirm that 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?

Do the following steps:

  1. Navigate to Administration> ETL & System Tasks > VMware - vCenter and ESX Server History Extractor.
  2. Click Edit Configuration and then click Advanced.

    History ETL1.jpg

  3. Click Entity catalog, and then select Sharing with Entity Catalog > Default Entity Catalog.

    Entity Catalog 1.jpg

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

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