2.7

Table Of Contents
2 If the problem still exists, manually restart the DBVM.
a Right-click your database, and select Power > Stop.
b Wait for the DBVM stop task to finish, and the database has a Stoppedstatus.
c Right-click your database, and select Power > Start.
NOTE Power > Start will not restart the DBVM.
3 If the problems still exists, update the DBVM key or certificate manually.
4 If the problem still exists, repair the database virtual machine manually.
a Right-click your database and select Backup and Recovery > Recover Database from Last State.
A message warns that the database will not be accessible during the recovery.
b Click OK.
c Wait for the repair task to finish.
Database Cannot Be Connected Using the JDBC Connection String
When you connect to a database that uses the JDBC provided by Data Director, the connection fails.
Problem
vFabric Data Director provides a JDBC connection string for external applications to connect to its managed
databases. Under rare conditions, connecting to a database using the JDBC connecting string can fail.
Cause
Several conditions can cause the problem.
n
DB Name Server is powered off.
n
Database server is powered off.
n
Database service is stopped by management tools bypassing vFabric Data Director.
n
Database IP Whitelist is configured incorrectly.
Solution
1 Verify that the DB Name Server status in System Health is green.
If the status is not green, ask the vSphere administrator to power on the DB Name Server.
2 Open the database in vFabric Data Director and check whether there is a Power State mismatch alarm.
If a mismatch alarm exists, repair the alarm. This action will power on the database server.
3 Connect the database through IP with the management tools that you use, and check the database status.
4 Open the database Properties dialog box and examine the IP Whitelist settings for the database.
The client machine must be in the IP Whitelist of the database.
VMware vFabric Data Director Administrator and User Guide
216 VMware, Inc.