You are on page 1of 3

Document 1916292.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=35...

Support Identifier: 18001614 (Commercial CbeOracle (Not Available) (2) Contact Us Help
PowerView is On
B...

Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...

Oracle VM 3: How to Forcefully Delete an Unassigned Oracle VM server when Fails with "OVMAPI_4010E Attempt
To Bottom
to send command: release_ownership" (Doc ID 1916292.1)

In this Document Was this document helpful?

Yes
Symptoms
No
Cause
Solution
Document Details

APPLIES TO: Type:


PROBLEM
Status:
PUBLISHED
Oracle VM - Version 3.0.1 to 3.3.1 [Release OVM30 to OVM33] Last Major
Update: Sep 12, 2014
Linux x86-64 Feb 25, 2017
Last
Update: English
SYMPTOMS Language:

This note explains how to forcefully delete an unassigned Oracle VM server after a delete server operation fails with the error
shown below. Take note of the word "Clustered" at the end of the second line in the error message below. This provides a Related Products
clue that there is likely a problem with the pool file system on the failed Oracle VM server. Oracle VM

OVMAPI_4010E Attempt to send command: release_ownership to server: myserver17 failed. Information Centers
OVMAPI_4004E Server Failed Command: release_ownership 0004fb000001000063823772361f87eb, Status: Information Center: Oracle VM
org.apache.xmlrpc.XmlRpcException: exceptions.Exception:Cannot release server in membership state: Clustered Release 3.x for x86
[1351538.2]

The following screen shot shows what the error message will look like as seen from the Oracle VM Manager:
Document References

No References available for this


document.

Recently Viewed

Oracle VM: How To


Regenerate The OVM
3.3.x/3.4.x DB [2038168.1]
Information Center: Oracle
VM Release 3.x for x86
[1351538.2]
CAUSE Oracle VM 3.2.1 log analysis
tool - OvmLogTool.py
[1530899.1]
The most likely cause will be that the local Berkeley database on the Oracle VM server is out of sync. The database may contain
information about the pool file system or storage repository that may no longer exist or may no longer be available to the Oracle Information Center:
Troubleshooting Oracle VM
VM server for one reason or another.
Release 3.x for x86
[1351539.2]
For example, the first screen shot showing the output from the ovs-agent-db dump_db server command clearly shows that
Cannot Refresh, Present-
the Oracle VM server should still have access to a NFS pool file system (or SAN). It may be that the storage admin has already
Unpresent NFS Repository on
un-exported the pool file system so the server no longer has access to it or perhaps the NFS file system for the pool file system Oracle VM 3.0.3 -
no longer exists at all. So, the underlying cause is that the local Berkeley database used by the agent shows that a pool file OVMRU_002006E:
system should still be mounted, but the agent cannot un-mount and clean up a pool file system information since it is not actually RepositoryName - Cannot
mounted. Perform Operation, the
Repository is not Presented
on any Servers [1437493.1]
Show More

The second screen shot below showing the output from the df command tells us that a storage repository is mounted but no
there is no pool file system. When you see the word "Clustered" in the error message this likely means the that the pool file
system cannot be un-mounted. In this case, the pool file system can't be unmounted since it is clearly not mounted at all.

1 of 3 11/22/2017, 11:58 AM
Document 1916292.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=35...

SOLUTION

Solution Overview
The following list shows the major steps needed to solve the problem:

Step 1: Acknowledge any outstanding server events


Step 2: Stop the agent on the Oracle VM server
Step 3: Delete the Oracle VM server from the model
Step 4: Reinstall Oracle VM Server on the deleted server (beyond the scope or purpose of this note)

Solution Detail
Step 1: Acknowledge any outstanding server events

There are many Oracle VM Manager jobs/operations that will fail simply because an Oracle VM server has unacknowledged
critical or major events. You will need to ensure all events have been acknowledged before proceeding any further.

The following screen shot shows all events have been acknowledged

Step 2: Stop the agent on the Oracle VM server

You will need to log onto the Oracle VM server as root and stop the agent using the following command:

service ovs-agent stop

Step 3: Delete the Oracle VM server from the model

You will now be able to delete the un-assigned Oracle VM server from the model once the agent is stopped from the previous
step. Simply select the un-assigned server in the navigation pane as shown below and then chose the Delete Server icon from
navigation tool bar.

Confirm that is is okay to delete the server

2 of 3 11/22/2017, 11:58 AM
Document 1916292.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=35...

Screen shot showing the server has been deleted from the model

Step 4: Reinstall Oracle VM Server on the deleted server

You should now be able to reinstall the Oracle VM Server product on the deleted server. Please follow the instructions found in
the latest version of the Oracle VM Installation and Upgrade Guide for installing your particular version of Oracle VM Server.

Didn't find what you are looking for? Ask in Community...

Related
Products
Oracle Linux and Virtualization > Oracle VM > Oracle VM > Oracle VM > Oracle VM Manager > physical storage, disks, paths, nfs, storage servers

Keywords
ORACLE VM MANAGER; ORACLE VM SERVER

Translations
English Source Japanese
Back to Top
Copyright (c) 2017, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

3 of 3 11/22/2017, 11:58 AM