VMware VCENTER CHARGEBACK 1.5 Manual page 141

Hide thumbs Also See for VCENTER CHARGEBACK 1.5:
Table of Contents

Advertisement

Solution
1
Stop all the VMware Cloud Director Data Collector instances.
2
Modify the host and database information for the VMware Cloud Director setup in the VMware Cloud
Director tab on the Cloud Data Collectors page in vCenter Chargeback.
You must modify the following properties:
VMware Cloud Director database host
n
VMware Cloud Director database name
n
VMware Cloud Director database username
n
VMware Cloud Director database port
n
VMware Cloud Director database password
n
3
Delete all the hierarchies imported in to vCenter Chargeback from the original VMware Cloud Director
setup.
4
Run the following database commands.
delete from cb_vcloud_unprocessed_event
delete from cb_vsm_server
delete from cb_vsm_network
delete from cb_vsm_ip
delete from cb_server_property where
server_property_name='cbEventListRawView.lastProcessTime'
delete from cb_server_property where server_property_name like '%vcLastProcessTime-%'
5
Restart the VMware Cloud Director Data Collector instances.
Unable to Connect to the vCenter Chargeback Database
vCenter Chargeback can function only if it can connect to the vCenter Chargeback database.
Problem
vCenter Chargeback is unable to connect to the corresponding vCenter Chargeback database. A database
connection failed error is displayed.
Cause
This issue can occur due to multiple reasons.
The database service is not started and running.
n
The database is not reachable over the network.
n
The port number for the SQL Server named database instance has changed.
n
The number of server processes for the Oracle Database has exceeded the set maximum limit.
n
Solution
1
Check whether the database service is started and running.
2
Check whether the database machine is reachable over the network.
VMware, Inc.
Chapter 10 Troubleshooting vCenter Chargeback
141

Advertisement

Table of Contents
loading

Table of Contents