Updated on 2025-08-05 GMT+08:00

GLOBAL_BAD_BLOCK_INFO

GLOBAL_BAD_BLOCK_INFO is executed on the CN to collect statistics on damaged data pages of all instances. The queried result displays basic information about damaged pages. The execution result on the DN is empty. Based on the information, you can use the page detection and repair function in Data Damage Detection and Repair Functions to perform further repair operations. By default, only the initial user, users with the SYSADMIN permission, users with the OPRADMIN permission in the O&M mode, and monitoring users can view the information. Other users can view the information only after being granted permissions.

Table 1 GLOBAL_BAD_BLOCK_INFO columns

Name

Type

Description

node_name

text

Information about the node where the current damaged page is located.

spc_node

oid

ID of the tablespace corresponding to the current damaged page.

db_node

oid

ID of the database corresponding to the current damaged page.

rel_node

oid

Relfilenode of the relation corresponding to the current damaged page.

bucket_node

integer

Bucket node of the damaged page. It is set to –1 for a non-segment-page table and to a value other than 0 for a segment-page table. This column is used to specify whether a table is a segment-page table during repair.

block_num

oid

Page number of the current damaged page.

fork_num

integer

File forknum of the current damaged page.

file_path

text

Relative path of the damaged page. The logical path instead of the actual file is displayed for a segment-page table.

check_time

timestamp with time zone

Time when an error is detected on the current damaged page.

repair_time

timestamp with time zone

Time when the current damaged page is repaired.