Return
-
Title
After a schema extension, "Enable Constraints 2" or "Disable Constraints 2" is "stuck" in DBQueue -
Description
After a schema extension the tasks "Enable Constraints 2" or "Disable Constraints 2" are "stuck" in DBQueue, i.e.not processing. -
Cause
Database inconsistency -
Resolution
1. Restore the One Identity database from the backup taken before the schema change
OR
2. Repair the inconsistencies using the following Data Consistency Checks:- Content/DynamicFKInvalid/Okject keys or FK invalid
- Configuration/Dynamic FK
- Content/consistency
- Database Model/Relationships
For more information, please refer to the Operational Guide, Checking data consistency.
When the repairs are complete, enable constraints again using the following:
EXEC QBM_PTriggerEnable '%'
EXEC QBM_PConstraintEnable '%'Please note: This can also be due to locks on tables from other resources such as a job server and web hosts.
Use the suggestions in knowledge base article number 4310886 to help troubleshoot resets.
-
Change Request
30447/30573/30626