40.5.4 Items that are output as SQL statement statistical information

1

Type

Type of information that is output:

SQL: SQL statement statistical information

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

N

2

HADB_system_version

Version of the HADB server that output the information to the statistics log file

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Y

3

Timestamp

Date and time the information was output to the statistics log file

The date and time the corresponding information was output to the statistics log file are output in the following format:

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

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Y

4

AP_name

Application identifier

• For a connection from an application program

  The application identifier specified in the adb_clt_ap_name operand in the client definition is output. If the adb_clt_ap_name option is omitted, ******** is output.

• For a connection from a command

  The command name is output.

  In the case of the adbsql command, the application identifier specified in adb_clt_ap_name in the client definition is output.

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Y

5

Connection_information

Connection information

The connection information in the KFAA81000-I message that is output to the message log file when connection was established is output.

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Y

6

Connect_time

Date and time the connection was established

The date and time the corresponding connection was established is output in the following format:

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

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Y

7

SQL_serial_number

SQL statement sequence number since the connection was established

The SQL statement sequence number that is output in the KFAA51000-I^#2 and KFAA51005-I^#3 messages that are output to the message log file.

You can identify the target SQL statement from this SQL statement sequence number.

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

Output format:

• Unsigned 8-byte integer

• Once 18,446,744,073,709,551,615 is reached, the value is set to 0 again.

N

8

SQL_type

SQL statement type^#4

The SQL statement type of the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the same value is output on all lines for that SQL statement. For an SQL statement that did not access any DB areas, the regular value is output.

N

9

SQL_total_time

SQL statement execution time^#5 (microseconds)

Amount of time required to execute the corresponding SQL statement is output.

This value is counted toward the execution time even if the SQL statement terminated abnormally.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 microseconds.

N

10

Fetch_row_cnt

Number of fetched rows^#6

The number of rows retrieved by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 rows.

N

11

Update_row_cnt

Number of rows updated^#7

The number of rows updated by the corresponding SQL statement is output.

The SQL statements subject to counting of the number of rows updated include the INSERT, UPDATE, and DELETE statements.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 rows.

N

12

Hashgrp_area_max_size

Maximum usage of the hash group area^#8 (bytes)

The largest value for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

13

Hashgrp_area_get_cnt

Number of times the hash group area was allocated^#8

The number of times the corresponding SQL statement allocated the hash group area is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

14

Hashtbl_area_max_size

Maximum usage of the hash table area (bytes)

The largest value for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

15

Lock_dbarea_request_cnt

Number of times locked resources (DB areas) were allocated

The number of times the corresponding SQL statement allocated locked resources (data DB areas and system-table DB areas) is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

16

Lock_dbarea_wait_cnt

Number of times allocation of locked resources (DB areas) was placed in wait status

The number of times the allocation of locked resources (data DB areas and system-table DB areas) by the corresponding SQL statement was placed in wait status is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

17

Lock_dbarea_wait_time

Wait time for allocation of locked resources (DB areas) (microseconds)

The amount of time that allocation of locked resources (data DB areas and system-table DB areas) by the corresponding SQL statement was placed in wait status is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 microseconds.

N

18

Lock_table_request_cnt

Number of times locked resources (tables) were allocated

The number of times the corresponding SQL statement allocated locked resources (table to be processed and system tables) is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

19

Lock_table_wait_cnt

Number of times allocation of locked resources (tables) was placed in wait status

The number of times the allocation of locked resources (table to be processed and system tables) by the corresponding SQL statement was placed in wait status is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

20

Lock_table_wait_time

Wait time for allocation of locked resources (tables) (microseconds)

The amount of time that allocation of locked resources (table to be processed and system tables) by the corresponding SQL statement was placed in wait status is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 microseconds.

N

21

DBbuff_dbarea_information_num

DB area information output number

If there are multiple entries for DB area information, a number starting with 1 is output to identify each entry.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

N

22

DBbuff_information_num

Global buffer information output number

If there are multiple entries for global buffer information per DB area, a number starting with 1 is output to identify each entry.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

N

23

DBbuff_dbarea_name

DB area name

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Y

24

DBbuff_name

Global buffer name

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Y

25

DBbuff_page_request_cnt

Number of page requests for the global buffer

The number of times a page was requested with the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

26

DBbuff_page_hit_cnt

Global buffer page hit count

The number of times a page was hit with the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

27

DBbuff_page_hit_rate

Global buffer page hit rate^#10 (%)

The hit rate for the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

N

28

DBbuff_page_put_cnt

Number of times data was written to the global buffer

The number of times data was written with the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

29

DBbuff_page_read_cnt

Number of times files were read into the global buffer

The number of times data was read with the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

30

DBbuff_page_write_cnt

Number of times data was written from the global buffer to files

The number of times data was written to files with the corresponding SQL statement is output (except for range index pages).

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

31

DBbuff_page_rng_request_cnt

Number of range index page requests for the global buffer

The number of requests issued by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

32

DBbuff_page_rng_hit_cnt

Range index page hit count in the global buffer

The hit count for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

33

DBbuff_page_rng_hit_rate

Range index page hit rate in the global buffer^#10 (%)

The hit rate for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

N

34

DBbuff_page_rng_put_cnt

Number of times data was written to range index pages in the global buffer

The number of times data was written with the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

35

DBbuff_page_rng_read_cnt

Number of times files were read into range index pages in the global buffer

The number of times files were read by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

36

DBbuff_page_rng_write_cnt

Number of times data was written from range index pages in the global buffer to files

The number of times data was written to files by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

37

DBbuff_tblscan_request_cnt

Number of page requests for table scan buffers

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The number of times the page requests were issued by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

38

DBbuff_tblscan_hit_cnt

Table scan buffer page hit count^#11

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The hit count for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

39

DBbuff_tblscan_hit_rate

Table scan buffer page hit rate^{#10, #11} (%)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The hit rate for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

N

40

DBbuff_tblscan_read_cnt

Number of times files were read into table scan buffers^#12

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The number of times files were read by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

41

DBbuff_tblscan_failed_cnt

Number of times a buffer shortage occurred in table scan buffer

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The number of times a buffer shortage occurred for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

42

DBbuff_tblscan_insufficient_buff_num

Number of table scan buffer sectors in which a shortage occurred

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The number of buffer sectors in which a shortage occurred for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

43

DBbuff_tblscan_reset_cnt

Number of times table scan buffers were reset

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The number of times table scan buffers were reset by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

44

DBbuff_wrktbl_clt_request_cnt

Number of local work table buffer page requests

The number of the page requests issued by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

45

DBbuff_wrktbl_clt_hit_cnt

Local work table buffer hit count

The hit count for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

46

DBbuff_wrktbl_clt_hit_rate

Local work table buffer hit rate^#10 (%)

The hit rate for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

47

DBbuff_wrktbl_clt_put_cnt

Number of times data was written into the local work table buffer

The number of times data was written by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

48

DBbuff_wrktbl_clt_read_cnt

Number of times files were read into the local work table buffer

The number of times files were read by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

49

DBbuff_wrktbl_clt_write_cnt

Number of times data was written from the local work table buffer to files

The number of times data was written to files by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

50

DBbuff_wrktbl_clt_tbl_cnt

Number of times the local work table buffer was created

The number of times the corresponding SQL statement created the local work table buffer is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

51

DBbuff_wrktbl_clt_sort_merge_cnt

Maximum number of sorting stages for the local work table

The maximum number of sorting stages for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

52

DBbuff_wrktbl_clt_sort_page_max_cnt

Maximum number of work table pages used for sorting the local work table

The largest number of work table pages among all values for the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

53

Log_usrbuf_out_cnt

Flush count due to full user log buffer

The flush count resulting from the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

54

Log_usrfile_max_size

Maximum usage of user log file (bytes)

The largest value for the corresponding SQL statement is output is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

55

DBarea_extension_cnt

DB area automatic extension count^#13

The number of times automatic extension of DB area files (regular files) has occurred in the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

56

Log_usrfile_write_cnt

Number of times user log files were written^#14

The number of times user log files have been written by the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

57

DBbuff_wrktbl_clt_request_fix_cnt

This value is used by the system.^#14

N

58

DBbuff_wrktbl_clt_pagein_fix_cnt

This value is used by the system.^#14

N

59

DBbuff_wrktbl_clt_pageout_fix_cnt

This value is used by the system.^#14

N

60

DBbuff_wrktbl_clt_max_used_blk_num

Maximum number of pages used in the local work table buffer^#14

The largest number of pages used by the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

61

Directory_send_num

This value is used by the system.^#14

N

62

Directory_recv_num

This value is used by the system.^#14

N

63

Log_send_num

This value is used by the system.^#14

N

64

Log_recv_num

This value is used by the system.^#14

N

65

DBbuff_send_num

This value is used by the system.^#14

N

66

DBbuff_recv_num

This value is used by the system.^#14

N

67

Node_com_num

Number of times communication took place between nodes^#14

The number of times communication was performed by the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615.

N

68

Node_com_time

Communication time between nodes^#14 (microseconds)

The time during which the applicable SQL statement communicated.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• The count is reset to 0 once it reaches 18,446,744,073,709,551,615 microseconds.

N

69

Bidx_page_split_cnt

Number of times an index page split occurred in B-tree indexes^#14

The number of times an index page split in B-tree indexes occurred in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

70

Tidx_page_split_cnt

Number of times an index page split occurred in text indexes^#14

The number of times an index page split in text indexes occurred in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

71

Bidx_validation_check_cnt

Number of times validity of row data was checked in retrievals using B-tree indexes^#14

The number of times validity was checked in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

72

Ridx_sgmt_skip_cnt

Number of times table segments were skipped in retrievals using range indexes^#14

The number of times segments were skipped in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

73

Ridx_chunk_skip_cnt

Number of times table chunks were skipped in retrievals using range indexes^#14

The number of times chunks were skipped in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

74

Ridx_chunk_read_cnt

Number of times table chunks were not skipped in retrievals using range indexes^#14

The number of times chunks were not skipped in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

75

Ridx_chunk_judge_cnt

Number of times storage of data values by table chunks in the range satisfying the search condition was checked in retrievals using range indexes^#14

The number of times checking occurred in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

76

Ridx_sgmt_read_cnt

Number of times table segments were not skipped in retrievals using range indexes^#14

The number of times segments were not skipped in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

77

Ridx_sgmt_judge_cnt

Number of times storage of data values by table segments in the range satisfying the search condition was checked in retrievals using range indexes^#14

The number of times checking occurred in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

78

SegmentRel_rthd_max_num

Maximum number of processing real threads used during segment release^#14

The largest number of processing real threads used during segment release in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

79

Csvread_file_cnt

Number of files opened by the ADB_CSVREAD function^#14

The number of files opened by the ADB_CSVREAD function of the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

80

Csvread_file_read_size

Total size of data that was read by the ADB_CSVREAD function^#14 (bytes)

The total size of data that was read by the ADB_CSVREAD function of the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

81

Hashgrp_area_shortage

Occurrence of a hash grouping area shortage^#14

Either of the following values is output:

• Y: A hash grouping area shortage occurred in the applicable SQL statement.

• N: A hash grouping area shortage did not occur in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

N

82

Hashgrp_area_sufficient_size

Size needed to avoid a hash grouping area shortage^#14 (kilobytes)

The size needed to prevent a hash grouping area shortage from occurring in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If an overflow occurs, 18446744073709551615 is output.

N

83

Hashtbl_area_shortage

Occurrence of a hash table area shortage^#14

Either of the following values is output:

• Y: A hash table area shortage occurred in the applicable SQL statement.

• N: A hash table area shortage did not occur in the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

N

84

Syndict_file_access_time

Total access time to the synonym dictionary file^#15 (microseconds)

Total amount of time required for the applicable SQL statement to access the synonym dictionary file is output.

This value is counted toward the access time even if the SQL statement terminated abnormally.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

85

Auditread_file_cnt

Number of files opened by the ADB_AUDITREAD function^#16

The number of files opened by the ADB_AUDITREAD function of the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

86

Auditread_file_read_size

Total size of data that was read by the ADB_AUDITREAD function^#16 (bytes)

The total size of data that was read by the ADB_AUDITREAD function of the applicable SQL statement.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

87

DBbuff_tblscan_read_size

Size of files read into the table scan buffer^#17 (kilobytes)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The size of files read by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

88

DBbuff_tblscan_rthd_min_size

Minimum value of memory in the table scan buffer used by each real thread^{#17, #18} (bytes)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The smallest amount of memory in the table scan buffer used by each real thread of the applicable SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

89

DBbuff_tblscan_rthd_max_size

Maximum value of memory in the table scan buffer used by each real thread^{#17, #18} (bytes)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The largest amount of memory in the table scan buffer used by each real thread of the applicable SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

90

DBbuff_tblscan_use_size

Total memory usage of the table scan buffer during execution of the SQL statement^{#17, #18} (bytes)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The total amount of memory that was used in the table scan buffer during execution of the applicable SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

91

DBbuff_tblscan_insufficient_buff_size

Total amount of memory requested when there was not enough free space in the table scan buffer during execution of the SQL statement^{#17, #18} (bytes)

This item is related to the -k and -v options of the adbbuff operand in the server definition.

The total amount of memory that was requested when there was not enough free space in the table scan buffer during execution of the applicable SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output for each DB area.^#9 If an SQL statement did not access any DB areas, no value is output for that SQL statement.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

92

Hashflt_disabled

Whether the hash filter is invalidated^#19

Either of the following values is output:

• Y: A hash filter is applicable to the corresponding SQL statement, but the hash filter is invalidated.

• N: Other than above

If any part of the hash filter is invalidated, Y is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

N

93

Tbldef_req_cnt

Number of times acquisition of table-definition information was requested^#19

The number of times acquisition of table-definition information was requested by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

94

Tbldef_access_cnt

Number of times table-definition information was acquired from the dictionary table^#19

The number of times table-definition information was acquired from the dictionary table by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

95

Tbldef_cache_access_cnt

Number of times table-definition information was acquired from the table-definition pool^#19

The number of times table-definition information was acquired from the table-definition pool by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

96

Tbldef_cache_register_cnt

Number of times table-definition information was registered to the table-definition pool^#19

The number of times table-definition information was registered by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

97

Tbldef_cache_sweep_cnt

Number of times table-definition information was purged from the table-definition pool^#19

The number of times table-definition information was purged by the corresponding SQL statement is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

• If overflow occurs, 18446744073709551615 is output.

N

98

DBbuff_page_wait_cnt

This value is used by the system.^#20

N

99

Max_sql_rthd_num

Maximum number of SQL processing real threads^#21

The maximum number of SQL processing real threads when the corresponding SQL statement was executed is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

100

Hashtbl_area_size

Size of the hash table area^#21 (megabytes)

The size of the hash table area when the corresponding SQL statement was executed is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N

101

Hashflt_area_size

Size of the hash filter area^#21 (megabytes)

The size of the hash filter area when the corresponding SQL statement was executed is output.

If, for a single SQL statement, there is information about more than one DB area, the value is output only on the first row for that SQL statement. No value is output in the subsequent rows.

Output format:

• Unsigned 8-byte integer

N