DSN1LOGP summary report

The DSN1LOGP utility generates a summary report, which is placed in the SYSSUMRY file. The report includes a summary of completed events and a restart summary. You can use the information in this report to identify lost work and inconsistent data that needs to be resolved.

The following figure shows an excerpt from the restart summary in a sample DSN1LOGP summary report. The report is described after the figure.

Figure 1. Partial sample of DSN1LOGP summary output
Start of change
DSN1157I RESTART SUMMARY
DSN1153I DSN1LSIT CHECKPOINT  MEMBER=DB2A                                    
               STARTRBA=0000000000002BBB8CAC  ENDRBA=0000000000002BBC59E8    
               STARTLRSN=00CA21F58479D042C000  ENDLRSN=00CA21F58480E67E4000  
               DATE=12.250  TIME=14:20:29                                    
                                                                             
DSN1162I DSN1LPRT  MEMBER=DB2A     UR  CONNID=BATCH     CORRID=ARCHIVE       AUTHID=SYSADM    PLAN=ARCHIVE
             START DATE=00.161 TIME=11:27:30  DISP=INFLIGHT            INFO=COMPLETE 
             STARTRBA=0000000000002BBC888E  STARTLRSN=00CA21F5849D6B88E000  NID=*    
              LUWID=DSNCAT.SYEC1DB2.CA21F58084CF.0003  COORDINATOR=*                 
              PARTICIPANTS=*                                                         
             DATA MODIFIED:                                                          
                  DATABASE=0119=JACKDB    PAGE SET=0002=JACKTS                       
                  DATABASE=0119=JACKDB    PAGE SET=0005=TESTIX                       

DSN1160I DATABASE WRITES PENDING:                                                    
                  DATABASE=0001=DSNDB01    PAGE SET=0008=DSNDB01X   START=0000000000002BB8BC60
                  DATABASE=0001=DSNDB01    PAGE SET=001F=DBD01      START=0000000000002BB8BED8
                  DATABASE=0006=DSNDB06    PAGE SET=006C=DSNADX01   START=0000000000002BB8EE55
                  DATABASE=0006=DSNDB06    PAGE SET=0787=DSNADH02   START=0000000000002BB8E858
                  DATABASE=0006=DSNDB06    PAGE SET=0076=DSNUCX01   
....
End of change
The following message acts as a heading, which is followed by messages that identify the units of recovery that have not yet completed and the page sets that they modified:
DSN1157I RESTART SUMMARY

Following the summary of outstanding units of recovery is a summary of page sets that have database writes that are pending.

In each case (units of recovery or databases with pending writes), the earliest required log record is identified by the START information. In this context, START information is the log RBA of the earliest log record that is required in order to complete outstanding writes for this page set.

Those units of recovery with a START log RBA equal to, or prior to, the point Y cannot be completed at restart. All page sets that were modified by these units of recovery are inconsistent after completion of restart when you attempt to identify lost work and inconsistent data.

All page sets that are identified in message DSN1160I with a START log RBA value equal to, or prior to, the point Y have database changes that cannot be written to disk. As in the previously described case, all of these page sets are inconsistent after completion of restart when you attempt to identify lost work and inconsistent data.

At this point, you need to identify only the page sets in preparation for restart. After restart, you need to resolve the problems in the page sets that are inconsistent.

Because the end of the log is inaccessible, some information is lost; therefore, the information is inaccurate. Some of the units of recovery that appear to be inflight might have successfully committed, or they might have modified additional page sets beyond point X. Additional data might have been written, including those page sets that are identified as having pending writes in the accessible portion of the log. New units of recovery might have been created, and these might have modified data. Db2 cannot detect that these events occurred.

From this and other information (such as system accounting information and console messages), you might be able to determine what work was actually outstanding and which page sets are likely to be inconsistent after you start Db2. This is because the record of each event contains the date and time to help you determine how recent the information is. In addition, the information is displayed in chronological sequence.