Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

40672

March 18th, 2014 02:00

Not able to delete device from OME

Hi,

I need to delete the server device in OME but it still appear in the device discovery inventory after delete. It also shown double entry in the discover inventory. I get know from this forum it need to delete device in ome database but it is not provide the step. Can you let me know which table name and  row I need to take care? below is my OME deatil.

 Server OS : Windows 2008R2, Database: MS SQL server 2008R2 (Install to local server).OME version: 1.2.1.0.

 

Double entry for device which cannot delete

==================================

Thanks

1 Rookie

 • 

5 Posts

March 18th, 2014 20:00

Hi Rob,

My OME version is 1.2.1.0. The reason why i need to delete the device is becasue this server has been decommission. So, I wil not going to discover it again. For some reason, this server have a double entry, I think this is because my list have 2 entry when i perform the import list of discover ranges in my first implementation on OME. By the way, delete the record in the table DiscoveryConfiguration is work! However, just need to aware that we need to disable the the triggers DiscoveryConfiguration_ArchiveOnDelete before we delete the 2nd entry. If the trigger not disable, the 2nd entry will not able to delete.

 

Big thanks again for your awesome response :)

DV

3 Apprentice

 • 

2.8K Posts

March 18th, 2014 10:00

Hi and thanks for the post.

 A few questions just to make sure I'm clear:

What version of OME are you using?

Where is the problem happening exactly (device tree or disc portal?)

Are you able to delete _both_ ?

is re-discovery bringing it back?

is it not able to delete from the console?

If you delete the discovery range from the console does it reappear before discovery is run?

Have you used the import file feature to import a list of discovery ranges?

Sorry for so many questions, but we've seen this a few times, but it is hard to reproduce.

DiscoveryConfiguration table is where these are kept. There should be two entries corresponding to those names and they should both be deleted. 

Thx

Rob

6 Posts

April 2nd, 2014 09:00

Hi Rob,


I am currently having the same issue with Openmanage Essentials v1.2.0.3441.

I have imported a list of servers from a file. There were a few duplicates in the file. I cannot delete the duplicates from the from the discovery ranges.


I am right clicking on the discovery range and selecting delete, but nothing happens if I try to delete a duplicate.


I get this warning in the User Interface Logs each time I try to delete a duplicate.

"Warning"    "4/2/2014 11:38:03 "    "DiscoveryConfigurations async"    "Adding/Updating dep-apdc"
"Warning"    "4/2/2014 11:38:03 "    "DiscoveryConfigurations async"    "Adding/Updating DEP-APDC"

3 Apprentice

 • 

2.8K Posts

April 2nd, 2014 10:00

Thanks for the post.

It looks like there is a bug where this situation might happen on the import.  If you look to the second post in this thread, the workaround is to delete the record from the DiscoveryConfiguration in the database (note the comment about the trigger).

Disclaimer: Always back up the database before doing any operations on a production database.  And feel free to open a ticket with customer support (800-945-3355 ) if you are not comfortable with SQL Management Studio.

Thanks,

Rob

No Events found!

Top