40.5.2 List of items that are output as connection operation information
The table below lists the titles of the items (columns) that are output as connection operation information and the content that is output. The columns are output in the order listed in the table.
No. |
Column title |
Information that is output |
Enclosing character |
---|---|---|---|
1 |
Type |
|
N |
2 |
Timestamp |
|
Y |
3 |
Last_execute_time |
|
Y |
4 |
AP_name |
|
Y |
5 |
Connection_num |
|
N |
6 |
Connect_time |
|
Y |
7 |
Tran_start_cnt |
|
N |
8 |
Tran_commit_cnt |
|
N |
9 |
Tran_rollback_cnt |
|
N |
10 |
SQL_execute_wait_total_time |
|
N |
11 |
SQL_execute_wait_cnt |
|
N |
12 |
Multi_stmt_insufficient_thd_cnt |
|
N |
13 |
SELECT_cnt |
|
N |
14 |
SELECT_total_time |
|
N |
15 |
Fetch_row_cnt |
|
N |
16 |
INSERT_cnt |
|
N |
17 |
INSERT_total_time |
|
N |
18 |
UPDATE_cnt |
|
N |
19 |
UPDATE_total_time |
|
N |
20 |
DELETE_cnt |
|
N |
21 |
DELETE_total_time |
|
N |
22 |
Update_row_cnt |
|
N |
23 |
TRUNCATE_TABLE_cnt |
|
N |
24 |
TRUNCATE_TABLE_total_time |
|
N |
25 |
PURGE_CHUNK_cnt |
|
N |
26 |
PURGE_CHUNK_total_time |
|
N |
27 |
Hashgrp_area_max_size |
|
N |
28 |
Hashgrp_area_get_cnt |
|
N |
29 |
Hashtbl_area_max_size |
|
N |
30 |
DBbuff_wrktbl_clt_read_cnt |
|
N |
31 |
DBbuff_wrktbl_clt_write_cnt |
|
N |
32 |
Log_usrbuf_out_cnt |
|
N |
33 |
Log_usrfile_max_size |
|
N |
34 |
DBarea_extension_cnt |
|
N |
35 |
Log_usrfile_write_cnt |
|
N |
36 |
DBbuff_wrktbl_clt_request_fix_cnt |
This value is used by the system. |
N |
37 |
DBbuff_wrktbl_clt_pagein_fix_cnt |
This value is used by the system. |
N |
38 |
DBbuff_wrktbl_clt_pageout_fix_cnt |
This value is used by the system. |
N |
39 |
DBbuff_blk_pagein_cnt |
This value is used by the system. |
N |
40 |
DBbuff_blk_pageout_cnt |
This value is used by the system. |
N |
41 |
DBbuff_blk_read_cnt |
This value is used by the system. |
N |
42 |
DBbuff_blk_write_cnt |
This value is used by the system. |
N |
43 |
Directory_send_num |
|
N |
44 |
Directory_recv_num |
This value is used by the system. |
N |
45 |
Log_send_num |
This value is used by the system. |
N |
46 |
Log_recv_num |
This value is used by the system. |
N |
47 |
DBbuff_send_num |
This value is used by the system. |
N |
48 |
DBbuff_recv_num |
This value is used by the system. |
N |
49 |
Node_com_num |
|
N |
50 |
Node_com_time |
|
N |
51 |
Log_usrfile_reduced_cnt |
|
N |
- Legend:
-
Y: The output value is enclosed in a pair of enclosing characters.
N: The output value is not enclosed in the enclosing character.
- #1
-
The year (YYYY) is output as four digits. The month (MM), day (DD), hour (hh), minute (mm), and second (ss) are each output as two digits. The microsecond (nnnnnn) is output as six digits. If there are not enough digits, leading zeros are added. Δ indicates a single-byte space.
- #2
-
The following figure shows the date and time that are output as the date and time of the previous output:
When connection operation information is output for the first time since connections A and B were established, what is displayed for the date and time of the previous output is the date and time each connection was established. The next time that connection operation information is output, the date and time of the previous output will be the date and time of the last output of the corresponding connection operation information.
- #3
-
This includes both the number of times transactions were started explicitly by application programs and the number of times transactions were started implicitly by the system at the time the HADB server started and during command execution.
- #4
-
This includes both the number of times transactions were terminated explicitly from application programs by issuing the COMMIT or ROLLBACK statement and the following values:
-
Number of times transactions were committed implicitly when definition SQL statements were executed
-
Number of times transactions were rolled back implicitly due to an SQL error
-
Number of times transactions were terminated implicitly by the system during command execution
-
- #5
-
This is the number of rows fetched on the HADB server. If an error occurs in an SQL statement using batch transfer of retrieval results, the displayed value might differ from the actual number of rows fetched by the application program.
The fetched row count does not include the number of rows retrieved when the following commands were executed:
-
adbarchivechunk command
-
adbexport command
-
adbgetcst command
-
adbidxrebuild command
-
adbmergechunk command
-
adbreorgsystemdata command
-
- #6
-
If an error occurs in an SQL statement using batch transfer of retrieval results, the rows that were updated successfully before the error occurred are counted. These rows are counted as updated rows even if the processing is rolled back implicitly.
- #7
-
If local hash grouping processing is applied, as many hash grouping areas are allocated as the number of SQL processing real threads. If local hash grouping processing is applied within a subquery that contains an external reference column, local hash grouping processing is performed as many times as the number of rows outside the subquery. Therefore, as many hash grouping areas are allocated as the value obtained from the following formula:
number-of-rows-in-external-queries × number-of-SQL-processing-real-threads
- #8
-
This does not include automatic extensions for the work table DB area. To determine whether automatic extension has occurred for the work table DB area, check the Wrktbl_page_use_max value in No. 13 in Table 40‒4: Columns output as HADB server statistical information in 40.5.1 Items that are output as HADB server statistical information.