Thanks. I guess I should've checked the version first.. we're on OVM 2.2.0 :( It seems that the .config file that people talk about does not exist.. The management console lives in a stand-alone OC4J installation. What are the chances to install a current management console and attach the old OMV pool? Cheers, Tony On 15/11/12 11:44 AM, Adam Bennis wrote: > Hey Tony - You'll find this useful > > https://forums.oracle.com/forums/thread.jspa?threadID=2451656&tstart=255 > <https://forums.oracle.com/forums/thread.jspa?threadID=2451656&tstart=255> > > I've had luck with both methods previously (ovm verson 3.0 and 3.1) > > Try the manager reinstall with the correct UUID first. > > Ads > > > On 15 November 2012 12:04, De DBA <dedba@xxxxxxxxxx > <mailto:dedba@xxxxxxxxxx>> wrote: > > G'day, > > Perhaps off-topic: We have lost our OVM management repository (and no > backup of course). There is no other option I think to recreate a new > repository and reconfigure the manager. > > The OVM pool does run a number of important VMs and we would be very sad > to have to recreate all those, so the pool should be re-registered in > the recreated repository. I've tried that in the past and ran into the > catch-22 that the management console does not want to register the pool > as it was registered to another console. That console is no longer > available and thus it is impossible to de-register the pool - if we'd > want to: perhaps it would delete all existing VMs? > > I can't find any pointers... Do you have any idea how to get around > this? Is there a documented method to recover from this situation? > > Cheers, > Tony > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l