13.7.2 List of items that are output as usage information for DB areas, tables, and indexes

1

Type

Type of information that is output^#6

Used: Usage information for DB areas, tables, and indexes

Used(Shared_lock): Usage information for DB areas, tables, and indexes (if the --shared-lock option is specified)

N

2

Timestamp

Timestamp when the adbdbstatus command was executed^#6

The date and time the adbdbstatus was executed are output in the following format:

"YYYY-MM-DDΔhh:mm:ss"^#1

Y

3

DBarea_name

DB area name^#6

Y

4

DBarea_ID

DB area ID^#6

N

5

DBarea_type

Type of DB area^#6

• dictionary: Dictionary DB area

• system_table: System-table DB area

• data: Data DB area

N

6

Rsv

--

--

7

Page_size

Page size (bytes)^#6

N

8

Segment_size

Segment size (pages)^#6

N

9

DBarea_filename

DB area file name^#6

File path of a DB area file that was allocated in the DB area is output.

• For a regular file

  The absolute path of the DB area file is output.

• For a block special file

  The name of the block special file allocated to the DB area file is output. For a symbolic link, the target of the symbolic link is output.

Y

10

Rsv

--

--

11

Object_type

Schema object type^{#2, #6}

• table: Table

• index: Index

N

12

Schema_name

Schema name^{#2, #6}

The schema name for a dictionary table (base table), system table (base table), or an index defined for such a table is always HADB.

Y

13

Object_identifier

Schema object identifier^{#2, #6}

The table or index identifier is output.

Y

14

Object_ID

Schema object ID^{#2, #6}

The table or index ID is output.

N

15

Chunk_ID

Chunk ID^{#2, #6}

N

16

Chunk_create_time

Timestamp when the chunk was created^{#2, #6}

The date and time the chunk was created are output in the following format:

"YYYY-MM-DDΔhh:mm:ss"^#1

Outputs are different for the following cases:

• For merged chunks, the date and time on which the oldest merge-source chunk was created is output.

• For chunks that were created via current chunk swapping caused by a chunk status change, the date and time when the adbchgchunkstatus command was executed is output.

• For chunks whose status is changed to the normal status by using the adbchgchunkstatus command after having been created as wait status chunks via a background import, the date and time when the adbchgchunkstatus command was executed is output.

• For chunks whose status is not changed to the normal status by using the adbchgchunkstatus command after having been created as wait status chunks via a background import, no value is output for this field.

• For a system table (base table), the date and time the adbinit command was executed or the date and time the adbreorgsystemdata command was last executed are output.

  However, if Pending_delete is indicated in the Chunk_status column, the last execution date and time of the adbreorgsystemdata command that has completed deletion of pre-reorganization data are output. The execution date and time of the adbreorgsystemdata command for which pre-reorganization data remains are not output.

Y

17

Chunk_swap_time

Timestamp when chunks were last swapped^{#2, #6, #7}

The date and time a new chunk was created and became the current chunk are output in the following format:

"YYYY-MM-DDΔhh:mm:ss"^#1

If chunks have not been swapped, no value is output.

Outputs are different for the following cases:

• For merged chunks, the date and time on which the newest current chunk swapping occurred in the merge-source chunks is output.

• For chunks whose status is changed to the normal status by using the adbchgchunkstatus command after having been created as wait status chunks via a background import, and that did not become a current chunk when the status was changed to normal status, the date and time when the adbchgchunkstatus command was executed is output.

• For a system table (base table), the following date and time are output only when Pending_delete is indicated in the Chunk_status column.

  - The last execution date and time of the adbreorgsystemdata command that has created post-reorganization data but that failed to delete pre-reorganization data

Y

18

Chunk_status

Chunk status^{#2, #6, #7}

• Normal: Normal status

• Wait: Wait status

• Pending_delete: Delete-pending status

N

19

Segment_type

Segment type^{#2, #6}

For tables (row store format):

• Base_row: Basic row segment

• Branch_row: Branch row segment

For tables (column store format):

• Column_data: Column-data segment

• Row_data: Row-data segment

For B-tree indexes:

• Lower_page: Lower-page segment of a B-tree index

• Upper_page: Upper-page segment of a B-tree index

For text indexes:

• String_page: String control segment

• Position_page: Position control segment

For range indexes:

• Range_control: DB area file control segment

• Range_index_control: Range control segment

N

20

Used_segments^#3

Number of segments in use^{#4, #6, #7}

The number of segments being used for each segment type or DB area file^#4 is output.

N

21

Used_pages^{#3, #8}

Number of pages in use^{#2, #4, #6}

The number of pages being used for each segment type^#4 is output.

N

22

Total_segments^#3

Total number of segments in the DB area file^{#4, #5, #7}

The number of segments that can be managed, based on the size of the DB area file at the time the adbdbstatus command was executed^#4, is output.

N

23

Initialized_pages^#3

Number of initialized pages in the DB area file^{#4, #5, #7}

This includes the number of directory pages. For details about directory pages, see Page types in Pages in DB area structure (segments and pages) in the HADB Setup and Operation Guide.

N

24

Storage_format

Chunk-data storage format^#2

For tables:

• row: Row store format

• column: Column store format

Other than tables

No value is output.

N