14.3.2 System activity statistical information

This section shows statistical information about the system activity.

pdstedit VV-RR(Object Option) ***** SYSTEM INFORMATION *****
INPUT          :/tmp/stjdata [1]
OUTPUT RANGE   :**/**/** **:**:** - **/**/** **:**:** [2]
-----------------------------------------------------------------------------
HOST = test [3]
-----------------------------------------------------------------------------
EDIT TIME 2012/02/03 09:00:00 - 2012/02/03 10:00:00 [4]
SERVER : ******** [5]                              [6]    [7]    [8]    [9]
                                                 FREQ    MAX    MIN    AVG
                                                 -----  -----  -----  -----
<SCHEDULE>[10]     QUEUE LENGTH[11]                 77      1      1      1
                  MESSAGE LENGTH[12]               77    660    432    615
<PROCESS>[13]      # OF USER SERVER ABORT[14]        0
                  # OF SYSTEM SERVER ABORT[15]      0
                  # OF PROCESS[16]                        48     44     44
                  # OF PROCESS ON SERVICE[17]              8      0      0
                  # OF REQ PROCESS OVER MAX[18]     0
<TRANSACTION>[19]  # OF COMMIT[20]                 242
                  # OF ROLLBACK[21]                12
<NAME>[22]         # OF CACHE HIT[23]                0
                  # OF LOCAL HIT[24]              743
                  # OF LOOK-UP[25]                742
<RPC>[26]          # OF TIME OUT[27]                 0
                  # OF ERROR[28]                    0
                  RESPONSE ON OWN UNIT[29]        192  63.6k    192  4.97k
                  RESPONSE TO OTHER UNIT[30]        0      0      0      0
                  EXEC TIME ON OWN UNIT[31]     1.48k  91.2k      0  1.41k
                  EXEC TIME FROM OTHER UNIT[32]     0      0      0      0
                  # OF SEND TO OWN PRCS[33]         0
                  # OF SEND TO OTHER PRCS[34]     200
                  # OF SEND TO OTHER UNIT[35]       0
                  # OF RECV FROM OWN PRCS[36]       0
                  # OF RECV FROM OTHER PRCS[37]    12
                  # OF RECV FROM OTHER UNIT[38]     0
                  # OF REGISTERED PORTS[39]         0       0     0      0
                  # OF ASSIGNED PORTS[40]           0       0     0      0
<LOCK>[41]         WAIT TIME[42]                    30      97     1     27
                  QUEUE LENGTH[43]                 30       4     1      2
                  # OF DEADLOCK[44]                 0
                  % OF USE LOCK TABLE[45]           5       0     0      0
                  # OF REQUEST WAIT QUEUE[124]  9.56k       1     0      0
                  # OF REQUEST[128]             9.60k
                  # OF REQUEST WAIT[129]           27
                  REQUEST WAIT TIME[130]                  363     2     58
<SHARED MEMORY>[46]STATIC GET SIZE[47]               0       0     0      0
                  STATIC POOL SIZE[48]              0       0     0      0
                  DYNAMIC GET SIZE[49]              0       0     0      0
                  DYNAMIC POOL SIZE[50]             0       0     0      0
                  SIZE EXCEPT GLOBAL BUFFER[51] 63.4M
                  STATIC SIZE[52]               9.08M
                  DYNAMIC SIZE[53]              3.90M
                  SIZE FOR GLOBAL BUFFER[54]    1.77M
<SYNC POINT>[55]   SYNC POINT GET INTERVAL[56]      10    169k 21.0k  75.3k
                  SYNC POINT GET TIME[57]          10   3.00k 1.00k  1.40k
<LOG>[58]          # OF BUFFER FULL[59]              0
                  # OF WAIT THREAD[60]              0
                  OUTPUT BLOCK LENGTH[61]         656    121k   340  3.17k
                  NOT BUS LENGTH[62]              656    121k   340  3.04k
                  # OF BUFFER FOR WAIT I/O[63]    139     100   100    100
                  # OF WRITE TO FILE[64]          671
                  # OF WRITE ERROR[65]              0
                  LOG FILE SWAP TIME[66]            5     159    57    116
                  LOG INPUT DATA LENGTH[67]        10    392k 20.0k   258k
                  # OF READ FROM FILE[68]          15
                  # OF READ ERROR[69]               0
                  FILE WRITE TIME[125]            671    115k 2.46k  19.6k
                  FILE READ TIME[126]              15    144k     9  16.5k
                  # OF BUFFERING[127]           10.4k
                  # OF BUF FLUSH WAIT QUEUE[131]   71       1     1      0
                  # OF BUF FLUSH[132]              71
                  # OF BUF FLUSH WAIT[133]         71
                  BUF FLUSH WAIT TIME[134]               169k 22.8k  31.0k
<DICTIONARY>[70]   # OF TBL-DEF GET REQ[71]        295
                  # OF TBL-CACHE HIT[72]          272
                  # OF CACHED TBL-DEF[73]          27      12     1      6
                  USED TBL-DEF SIZE[74]            23   26.0k 5.60k  9.95k
                  TBL-CACHE SIZE[75]               27    118k 26.0k  79.1k
                  # OF ACCESS PRIV CHECK[76]        0
                  # OF CACHE HIT (AP CHECK)[77]     0
                  # OF CON/DBA DEF GET REQ[78]     45
                  # OF CON/DBA CACHE HIT[79]       43
                  # OF CON/DBA CACHED USER[80]      6       1     1      1
                  DICT SERV TRANS DATA SIZE[81]     0       0     0      0
                  # OF TRANS[82]                    0
                  # OF VIEW DEF GET REQ[83]         0
                  # OF VIEW CACHE HIT[84]           0
                  # OF VIEW CACHED DEF[85]          0
                  USED VIEW SIZE[86]                0       0     0      0
                  VIEW CACHE SIZE[87]               0       0     0      0
                  CACHE-MISS VIEW SIZE[88]          0       0     0      0
                  # OF TYPE-DEF GET REQ[89]         0
                  # OF TYPE-DEF CACHE HIT[90]       0
                  # OF CACHED TYPE-DEF[91]          0       0     0      0
                  TYPE-DEF CACHE SIZE[92]           0       0     0      0
                  TYPE-DEF CACHE TOTAL SIZE[93]     0       0     0      0
                  TYPE-DEF CACHE ALLOC SIZE[94]     4       0     0      0
                  # OF RTN-DEF GET REQ[95]          0
                  # OF RTN-DEF CACHE HIT[96]        0
                  # OF CACHED RTN-DEF[97]           0       0     0      0
                  RTN-DEF CACHE SIZE[98]            0       0     0      0
                  RTN-DEF CACHE TOTAL SIZE[99]      0       0     0      0
                  RTN-DEF CACHE ALLOC SIZE[100]     4    100k   100k   100k
                  # OF PLG-RTN GET REQ[101]         0
                  # OF PLG-RTN CACHE HIT[102]       0
                  # OF REGISTRY GET REQ[103]        0
                  # OF REGISTRY CACHE HIT[104]      0
                  # OF CACHED REGISTRY-DEF[105]     0       0     0      0
                  REGISTRY CACHE SIZE[106]          0       0     0      0
                  REGISTRY CACHE TOTAL SIZE[107]    0       0     0      0
                  DIRECTORY USER CHECK TIME[108]    0       0     0      0
                  GROUP CHECK TIME[109]             0       0     0      0
<FES-BES-DIC(SDS)  # OF SQLOBJ INFO GET[111]       240
INFORMATION>      # OF CACHE HIT (SQLOBJ)[112]     41
[110]             # OF CACHED SQLOBJ[113]         203      65     1     27
                  CACHED SQLOBJ TOTAL SIZE[114]   203    277k 5.00k   137k
                  # OF SWAP OUT SQLOBJ[115]        36
                  REQUEST SQLOBJ SIZE[116]        163   9.44k 2.02k  4.62k
                  # OF STRT INFO GET[117]           0
                  # OF CACHED HIT (STRT)[118]       0
                  # OF CACHED STRT[119]             0       0     0      0
                  CACHED STRT TOTAL SIZE[120]       0       0     0      0
                  # OF SWAP OUT STRT[121]           0
                  REQUEST STRT SIZE[122]            0       0     0      0
                  # OF STRT RECOMPILE[123]          0
-----------------------------------------------------------------------------
FILE KIND   LOG KIND   FIRST                 LAST                       NUM
STJ         sys        2012/02/03 09:30:49   2012/02/03 09:37:00          5
-----------------------------------------------------------------------------

NO FILE KIND:LOG FILE NAME
 LOG KIND             FIRST                 LAST                       NUM
1 STJ      :/tmp/stjdata/pdstj01
 sys                  2012/02/03 09:30:49   2012/02/03 09:31:50          4
 uap                  2012/02/03 09:29:26   2012/02/03 09:31:04         26
 sql                  2012/02/03 09:29:25   2012/02/03 09:31:04        440
 sop                  2012/02/03 09:29:27   2012/02/03 09:31:04         98
 dop                  2012/02/03 09:29:27   2012/02/03 09:31:04         92
 pcd                  ****/**/** **:**:**   ****/**/** **:**:**          0
 obj                  ****/**/** **:**:**   ****/**/** **:**:**          0
 sqh                  ****/**/** **:**:**   ****/**/** **:**:**          0
 buf                  2012/02/03 09:30:00   2012/02/03 09:32:24         21
 fil                  2012/02/03 09:30:00   2012/02/03 09:32:24        224
 dfw                  2012/02/03 09:29:30   2012/02/03 09:32:24         71
 idx                  2012/02/03 09:30:00   2012/02/03 09:32:24          7
 fsv                  ****/**/** **:**:**   ****/**/** **:**:**          0
 hba                  ****/**/** **:**:**   ****/**/** **:**:**          0
2 STJ      :/tmp/stjdata/pdstj02
 sys                  2012/02/03 09:34:58   2012/02/03 09:37:00          6
 uap                  2012/02/03 09:34:00   2012/02/03 09:36:17         19
 sql                  2012/02/03 09:33:59   2012/02/03 09:36:17        456
 sop                  2012/02/03 09:34:02   2012/02/03 09:36:16         65
 dop                  2012/02/03 09:34:02   2012/02/03 09:36:16         96
 pcd                  ****/**/** **:**:**   ****/**/** **:**:**          0
 obj                  ****/**/** **:**:**   ****/**/** **:**:**          0
 sqh                  ****/**/** **:**:**   ****/**/** **:**:**          0
 buf                  2012/02/03 09:34:10   2012/02/03 09:36:19         27
 fil                  2012/02/03 09:34:10   2012/02/03 09:36:19        288
 dfw                  2012/02/03 09:34:04   2012/02/03 09:36:19         41
 idx                  2012/02/03 09:34:10   2012/02/03 09:36:19          9
 fsv                  ****/**/** **:**:**   ****/**/** **:**:**          0
 hba                  ****/**/** **:**:**   ****/**/** **:**:**          0

Explanation
  1. Name of input statistics unload file or name of the directory containing the input statistics unload file (maximum of 58 bytes)
  2. Output range (output start date/time to output end date/time)
  3. Name of host requesting output of system activity statistical information
  4. Edit period (collection start time to collection end time)
  5. Server name. If sys was specified in the -k option, ******** is displayed
  6. Number of occurrences of each item
  7. Maximum values
  8. Minimum values
  9. Average values
  10. Schedule information
  11. Number of requests in the schedule queue
    This information includes the number of requests to the server registered in the schedule queue and the maximum, minimum, and average numbers of those requests in the schedule queue at any one time.
  12. Length of schedule message (bytes)
    This is the number of messages containing the server processing requests and the maximum, minimum, and average message lengths.
  13. Process information
  14. Number of times the server terminated abnormally
    This is the number of times the single server, front-end server, dictionary server, and back-end server processes terminated abnormally.
  15. Number of times the HiRDB internal server terminated abnormally
    This is the number of times the HiRDB's internal server processes terminated abnormally.
  16. Number of internal server processes that were used by servers and HiRDB
    This is the number of internal server processes used by a single server, front-end server, dictionary server, back-end server, and HiRDB.
  17. Number of server processes in service
    This is the number of server processes currently providing services.
  18. Number of service requests exceeding the maximum number of startup processes
    This is the number of service requests that exceeds the maximum number of processes that can be started. For the single server or front-end server, the maximum number of startup processes is the value of the pd_max_users operand; for the back-end server, it is the value of the pd_max_bes_process operand; for the dictionary server, it is the value of the pd_max_dic_process operand. The number of service requests may be greater than the actual number of excess requests because it includes the retried requests.
  19. Transaction information
  20. Commits count
    This is the number of transactions that committed among all the transactions processed at the single server, front-end server, dictionary server, and back-end server.
  21. Rollbacks count
    This is the number of transactions that rolled back among all the transactions processed at the single server, front-end server, dictionary server, and back-end server.
  22. Name server information
  23. Information used by the system (not by users)
  24. Information used by the system (not by users)
  25. Information used by the system (not by users)
  26. RPC information
  27. Information used by the system (not by users)
  28. Information used by the system (not by users)
  29. Service response time for local unit's servers (in 100 microseconds)#2
    This information includes the number of service responses for the local unit's servers and the maximum, minimum, and average response time.
  30. Service response time for remote unit's servers (in 100 microseconds)#2
    This information includes the number of service responses for the remote unit's servers and the maximum, minimum, and average response time.
  31. Execution time per service from local unit's servers (in 100 microseconds)#2
    This information includes the number of executions per service from the local unit's servers and the maximum, minimum, and average execution time.
  32. Execution time per service from remote unit's servers (in 100 microseconds)#2
    This information includes the number of executions per service from the remote unit's servers and the maximum, minimum, and average execution time.
  33. Number of SENDs to local process
    This is the number of times SEND (message send) was executed on the local process.
  34. Number of SENDs to other processes on local unit
    This is the number of times SEND (message send) was executed on other processes on the local unit.
  35. Number of SENDs to remote unit
    This is the number of times SEND (message send) was executed on the remote unit.
  36. Number of RECEIVEs from local unit
    This is the number of times RECEIVE (message receive) was executed from the local unit.
  37. Number of RECEIVEs from other processes on local unit
    This is the number of times RECEIVE (message receive) was executed from other processes on the local unit.
  38. Number of RECEIVEs from remote unit
    This is the number of times RECEIVE (message receive) was executed from the remote unit.
  39. Number of HiRDB-reserved ports used
    This is the number of port numbers actually used among all the port numbers reserved by HiRDB, and the maximum, minimum, and average values of port numbers.
  40. Number of additional ports automatically allocated by the OS when the system ran out of ports reserved by HiRDB
    This is the number of ports automatically allocated by OS when all the port numbers reserved by HiRDB were in use, and the maximum, minimum, and average values of port numbers.
  41. Lock information
  42. Lock release wait time (milliseconds)#2
    This information includes the number of lock requests in the server that resulted in the lock release wait status because the requested resource was already locked by another user, and the maximum, minimum, and average wait time.
  43. Number of lock-release waits (number of users)
    This information includes the number of users in the server that resulted in the lock release wait status because the requested resource was already locked by another user, and the maximum, minimum, and average numbers of the users placed in lock release wait status.
  44. Deadlocks count
    This is the number of times a lock request resulted in deadlock in the server.
  45. Usage rate of pool partition for locking (%)
    This information includes the number of times the usage rate of the pool partition for locking was obtained, and the maximum, minimum, and average usage rates of the pool partition for locking when those events occurred. The usage rate of the pool partition for locking is obtained at the following times:
    • When a specific amount of time has elapsed since statistical information about system activities was last output to the statistics log file; this amount of elapsed time is determined as follows:
      [Figure]If the pdstbegin operand was specified or the pdstbegin command was used to start collection of statistical information, the usage rate of the pool partition for locking is obtained when the time (in minutes) specified in the pdstbegin operand or the -m option of the pdstbegin command has elapsed.
      [Figure]If Y was specified in the pd_statistics operand and the pdstbegin operand was omitted, the usage rage of the pool partition for locking is obtained every 10 minutes.
    • When the usage rate of the pool partition for locking has increased by 5% since the last time the usage rate was obtained.
    • When HiRDB terminates normally.
    • When the pdstjsync command is executed.
    If there are multiple pool partitions for locking (2 or a greater value was specified in the pd_lck_pool_partition or pd_fes_lck_pool_partition operand), the usage rate is calculated and output for each pool partition for locking.
  46. Shared memory information
  47. Information used by the system (not by users)
  48. Information used by the system (not by users)
  49. Information used by the system (not by users)
  50. Information used by the system (not by users)
  51. Size of shared memory allocated for the server and HiRDB internal server (bytes)
    This is the size of shared memory allocated on the unit for the server and HiRDB internal server.
  52. Size of shared static memory (bytes)
    Of the memory allocated on the unit for the server or HiRDB internal server, this is the size allocated as the shared static memory.
  53. Size of shared dynamic memory (bytes)
    Of the memory allocated on the unit for the server or HiRDB internal server, this is the size allocated as the shared dynamic memory.
  54. Allocation size of shared memory for global buffer pool (bytes)
    This is the size of the global buffer allocated in the server (if the global buffer uses multiple shared memory segments, this is the total size).
  55. Synchronization point information
  56. Synchronization point dump interval (milliseconds)#2
    This information includes the number of times a synchronization point dump is collected and the maximum, minimum, and average intervals between two synchronization point dump collections.
  57. Synchronization point dump time (milliseconds)#2
    This information includes the number of synchronization point dumps and the maximum, minimum, and average time required for collecting a synchronization point dump. If this value is large, it may have taken a long time to validate the synchronization point dump because a transaction requiring a long processing time was executed concurrently.
  58. Log information
  59. Buffer-fulls count
    This is the number of times the log output buffer became full at the HiRDB system or server.
  60. Waits count due to a shortage of current buffer
    This is the number of times threads were placed in wait status during output operation on the log input/output buffer at the HiRDB system or server because the log input/output buffer was being used for output operation on the system log file.
  61. Output block length (bytes)
    This information includes the number of times data was output from the log input/output buffer to the system log file at the HiRDB system or server and the maximum, minimum, and average block lengths.
    For bus output, this is the total length. If a file output request is issued for a log buffer while file output is underway on another log buffer, HiRDB keeps storing the remaining system log in the log buffer requested for file output until the current log buffer being output is released. When the current log buffer is released, HiRDB then outputs both at the same time. This is called bus output.
  62. Data length excluding the bus output (bytes)
    This information includes the number of times data was output from the log input/output buffer to system log file, excluding the bus output, at the HiRDB system or server, and the maximum, minimum, and average log block lengths.
  63. Number of buffer sectors placed in output wait status
    This information includes the number of log output buffer sectors waiting for completion of output to the system log file when output to the system log file was completed at the HiRDB system or server, and the maximum number of such buffer sectors [Figure] 100, the minimum number of such buffer sectors [Figure] 100, and the average number of such buffer sectors [Figure] 100.
    The maximum, minimum, and average numbers of buffer sectors are obtained by dividing the displayed maximum, minimum, and average values by 100.
  64. Number of times data was written into file
    This is the number of times data was written into system log file at the HiRDB system or server.
    This value includes the number of write operations executed to change the status of system log file. If dual system log files are used, the value also includes the number of write operations for each file version. This value also includes not only the number of system log block write operations, but also the number of file write operations that occur when the file status changes due to swapping of system log files. If the system log parallel output facility is used, data is written to the dual system log files in parallel. Therefore, a completion of write operations in both systems is counted as 1.
  65. Number of times write error occurred
    This is the number of times a system log file write error occurred at the HiRDB system or server.
  66. Log file swapping time (milliseconds)#2
    This information includes the number of times swapping occurred on the system log files at the HiRDB system or server, and the maximum, minimum, and average time elapsed before system log files were swapped.
  67. Length of log input data (bytes)
    This information includes the number of logged entries made from the system log file during rollback at the HiRDB system or server, and the maximum, minimum, and average lengths of logged data.
  68. File reads count
    This is the number of times logged data was read from the system log file during rollback at the HiRDB system or server.
  69. Number of read errors
    This is the number of times a system log file read error occurred at the HiRDB system or server.
  70. Dictionary information
  71. Number of table definition information acquisition requests
    This is the number of times table manipulation was executed in the single server or front-end server. If the automatic numbering facility is used, the operation of the sequence generators is also included in this value.
  72. Table definition information buffer hits count
    This is the number of times requested table definition information was found in the table definition information buffer in the single server or front-end server. If the automatic numbering facility is used, the operation of the sequence generators is also included in this value.
    If the table definition information buffer hits count is less than the number of table definition information acquisition requests, the size of the table definition information buffer should be reevaluated.
  73. Number of table definition information items in the table definition information buffer
    This is the number of table definition information items buffered in the table definition information buffer in the single server or front-end server, and the maximum, minimum, and average numbers of table definition information items. If the automatic numbering facility is used, the operation of the sequence generators is also included in this value.
  74. Length of table definition information placed in the table definition information buffer (bytes)
    This information includes the number of table definition information items placed in the table definition information buffer in the single server or front-end server, and the maximum, minimum, and average sizes of the table definition information buffer used per table definition information item. If the automatic numbering facility is used, the operation of the sequence generators is also included in this value.
  75. Size of table definition information buffer used (bytes)
    This information includes the number of table definition information items placed in the table definition information buffer in the single server or front-end server, and the maximum, minimum, and average values of the total length of the table definition information. If the automatic numbering facility is used, the operation of the sequence generators is also included in this value.
    If the maximum value is extremely small compared to the size of the table definition information buffer, the table definition information buffer may be too large. In this case, you should reevaluate the size of this buffer.
  76. Table access privilege information acquisitions count
    This is the number of times table access privilege was acquired to manipulate a table at the single server or front-end server.
  77. Table access privilege information buffer hits count
    This is the number of times the requested table access privilege was found in the table access privilege information buffer at the single server or front-end server.
    If this value is extremely small compared to the acquisitions count, privileges may be granted to more than 100 users per table. In this case, you should evaluate whether PUBLIC privileges can be granted for the corresponding table.
  78. Number of user privilege information acquisition requests
    This is the number of times a CONNECT request was issued from a UAP to a single server or front-end server.
  79. User privilege information buffer hits count
    This is the number of times the requested user privilege information was found in the user privilege information buffer for the CONNECT requests issued from a UAP to a single server or front-end server.
    If this value is less than the number of user privilege information acquisition requests, you should reevaluate the size of the user privilege information buffer.
  80. Number of user privilege information buffer users
    This information includes the number of times the requested user privilege information was placed in the user privilege information buffer for the CONNECT requests issued from a UAP to a single server or front-end server, and the maximum, minimum, and average numbers of such users.
    If the maximum value times 34 (bytes) is extremely small compared to the size of the user privilege information buffer, you should reevaluate the size of the user privilege information buffer.
  81. Length of data handled during communication with dictionary server (bytes)
    This information includes the number of table definition information acquisition requests when the requested table definition information was not found in the table definition information buffer at the front-end server, and the maximum, minimum, and average lengths of data handled during communication with the dictionary server.
  82. Dictionary server communications count
    This is the number of times communication was established with the dictionary server to acquire table definition information because the requested table definition information was not found in the table definition information buffer at the front-end server.
  83. Number of view analysis information acquisition requests
    This is the number of times view analysis information was acquired to manipulate a view at the single server or front-end server.
  84. View analysis information buffer hits count
    This is the number of times the requested view analysis information was found in the view analysis information buffer at the single server or front-end server.
    If the view analysis information buffer hits count is less than the number of view analysis information acquisition requests, you should reevaluate the size of the view analysis information buffer.
  85. Number of analysis information items in view analysis information buffer
    This is the number of view analysis information items placed in the view analysis information buffer.
  86. Size of view analysis information buffer used per view definition information item (bytes)
    This information includes the number of times view analysis information was collected in the view analysis information buffer and the maximum, minimum, and average sizes of the view analysis information buffer used per view analysis information item. If the number of times view analysis information was collected in the view analysis information buffer does not match the buffer miss count (VIEW DEF GET REQ - VIEW CACHE HIT), the view analysis information buffer is not sufficient. Perform tuning by referencing Tuning the buffer length for view analysis information in the HiRDB Version 9 System Operation Guide.
  87. Size of view analysis information buffer used (bytes)
    This information includes the number of view analysis information items in the view analysis information buffer, and the maximum, minimum, and average sizes.
    If the maximum value is extremely small compared to the size of the view analysis information buffer, the view analysis information buffer may be too large. In this case, you should evaluate whether the size of the view analysis information buffer is reasonable.
  88. Size of view analysis information resulting in buffer misses (bytes)
    Zero is output as the count, maximum, minimum, and average values. This information need not be considered because the size of view analysis information that resulted in a buffer misses is not used for tuning. To check the buffer miss count, use the formula VIEW DEF GET REQ - VIEW CACHE HIT.
  89. Number of type definition information acquisition requests
    This is the number of times type definition was referenced at the single server or front-end server.
  90. User-defined type information buffer hits count
    This is the number of times the requested type definition information was found in the user-defined type information buffer at the single server or front-end server.
  91. Number of type definition information items in the user-defined type information buffer
    This is the number of table definition information items buffered in the user-defined type information buffer in the single server or front-end server, and the maximum, minimum, and average numbers of type definition information items.
  92. Size of user-defined type information buffer used per type definition information item (bytes)
    This information includes the number of type definition information items placed in the user-defined type information buffer at the single server or front-end server, and the maximum, minimum, and average sizes of the user-defined type information buffer used per type definition information item.
  93. Total size of user-defined type information buffer used (bytes)
    This information includes the number of type definition information items acquired at the single server or front-end server, and the maximum, minimum, and average sizes of the user-defined type information buffer.
    If the maximum value is less than the size of the allocated user-defined type information buffer, the buffer size may be too large. You should reevaluate the size of the user-defined type information buffer.
  94. Size of allocated user-defined type information buffer (bytes)
    This information includes the number of buffer sectors allocated for user-defined type information at the single server or front-end server, and the maximum, minimum, and average sizes of the user-defined type information buffer. In this case, the maximum, minimum, and average values are the same.
  95. Number of routine definition information acquisition requests
    This is the number of times routine definition was referenced at the single server or front-end server.
  96. Routine definition information buffer hits count
    This is the number of times the requested routine definition information was found in the routine definition information buffer at the single server or front-end server.
    If the routine definition information buffer hits count is less than the number of routine definition information acquisition requests, you should reevaluate the size of the routine definition information buffer.
  97. Number of routine definition information items in the routine definition information buffer
    This is the number of routine definition information items buffered in the routine definition information buffer in the single server or front-end server, and the maximum, minimum, and average numbers of routine definition information items.
  98. Size of routine definition information buffer used per routine definition information item that was placed in the routine definition information buffer (bytes)
    This information includes the number of routine definition information items placed in the routine definition information buffer at the single server or front-end server, and the maximum, minimum, and average sizes of the routine definition information buffer per routine definition information item.
  99. Total size of routine definition information buffer (bytes)
    This information includes the number of items placed in the routine definition information buffer at the single server or front-end server, and the maximum, minimum, and average sizes of the routine definition information buffer used.
  100. Size of allocated routine definition information buffer (bytes)
    This information includes the number of buffer sectors allocated for routine definition information at the single server and front-end server, and the maximum, minimum, and average sizes of the routine definition information buffer. In this case, the maximum, minimum, and average values are the same.
  101. Number of routine definition acquisition requests for plug-in function
    This is the number of times a plug-in function's routine was referenced at the single server or front-end server.
  102. Plug-in function's routine definition information buffer hits count
    This is the number of times a requested plug-in function's routine information was found in the routine definition information buffer at the single server or front-end server.
    If the plug-in function's routine definition information buffer hits count is less than the number of routine definition acquisition requests for the plug-in function, you should reevaluate the size of the routine definition information buffer.
  103. Number of registry information acquisition requests
    This is the number of times registry information was referenced at the single server or front-end server.
  104. Registry information buffer hits count
    This is the number of times the requested registry information was found in the registry information buffer at the single server or front-end server.
    If the registry information buffer hits count is less than the number of registry information acquisition requests, you should reevaluate the size of the registry information buffer.
  105. Number of registry information items in the registry information buffer
    This is the number of registry information items buffered in the registry information buffer in the single server or front-end server, and the maximum, minimum, and average numbers of registry information items.
  106. Size of registry information buffer per registry information item (bytes)
    This information includes the number of registry information items placed in the registry information buffer at the single server or front-end server, and the maximum, minimum, and average sizes of the registry information buffer per registry information item.
  107. Total size of registry information buffer used (bytes)
    This information includes the number of registry information items placed in the registry information buffer at the single server or front-end server, and the maximum, minimum, and average sizes of the registry information buffer used.
  108. User authentication time for directory registration (microseconds)#2
    This information is used internally by the system.
  109. Group checking time (microseconds)#2
    This information is used internally by the system.
  110. SQL object information for single server, front-end server, back-end server, or dictionary server
  111. Number of SQL object acquisition requests
    This is the number of times an SQL object was acquired at the single server, front-end server, back-end server, or dictionary server.
  112. SQL object buffer hits count
    This is the number of times a requested SQL object was found in the SQL object buffer at the single server, front-end server, back-end server, or dictionary server.
    If the SQL object buffer hits count is less than the number of SQL object acquisition requests, you should reevaluate the size of the SQL object buffer.
  113. Number of SQL objects in the SQL object buffer
    This information includes the number of SQL objects in the SQL object buffer at the single server, front-end server, back-end server, and dictionary server, the information update count for the number of SQL objects, and the maximum, minimum, and average values. The information update count is the number of times one of the maximum, minimum, or average number of SQL objects was updated.
  114. Total length of SQL objects in the SQL object buffer (bytes)
    This information includes the information update count for the total size of SQL objects in the SQL object buffer at the single server, front-end server, back-end server, and dictionary server, and the maximum, minimum, and average values. The information update count is the number of times one of the maximum, minimum, or average value of this total size of SQL objects was updated.
    Note
    HiRDB manages the SQL object buffer in increments of 1 kilobyte. Therefore, each SQL object uses an SQL object buffer whose size is at least the size of the SQL object rounded up to a full kilobyte. The sum of these SQL object sizes is not the total size of the space used by the SQL objects. There may not be free space in the SQL object buffer even when the sum of the SQL object sizes is less than the value specified as the size of the SQL object buffer.
  115. Number of SQL objects taken out of the SQL object buffer
    This is the number of SQL objects that were invalidated in the SQL object buffer to make space for new SQL objects at the single server, front-end server, back-end server, or dictionary server.
  116. Length of SQL object (bytes)
    This information includes the number of SQL objects placed in the SQL object buffer at the single server, front-end server, back-end server, or dictionary server, and the maximum, minimum, and average lengths of the SQL object.
  117. Number of stored procedure object acquisition requests
    This is the number of requests issued to place stored procedure objects in the SQL object buffer at the single server or front-end server.
    For the back-end server and dictionary server, this value is included in the number of SQL object acquisition requests.
  118. SQL object buffer hits count for stored procedure objects
    This is the number of times a requested stored procedure object was found in the SQL object buffer at the single server or front-end server.
    If the SQL object buffer hits count for stored procedure objects is less than the number of stored procedure object acquisition requests at the single server or front-end server, you should reevaluate the size of the SQL object buffer.
    For the back-end server and dictionary server, this value is included in the SQL object buffer hits count.
  119. Number of stored procedure objects placed in the SQL object buffer
    This is the number of stored procedure objects buffered in the SQL object buffer in the single server or front-end server, and the maximum, minimum, and average numbers of objects.
    For the back-end server and dictionary server, this value is included in the number of SQL objects in the SQL object buffer.
  120. Total length of stored procedure objects in the SQL object buffer
    This information includes the number of times a stored procedure object was acquired from the SQL object buffer at the single server or front-end server, and the maximum, minimum, and average lengths of such objects.
    For the back-end server and dictionary server, this value is included in the total length of SQL objects in the SQL object buffer.
  121. Number of stored procedure objects taken out of the SQL object buffer
    This is the number of stored procedure objects invalidated in the SQL object buffer to create space for new stored procedure objects at the single server or front-end server.
    For the back-end server and dictionary server, this value is included in the number of SQL objects taken out of the SQL object buffer.
  122. Length of stored procedure objects (bytes)
    This information includes the number of stored procedure objects placed in the SQL object buffer at the single server or front-end server, and the maximum, minimum, and average lengths of such objects.
    For the back-end server and dictionary server, this value is included in the length of SQL objects.
  123. Number of times stored procedure objects were recompiled
    This is the number of times stored procedure objects were recompiled due to changes made to indexes at the single server or front-end server.
    This information is not applicable to the back-end server or dictionary server.
  124. Number of thread-to-thread lock-release waits for the pool partition for locking
    If there are multiple pool partitions for locking (a value of 2 or greater was specified in the pd_lck_pool_partition or pd_fes_lck_pool_partition operand), the numbers of thread-to-thread lock-release waits obtained for all pool partitions for locking are totaled, and then the maximum, minimum, and average values are output.
  125. File write operation time#2
    This information includes the maximum, minimum, and average times required to write data to the system log file in the HiRDB system or server.
    This value include not only the time required to output system logs to a file but also the time required for write operations when system log file status changes occur. If dual system log files are used, the time required for write operations in both systems is included. This value also includes not only the time required for writing system log blocks, but also the time required for write operations when file status changes due to system log file swapping occur. If the system log parallel output facility is used, data is written to dual system log files in parallel, which means that the calculation is based on the amount of time required until write operations are completed in both systems since write operation began in one of the systems. If you process an input statistics unload file obtained by a HiRDB version earlier than 08-04 using a statistics analysis utility whose version is 08-04 or later, the utility displays 0 as the average and maximum values and 4.29G as the minimum value.
  126. File read operation time#2
    This information includes the maximum, minimum, and average times spent reading data from the system log file in the HiRDB system or server during rollback. If you process an input statistics unload file obtained by a HiRDB version earlier than 08-04 using a statistics analysis utility whose version is 08-04 or later, the utility displays 0 as the average and maximum values and 4.29G as the minimum value.
  127. Log output buffer write operations count
    This is the number of times data was written to the log output buffer in the HiRDB system or server. If you process an input statistics unload file obtained by a HiRDB version earlier than 08-04 using a statistics analysis utility whose version is 08-04 or later, the utility displays 0 as the count.
  128. Number of thread-to-thread lock requests for the pool partitions for locking
    If there are multiple pool partitions for locking (a value greater than 1 was specified in the pd_lck_pool_partition or pd_fes_lck_pool_partition operand), the numbers of thread-to-thread lock-release waits obtained for all pool partitions for locking are totaled, and then the maximum, minimum, and average values are output.
  129. Number of thread-to-thread lock-release waits for the pool partition for locking
    If there are multiple pool partitions for locking (a value greater than 1 was specified in the pd_lck_pool_partition or pd_fes_lck_pool_partition operand), the numbers of thread-to-thread lock-release waits obtained for all pool partitions for locking are totaled, and then the maximum, minimum, and average values are output.
  130. Thread-to-thread lock-release wait time for the pool partition for locking (microseconds)#1, #2
    This information is output if the pdstbegin -w command was used to obtain the thread-to-thread lock-release wait time. If the thread-to-thread lock-release wait time was not obtained, zero is output.
    If there are multiple pool partitions for locking (a value greater than 1 was specified in the pd_lck_pool_partition or pd_fes_lck_pool_partition operand), the numbers of thread-to-thread lock-release waits obtained for all pool partitions for locking are totaled, and then the maximum, minimum, and average values are output.
  131. Length of log flush queue
  132. Number of log flush requests
  133. Number of log flush waits
  134. Log flush request time#1, #2
    This information is output when the pdstbegin -w command was used to obtain the thread-to-thread lock-release wait time. If the thread-to-thread lock-release wait time was not obtained, zero is output.
#1
Because the precision of the displayed values depends on the OS and the hardware being used, a displayed value might be smaller than the actual value.
#2
If a negative value is obtained because, for example, the OS time was moved back, a value of 0 is output as the statistical information. For a reason such as this, the displayed value might be smaller than the actual value.