12.5 Notes

  1. The maximum number of pdpgbfon commands that can be executed concurrently is the same as for the pdrorg command because pdpgbfon executes pdrorg internally. Specifically, the maximum number of pdpgbfon commands that can be executed concurrently equals the maximum number of pdrorg commands that can be executed concurrently minus the number of pdrorg commands that are currently executing.
  2. pdpgbfon cannot process LOB RDAREAs. This means that pdpgbfon cannot process any LOB RDAREA containing an abstract data type or plug-in index.
  3. To terminate pdpgbfon forcibly, use the pdcancel command. Other commands such as the OS's kill command cannot terminate pdpgbfon.
  4. When a shared table or shared index is read, the updatable back-end server and all reference-only back-end servers are processed by pdpgbfon.
  5. Executing pdpgbfon on an RDAREA that has the SCHEDULE attribute and that is not open serves no purposes (because the RDAREA will be closed after the processing).
  6. For a HiRDB/Parallel Server, if a transmission message from the back-end server to pdreclaim is delayed for 1 second or more due to traffic on the communication line, the corresponding back-end server's processing result may not be displayed at the standard output. In such a case, you can check the KFPL00714-I message that is output to the message log file or syslogfile to determine the processing result.
  7. If the target table contains a user-defined column of an abstract data type, pdpgbfon cannot be executed.
  8. Table 12-3 shows the pdpgbfon return codes.

    Table 12-3 Return codes of pdpgbfon

    Return codeDescriptionAction
    0Global buffer read operation was completed.None
    4Buffer miss occurred (some pages were not read), because there were not enough buffer sectors when data was read into the global buffer.If necessary, increase the number of global buffer sectors.
    If a single global buffer is shared among multiple resources, a page of another resource may be read into the global buffer by another job before or during execution of pdpgbfon. In this case, sweeping a page of the other resource out of the global buffer is also treated as a buffer miss; therefore, whether the buffer miss applies to the target resource's page or another resource's page cannot be determined. If you are using only the return code to determine whether or not all pages were read into the global buffer successfully, do not execute any other job until pdpgbfon has terminated.
    8pdpgbfon terminated abnormally (global buffer read operation was cancelled).The table and index status is guaranteed and can be accessed from UAPs even after abnormal termination.
    To re-execute pdpgbfon, see the displayed error message and eliminate the cause of the error.
    12pdrorg terminated abnormally (pdrorg that runs as an extension of pdpgbfon terminated abnormally).The table and index status is guaranteed and can be accessed from UAPs even after abnormal termination.
    To re-execute pdpgbfon, see the displayed error message, eliminate the cause of the error, then re-execute pdpgbfon.
  9. Do not execute a definition SQL statement on a table or index that is being processed by pdpgbfon. If a definition SQL statement is so executed, pdpgbfon terminates abnormally. If pdpgbfon is executing in units of schemas, it processes all tables and indexes that belong to the corresponding schema.
  10. If you selected utf-8 as the character encoding in the pdsetup command, you can use a file with a BOM as the control statements file for pdpgbfon. Note that even when a file with a BOM is used as the control statements file, the BOM is skipped.