SESSION SKIP APPLY Command | bcmadmin | Teradata Business Continuity Manager - SESSION SKIP APPLY - 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

Purpose

Allows Business Continuity Manager to skip a session that is interrupted.

Syntax

SESSION SKIP APPLY <BCM Session ID> <transaction ID>ON <tdpid> [ACTIVE];

Parameters

BCM Session ID
Assigned Business Continuity Manager session ID.
Transaction ID
Assigned Transaction ID.
tdpid
Unique identifier (TDPID) of a database system.
ACTIVE
Disables the default behavior which sets all tables to unrecoverable. Instead, checks to see if the objects can be set to Active.

Usage Considerations

This command informs the recovery engine that the specified transaction on the specified session and TDPID should be skipped during recovery.
Skipping a transaction can cause tables to become out of sync immediately and other tables to become unrecoverable in subsequent transactions.
The transaction ID specified must be the transaction ID that is currently blocking recovery of the specified session. If the transaction ID does not match the session's interrupt transaction ID, the following error is returned: Specified transaction ID does not match expected interrupted transaction ID for session.

Example

bcmadmin> SESSION SKIP APPLY 1000 437 on flash;
Warning: Skipping this transaction can cause tables to 
become out of sync immediately and other tables to 
become unrecoverable in subsequent transactions.

To see a list of affected tables refer to the SESSION
SKIP LIST command.
Enter 'Yes' to skip this transaction: yes

Tables affected by transaction
____________________________________
db2inst2.doc_test3
db2inst2.doc_test4
____________________________________
2 tables