Reporting for BMC AMI Check


This topic describes the BMC AMI Check for Db2 product reports.

Internal IDS report

The Internal IDS report correlates the Db2 internal object identifiers to their full external names. You can use this to interpret product messages with internal identifiers.

INTERNAL IDS REPORT                              
PBG TBLSPC DBNAME.PBG00010 DB=0228  PS=009D  FILE=009C   PTNS=1        MXPT=10       SGSZ=64
  TBL 009E PBG00010_TBL1
C NPI DBNAME.PBG0X001      FANSET=009F    PGSET=00A0    TYPE=DF    KYLEN=12     KYCOLS=3
  NPI DBNAME.PBG0X002      FANSET=00A1    PGSET=00A2    TYPE=DF    KYLEN=8      KYCOLS=2

Each line of this report represents part of the object being processed:

  • The first line specifies the database.tableSpace, followed by the hexadecimal value for the DBID (DB), PSID (PS), OBID (FILE), and the number of partitions (PTNS).
  • The second line specifies the table OBID and name.
  • The remaining lines show the following index information: 

    Field name

    Description

    FANSET

    OBID

    PGSET

    ISOBID

    TYPE

    First character: Dup or Unique, second character: Fixed or Variable.

    KYLEN

    Key length in bytes

    KYCOLS

    Number of table columns in the index

Object space report

The Object space report documents the type and size of the objects being processed.

  OBJECT SPACE REPORT              PHYS  LOGL                  TTL        ALLOCATED      USED SPACE   PG   NO.   NO.
  DBNAME    SPNAME     OBID  PSID  PART  PART  TYPE  CX?  I/J  PTNS    (# 4K PAGES)    (# 4K PAGES)   SZ  XTNT  DSET
 --------  --------   ----  ----  ----  ----  ----  ---  ---  ----  --------------  --------------  ---  ----  ----
 DBNAME    PBG00010   009C  009D     1     1  PTTS        J      1           3,636           3,392   4K     2     1
  DBNAME    PBG00010                                           TOTS           3,636           3,392                 
                                                                                                                   
  DBNAME    PBG0X001   009F  00A0               NPI        J                  3,780           1,385                 
  DBNAME    PBG0X002   00A1  00A2               NPI        J                  3,780           1,040                 
                                                                                                                   
          TOTALS                                                             11,196           5,817

Index read report

The Index read report documents the size and content of the index that was processed.

INDEX READ REPORT
INDEX READ COMPLETE(00) IX=DBNAME.PBG0X001   KEYS=225,651      ROWS=225,651
            LFPGS=1,376  TRPGS=6   VLS=3  ROWS=225,651  CLR=   99.7
            FROFF=1,369  NROFF=7   FNR=5  LFFR=0 AVGK=   12.0

Check completion report

The Check completion report displays a line for each index that was processed, listing its status, identification, and size.

CHECK COMPLETION REPORT
CHECK SUCCESSFUL FOR INDEX DBNAME.PBG0X001 (0), 225,651  ROWS

Reporting when no discrepancies are found

 If there are no discrepancies between the index and its table, BMC AMI Check writes a report to that effect to the SUMMARY DD.

The number in parentheses indicates the partition number. If the message is for a nonpartitioning index, the number in parentheses is 0. The following figure illustrates a report for a two-partition table space with one partitioning index and two nonpartitioning indexes:

NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX01 (1), 500  ROWS.
NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX01 (2), 496  ROWS.
NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX03 (0), 996  ROWS.
NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX02 (0), 996  ROWS.

For details of the SUMMARY DD, see Automation-reference.

Reporting when discrepancies are found

If there are discrepancies between an index and the table, BMC AMI Check issues information about those discrepancies.

BMC AMI Check writes a discrepancies summary report to the SUMMARY DD. The number in parentheses indicates the partition number. If the message is for a non-partitioning index, the number in parentheses is 0. The following figure illustrates an example discrepancies summary report:

NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX01 (1), 500  ROWS.             
NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX01 (2), 496  ROWS.             
NGTB120 - CHECK SUCCESSFUL FOR INDEX C040IX03 (0), 996  ROWS.             
                                                                         
NGTB990 - STARTING ERROR ANALYSIS:                                        
NGTB990 - INDEX = BI12DWW.C040IX02                                        
NGTB990 - TABLE = BI12DWW.TEST_TS0040_TBL0                                
NGTB990 - TBSPC = BI12DWW9.PART0040                                       
NGTB990 -                                                                 
NGTB990 - IXDSN = BI12V90V.DSNDBC.BI12DWW9.C040IX02.I0001.A001            
NGTB990 -                                                                 
                                                                         
NGTB909 - IX BI12DWW9.C040IX02 - 4 ERRORS, 4 RECORDED, MAXERROR = 7952,57

The SYSERROR output includes the discrepancies summary report and the additional details that appear in the following example:

NGTB909 - IX BI12DWW9.C040IX02 - 4 ERRORS, 4 RECORDED, MAXERROR = 7952,576                    
NGTB909 - 2 TSPC ROWS WITH NO MATCHING INDEX ENTRY                                            
NGTB909 - 2 INDEX KEYS WITH NO MATCHING TS ROW                                                
NGTB909 - TS ROW HAS NO IX ENTRY POINTING TO IT - TSPG 00000006, RW 26, IX C040IX02           
                                                                                             
NGTB909 -   TSKEY - 00C100E7C1 C3C5404040 C8C5D3D3D6 4040404040 20060428     A XACE   HELLO
                                                                                             
NGTB909 - TS ROW HAS NO IX ENTRY POINTING TO IT - TSPG 00000006, RW 27, IX C040IX02           
                                                                                             
NGTB909 -   TSKEY - 00C100E7C1 C3C5404040 C8C5D3D3D6 4040404040 20060428     A XACE   HELLO
                                                                                             
NGTB909 - IX ENTRY HAS NO MATCHING TS ROW, TSPG 0000000A, RW 2, IXPAGE 00000003, IX C040IX02  
                                                                                             
NGTB909 -   IXKEY - 00C200C3C4 C5D3E3C140 C5C3C8D640 4040404040 20070101     B CDELTA ECHO
                                                                                             
NGTB909 - IX ENTRY HAS NO MATCHING TS ROW, TSPG 0000000A, RW 22, IXPAGE 00000003, IX C040IX02
                                                                                             
NGTB909 -   IXKEY - 00C200C3C4 C5D3E3C140 C5C3C8D640 4040404040 20070101     B CDELTA ECHO
                                                                                             
NGTB117 - RUN TERMINATED - 1 INDEXES WITH ERRORS.

This example report shows that BMC AMI Check found four discrepancies.

You can use the MAXPRINT parameter to limit the number of reported errors and reduce runtime. 

For details of the SUMMARY DD, see Automation-reference.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*