Skip to main content

Search

Welcome to Tibero GTS!

Check Backup Integrity Before Performing Recovery

Document Type | Technical Information

Category | Backup/Recovery

Applicable Product Versions | T5, T6, T7

Document Number | TBATI048

 

Overview

This explains the method to verify the integrity of a backup file after restoring a Hot Backup for Recovery.
Note
Recovery may fail if performed with an incorrectly executed HOT Backup; therefore, it is necessary to verify the backup’s integrity before Recovery.
 
 

Method

1. Perform HOT BACKUP RESTORE

Restore the operating system's HOT BACKUP.
 

2. Modify TRACE Statement Path for CONTROL FILE Creation

When creating the control file, modify the paths accordingly. (Backup path → Restore path)
CREATE CONTROLFILE REUSE DATABASE "tibero"
LOGFILE
GROUP 1 '/BackupPath/log011.log' SIZE 50M,  ---Change to restore path
GROUP 2 '/BackupPath/log021.log' SIZE 50M,  ---Change to restore path
GROUP 3 '/BackupPath/log031.log' SIZE 50M   ---Change to restore path
NORESETLOGS
DATAFILE
      '/BackupPath/system01.dtf',   ---Change to restore path
      '/BackupPath/undo001.dtf',    ---Change to restore path
      '/BackupPath/usr01.dtf',      ---Change to restore path
      '/BackupPath/syssub01.dtf',   ---Change to restore path
      '/BackupPath/test01.dtf'      ---Change to restore path
ARCHIVELOG
MAXLOGFILES 100
MAXLOGMEMBERS 8
MAXDATAFILES 10240
MAXARCHIVELOG 500
MAXBACKUPSET 500
MAXLOGHISTORY 500
CHARACTER SET MSWIN949
NATIONAL CHARACTER SET UTF16;


3. Perform DATA FILE HEADER DUMP

SQL> alter system dump datafile_header;
System altered.
 

4. Check the DUMP FILE 

Check the status information of each Data File and the backup_ckpt information in the trace file located in the TRACE_DUMP_DEST directory.

  • If status=0x6 and backup_ckpt value is not 0 for each Data File → The HOT BACKUP was performed correctly.
  • If status=0x2 and backup_ckpt value is 0 for each Data File → The HOT BACKUP was performed abnormally.
SQL>  show parameter TRACE_DUMP_DEST
NAME                     TYPE     VALUE
----------------------- -------- -------------------------------------------------------------------------------
TRACE_DUMP_DEST          DIRNAME  /home/at/tibero7/instance/tibero/dump/tracedump/
  • Brief Check of DUMP FILE
OS> cd /home/at/tibero7/instance/tibero/dump/tracedump/
OS> cat tb_dump_2720457_158_352862.trc |grep -E "flag|status|backup_ckpt"
flags=0xb,name=#3(/home/at/tibero7/database/tibero/system01.dtf),
 tsid=0(type:0, name=SYSTEM),relid=0, root dba=00_00000000, status=0x6, 
 backup_ckpt=0000.0004356e 2026-03-11 10:38:52, --Normal
flags=0xb,name=#4(/home/at/tibero7/database/tibero/undo001.dtf),
 tsid=1(type:1, name=UNDO0),relid=1, root dba=00_00000000, status=0x6, 
 backup_ckpt=0000.0004356e 2026-03-11 10:38:52, --Normal
flags=0x3,name=#6(/home/at/tibero7/database/tibero/usr01.dtf),
 tsid=3(type:0, name=USR),relid=2, root dba=00_00000000, status=0x2, 
 backup_ckpt=0000.00000000 2026-03-11 10:39:00, --Abnormal
flags=0xb,name=#7(/home/at/tibero7/database/tibero/syssub01.dtf),
 tsid=4(type:0, name=SYSSUB),relid=3, root dba=00_00000000, status=0x6, 
 backup_ckpt=0000.0004356e 2026-03-11 10:38:52, --Normal
  • Detailed Information of DUMP FILE 
HOT BACKUP Abnormal Process
HOT BACKUP Abnormal Process
**Dump start at 2025-02-12 09:54:59   flags=0xb,name=#3(/GPFS/reco2/clon/system01.dtf),create_bcnt=64000, blksize=8192,tsid=0,prev_dtf=-1,refno=0
ckpt=0000.00115d90 2025-02-1115:19:01,cnt=250, create=0000.000000001 2025-01-17 11:11:27,
stop=ffff.ffffffff 2025-02-12 09:54:28,offline=0000.00000000 ,   online_ckpt=0000.00000000
DATAFILE DUMP [0/0]
DUMPING COMMON HEADER BLOCK
dbname='tibero' dbid=bc4c00ad version=6.7 cf_seqno=515 filetype=2 fileno=0 blksize=8192 filesize=524288000   DUMPING DATA FILE HEADER BLOCK
tsid=0(type=0, name=SYSTEM),relid=0, root dba=00.00000000, status=0x6,
create=0000.000000001 2025-01-17 11:11:27,
resetlogs=0000.00000000 ,
ckpt=0000.00115d90 2025-02-11 15:19:01,cnt=250,prev=249,   backup_begin_ckpt=0000.00115d90 2025-02-11 15:19:10, 
backup_ckpt=0000.0011bcc8 2025-02-12 09:49:02,   backup_begin=0000.0011bcc8 2025-02-12 09:49:01,   backup_ckpt=0000.0011bcc8 2025-02-12 09:49:02,		**Dump start at 2025-02-12 10:18:56   flags=0x3,name=#3(/GPFS/reco2/clon/system01.dtf),create_bcnt=64000, blksize=8192,tsid=0,prev_dtf=-1,refno=0
ckpt=0000.00130854 2025-02-12 10:17:30,cnt=264,   create=0000.000000001 2025-01-17 11:11:27,
stop=ffff.ffffffff 2025-02-12 10:18:55,offline=0000.00000000 , 
online_ckpt=0000.00000000
DATAFILE DUMP [0/0]
DUMPING COMMON HEADER BLOCK
dbname='tibero' dbid=bc4c00ad version=6.7 cf_seqno=570   filetype=2 fileno=0 blksize=8192 filesize=524288000
DUMPING DATA FILE HEADER BLOCK
tsid=0(type=0, name=SYSTEM),relid=0, root dba=00.00000000, status=0x2,
create=0000.000000001 2025-01-17 11:11:27,
resetlogs=0000.00000000 , 
ckpt=0000.00130854 2025-02-12 10:17:30, cnt=264,prev=263,
backup_begin_ckpt=0000.00115d90 2025-02-11 15:19:10, 
backup_ckpt=0000.00000000 2025-02-12 09:51:06,   backup_begin=0000.0011bcc8 2025-02-12 09:49:01,   backup_ckpt=0000.00000000 2025-02-12 09:51:06,
 
5. Proceed with RECOVERY after confirming integrity
You must perform the Recovery operation only after verifying the backup integrity through Data File Header Dump.
Caution
Recovery may fail if performed with an abnormal HOT Backup.
 
 

Related to