SYSTEM RECOVER Command | bcmadmin | Teradata Business Continuity Manager - SYSTEM RECOVER - 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

Recovers dDatabase systems or tables that are in Out of Service, Interrupted, or Read-Only state.

Syntax

SYSTEM RECOVER <tdpid> [, <tdpid>, ...] [REASON '<reason>']

Parameters

tdpid
Unique identifier (TDPID) of a database system.
REASON
Reason for clearing. Use quotation marks when the reason is more than one word.

Usage Considerations

All Business Continuity Manager managed tables for the specified TDPIDs change to Restore state and go through recovery.

If the table cannot recover successfully due to a transient error, then the table remains in Interrupted state, which raises an alert. After resolving the error, retry the recovery.

If Business Continuity Manager cannot successfully recover the table due to data consistency issues, then the table enters Unrecoverable state.

The command operation replays the Recovery Log to bring the database server from Out of Service, Interrupted, or Read-Only state to Active state without requiring manual intervention to restore the data. If the recovery operation is unsuccessful, the database system or table becomes Interrupted or Unrecoverable based on the error returned.

Running this operation on a database system places each table in that database system from Out of Service or Interrupted into Restore state. The system completes recovery within a short period while tables on the system continue recovery at an individual level. As each table completes recovery successfully, it becomes Active and accessible for client transactions.

Example

The following example demonstrates system level recovery after running SYSTEM FREEZE.

bcmadmin>  system freeze bltor; 
Operation Number : 4
Operation Name   : Freezing Systems
User             : admin
User Name        : Main Administration User
Start Time       : 10/19 12:34:06
Systems:
    [1] bltor
Updates:
    10/19 12:34:08 [-] Info: Freezing selected systems
    10/19 12:34:08 [-] Info: Successfully froze 1 systems
    10/19 12:34:08 [-] Info: Operation finished
Status      : Finished (1)
Finish Time : 10/19 12:34:08
Systems:
    [1] bltor - Finished (1)

bcmadmin> system recover bltor;
Operation Number : 5
Operation Name   : Recovering Systems
User             : admin
User Name        : Main Administration User
Start Time       : 10/19 12:34:38
Systems:
    [1] bltor
Updates:
    10/19 12:34:38 [-] Info: Recovering selected systems
    10/19 12:34:38 [-] Info: Successfully started recovery on 1 systems
    10/19 12:34:38 [-] Info: Operation finished
Status      : Finished (1)
Finish Time : 10/19 12:34:38
Systems:
    [1] bltor - Finished (1)