When SCOM "forward" alerts to the connector the status on SCOM remains i"pending" even if the event is arrived in BSM

  • KM01284892
  • 01-Dec-2014
  • 01-Dec-2014

Summary

When SCOM "forward" alerts to the connector the status on SCOM remains i"pending" even if the event is arrived in BSM. After sometime the status in SCOM is changed to the correct one, but it seems there is a huge delay. Is this normal?

Question

When SCOM "forward" alerts to the connector the status on SCOM remains i"pending" even if the event is arrived in BSM. After sometime the status in SCOM is changed to the correct one, but it seems there is a huge delay. Is this normal?

Answer

The delay happens because the SCOM console is using a caching mechanism which means the alert information is not reflected in real time.  Opening SCOM console with the /clearcache command line option clears the local console cache and fetch the last rows from database.  This is not a problem with the connector.
 
 
More on running the console with the clearcache see http://technet.microsoft.com/en-us/library/hh212884.aspx.