Update from Configuration Database for multi node systems always think one node is out of sync with the Configuration database

ID:    D27793
Published:    15 July 2021

Defect Id


Originally Reported Against

SBM 11.8




The issue presents itself for multi node SBM systems when the administrator is trying to synchronize the nodes when a node is update the other node then thinks it is out of sync even though they we both updated from the same configuration version.  At this point the SBM Configurator thinks that the Node is now not in sync with the configuration database and then asked to Admin if they would like to sync it with the Config DB again.  For a 2 node installation, this seem to back and forth forever.  

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs