Search the VMware Knowledge Base (KB)
View by Article ID

VMware vCenter Server 5.x and 6.0 does not function correctly when Windows Oracle Client, p14543814 (Patch 10), or prior to p16656151 (Patch 19) is in use (2039874)

  • 18 Ratings


  • VMware vCenter Server 5.x  and 6.0 do not function correctly when the Windows Oracle Client versions, to,,, and are present on vCenter Server or its database server.

    Note:  This issue does not occur on Oracle Client and

  • Creating a virtual machine fails.
  • When creating a new virtual machine on vCenter Server 5.x, you see the error:

    An internal error occurred in the vSphere Client.
    Details: Object reference not set to an instance of an object.

  • You cannot edit, power on, nor migrate existing virtual machines.
  • Attempting to edit, power on, or migrate existing virtual machines fails.
  • Running this query displays the same DBMS_LOB.GETLENGTH(DATA) value across multiple vmx-## for the same HOST_ID:
select host_id, config_option_ver, dbms_lob.getlength(data) from vpx_host_vm_config_option

From an affected database, you see output similar to:

SQL> select host_id, config_option_ver, dbms_lob.getlength(data) from vpx_host_vm_config_option;

     ---------- -------------------- ------------------------
             38 vmx-03               386901
             38 vmx-04               386901
             38 vmx-07               386901
             38 vmx-08               386901


This issue is resolved in Windows Oracle Client p16656151 (Patch 19) or later,, or later, or, You can download the latest version from the Oracle site.

Note: Upgrading to Oracle Client does not resolve corrupted entries that already exist. 

To resolve this issue:
  1. Verify and upgrade the Windows Oracle Client on your vCenter Server and\or the vCenter Server database server.
  2. Remove the affected host from the vCenter Server inventory. 
  3. Add the affected host back into the vCenter Server inventory.

    Note: Oracle 11g and 12c are deprecated for vCenter Server Appliance 6.0.  For more information, see VMware vSphere 6.0 Release Notes.
If the preceding steps do not resolve the issue there may be corruption in the database. To resolve this issue the vCenter Server must be reinstalled with a new or initialized vCenter Server database. For more information on initializing the vCenter Server database, see  Reinitializing the vCenter Server database (2031295).

Additional Information

For more information on verifying the interoperability of your specific product, see the VMware Product Interoperability Matrix.

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

01/24/2013 - Updated Symptoms. 05/03/2013 - Updated language and added interop matrix link 05/09/2013 - Updated with Oracle patch resolution 09/05/2013 - Added 5.5 to product list 04/02/2015 - Added VMware vCenter Server 6.0.x

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 18 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 18 Ratings