Document Type | Technical Information
Category | Backup/Recovery
Applicable Product Versions | 6FS07PS, 7FS02PS
Document Number | TBATI022
Overview
Tibero recovery operations include Crash Recovery and Media Recovery.
- Crash Recovery: Automatically performs recovery using Checkpoint and TSN (Transaction Sequence Number) during the restart process after an abnormal database shutdown.
- Media Recovery: The recovery method used when physical damage occurs to files constituting Tibero.
This document guides the manual Media Recovery procedure when damage occurs to Tibero configuration files.
Method
Roles by Tibero Boot Modes
MODE | Description | Main Tasks |
|---|---|---|
NOMOUNT | Instance startup (SGA + background processes) | Database creation, control file recreation |
MOUNT | Control file open | Check Redo and data file information, set Archive mode, perform Media Recovery |
NORMAL | Open all data files | Compare TSN and Checkpoint status, then perform Crash Recovery |
Types of Recovery After Tibero Abnormal Shutdown
Recovery Type | Description |
|---|---|
Crash Recovery (Automatic) | Automatic recovery upon DB restart after abnormal shutdown due to system failure |
Media Recovery (Manual) | Manual recovery when files themselves are damaged due to disk damage, etc. |
Recovery Related Views
Media Recovery is usually performed in MOUNT MODE, and the related dynamic views for recovery are as follows.
By querying these VIEWS, you can check the files to be recovered and confirm the progress of the recovery.
VIEW | Description |
|---|---|
V$RECOVER_FILE | Outputs the list of data files requiring recovery |
V$RECOVERY_FILE_STATUS | Allows checking the status of files targeted for recovery |
Types of Media Recovery
Complete Recovery
When damage occurs to configuration files during Tibero boot, making normal startup impossible during the Crash Recovery phase, Media Recovery is required.
- If all backup files necessary for recovery exist, a complete recovery is possible by applying Archive Files and Online Redo Logs to the backed-up data files, restoring to the most recent logs.
Incomplete Recovery
When damage occurs to configuration files during Tibero boot, making normal startup impossible during the Crash Recovery phase, Media Recovery is required.
- If only some of the backup files necessary for recovery exist, incomplete recovery is possible by applying part of the Log Files or recovering to a specific point in time.
- After Media Recovery in MOUNT MODE, when starting Tibero, it is necessary to start with
tbboot resetlogs.
- Because starting Tibero with resetlogs initializes the Redo Log, it is strongly recommended to perform a backup again.
Incomplete Recovery Options
Incomplete Recovery | Description |
|---|---|
Change-Based (TSN) | Recovery up to a TSN (unique transaction number) point: alter database recover automatic database until change {TSN}; |
Time-Based | Recovery up to a specific time point: alter database recover automatic database until time '{time}'; |
Cancel-Based (Archive) | Recovery up to the Archive File point: alter database recover until cancel; |
Summary
Item | Description |
|---|---|
Recovery Method | Manual operation, Media Recovery performed in mount mode |
Complete Recovery | Includes existing REDO logs, capable of restoring to the most recent state, resetlogs not required |
Incomplete Recovery | After recovery based on change/time/cancel, starting Tibero requires resetlogs |
Follow-Up Actions | Full backup is mandatory after recovery completion |