SYSTEM HALT Command | bcmadmin | Teradata Business Continuity Manager - SYSTEM HALT - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 2.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
2.00
Published
August 2024
ft:locale
en-US
ft:lastEdition
2025-01-31
dita:mapPath
sko1694443904278.ditamap
dita:ditavalPath
ft:empty
dita:id
otc1639627713801
lifecycle
latest
Product Category
Analytical Ecosystem

Purpose

Changes a table or database system in the Active state to the Out of Service state.

If a multi table write runs, and a table is in Out of Service or Interrupted state, then all associated tables in the write automatically become Out of Service or Interrupted.

Syntax

SYSTEM HALT tdpid | tdpid [ON database.tablename[,tdpid,...]];

Parameters

database.tablename
Name of a database and table currently in the Business Continuity Manager Data Dictionary. The table name that you specify must be fully qualified.
tdpid
Unique identifier (TDPID) of a database system.

Usage Considerations

If making a state change for a table on all the database systems, the table has the same data across all database systems when this operation completes.

When running this command, Business Continuity Manager holds any new transactions/statements until all in-flight transactions close for the object. RecoveryCheckpointTimeout determines the duration of wait time. If in-flight transactions are not closed within this time limit, the operation aborts, an error displays, and the state returns to the state prior to the attempt.

When making the state change to the database system, all tables managed by Business Continuity Manager on that database system become Out of Service.

If applied to the database system successfully, all tables in the database system become Out of Service. If this operation is applied to a database system, all tables must be in the Active state, else the operation results in an error, and no action takes place.

Example

The following example shows using SYSTEM HALT to place a table t4_cp_tpp from a database cp_tpp004u in Out of Service state. The DBA then runs OPERATION CHECK to confirm operation completion.

bcmadmin>  system halt cp_tpp004u.t4_cp_tpp; 
The request is currently processing as operation number 2.
You may check its status using the command 'operation check 2'.
bcmadmin> operation check 2;
Operation Number : 2
Operation Name   : Halting Table
User             : admin
User Name        : Main Administration User
Progress (%)     : 100
Status           : Finished (1)
Start Time       : 01/08 13:13:33
Finish Time      : 01/08 13:13:36
Systems:
    [1] bltor - Finished (1)
    [2] fast - Finished (1)
Updates:
    01/08 13:13:36 [-] Info: Halting table cp_tpp004u.t4_cp_tpp
    01/08 13:13:36 [-] Info: Requesting mgmt X lock on 'cp_tpp004u.t4_cp_tpp'
    01/08 13:13:36 [-] Info: Mgmt X lock on 'cp_tpp004u.t4_cp_tpp' granted
    01/08 13:13:36 [-] Info: Releasing mgmt X lock on 'cp_tpp004u.t4_cp_tpp'
    01/08 13:13:36 [-] Info: Successfully halted table on 2 systems
    01/08 13:13:36 [-] Info: Operation finished