Symptoms:
This issue occurs because of corruption in the NSX Database.
To resolve this issue, contact Broadcom Support and note this Knowledge Base article ID (319562) in the problem description. Workaround:To work around this issue: