A few important SCOM KB Articles were released
I ran into this one myself with a new installation and ended up just re-installing the database clean. This would have helped!
Archive for January 2008
I ran into this one myself with a new installation and ended up just re-installing the database clean. This would have helped!
Are you getting this error from your Data Warehouse?
I immediately started getting these alerts after I upgraded my Data Warehouse Library Management Pack to version 6.0.5000.26 from this knowledge base article http://www.microsoft.com/downloads/details.aspx?FamilyID=09f74984-7e9d-42ef-8b38-ad770b084363&DisplayLang=en. I believe the issues exists in SP1 RC1 as well.
The problem is caused by a few hardware MPs, primarily HP and Dell that populate the Data Warehouse with “last discovered on” date as a property, basically, making an object different every time they happen to run the discovery and not only when object really changed.
This has been fixed in SP1 (RTM not in RC0) with some scripts that I am posting. Theses scripts came from Microsoft and were installed by a number of other customers with no issues, however I cannot claim that they are fully tested. They will not prevent upgrade to SP1.
The scripts create indexes in the Data Warehouse. I verified them with one our DBA’s and he said they were safe to run. As soon as I ran the scripts the alerts stopped immediately
If you are getting this error. You can fix it by installing Operations Manager 2007 Data Warehouse Library Management Pack 6.0.5000.26
After installing that you might get this new error. Performance data collection process unable to store data in the Data Warehouse in a timely manner.
You can fix this error by referencing.
http://www.scom2k7.com/performance-data-collection-process-unable-to-store-data-in-the-data-warehouse-in-a-timely-manner/