Registering A Previously-Managed Oracle VM Server Produces The Error "has been managed" or "OVM-2008 ..."

(Doc ID 789936.1)

Last updated on MARCH 25, 2012

Applies to:

Oracle VM - Version: 2.1.2 to 2.2 - Release: OVM212 to OVM22
Linux x86
Linux x86-64
***Checked for relevance on 25-Mar-2012***


In some cases, you need to re-register an OracleVM Server managed by an OracleVM manager to a new manager.  Embedded in each server are records of its current affiliation.  These records will prevent the server from being registered again.  Usually dropping a server from a pool removes these records, but should an error prevent that it is possible to remove the setting manually.

During creating a new server pool with the existing OVM Server, you could come across the error on Oracle VM 2.1.2 like below:

The same error has a different appearance on 2.1.5 and 2.2.0:


Try to manage a OVM server once managed by another OVM manager.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms