APAR UPDATE March 25th 2024

This was a pretty slow month with one HIPER and few other fixes.

HIPERs:

PH59407 WITH UI92301 APPLIED, GET SQLCODE -204 DUE TO CURRENTSCHEMA NOT APPLIED. [Caused by PH53916]

Interesting for RTS:

None.

RUNSTATS:

None.

Query performance:

PH58683 INEFFICIENT INDEX MAY BE CHOSEN FOR AN SQL STATEMENT CONTAINING EQUAL AND RANGE PREDICATES

PH59503 DB2 NATIVE REST PACKAGES CONTAINS STMTNO COLUMN VALUE 0 FOR ALL ROWS IN SYSIBM.SYSPACKSTMT. This comes with a little SQL that you should execute to see how many Restful packages you must drop and recreate:

SELECT A.COLLID             
      ,A.NAME               
      ,A.VERSION            
      ,A.STATEMENT          
FROM SYSIBM.SYSPACKSTMT A   
    ,SYSIBM.SYSPACKAGE  B   
WHERE A.COLLID   = B.COLLID 
  AND A.NAME     = B.NAME   
  AND A.VERSION  = B.VERSION
  AND B.HOSTLANG = 'R'      
  AND A.SECTNO   = 1        
  AND A.STMTNO   = 0        
FOR FETCH ONLY              
WITH UR                     
;                           

PH59939 AN UTILITY CALL CATMAINT UPDATE SCHEMA SWITCH MAY SWITCH THE SCHEMA FOR AN UDF RESULTING WITH CATALOG INCONSISTENCIES. This is still OPEN but you can run the following SQL to see if you might get hit by the problem caused by use of SCHEMA SWITCH:

SELECT SR.SCHEMA                             
      ,SR.NAME                               
FROM SYSIBM.SYSROUTINES SR                   
WHERE SR.ORIGIN = 'Q'                        
  AND NOT EXISTS (SELECT 1                   
                  FROM SYSIBM.SYSPACKAGE SP  
                  WHERE SP.COLLID = SR.SCHEMA
                    AND SP.NAME   = SP.NAME  
                 )                           
FOR FETCH ONLY                               
WITH UR                                      
;                                            

IAG2:

PH59483 IAG2 INSERT PROCESSING ABENDS0C4 00000004 PIC04 RC04 IN DSNISFPIOFFSET01598

FIT/FTB:

None.

Now come the three tables containing all the APARs.

First are the Real-time Statistics APARs – If the RTS are incorrect then any Utility generation or Access path decision based upon them could also be incorrect.

Next are the RUNSTATS APARs – If RUNSTATS causes data problems this, obviously, can have a major impact upon performance after the following BIND, REBIND or dynamic SQL PREPARE.

Finally, come the SQL PERFORMANCE APARs – In here are all relevant performance APARs as well as HIPERs that do not fit into any other category. A HIPER warrants a check in all cases.

All three tables have the same headings:

APAR – The assigned APAR for the problem.

CLOSED – This is the date in YYYY-MM-DD format when the APAR was closed.

STATUS – This column is NEW, NEW & CLOSED, CLOSED or PE xxxxx. A PE means that this APAR went PE and the xxxxx is the corrective APAR.

Db2 12 – If the PTF is for Db2 12 then it is listed here else N/A or OPEN.

Db2 13 – If the PTF is for Db2 13 then it is listed here else N/A or OPEN.

HIPER – Contains Y if the APAR is a HIPER. Can also contain (Y) if it is OPEN but presumed to be a HIPER, else it is blank.

Description – This is the APAR description taken from the header text. Sometimes I add extra details if the description is misleading or incorrect.

Note: If the PTF column has OPEN it means that the PTF was still open when the last check was done; of course it could have been Closed since this post was updated. Every year all APARs that were closed over two years ago are deleted.

RTS APARs:

RUNSTATS APARs:

SQL PERFORMANCE and general HIPERs:

If you have any comments or wishes please feel free to contact me!

TTFN,

Roy Boxwell