An object becomes interrupted on a system if a SQL statement succeeds on at least one system but fails with an error on another system. This mismatch causes objects to become interrupted on the system with the error. Unity replays the SQL statement to attempt recovery. Some errors may recover automatically, although others require manual intervention.
If an object is interrupted on a system, and another SQL statement or session needs to use that object, any other objects used by that session or SQL statement also become interrupted. This is a cascade interrupt. Once the objects or sessions required for this object recover, the cascade interrupts recover as well.
The recovery may take a few attempts, but if no more root cause interrupts occur, the objects become active.