This issue occurs when the vCenter Server installer generates and validates the JDBC URL for the vCenter Server database. If the installer fails to connect to the database using the generated JDBC URL, the installer prompts you to specify the JDBC URL. You can also specify the JDBC URL during the vCenter Single Sign-On installation.
The short form of the JDBC URL has the format:
jdbc:oracle:thin:@//scan-name:port/servicename The long form uses the TNSNAMES compliant descriptor:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=scan-name)(PORT=1521)))(LOAD_BALANCE=ON)(CONNECT_DATA=(SERVICE_NAME=servicename)) The long form is not necessary to support load balancing with Round Robin DNS and SCAN. The long form is appropriate when using TCPS for encrypted database connections via Oracle Wallets or JKS keystores.
For more information, see
JDBC URL Formats for the vCenter Server and vCenter Single Sign-On Databases section in the
vSphere 5.1 Upgrade Guide.