Skip Interrupted Tables | Teradata Business Continuity Manager - Skipping Interrupted Requests - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 1.01.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
1.01.01
Published
March 2023
Language
English (United States)
Last Update
2023-03-13
dita:mapPath
qra1653979755546.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2550
lifecycle
previous
Product Category
Analytical Ecosystem
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.
  1. From the Interrupted Sessions screen of the Business Continuity Manager UI, select the session you want to skip.
  2. Select SKIP in the Interrupted Sessions Details window.
  3. In the Skip Interrupted Session dialog box, select SKIP again.