When Business Continuity Manager detects a request that succeeded on the active system but failed on the standby system, the session and tables with the failed request become interrupted on the standby system.
- Lack of spool or perm space
- Missing user grants
- Missing database objects
- Foreign key violations
- Any other errors, such as AMP step failure
The interrupted state means that Business Continuity Manager can still automatically recover the session and tables from the Recovery Log after resolving the initial problem on that system.
When there is an interrupted request, Business Continuity Manager raises an alert to inform the DBA. The DBA can then fix the problem identified on the failing system. For example, the DBA can add more spool or perm space, correct user permissions, and create or drop required objects.
It is important to respond to the alert immediately because any subsequent work depending on the work done by the initial interrupted session also becomes interrupted. These secondary or cascade interrupts are filtered in the Business Continuity Manager UI and at the bcmadmin command line so you can resolve the initial session that caused the issue.
If ignored, an interrupt alert can escalate from a minor isolated issue, involving a single session and a small set of tables, to a more significant problem that can cause the entire system to become interrupted.