Problems after migrating to IBM DB2 Version 11 New Function Mode

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Log Master for DB2



    PROBLEM:

     

    Problems after migrating to IBM DB2 Version 11 New Function Mode

      

    LP: Log Master for DB2 11.1.00

      

    Issue Summary:

      

    PROBLEMS might occur after a migration to DB2 NFM when the Log Master Repository is accessed for: 

      

     LOGSCAN with ONGOING processing (which might prevent the start point from advancing)

      

    LOGSCAN with OVERTIME processing 

      

    ■ Repository maintenance via the online interface or via batch processing using REPOS UPDATE/DELETE syntax

      

    Beginning with Log Master 11.1, the Log Master repository supports extended 10-byte RBA and LRSN values. When running under DB2 11 NFM, the repository must contain only 10-byte RBA and LRSN values. Problems arise if the repository contains both non-extended 6-byte values and 10-byte extended values.

     


    CAUSE:

    6 byte RBA and LRSN values are extended to 10-byte RBA and LRSN values with DB2 V11.1 NFM.


    SOLUTION:

     

      Unless a new Log Master repository is used following migration to IBM DB2 Version 11 New Function Mode, the existing Log Master repository needs to be converted in much the same way as the DB2 catalog for RBA and LRSN values. The process involves adjusting  the values according to the conventions for the type: 
      
        
      
         6 byte RBA                       10 byte extended RBA 
      
            123456789ABC                00000000   123456789ABC
      
        
      
         6 byte LRSN                     10 byteLRSN 
      
            CE2645CE7F57                00   CE2645CE7F57000000 
      
        
      
      Accessing the Repository
      
        
      
      Code modifications included in BPU7406 and BPU7562 allow Log Master to access and update a converted repository at all supported DB2 levels or a repository that has not been converted at all DB2 levels below v11 New Function Mode. This should provide time to schedule the migration process with the caveat that previous versions of Log Master will not work with a converted repository so any “repository sharing” would need to end. 
      
      You should apply the PTFs regardless of your IBM DB2 release and function mode.
      
      After you apply the PTFs, if Log Master discovers that the DB2 subsystem has been migrated to DB2 11 NFM but the repository contains 6-byte values,you will receive the following message and will need to convert the repository (as explained in the next step): 
      BMC097800S REPOSITORY INTERNAL ERROR 14: REPOSITORY CONVERSION TO EXTENDED RBA REQUIRED - BPU7406 
      
      
      Converting the Log Master Repository
      
        
      
      An additional mechanism has been added to allow Log Master to perform the repository conversion and the conversion process must be applied to each Log Master repository that will be used across the DB2 Version 11 New Function Mode migration point.  
      
        
      
      It is recommended that a full backup of the Log Master repository be performed before the conversion and that no Log Master jobs are executed during the conversion. 
      
        
      
      Conversion is performed with the specification of an additional prepended parameter: 
      
        
      
      ·         REPOSCONV                      Perform the conversion and COMMIT the results 
      
      ·         REPOSCONV_TEST          Perform the conversion but ROLLBACK the results (test run) 
      
        
      
      E.g., 
    //ALPMAIN EXEC PGM=ALPMAIN,PARM='REPOSCONV_TEST,DKW,,ALPOPTS(ALP$OPTS)' 
    //STEPLIB  DD DISP=SHR,DSN=SYS3.DKW.DSNEXIT                           
    //         DD DISP=SHR,DSN=CSGI.DB2V10M.DSNLOAD                       
    //         DD DISP=SHR,DSN=BMC.ALP1110.LOADLIB                       
    //ALPPRINT DD SYSOUT=*,LRECL=200                                      
    //ALPDUMP  DD SYSOUT=*                                                
    //SYSUDUMP DD SYSOUT=* 
                                                                                           
     See Log Master documentation for a description of the standard parameters.   
        
      
      Any Log Master SYSIN, if specified, will be ignored.  
      
        
      
      As with standard Log Master processing, the conversion will use information from the options module to determine the tables to be updated. In addition and as applicable, the code will determine the data sharing conversion RBA (MAX RBA FOR TORBA from DSNJU004) to guide conversion of columns that may contain either an RBA or an LRSN. 
      
        
      
      Sample Output: 
      
      . . .
      
      10:59:52 BMC097083I LOG MASTER REPOSITORY UPDATE - MAX RBA FOR TORBA:  2002A9EC49E1              
    10:59:52 BMC097083I ROWS UPDATED   TABLE NAME COLUMN NAME        ACTION                       
    10:59:52 BMC097083I ------------   ---------- ------------------ ----------------------------   
    10:59:52 BMC097083I            0   ALPWHIS    START_RBA          PAD HIGH VALUES                
    10:59:52 BMC097083I            0                                 EXTEND RBA                     
    10:59:52 BMC097083I            6                                 EXTEND LRSN                    
    10:59:52 BMC097083I            0              END_RBA            PAD HIGH VALUES                
    10:59:52 BMC097083I            0                                 EXTEND RBA                     
    10:59:52 BMC097083I            6                                 EXTEND LRSN                    
    10:59:52 BMC097083I ------------   ---------- ------------------ ----------------------------   
    10:59:52 BMC097083I            0   ALPWLSH    ACTUAL_FROM_RBA    PAD HIGH VALUES                
    10:59:52 BMC097083I            0                                 EXTEND RBA                     
    10:59:52 BMC097083I            4                                 EXTEND LRSN                    
    . . .  
    10:59:52 BMC097083I            0              REDORBA            PAD HIGH VALUES                
    10:59:52 BMC097083I            4                                 ELIMINATE BLANKS               
    10:59:52 BMC097083I            0                                 EXTEND RBA                     
    10:59:52 BMC097083I            0                                 EXTEND LRSN                    
    10:59:52 BMC097083I ------------   ---------- ------------------ ----------------------------   
    . . .  
    10:59:52 BMC097083I            1   ALPURID    URID               PAD HIGH VALUES                
    10:59:52 BMC097083I            0                                 EXTEND RBA                     
    10:59:52 BMC097083I            7                                 EXTEND LRSN                    
    10:59:52 BMC097083I            3                                 EXTEND RBA - RECORD TYPE 2     
    10:59:52 BMC097083I            0                                 EXTEND LRSN - RECORD TYPE 3    
    10:59:52 BMC097083I            0              URIDLRSN           PAD HIGH VALUES                
    10:59:52 BMC097083I           11                                 EXTEND LRSN                    
    10:59:52 BMC097083I ------------   ----------------------------------------------------------   
    10:59:52 BMC097083I           65   TOTAL UPDATES                                                
    10:59:52 BMC097083I UPDATES ROLLED BACK                                         
              
      
         
      
      This output reflects a subsystem that started as a standalone subsystem and was converted to data sharing(MAX TORBA) at 2002A9EC49E1.    Since REPOSCONV_TEST was specified the updates were rolled back. The actual number of lines updated will depend on your use of the product and whether the subsystem is standalone, data sharing, or converted to data sharing.  
      
        
      
      Updates applied: 
      
        
    table column EXTEND RBA 
    Column is an RBA field or either RBA/LRSN where value <= MAX TORBA 
    Old value: xxxxxxxxxxxx 
    New value: 00000000xxxxxxxxxxxx 

    table column EXTEND LRSN 
    Column is an LRSN field or either RBA/LRSN where value > MAX TORBA 
    Old value: xxxxxxxxxxxx 
    New value: 00xxxxxxxxxxxx000000 

    table column PAD HIGH VALUES 
    Column is either RBA/LRSN but we need to pad with x’FF’ rather than x’00’ 
    Old value: FFFFFFFFFFFF 
    New value: FFFFFFFFFFFFFFFFFFFF 

    table column ELIMINATE BLANKS    
    Column is deprecated 
    404040404040    -> (empty field) 
    NOTE: 
      
    After you convert the repository, the repository should not be shared with any Log Master release earlier than 11.1. After you apply the PTF and convert the repository, if Log Master discovers both 6-byte and 10-byte values in the repository, you will receive the following message and will need to perform the repository conversion again: 
      
    BMC097800S REPOSITORY INTERNAL ERROR 15: CONVERTED REPOSITORY INCLUDES NON-EXTENDED RBAS - BPU7406 
      

     


    Article Number:

    000105105


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles