Quiet Point Analysis

DB2 creates checkpoints used to reconstruct previous states after a restart. Database objects also need periodical checkpoints in case a recovery is required. Within these checkpoints, data must be consistent in all logically related objects with no applications creating or updating objects. These points in time are called consistent points or recovery points and are crucial for recovery scenarios.      
caladb219
DB2 creates checkpoints used to reconstruct previous states after a restart. Database objects also need periodical checkpoints in case a recovery is required. Within these checkpoints, data must be consistent in all logically related objects with no applications creating or updating objects. These points in time are called consistent points or recovery points and are crucial for recovery scenarios.      
To create a consistent point in time you can QUIESCE all related objects. However, all objects will be in-accessible to applications while the QUIESCE is being performed. CA Log Analyzer with the Quiet Point Analysis report helps you find points in time in which objects are not being updated.
The report scans the log and identifies favorable recovery points for a selected group of objects. More precisely, it locates log ranges with no activity (no data updates) on the selected group of objects. Those log ranges are called quiet points and you can register the lower RBA of the range as a recovery point in the SYSIBM.SYSCOPY catalog table. These points exist even in very busy environments and can be an alternative to using QUIESCE.
To generate a Quiet Point Analysis Report, select Quiet Point Analysis from the CA Log Analyzer Main Menu and follow the online help to generate the report.
Quiet Point Analysis Options:
  • Select tabular or XML format of the report output.
  • Choose a threshold value for a minimum quiet range in milliseconds.
  • When multiple quiet points are found in the log range choose which one to register. 
  • Register a recovery point in the SYSCOPY catalog table.
  • Register a recovery point as a Log Label.
  • Define the objects using a list of tablespaces or by existing Object List.
    For more information, see Object List Manager in CA Database Management Solutions for DB2 for z/OS documentation.
A demonstration is available here: