The utility displays the storage condition of all segments and all pages in an RDAREA. From the displayed analysis results, you can determine the RDAREA's utilization efficiency and capacity status.

The following shows the results of condition analysis by RDAREA (physical analysis):

• In text format (-a option is omitted)
  

  pddbst VV-RR(Object Option) ** RD Area Physical Analysis ** 2002/03/29 16:40:10 [1] Max Sum Segment : 150 [2] Max Sum Page : 750 [3] RD Area Count : 1/ 1 [4] -------------------------------------------------------------------------------- RD Area Name : USER_RDAREA_1 [5] Server : BES01 [6] Original RD Area Name : USER_RDAREA_1 [30] Generation Number : 0[31] Replica RD Area Count : 0[32] [33] [34] [35] [36] History1 Hold Status : Hold Code : 0 Hold Time : History2 Hold Status : Hold Code : 0 Hold Time : Unused Segment: 98 [7] Segment Size : 5 Pages[8] Page Size : 4096 Bytes[9] Used(Full) Used( Full) Sum [10] [11] [12] [13] [14] Segment 35%( 0%) 52( 0) 150 [15] [16] [17] [18] [19] Page 35%( 0%) 256( 0) 750 Auto Extend Use : USE[20] Auto Extend Segment : 4 [21] Auto Extend Status : NOSUP[22] Error Code : 0 [23] HiRDB File Name : c:\dbarea\rdsys04\u_rd20_1 [24] File Size : 5 segments[25] Extent Count : 1/ 24 [26] HiRDB File Name : c:\dbarea\rdsys04\u_rd20_2 File Size : 6 segments Extent Count : 1/ 24 HiRDB File Name : c:\dbarea\rdsys04\u_rd20_3 File Size : 18 segments Extent Count : 1/ 24 RD Area Name : USER_RDLOB_1 Server : BES01 Original RD Area Name : USER_RDLOB_1 Generation Number : 0 Replica RD Area Count : 0 History1 Hold Status : Hold Code : 0 Hold Time : History2 Hold Status : Hold Code : 0 Hold Time : Unused Segment: 770( 770) Segment Size : 1 Pages Page Size : 8192 Bytes Used Used Sum Segment 93% 10230 11000 [27] [28] Segment Over : N Last Segment : 10230/ 11000 [29] Lobmap Over : N Freeze Specified : Y [37] Auto Extend Use : USE Auto Extend Segment : 10 Auto Extend Status : NOSUP Error Code : 0 HiRDB File Name : c:\dbarea\rdsys04\u101 File Size : 4000 segments Extent Count : 1/ 24 Segment : 4000/ 4000 Freeze Status : U[38] ****/**/** **:**:** [39] HiRDB File Name : c:\dbarea\rdsys04\u201 File Size : 5000 segments Extent Count : 1/ 24 Segment : 5000/ 5000 Freeze Status : F 2002/03/29 16:38:19 HiRDB File Name : c:\dbarea\rdsys04\u301 File Size : 2000 segments Extent Count : 1/ 24 Segment : 1230/ 2000 Freeze Status : U ****/**/** **:**:**

Explanation

RDAREA information is displayed in ascending order of the RDAREA names. HiRDB file information is displayed in the order of the physical file IDs.

1. Date and time of completion of acquisition of the information required for this condition analysis, in the format YYYY/MM/DD hh:mm:ss:
   YYYY: Year. MM: Month. DD: Date. hh: Hour. mm: Minute. ss: Second.
   
2. Maximum total number of segments in the analyzed RDAREAs.
3. Maximum total number of pages in the analyzed RDAREAs.
4. Number of specified RDAREAs and number of RDAREAs analyzed successfully.
5. Name of an analyzed RDAREA.
6. Name of the server managing the RDAREA.
7. Total number of unused segments in the RDAREA. The parentheses enclose the total number of unused segments in the HiRDB files that are not in the frozen update status in the corresponding RDAREA.
8. Segment size (number of pages per segment).
9. Page size (in bytes).
10. Percentage ratio of used segments:
    number of used segments/value of 14 100 (%)
    
11. Percentage ratio of full segments:
    number of full segments/value of 14 100 (%)
    
12. Number of used segments.
13. Number of full segments.
14. Total number of segments in the RDAREA (number of used segments + number of unused segments).
15. Percentage ratio of used pages:
    number of used pages/value of 19 100 (%)
    
16. Percentage ratio of full pages:
    number of full pages/value of 19 100 (%)
    
17. Number of used pages.
18. Number of full pages.
19. Total number of pages in the segments in the RDAREA (number of used pages + number of unused pages).
20. Utilization status of the automatic extension facility:
    USE: Automatic extension facility is used.
    NOUSE: Automatic extension facility is not used.
    The HiRDB file indicated as the last HiRDB File Name is subject to automatic extension.
    
21. Number of extension segments.
22. Suppression status of the automatic extension facility:
    SUP: Suppressed.
    NOSUP: Not suppressed
    
23. Error code in the event of an automatic extension error.
    

    -1556:

    Take one of the following actions:

    Use the pdfbkup, pdfmkfs, and pdfrstr commands to integrate the extents of the HiRDB file system area that contains the corresponding HiRDB file system.

    Use pdmod to expand the RDAREA.

    Other:

    See the list of HiRDB file system error codes in the manual HiRDB Version 8 Messages.

24. HiRDB file name in the corresponding RDAREA.
25. Total number of segments for the HiRDB file.
26. Number of HiRDB file segments stored/maximum number of segments.
27. Whether or not the order is lost in a LOB RDAREA:
    Y: Order is lost.
    N: Order is not lost.
    
28. Position information indicating that the segment being used is the last segment; this is indicated in a last position/total number of segments format; always indicates the last segment when {27} is Y.
29. Whether or not the LOB management entries are all used:
    Y: All are used.
    N: There are unused entries.
    
30. Name of the analyzed RDAREA.
31. Always 0.
32. Always 0.
33. Shutdown history of the corresponding RDAREA.
    History1: Shutdown information immediately before the shutdown was released (if the RDAREA is currently shut down, this field displays the current shutdown information)
    History2: Shutdown information immediately preceding History1
    
34. Shutdown type of the corresponding RDAREA. If there is no history, this field is blank.
    CMD: Command shutdown by HiRDB error detection
    FLT: Error shutdown
    
35. Code indicating the cause of the shutdown of the corresponding RDAREA. For details about the shutdown cause code, see 15.3.1(2)(a) For an RDAREA other than a LOB RDAREA.
36. Shutdown time of the corresponding RDAREA. If there is no history, this field is blank.
37. Whether or not the RDAREA is in frozen update status:
    Y: Placed in frozen update status by the pddbfrz command.
    N: Not placed in frozen update status by the pddbfrz command.
    
38. Whether or not the HiRDB files constituting the RDAREA are in frozen update status:
    

    U:

    Not in frozen update status. During backup, such HiRDB files need to be backed up.

    F:

    In the frozen update status. If a backup was made subsequent to the displayed date and time, there is no need to back up these HiRDB files again.

39. Date and time the frozen update status was changed.
    

    When ****/**/** **:**:** is displayed:

    This information is displayed if the RDAREA has never been placed in frozen update status since it was created or re-initialized.

    Other that the above:

    The displayed information indicates the date and time the RDAREA was placed in frozen update status or released from frozen update status.

Note 1

Nos. 10-11 and 15-19 are not displayed for a LOB RDAREA.

Note 2

Nos. 27-29 and 37 are displayed for a LOB RDAREA.

• In DAT format (when the -a option is specified)
  Table 15-2 describes the results of condition analysis by RDAREA (physical analysis).
  Rules for output in DAT format are as follows:
  
  • The items described in Table 15-2 are separated by the comma (,).
  • Information about one RDAREA is displayed per line. If a single RDAREA consists of multiple HiRDB files, the information for the RDAREA consists of as many lines as there are component HiRDB files.
  • RDAREA information is displayed in ascending order of the RDAREA names. HiRDB file information is displayed in the order of the physical file IDs.
    

    Table 15-2 Results of condition analysis by RDAREA (physical analysis) in DAT format

    Title bar1	Description	Output format	Max. length (bytes)2
    VERSION	HiRDB version	Character string (vv-rr)	5
    INF_GET_TIME	Date (year, month, date) and time that information acquisition was completed	Character string (yyyy/mm/dd hh:mm:ss)	19
    RDAREA_NAME	Name of the RDAREA	Character string	30
    SERVER	Name of the server containing the RDAREA	Character string	8
    MAX_SUM_SEGMENT	Maximum total number of segments in the RDAREA	Numeric value	10
    MAX_SUM_PAGE	Maximum total number of pages in the RDAREA	Numeric value	10
    SPECIFIED_RDAREA_COUNT	Number of RDAREAs to be analyzed	Numeric value	10
    ANALYZED_RDAREA_COUNT	Number of RDAREAs analyzed normally	Numeric value	10
    SEGMENT_SIZE	Number of pages per segment	Numeric value	10
    PAGE_SIZE	Page size	Numeric value	10
    HOLD_STATUS(HISTORY1)5	RDAREA shutdown type (type of the last shutdown that was released; or if RDAREA is currently shut down, the current shutdown type): CMD: Command shutdown by HiRDB error detection FLT: Error shutdown	Character string	3
    HOLD_CODE(HISTORY1)	RDAREA shutdown cause code (cause code of the last shutdown that was released, or if RDAREA is currently shut down, the current shutdown cause code) (For details about the shutdown cause code, see the description for the text format.)	Numeric value	5
    HOLD_TIME(HISTORY1)5	RDAREA shutdown time (time of the last shutdown that was released; or if RDAREA is currently shut down, the current shutdown time)	Character string (yyyy/mm/dd hh:mm:ss)	19
    HOLD_STATUS(HISTORY2)5	RDAREA shutdown type (shutdown type immediately preceding History1): CMD: Command shutdown FLT: Error shutdown	Character string	3
    HOLD_CODE(HISTORY2)	RDAREA shutdown cause code (shutdown cause code immediately preceding History1) (For details about the shutdown cause code, see the description for the text format.)	Numeric value	5
    HOLD_TIME(HISTORY2)5	RDAREA shutdown time (shutdown time immediately preceding History1)	Character string (yyyy/mm/dd hh:mm:ss)	19
    FREEZE_SPECIFIED3	Whether or not frozen update was specified for the RDAREA: Y: Frozen update was specified with the pddbfrz command N: Frozen update was not specified with the pddbfrz command	Character string	1
    UNUSED_SEGMENT	Total number of unallocated segments in the RDAREA	Numeric value	10
    UNUSED_SEGMENT_NOT_FREEZE3	Total number of unallocated segments in HiRDB files that are not in frozen update status in the RDAREA	Numeric value	10
    USED_SEGMENT	Number of used segments	Numeric value	10
    USED_SEGMENT_RATIO	Percentage of used segments (number of used segments/total number of segments in RDAREA) 100	Numeric value	3
    FULL_SEGMENT	Number of full segments	Numeric value	10
    FULL_SEGMENT_RATIO	Percentage of full segments (number of full segments/total number or segments in RDAREA) 100	Numeric value	3
    SUM_SEGMENT	Total number of segments in the RDAREA	Numeric value	10
    SEGMENT_OVER3	Whether or not all segments are in use or have been used: Y: Used N: Not used	Character string	1
    LAST_SEGMENT_IN_USE3	Last segment in use (if end-of-segment is Y, the last segment)	Numeric value	10
    TOTAL_SEGMENT_ NUMBER3	Total number of segments	Numeric value	10
    LOBMAP_OVER3	Whether or not all LOB management entries have been used: Y: Used N: Not used	Character string	1
    USED_LOB_ MANAGEMENT_ENTRY_NUMBER	Information used by the system	Numeric value	10
    TOTAL_LOB_ MANAGEMENT_ENTRY_NUMBER	Information used by the system	Numeric value	10
    USED_PAGE	Number of used pages	Numeric value	10
    USED_PAGE_RATIO	Percentage of used pages (number of used pages/total number of pages in all segments in RDAREA) 100	Numeric value	3
    FULL_PAGE	Number of full pages	Numeric value	10
    FULL_PAGE_RATIO	Percentage of full pages (number of full pages/total number of pages in all segments in RDAREA) 100	Numeric value	3
    SUM_PAGE	Total number of pages in all segments in the RDAREA	Numeric value	10
    AUTO_EXTEND_USE	Usage status of automatic extension facility: USE: Used NOUSE: Not used The last HiRDB file displayed in the HiRDB file information uses the automatic extension facility.	Character string	5
    AUTO_EXTEND_SEGMENT	Number of extended segments	Numeric value	5
    AUTO_EXTEND_STATUS	Automatic extension facility suppression status: SUP: Suppressed NOSUP: Not suppressed	Character string	5
    ERROR_CODE	Error code for an automatic extension error	Numeric value	5
    HiRDB_FILE_NAME	HiRDB file name in the RDAREA (absolute path name)	Character string	167
    FILE_SIZE	HiRDB file size (total number of segments)	Numeric value	10
    EXTENT_COUNT	HiRDB file partition storage count	Numeric value	3
    MAX_EXTENT_COUNT	Maximum HiRDB file partition storage count value	Numeric value	3
    USED_SEGMENT_IN_FILE3	Number of used segments in HiRDB file	Numeric value	10
    TOTAL_SEGMENT_IN_FILE3	Total number of segments in HiRDB file	Numeric value	10
    FREEZE_STATUS3	Frozen update status of HiRDB file: U: Not in frozen update status (when a backup is made, this HiRDB file must be backed up) F: In frozen update status (if the HiRDB file was backed up after the displayed date and time, there is no need to back it up again)	Character string	1
    FREEZE_TIME3	Frozen update status change date and time: ****/**/** **:**:**: The file has not been placed in frozen update status since the RDAREA was created or reinitialized Other: Date and time that frozen update status was set or released	Character string (yyyy/mm/dd hh:mm:ss)	19
    ORIGINAL_RDAREA_NAME4	Target RDAREA name	Character string	30
    GENERATION_NUMBER4	Always 0	Numeric value	2
    REPLICA_RDAREA_COUNT4	Always 0	Numeric value	2

¹ The title bar is displayed when the -h option is specified.

² When the output format is character string, this information is enclosed in double quotation marks (""), in which case the maximum length does not include the double quotation marks. When the output format is not character string, the information is not enclosed in double quotation marks.

³ This information is displayed only for a LOB RDAREA. For any other type of RDAREA, no data is output (example: ...,,...).

⁴ No data is displayed (example: ...,,...).

⁵ If the RDAREA has never been shut down, no data is output (example: ...,,...).

The results of condition analysis by RDAREA (physical analysis) can be analyzed as shown in Table 15-3.

Table 15-3 Analyzing the analysis results by RDAREA (physical analysis)

Status in the RDAREA					Description
Entire RDAREA	Unused segments	Many			There is sufficient capacity.
		Few	Used free pages	Many	The RDAREA is not being used efficiently. Execute condition analysis by RDAREA (logical analysis), check for a table or index that has many used segments and unused pages; if necessary, reorganize such a table or index or release free pages.1
				Few	There is not enough capacity. Extend the RDAREA.2

¹ For details about table and index reorganization, see Chapter 8. Database Reorganization Utility (pdrorg). For details about releasing free table and index pages, see Chapter 11. Free Page Release Utility (pdreclaim).

² For details about RDAREA expansion, see Chapter 7. Database Structure Modification Utility (pdmod).

A user LOB RDAREA can be analyzed as follows:

• Information about segments in the RDAREA
  

  Percentage of used segments	End-of-segment	Description
  Large (there are only a few unused segments)	Y	There is not enough capacity and database access performance has been affected adversely. Expand the user LOB RDAREA and reorganize the table or index.1, 2
  	N	There is not enough capacity. The user LOB RDAREA must be extended.1
  Small (there are many unused segments)	Y	Database access performance has been affected adversely. Reorganize the table or index.2
  	N	No action is necessary.

Note

If an RDAREA storing the LOB attribute of a plug-in-provided abstract data type or an RDAREA storing a plug-in index is analyzed, the percentage of used segments in the RDAREA depends on the method used by the plug-in to allocate segments. For example, if a plug-in completes allocation of segments during index definition, most of the segments may become used segments immediately upon definition (before data is stored).

¹ For details about RDAREA expansion, see Chapter 7. Database Structure Modification Utility (pdmod).

² For details about table and index reorganization, see Chapter 8. Database Reorganization Utility (pdrorg).

• End-of-Lobmap
  If this is Y, LOB column search performance may become poor; you should reorganize the LOB column structure base table.