In some cases, the DBA is unable to resolve an interrupted request directly on the Teradata system. For example, this may happen if a user was mapped to the wrong routing rule and accidentally run a request that requires objects that do not exist on a given Teradata system. For these situations, it is possible to skip requests, allowing Business Continuity Manager recovery process to continue recovering any other workloads that were dependent on the request.
Skipping a request can result in tables becoming unrecoverable. For Business Continuity Manager, the copy of the table is no longer in sync with the copies of the table on other systems. It is not recommended to override this. The best practice is to allow the table to become unrecoverable, and then use Business Continuity Manager validation and resync features to synchronize the table if needed.
- From the Interrupted Sessions screen of the Business Continuity Manager UI, select the session you want to skip.
- Select SKIP in the Interrupted Sessions Details window.
- In the Skip Interrupted Session dialog box, select SKIP again.