Multiple entries for operating system?

[Raymond Kim]

Wow, it's been literally years since I last posted to this forum.

Here's my situation: I maintain a server inventory database that relies heavily on the SIM DB back end to keep it up-to-date. I just discovered that a number of servers have multiple entries for the operating system. I ran a query on the CIM_OperatingSystem table and confirmed this.

I have always been under the assumption that the contents of this table was one-to-one (i.e. only one line for each server). Is this an incorrect assumption?

Let me know how this is supposed to work. I'm running SIM Server agent 7.5 and SIM front end version 5 (SP 4).

Thanks . . .

[Joel Rubenstein]

Is your SIM installation an upgrade from SIM 4.X ?

[Raymond Kim]

Not really sure (I'm not the primary SIM administrator), but I *think* it was.

[Joel Rubenstein]

What is the name of the SIM database?

[Raymond Kim]

Insight_v1_0_114727421

[Joel Rubenstein · Accepted solution]

This duplicate data in the reports is a result of duplicated data in the CIM_OperatingSystem database table. The duplicate data from SNMP and WMI is not being properly merged. This is due to the fact that the DC_PolledData database table was not properly updated during the SIM upgrade.

The following SQL statements can be used to fix the database issue

Update DC_PolledData set preferredProto=8 where PollId=11
Update DC_PolledData set preferredProto=8 where PollId=12
Update DC_PolledData set preferredProto=8 where PollId=13
Update DC_PolledData set preferredProto=8 where PollId=14
Update DC_PolledData set preferredProto=8 where PollId=18
Update DC_PolledData set preferredProto=8 where PollId=19
Update DC_PolledData set preferredProto=8 where PollId=20
Update DC_PolledData set preferredProto=8 where PollId=21
Update DC_PolledData set preferredProto=8 where PollId=162
Update DC_PolledData set preferredProto=8 where PollId=193
Update DC_PolledData set preferredProto=8 where PollId=194
Update DC_PolledData set preferredProto=8 where PollId=195
Update DC_PolledData set preferredProto=8 where PollId=225
Update DC_PolledData set preferredProto=8 where PollId=226
Update DC_PolledData set preferredProto=8 where PollId=227
Update DC_PolledData set preferredProto=8 where PollId=228
Update DC_PolledData set preferredProto=8 where PollId=507
Update DC_PolledData set preferredProto=8 where PollId=580
Update DC_PolledData set preferredProto=8 where PollId=581
Update DC_PolledData set preferredProto=8 where PollId=582
Update DC_PolledData set preferredProto=8 where PollId=593
Update DC_PolledData set preferredProto=8 where PollId=594
Update DC_PolledData set preferredProto=8 where PollId=595
Update DC_PolledData set preferredProto=8 where PollId=703
Update DC_PolledData set preferredProto=8 where PollId=713
Update DC_PolledData set preferredProto=8 where PollId=2162

The SIM service must be restarted after the database changes are made.

After data collection is run on the affected servers the duplicate data will no longer displayed.

[Raymond Kim]

Okay -- let me give this a try. I'll let you know how I make out. Thanks!

[Raymond Kim]

It worked! We ran the query and rediscovered one of the servers that had the problem. It came back with only one entry for R_OperatingSystem.

Thanks for the assist!

[Raymond Kim]

Ran described query and rediscovered server.