Nonstop Database, HiRDB Version 9 Command Reference

[Contents][Index][Back][Next]

12.4 pdpgbfon processing results

When pdpgbfon terminates normally, its processing results are displayed at the standard output where the command was executed.

Organization of this section
(1) When data pages are read into the global buffer
(2) When index pages are read into the global buffer

(1) When data pages are read into the global buffer

 
pdpgbfon VV-RR     *** BUFFER INFORMATION ***     YYYY-MM-DD hh:mm:ss [1]
 
TABLE NAME : USERA.TBL1 [2]
 [3]  [4]              [5]            [6]           [7]
No.  SERVER           RFGET          READ         RFFLS
  1  bes1             1,275           596             0
  2  bes2             1,271           594             0
  3  bes3             1,273           596             0
 
 8365 20:03:54 un01          KFPL00738-I Pdpgbfon terminated, return code=0
 

Explanation
  1. Header for the processing results
    VV-RR: Version and revision numbers
    YYYY-MM-DD hh:mm:ss: Date and time execution of pdpgbfon started
  2. Name of the resource that was processed
  3. Serially assigned numbers
  4. Names of the server
  5. Reference GET counts#
    Each is the number of times pdpgbfon referenced the global buffer.
    This count is higher than the number of corresponding resource pages used because it includes the management (directory) page reference count. If a referenced page has already been read in the global buffer, no real READ occurs.
  6. Real READ counts#
    Each is the number of input requests issued to the database by pdpgbfon because the target page was not found in the global buffer.
  7. Reference buffer flush counts#
    Each is the number of times an unupdated page was flushed out of the global buffer by the LRU method because a space shortage occurred in the global buffer when pdpgbfon read a page into the global buffer.
    If this value is not 0 when pdpgbfon is executed while the global buffer contains no other resource page information (such as immediately after HiRDB startup), the global buffer is not large enough to read all pages.
#: The maximum count that can be displayed is 4,294,967,295. If this value is exceeded, an overflow occurs.

(2) When index pages are read into the global buffer

 
pdpgbfon VV-RR     *** BUFFER INFORMATION ***     YYYY-MM-DD HH:MM:SS [1]
 
INDEX NAME : USERA.(PRIMARY0000131193)[2]
 [3]  [4]              [5]            [6]           [7]
No.  SERVER           RFGET          READ         RFFLS
  1  bes1                75            69             0
  2  bes2                75            69             0
  3  bes3                75            69             0
 
INDEX NAME : USERA.IDX01
No.  SERVER           RFGET          READ         RFFLS
  1  bes1               525           478             0
  2  bes2               523           476             0
  3  bes3               524           477             0
 
 8373 20:04:04 un01          KFPL00738-I Pdpgbfon terminated, return code=0
 

Explanation
See the explanation in (1) When data pages are read into the global buffer. Even when an index-dedicated global buffer is allocated, the utility uses the global buffer allocated to the RDAREA (if it is not specified, the global buffer specified in the -o option) to access the management (directory) page of the RDAREA that stores the corresponding index. Therefore, if a space shortage occurs in the global buffer allocated to the RDAREA, the reference buffer flush count is displayed even when there is sufficient space in the index-dedicated global buffer.