You use the database condition analysis utility (pddbst command) to execute physical analysis of RDAREAs in order to determine if there are HiRDB files that are full.

Execution example of the database condition analysis utility

RD Area Name   : LOB001
    :
    :
 Freeze Specified : Y
  HiRDB File Name : /rdarea/lob001/file01
   File Size      :     8192 segments   Extent Count :  1/ 24
   Segment        :      8190/      8192
   Freeze Status  : U
  HiRDB File Name : /rdarea/lob001/file02
   File Size      :      8192 segments   Extent Count :  1/ 24
   Segment        :      8000/      8192
   Freeze Status  : F    2001/12/06    20:37:05
  HiRDB File Name : /rdarea/lob001/file03
   File Size      :      8192 segments   Extent Count :  1/ 24
   Segment        :      1000/      8192
   Freeze Status  : U

Explanation

The information in the underlined portions above tells you that the HiRDB file currently being used (where date is being stored currently) is /rdarea/lob001/file03. Therefore, the previous HiRDB file (/rdarea/lob001/file02) has become full.

Remarks

• LOB data is stored in consecutive pages as much as possible, so if data will not fit onto a single page, there might be some pages at the end of the HiRDB file that are not usable, as shown in this example.
• When LOB data is deleted, the page that was used does not become 100% free. This is why the example shows 8,000 out of 8,192 segments.
• When the page of the HiRDB file being used (such as in /rdarea/lob001/file03) is the last page, that HiRDB file is also considered to be full.

The following explains other items in the example that relate to frozen update status:

Freeze Specified: Indicates whether the frozen update command has been executed for the RDAREA:

Y: Frozen update command has been executed.

N: Frozen update command has not been issued.

Freeze Status: Indicates whether the HiRDB file is in frozen update status of permit update status:

F: File is in frozen update status.

U: File is in permit update status.