Database event grooming does not complete on Microsoft Operations Manager 2000 SP1 computer (835853)


The information in this article applies to:

  • Microsoft Operations Manager 2000 SP1

SYMPTOMS

Database event grooming may not be completed on a Microsoft Operations Manager (MOM) 2000 Service Pack 1 (SP1)-based server. The SQL Error.log file may contain a report that is similar to the following report:
Job 'OnePoint - Groom Events' : Step 2, 'Groom other events' : Began Executing 
2003-02-27 10:23:32

Msg 547, Sev 16: DELETE statement conflicted with COLUMN REFERENCE constraint 
'FK_EventParam_Event'. The conflict occurred in database 'OnePoint', table 
'EventParam', column 'idEvent'. [SQLSTATE 23000]
Msg 50000, Sev 16: Grooming job 'Other Events' failed with error 547 [SQLSTATE 
42000]
Msg 3621, Sev 16: The statement has been terminated. [SQLSTATE 01000]
Msg 0, Sev 0: Associated statement is not prepared [SQLSTATE HY007]

CAUSE

This problem may occur if any one of the temporary tables that the grooming task creates is larger than the Number of records to delete in each grooming transaction value in the grooming properties.

WORKAROUND

To work around this problem, increase the value of the Number of records to delete in each grooming transaction value in the database grooming properties. To do so, follow these steps:
  1. Click Start, point to Programs, point to Microsoft Operations Manager, and then click MOM Administrator Console.
  2. Expand Microsoft Operations Manager (Default), expand Configuration, and then click Global Settings.
  3. On the right pane, double-click Database Grooming.
  4. Double-click the task that the SQL error log reports. The error log sample in this article reports the Other Events task.
  5. Make a note of the current Number of records to delete in each grooming transaction value.
  6. Increase the Count value to a very high number. For example, 500000.
  7. On the Data Access Server/Consolidator-Agent Manager (DCAM) computer, follow these steps:
    1. Click Start, point to Settings, and then click Control Panel.
    2. Double-click Administrative Tools.
    3. Double-click Services.
    4. Stop the OnePoint service.
  8. Rerun the database grooming task.
  9. After the grooming task is completed, restore the Number of records to delete in each grooming transaction value in the grooming task properties to the value that you noted in step 5.
  10. Restart the OnePoint service on the DCAM computer. Note You may have a high number of queued events after you restart the service.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbDatabase kbPerformance kbnofix kbBug KB835853 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.