VMware Cloud Community
mrikking
Contributor
Contributor

Capacity planner: all attempts to open a database, failed.

Running the capacity planner i receive the following message:

OpenDatabase: All attempts to open a database, failed. This problem may be due to high activity by the collector. Reduce the number of systems collected at the same time if this is the case.

The inventory and performance tasks have both been set for 2 simultaneous systems. Anybody else got this? (Found one thread with little assistance)

W2K3 R2 STD, did compact, runnin at gig/full, all minimums for software dubbled.

0 Kudos
6 Replies
hulbertmike
Contributor
Contributor

Anyone found an answer on this one?

0 Kudos
happyhammer
Hot Shot
Hot Shot

prob not the answer you want to hear but you could stop cap plan service, rename the aog database to .old and restart service which will create a fresh database and start again

0 Kudos
Roanry
Contributor
Contributor

Sorry posted to wrong guy. Smiley Happy

0 Kudos
Roanry
Contributor
Contributor

You have too many collections occuring on your CP collector. The best practices is no more then 250 active collections. (thats how we have it setup with zero issues)

If you are not collecting on that many servers try installing another collector on a VM in the same location where you are trying to collect perf and inventory data from.

0 Kudos
BernieK
Enthusiast
Enthusiast

May not be relevant but I got that message when I was testing - I only had 4 systems in the test environment so the number of systems wasn't the problem.

Data Manager was installed in an XP VM with 512 MB RAM, I increased the RAM to 2GB and the problem disappeared.

HTH

Bernie

0 Kudos
skayser
Enthusiast
Enthusiast

Happened to me when I installed Capacity Planner on a non-english system. Saw the syntax errors on UPDATE from KB #7046256, stopped the CP service, changed the regional settings to English (US), and ran into the error when getting back to CP. Stopped CP, deleted the .mdb in the installation directory, and everything's fine now.

0 Kudos