Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Quiet Point report

The Quiet Point report provides information about the ranges within your time frame when the DB2 log shows no activity for a set of table spaces specified by your filter.

The report lists only quiet ranges in common for all table spaces specified in the filter. Use the Quiet Point report to identify common ranges of consistency between multiple table spaces for use in recovery planning and redo operations.

Note

To generate this report, ensure that your filter refers to at least one specific DB2 object (such as a table name or a column name). This action causes you to define (either directly or indirectly) a set of table spaces that Log Master can search for quiet ranges.

To request a Quiet Point report

  1. From any task dialog (any option from 0 through 7 under the Actions category on the Main Menu), select the Define Report and File Outputs option
  2. On the Output Options panel, select Quiet Point.

Be aware of the following points as you define a Quiet Point report:

  • By default, the Quiet Point report includes all quiet ranges for the specified DB2 objects (no minimum). However, you can exclude shorter quiet ranges from the report by specifying a minimum duration for quiet ranges by using the Duration field of the Report Output panel. Log Master suppresses any quiet ranges that are shorter than the duration that you specify. Consider excluding shorter quiet ranges that represent momentary pauses between parts of an ongoing 'logical' transaction. Doing so enables you to concentrate on times when there is truly no activity for your table spaces. If you use a report template, you can sort quiet ranges based on duration or number of open transactions.

  • By default, the Quiet Point report includes only completely quiet ranges. However, you can include almost-quiet ranges in the Quiet Point report by specifying a maximum number of transactions (units of recovery) to allow in the MaxUrids field of the Report Output panel. Log Master includes a quiet range in the report when the number of open transactions that affect your specified DB2 objects during the range is less than or equal to the number that you specify. Consider using this option to report on periods of high activity for your specified objects, when completely quiet ranges might not exist. For each quiet range, the report lists the number of open transactions that are present during the range.

  • The Quiet Point report lists date and time values for the start point and end point of each quiet range (see the example later in this topic). If a Quiet Point report is generated in a non-data-sharing environment and a quiet range ends when a DB2 Load or Reorg utility starts running, Log Master prints 'n/a' for the date and time value of the end point. Log Master takes this action because of the way that DB2 records the execution of these utilities.

  • You can insert a quiesce record in SYSIBM.SYSCOPY at the same time that you generate the Quiet Point report by entering Y in the Quiesce at Last Quiet Point field of the Report Output panel.

    Log Master inserts DB2 quiesce records into the SYSIBM.SYSCOPY table (using the RBA/LRSN of the latest quiet range included in the report). The quiesce records define quiet points for each table space defined or implied in your filter. The quiesce record corresponds to the first or last completely quiet range included in the report, depending on your sort order, first for descending, last for ascending.

    Log Master also inserts index quiesce records into SYSIBM.SYSCOPY for any COPY YES indexes associated with the table spaces. Log Master records the correct quiet point registration so all recoverable objects have the proper QUIESCE entry in SYSCOPY.

    Do not use Quiesce at Last Quiet Point if Log Master is performing dynamic filter processing (if the value of either the FILTER METHOD keyword or the FLTRMTHD installation option is DYNAMIC.)

    Log Master does not insert a quiesce record if

    • Log Master finds no quiet ranges that meet your criteria

    • The report includes only almost-quiet ranges

  • When generating a Quiet Point report, you can add a non-invasive quiet point (an IBM QUIESCE-free quiesce point) by defining a log mark. From the Report Output panel, you define this log mark by specifying a log mark name in the Log Mark at Last Quiet Point field and providing a description in the Log Mark Desc field.

    When you define a log mark, Log Master stores this information in the ALPMARK table in the Log Master Repository. You can use this log mark in place of the RBA or LRSN value in subsequent Log Master jobs. Note the following restrictions:

    • Log Master does not insert a log mark if no quiet ranges meet the specified criteria, or if the report includes only almost-quiet ranges.

    • Do not use Log Mark at Last Quiet Point if Log Master is performing dynamic filtering processing (that is, if the value of either the FILTER METHOD keyword or the FLTRMTHD installation option is DYNAMIC).

  • If you use a report template to customize the Quiet Point report, you can direct Log Master to sort the quiet ranges based on duration. If you sort in ascending order, Log Master uses the longest quiet range in your report as the point to insert a quiesce record in SYSIBM.SYSCOPY.

  • When it does not find a quiet point, Log Master normally issues message BMC097547W and completes with return code 4. However, when generating a Quiet Point report, you can specify the return code or message severity code that you want Log Master to use. Specifying the message severity code or return code in the No Quiet Point RC field enables you to include subsequent conditional job steps based on the issued message or return code.

    Note the following additional information about the values that you specify for this field:

    • If you specify a return code rather than a message severity code, the resulting message severity code is as follows:

      Specified return code

      Message severity code

      Severity code description

      0

      I

      Information

      >0 and <=4

      W

      Warning

      >4 and <=8

      E

      Error

      >8 and <=12

      S

      Severe error

      >12

      U

      Unrecoverable error

    • Log Master completes with the highest return code set during processing. Therefore, for example, if you specify a value of 5 for No Quiet Point RC but Log Master encounters an unrecoverable error, the job ends with return code 16, not 5.

  • Log Master cannot produce a Quiet Point report when the input source for your work ID is either individual DB2 log files or a logical log file generated by Log Master or another program.

Example of a Quiet Point report

The following figure shows an example of a Quiet Point report. If you request the insertion of a quiesce record or log mark, the Quiet Point report includes a message to document your request as shown towards the end of the following example:

Example of Quiet Point report by log RBA

 Date: 2015-03-18            LOG MASTER FOR DB2 -  V11.02.00        Page:       1
 Time: 16.24.40         Copyright BMC Software, Inc. 1995-2015

                          Quiet Point Report, By Log RBA
 --------------------------------------------------------------------------------

 From: Mark DB2DBA.START.RBA(0) (x'C32EE60188A4')
   To: Current x'C32EE6C06310'

 --------------------------------------------------------------------------------
 Report Information:

 Work ID    : DB2DBA.$$WORKID0012         Run Number:    3  Subsystem: DXW2
 Description:   DB2DBA GENERATE MONTHLY REPORTS
 Duration   : 00.00.00.500000
 Max Urids  : 2
 --------------------------------------------------------------------------------

 Tablespace Name: DB2DBADB.DB2DBAS1             DBID: 363    PSID: 2
 Tablespace Name: DB2DBADB.DB2DBAS3             DBID: 363    PSID: 14
   Range From: RBA/LRSN: x'C32EE60188A4'   Date: 2015-03-18 16.18.13.354112
           To: RBA/LRSN: x'C32EE603D0DD'   Date: 2015-03-18 16.18.15.747088
        Urids: 0 ** QUIET POINT **
   Range From: RBA/LRSN: x'C32EE603D106'   Date: 2015-03-18 16.18.15.747728
           To: RBA/LRSN: x'C32EE61412C1'   Date: 2015-03-18 16.18.32.794192
        Urids: 2
   Range From: RBA/LRSN: x'C32EE61434F8'   Date: 2015-03-18 16.18.32.934320
           To: RBA/LRSN: x'C32EE6156208'   Date: 2015-03-18 16.18.34.167488
        Urids: 2
   Range From: RBA/LRSN: x'C32EE6156209'   Date: 2015-03-18 16.18.34.167488
           To: RBA/LRSN: x'C32EE6231B8B'   Date: 2015-03-18 16.18.48.558832
        Urids: 1
   Range From: RBA/LRSN: x'C32EE6231D35'   Date: 2015-03-18 16.18.48.565632
           To: RBA/LRSN: x'C32EE626ED75'   Date: 2015-03-18 16.18.52.564368
        Urids: 1
   Range From: RBA/LRSN: x'C32EE626F58B'   Date: 2015-03-18 16.18.52.597472
           To: RBA/LRSN: x'C32EE62D0E14'   Date: 2015-03-18 16.18.58.989440
        Urids: 1
   Range From: RBA/LRSN: x'C32EE62D0E15'   Date: 2015-03-18 16.18.58.989440
           To: RBA/LRSN: x'C32EE6C06310'   Date: 2015-03-18 16.21.36.310368
        Urids: 0 ** QUIET POINT **

   Quiesce recorded in SYSIBM.SYSCOPY at x'C32EE6C06310' 
   Mark SYSUSR.QPMARK recorded at x'C32EE6C06310'

 4 quiet point ranges shorter than the duration were suppressed in report

Quiet Point report contents

For each table space specified, the report presents table space information, including database name, table space name, DSNUM, DBID, and PSID. For each quiet point found, the report presents the following quiet point information:

  • starting and ending RBA/LRSNs for the range of the quiet point

  • end time of the last unit of recovery identifier (URID) using the table space

  • start time of the next log page referencing the table space

For each COPY YES index, the report includes information similar to that for table spaces, as well as the index name, DBID, and ISOBID.


Quiet Point report ordering

Log Master sorts the quiet ranges in a standard default Quiet Point report by RBA/LRSN value. The quiet ranges in the report are common to all of the table spaces selected (directly or indirectly) by your filter.

If you use a report template to customize the Quiet Point report, you can direct Log Master to sort the quiet ranges based on duration or number of open transactions. If you sort by duration in ascending order, Log Master uses the longest quiet range in your report as the point to insert a quiesce record in SYSIBM.SYSCOPY.

Was this page helpful? Yes No Submitting... Thank you

Comments