GLOBAL_BAD_BLOCK_INFO
GLOBAL_BAD_BLOCK_INFO is executed on the CN to collect statistics on damaged data pages of all instances. The basic information about damaged pages is displayed in the query result. 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 initial users, users with the sysadmin permission, users with the O&M administrator permission in the O&M mode, and monitoring users can view the information. Other users can view the information only after being granted with permissions.
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 current 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 current 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 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot