This is a known issue with vRealize Business for Cloud.
To resolve this issue:
- Set the time zone back to UTC.
- Clean up the Postgres DB.
To set the time zone back to UTC:
- Enter the command line interface of vRealize Business.
- Run these commands:
- monit stop all
- /opt/vmware/share/vami/vami_set_timezone_cmd UTC
- monit start all
To clean up the Postgres DB:
Note: Before cleaning up the Postgres DB, VMware recommends to take a backup of the Prostgres DB, or snapshot, or both. Run this script from the command linke of vRealize Business to take a backup of the Postgres DB:
/usr/ITFM-Cloud/va-tools/bin/create_dump.sh.
- Enter the command line interface of vRealize Business.
- Run these commands:
monit stop all
monit start postgres
/usr/ITFM-Cloud/va-tools/bin/db-client.sh
select * from itfm_sync_job_run_status order by jr_id desc limit 10;
Note: This shows the top ten for itfm_sync_job_run_status. Make a note of the jr_id from the sixth entry down.
delete from itfm_sync_job_run_status where jr_id < Enter the jr_id of the sixth entry;
\q
monit start all
vRealize Business for Cloud now run cost calculations appropriately without attempting to do the total at once. If there is still an issue the following commands must be done to the MongoDB on the vRealize Business for Cloud Appliance:
-
monit stop itbm-server
-
mongo
-
use fr_stable_system
-
db.uptime.updateMany({value: {$lt:0}}, {$set:{value:0}})
-
use fr_system
-
db.uptime.updateMany({value: {$lt:0}}, {$set:{value:0}})
-
Ctrl+c
-
monit start itbm-server
Then re-attempt Cost Calculation.