Hey, For few days the Event.vEvent, Event.vEventDetail, Event.vEventParameter ... tables on Scom DWDB are totally empty and are not filling up ... so each query using this database return NULL. I don't really understand why this happen, and what impact could it have on SCOM. If someone can help me on that :) Regards.

Hello, Did you chnage the Event retention period, Check it in: Console >> Reporting >> Microsoft Data Warehouse Reports >> Data Warehouse Properties >> Event Collection section It is by default 100 days.. To change the Opeartions Data Warehouse retention: http://blogs.technet.com/b/stefan_stranger/archive/2009/08/15/everything-you-wanted-to-know-about-opsmgr-data-warehouse-grooming-but-were-afraid-to-ask.aspxRegards, Mazen Ahmed

Yes, I have changed it few days ago by using the link you've just shared by the way. I think it's linked but i don't understand why there are no more events... The query on the retention give me the following results: More informations: We can see that there are no Raw datas for event/conf/client ....

Check this Rule >> Event data collector >> in the Overrids parameters "Drop items" should be "False"Regards, Mazen Ahmed

Thanks for the reply but it is already overridden with "False" value ..

Maybe given that the retention period have been reduced all past events have been deleted and given that it can't store new ones, there is no data in Even data set .. I don't know if these errors are linked to the problem but there is always a reference to Event data set... For 2 months or more, the following error is flooding my scom DWDB server: And I got similar 31552 and 31553 event on my MS/RMS: Traduction: Failed to store data in datawarehouse 31553 : Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations Exception 'SqlException' : Error 777971002, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. These errors generate a critical state for the MS and RMS on Data warehouse maintenance data set. If someone have more information on the link between these errors and how to solve them it could be great :)

this could be a grooming issue affecting the OperationsManagerDW How many tables do you have of the following: Perf.PerfHourly_xxxxxxxxxxxxxxxxxxxxxxxxxx State.StateHourly_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Event.Event_xxxxxxxxxxxxxxxxxxxxxxxRegards, Mazen Ahmed

Thanks for the answer. 4 tables for State.StateHourly_xxx 9 tables for Perf.PerHourly_xxx And 1 for the Event.Event_xxx See below Regards

Any news for my problem ? :)

Hi, Regarding the event 18054, please also refer to the following post: After moving your OperationsManager Databaseyou might find event 18054 errors in the SQL server application log http://blogs.technet.com/b/kevinholman/archive/2010/10/26/after-moving-your-operationsmanager-database-you-might-find-event-18054-errors-in-the-sql-server-application-log.aspx If you want to try the method, please perform a full backup first. Thanks. Nicholas Li TechNet Community Support

Hi, thanks for trying to help me, I have tried the previous method with no success. The table is still empty and errors keep coming.. If someone get any more ideas :) Regards

Do someone have any more ideas ?