CA Database Analyzer in BMC compatibility mode runs out of storage with error message IDI8301E.

Document ID : KB000052522
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Executing CA Database Analyzer in BMC compatible mode using BMC Pointer Checker Plus (PCP) JCL and control statements. Multiple databases are processed in one step and the job runs out of storage.

The failure is occuring on the first check and all other checks are flushed.

IDI8301E NO MORE SPACE FOR DATA IN DATA SPACE "TOOLKIT ".   
   
DBA2102E NO VIRTUAL MEMORY AVAILABLE FOR "PRTNOTPT" POINTER CHECKING.   
DBA2103I POINTER CHECKING HAS BEEN DISCONTINUED FOR THIS SEGMENT. 
DBA2104W ALL POINTER ERRORS PRODUCED BY THIS EXECUTION MUST BE RE-VALIDATED. 

The following parameters are set:

 GLBL    TYPE(FULL), FREESPACEPLOT(N), + 
            REPORTS(ROOTDIST(-10+10),RAPCHAIN(Y),VLSDIST(Y))    
 CHECK  DBD(DATABASE) DSG(DSGGROUP)          WORKDDN(WORK02) 

Additional CHECK statements flushed.

   The following error messages are also reported:   
   
 DBA3905I ERROR MESSAGES FOR DATA BASE "DATABASE", DD NAME "DDNAME".        
 DBA0904W  32.70% OF THE POINTERS IN PART     POINT OUTSIDE THEIR CONTAINING CYLINDER 
 DBA0904W  21.47% OF THE POINTERS IN PARTLEVL POINT OUTSIDE THEIR CONTAINING CYLINDER 
 DBA6608E FOR PARENT PART     AND CHILD XXXXXXXX, THE NON-ZERO PCF COUNT IS 2,298,300 
            BUT THE TOTAL NUMBER OF XXXXXXXX SEGMENTS WITH PTF = 0 IS 2,298,228 
 DBA6608E FOR PARENT PART     AND CHILD YYYYYYYY, THE NON-ZERO PCF COUNT IS 2,688,303 
            BUT THE TOTAL NUMBER OF YYYYYYYY SEGMENTS WITH PTF = 0 IS 2,688,186 
 DBA6623E THE "PP      " POINTERS IN SEGMENT "YYYYYYYY" FOR SEGMENT "PART    " ARE IN ERROR. 

Solution:

To provide more storage for pointer checking, please use:

CHECKALL DBD(DATABASE) FREESPACEPLOT(N) MULTISPACE(Y)

The CHECKALL control statement tells Database Analyzer to process all interrelated databases and can be used in place of all the CHECK and GLBL statements.

The MULTISPACE control statement uses a separate data space for each unique DD pair with pointers. This may be necessary if you have large multi-DSG databases with many secondary indexes and/or logical relationships. CA Database Analyzer still checks local pointers in the utility data space and logical parent pointers to their associated counter.

Alternatively you can add one or both of the following to reduce the amount of storage:

LPCKCHECK(N) INDEXKEYCHECK(N) 

The LPCKCHECK control statement verifies the logical parent concatenated key (LPCK) in the logical child.

The INDEXKEYCHECK control statement checks the key value in a primary or secondary index against the key in the target segment during database analysis.