Scalable Database Server, HiRDB Version 8 Command Reference

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

15.4.1 Output format of the execution results

The execution results of the facility for predicting reorganization time depend on the values of the -e and -m options. Table 15-5 shows the relationship between the options and the output information.

Table 15-5 Relationship between the options and the output information (facility for predicting reorganization time)

-e option specification -m option Information about scheduled database maintenance date Information about maintenance method Information for each analysis item
1 (prediction level 1) Specified Y Y [Figure]
Omitted Y [Figure] [Figure]
2 (prediction level 2) N/A Y Y Y

Legend:
Y: The corresponding information is output.
[Figure]: The corresponding information is not output.
N/A: Cannot be specified.
Organization of this subsection
(1) Scheduled database maintenance date
(2) Maintenance method
(3) Information by analysis item

(1) Scheduled database maintenance date

This example displays RDAREAs whose segment usage rate is predicted to exceed the standard value within the monitoring period. The RDAREAs are displayed in chronological order of the scheduled database maintenance dates.

 
 pddbst vv-rr       ***** Rdarea resource forecast *****     yyyy/mm/dd hh:mm:ss
No         Date        RdareaName                       ResKind
---------- ----------- -------------------------------- ----------
         1 2005/05/31  "RDUSER01"                       Segment
         2 2005/06/01  "RDUSER12"                       Segment
         3 2005/06/03  "rd0002"                         Segment
         4 2005/06/04  "lobrdarea701"                   Segment
         5 2005/06/11  "RDUSER02"                       Segment
---------- ----------- -------------------------------- ----------

Note
For a HiRDB/Parallel Server, a scheduled database maintenance date is based on the dictionary server's date and time settings.

Explanation

No:
Analysis result number (maximum of 10 digits)

Date:
Date predicted by the facility on which the segment usage rate will exceed the standard value (scheduled database maintenance date) (in the format YYYY/MM/DD)

RdareaName:
Name of the RDAREA whose maintenance is predicted to be necessary (maximum of 32 characters)

ResKind:
Item that is predicted to exceed its standard value (maximum of 10 characters):
Segment: Segment usage rate

(2) Maintenance method

This example displays RDAREAs whose segment usage rate is predicted to exceed the standard value within the monitoring period. The RDAREAs are displayed in chronological order of the scheduled database maintenance dates, together with the recommended maintenance method. In prediction level 2, of the tables and indexes for which maintenance is determined to be necessary from the information by analysis item, the example displays those that affect maintenance of RDAREAs.

 
 pddbst vv-rr       ***** Maintenance Information *****       yyyy/mm/dd hh:mm:ss
No          : 1
Rdarea Name : "RDUSER01"
Method      : 
Segment     : 42560
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                   Date
------------- ------------ ---- -------------------------------------- ----------
      28089 *       9363    T   "k1234567"."table01"                   2005/05/31
          0        12342 *  T   "k1234567"."table02"                   2005/05/31
        851         7235 *  I   "k1234567"."index01"                   2005/05/31
          3          -10    T   "k1234567"."table10"                   2005/05/31
===================================================================================
No          : 2
Rdarea Name : "RDUSER12"
Method      : 
Segment     : 32985
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                   Date
------------- ------------ ---- -------------------------------------- ----------
       3628        23749 *  T   "k1234567"."table01"                   2005/06/01
       1319         5937 *  T   "k1234567"."table03"                   2005/06/01
       1649 *       3628    I   "k1234567"."index01"                   2005/06/01
       2638 *        989    T   "k1234567"."table11"                   2005/06/01
===================================================================================
No          : 3
Rdarea Name : "rd0002"
Method      : Expand
Segment     : 1523
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                   Date
------------- ------------ ---- -------------------------------------- ----------
        228         1035    T   "k1234567"."table01"                   2005/06/03
          0          121    T   "k1234567"."table03"                   2005/06/03
         30           60    I   "k1234567"."index07"                   2005/06/03
===================================================================================
No          : 4
Rdarea Name : "lobrdarea701"
Method      : 
Segment     : 2498
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                   Date
------------- ------------ ---- -------------------------------------- ----------
          0         2764 *  L   "k1234567"."table701"                  2005/06/04
===================================================================================
No          : 5
Rdarea Name : "RDUSER02"
Method      : Expand
Segment     : 31854
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                   Date
------------- ------------ ---- -------------------------------------- ----------
       3503        23934    T   "k1234567"."table21"                   2005/06/11
       1592         3503    I   "k1234567"."index22"                   2005/06/11
       2548          955    T   "k1234567"."table23"                   2005/06/11
===================================================================================

Note
For a HiRDB/Parallel Server, a scheduled database maintenance date is based on the dictionary server's date and time settings.

Explanation

No:
Analysis result number (maximum of 10 digits)

Rdarea Name:
Name of the RDAREA whose maintenance is predicted to be necessary (maximum of 32 characters)

Method:
RDAREA maintenance method (maximum of 20 characters):
Expand:
Expand the RDAREA
Extend:
Maintenance is not necessary (HiRDB will perform automatic extension of the RDAREA)
Reinit:
Re-initialize the RDAREA
blank:
Maintenance is not necessary

Segment:
Number of segments to be released (maximum of 10 digits)
  • In prediction level 1
    This is the minimum number of segments that need to be allocated during maintenance.
    If Expand is displayed for Method, expand the RDAREA so that the actual number of segments will be greater than the value displayed here.
  • In prediction level 2
    This is the minimum number of segments that need to be allocated during maintenance. If maintenance of a table or index is predicted to be necessary, the displayed value reflects the result of executing such necessary maintenance. For example, if Expand is displayed for Method, the minimum number of segments that must be allocated is displayed, assuming that the necessary maintenance will be executed prior to RDAREA expansion.

Reclaim:
Number of segments predicted to be released when used free segments are released after used free pages are released (maximum of 13 digits)
If the facility predicts that release of used free segments is necessary as the table or index maintenance method, an asterisk (*) is displayed to the right of this item.

Reorganize:
Number of segments predicted to be released when reorganization is executed (maximum of 13 digits)
If the facility predicts that reorganization is necessary as the table or index maintenance method, an asterisk (*) is displayed to the right of this item.
If the facility predicts that reorganization will result in many data storage pages, a negative value (with a minus sign) is displayed.

Type:
Type of maintenance target (1 character):
T: Table
I: Index
L: LOB RDAREA

Name:
Name of the table or index (including authorization identifier) that is to be maintained (maximum of 52 characters). When Type is L, the facility displays the name of the table for which the LOB column has been defined.
The output format is "authorization-identifier"."table-identifier" or "authorization-identifier"."index-identifier". For a data dictionary table, the authorization identifier is "(Data dictionary)".

Date:
Scheduled database maintenance date (in the format YYYY/MM/DD)
  1. An asterisk (*) indicating a need for reorganization is displayed for a resource for which the number of used segments is increased as a result of reorganization.
  2. Maintenance times may differ within the same RDAREA.
  3. Both expansion and reorganization are indicated for an RDAREA.

The following shows an output example, where [1] through [3] correspond to the numbers above:

 
 pddbst VV-RR       ***** Maintenance Information *****       yyyy/mm/dd hh:mm:ss
No          : 1
Rdarea Name : "RDUSER01"
Method      : 
Segment     : 42560
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                        Date
------------- ------------ ---- ------------------------------------------- ----------
          3           10 *  T   "k1234567"."table10"                    [2] 2005/05/16
      28089 *       9363    T   "k1234567"."table01"                        2005/05/31
          0        12342 *  T   "k1234567"."table02"                        2005/05/31
        851         7535 *  I   "k1234567"."index01"                        2005/05/31
          3      [1] -10 *  T   "k1234567"."table11"                        2005/05/31
          3     [1] -300 *  T   "k1234567"."table12"                        2005/05/31
======================================================================================
No          : 2
Rdarea Name : "rd0002"
Method      : Expand [3]
Segment     : 1523
--------------------------------------------------------------------------------------
 Reclaim      Reorganize   Type Name                                        Date
------------- ------------ ---- ------------------------------------------- ----------
        228     [3] 1035 *  T   "k1234567"."table01"                        2005/06/03
          0      [3] 121 *  T   "k1234567"."table03"                        2005/06/03
         30       [3] 60 *  I   "k1234567"."index07"                        2005/06/03
          3     [3] -300 *  T   "k1234567"."table22"                        2005/06/03
======================================================================================

(3) Information by analysis item

This example displays in chronological order of the scheduled database maintenance dates the RDAREAs, tables, and indexes whose segment usage has exceeded a standard value within the monitoring interval. Also included is the maintenance method, as well as detailed information about the resources that are displayed for the maintenance method.

 pddbst VV-RR       ***** Analysis Item Data *****       yyyy/mm/dd hh:mm:ss
No        : 1
Date      : 2005/05/25
Method    : Reclaim
Type      : T
Name      : "k1234567"."table01" ("RDUSER01")
StateDate : 2005/05/19 00:10:32
------------------------------------------------------------------------------------
Information                               Value      Method               Date
---------------------------------------- ----------- -------------------- ----------
Empty Page Ratio                          40 ( 50) * Reclaim pages        2005/05/25
Unused Page Ratio (30)                    20 ( 30)
Used Segment for Cluster                  40 ( 50)
Unused Page Differ From PCTFREE (10,10)   50 ( 75)
====================================================================================
No        : 2
Date      : 2005/05/31
Method    : 
Type      : R
Name      : "RDUSER01"
StateDate : 2005/05/19 00:10:32
------------------------------------------------------------------------------------
Information                               Value      Method               Date
---------------------------------------- ----------- -------------------- ----------
Used Segment Ratio (0,10)                 40 ( 80)                        2005/05/31
====================================================================================
No        : 3
Date      : 2005/06/01
Method    : Reorganize
Type      : T*
Name      : "k1234567"."table10" ("RDUSER01")
StateDate : 2005/05/19 00:10:32
------------------------------------------------------------------------------------
Information                                Value     Method               Date
---------------------------------------- ----------- -------------------- ----------
Empty Page Ratio                          25 ( 50)   Reclaim pages        2005/08/10
Unused Page Ratio (30)                    25 ( 30) * Reorganize           2005/06/01
Used Segment for Cluster                  40 ( 50)
Unused Page Differ From PCTFREE (10,10)   60 ( 75)
====================================================================================
No        : 4
Date      : 2005/06/03
Method    : Expand 
Type      : R
Name      : "rd0002"
StateDate : 2005/05/19 00:10:32
------------------------------------------------------------------------------------
Information                               Value      Method               Date
---------------------------------------- ----------- -------------------- ----------
Used Segment Ratio (0,10)                 78 ( 95)   Expand               2005/06/03
====================================================================================
No        : 5
Date      : 2005/06/04
Method    : Reclaim
Type      : I
Name      : "k1234567"."index07" ("rd0002")
StateDate : 2005/05/19 00:10:32
------------------------------------------------------------------------------------
Information                                Value     Method               Date
---------------------------------------- ----------- -------------------- ----------
Empty Page Ratio                          38 ( 50)   Reclaim              2005/06/04
Unused Page Ratio (30)                    20 ( 30)
Unused Page Differ From PCTFREE (10,10)   70 ( 75)
====================================================================================
No        : 6
Date      : 2005/06/04
Method    : Reorganize
Type      : L
Name      : "k77a777"."table707" ("lobrdarea701")
StateDate : 2005/05/19 00:10:32 
------------------------------------------------------------------------------------
Information                                Value     Method               Date
---------------------------------------- ----------- -------------------- ----------
Used Segment for LOB Columns (0,10)       70 ( 80) * Reorganize           2005/06/04
====================================================================================
No        : 7
Date      : 2005/06/06
Method    : Expand 
Type      : R
Name      : "RDUSER12"
StateDate : 2005/05/19 00:10:32 
------------------------------------------------------------------------------------
Information                                Value     Method               Date
---------------------------------------- ----------- -------------------- ----------
Used Segment Ratio (0,10)                 70 ( 80) * Expand               2005/07/01
====================================================================================              :

Note
In the case of a HiRDB/Parallel Server, a scheduled database maintenance date is based on the dictionary server's date and time settings.

Explanation

No:
Analysis result number (maximum of 10 digits). This corresponds to the number assigned to the information about each scheduled database maintenance date.

Method:
Maintenance method for the target type (Type) (maximum of 14 characters):
ReclaimS
Use pdreclaim to release used free segments.
ReclaimP
Use pdreclaim to release used free pages.
Reorganize
Use pdrorg to perform reorganization. When reorganization is executed, the area to be used may increase because free area is allocated according to the specified PCTFREE value. If there is a shortage of space, extend the RDAREA beforehand.
Expand
Use pdmod to expand the RDAREA.
Extend
Maintenance is not needed (HiRDB performs automatic extension of the RDAREA). If HiRDB cannot allocate the area required for automatic extension, the user must use pdmod to extend the RDAREA.
Reinit
Re-initialize the RDAREA. If 16 HiRDB files have already been allocated to the RDAREA, the RDAREA can no longer be extended. In such a case, you must take appropriate action, such as re-initializing the RDAREA to increase the size and number of HiRDB files.
blank
No maintenance is needed.

Type:
Target type for which maintenance is determined to be necessary (2 characters):
T: Table
I: Index
L: LOB RDAREA
R: RDAREA
An asterisk (*) indicates that the target type is displayed in the information by analysis type, but not in the information about the maintenance method (example: T*). Therefore, in the case of a target type with an asterisk displayed, you must perform the indicated maintenance. In the case of a target type without an asterisk displayed, perform only the maintenance indicated in the information about the maintenance method.

Name:
Name of the RDAREA, table, or index (including the authorization identifier) that is the target of maintenance (maximum of 78 characters)
For an RDAREA
When RDAREA extension is instructed: "RDAREA-name"
For a LOB RDAREA: "authorization-identifier"."table-identifier"("RDAREA-name")
For a table
For a non-row-partitioned table: "authorization-identifier"."table-identifier"
For a row-partitioned table: "authorization-identifier"."table-identifier"("RDAREA-name")
For an index
For a non-row-partitioned table: "authorization-identifier"."index-identifier"
For a row-partitioned table: "authorization-identifier"."index-identifier"("RDAREA-name")

StateDate:
Date and time the most recent information was acquired in the information used for analysis (in the format YYYY/MM/DD hh:mm:ss)

Information:
Names of analyzed items and the standard values used for the analyses. For details about the item names and standard values, see 15.5 Standard value definition file (facility for predicting reorganization time).

Value:
Analysis values. Each set of analysis values is output in the format analysis-value (standard-value). For details about the standard values, see 15.5 Standard value definition file (facility for predicting reorganization time).
An asterisk (*) is displayed following the set of analysis values for the item with the earliest prediction date among all the analyzed items for which maintenance was determined to be necessary as a result of prediction processing.

Date:
Scheduled database maintenance date (in the format YYYY/MM/DD).

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.