A fix is available
APAR status
Closed as program error.
Error description
The most relevant image copy is used to collect mini logs, then this image copy is dropped. IBM Db2 Change Accumulation Tool starts to use the second most relevant copy to collect mini logs. When IBM Db2 Change Accumulation Tool searches for the suitable mini logs to adjust log reading interval, it first verifies that the mini log control table (MCT) contains mini log with the RANGE_LOW that is equal to the START_RBA of the image copy that the mini log control table (MCT) contains mini log with the RANGE_LOW that is equal to the START_RBA of the image copy that is used for the object. If such mini log exists, its RANGE_HIGH is used to check the next mini log record, RANGE_LOW of which should be equal to RANGE_HIGH of the previous one. All checks are made for MCT that is sorted by RANGE_LOW. When mini logs are collected to TO_CURRENT end point, RANGE_HIGH of the first mini log that is collected for the second relevant copy is always bigger than RANGE_LOW of the first mini log collected for the dropped image copy, so the RANGE_HIGH of this mini log would always be used for all subsequent mini log calls. This means that more logs are read for each subsequent call and elapsed time becomes bigger. The processing of MCT was changed to consider MCT records that are fully overlapped by the previous ones to allow to continue the search through MCT to find the mini logs that cover bigger range that is suitable for specified IBM Db2 Change Accumulation Tool parameters.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users * **************************************************************** * PROBLEM DESCRIPTION: Fix for PMR TS004433727 (APAR PH31841) * * * * The problem occurs for the following * * situation. * * The most relevant image copy is used * * to collect mini logs, then this image * * copy is dropped. IBM Db2 Change * * Accumulation Tool starts to use * * the second most relevant copy * * to collect mini logs. * * When IBM Db2 Change Accumulation Tool * * searches for the suitable mini logs * * to adjust log reading interval, it * * first verifies that the mini log * * control table (MCT) contains mini log * * with the RANGE_LOW that is equal to * * the START_RBA of the image copy that * * is used for the object. If such mini * * log exists, its RANGE_HIGH is used to * * check the next mini log record, * * RANGE_LOW of which should be equal to * * RANGE_HIGH of the previous one. All * * checks are made for MCT that is sorted * * by RANGE_LOW. * * When mini logs are collected to * * TO_CURRENT end point, RANGE_HIGH of * * the first mini log that is collected * * for the second relevant copy is always * * bigger than RANGE_LOW of the first mini * * log collected for the dropped image * * copy, so the RANGE_HIGH of this mini * * log would always be used for all * * subsequent mini log calls. This means * * that more logs are read for each * * subsequent call and elapsed time * * becomes bigger. * * The processing of MCT was changed to * * consider MCT records that are fully * * overlapped by the previous ones to * * allow to continue the search through * * MCT to find the mini logs that cover * * bigger range that is suitable for * * specified IBM Db2 Change Accumulation * * Tool parameters. * **************************************************************** * RECOMMENDATION: APPLY the PTF. Manual MCT clean up can be * * performed as a workaround to delete records * * of mini logs that were collected for * * the deleted image copy * **************************************************************** Fix for PMR TS004433727 (APAR PH31841) The problem occurs for the following situation. The most relevant image copy is used to collect mini logs, then this image copy is dropped. IBM Db2 Change Accumulation Tool starts to use the second most relevant copy to collect mini logs. When IBM Db2 Change Accumulation Tool searches for the suitable mini logs to adjust log reading interval, it first verifies that the mini log control table (MCT) contains mini log with the RANGE_LOW that is equal to the START_RBA of the image copy that is used for the object. If such mini log exists, its RANGE_HIGH is used to check the next mini log record, RANGE_LOW of which should be equal to RANGE_HIGH of the previous one. All checks are made for MCT that is sorted by RANGE_LOW. When mini logs are collected to TO_CURRENT end point, RANGE_HIGH of the first mini log that is collected for the second relevant copy is always bigger than RANGE_LOW of the first mini log collected for the dropped image copy, so the RANGE_HIGH of this mini log would always be used for all subsequent mini log calls. This means that more logs are read for each subsequent call and elapsed time becomes bigger. The processing of MCT was changed to consider MCT records that are fully overlapped by the previous ones to allow to continue the search through MCT to find the mini logs that cover bigger range that is suitable for specified IBM Db2 Change Accumulation Tool parameters.
Problem conclusion
Apply the PTF
Temporary fix
Comments
APAR Information
APAR number
PH31841
Reported component name
DB2 CHANGE ACCU
Reported component ID
5655F5500
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-11-18
Closed date
2020-12-03
Last modified date
2021-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
GGC#A001 GGC#ACIR GGC#ACIW GGC#ACON GGC#ACRD GGC#ACUP GGC#ADIS GGC#ADSC GGC#AEXT GGC#AFMT GGC#AFRR GGC#ALLO GGC#AMIN GGC#ASYS GGC#AUMX GGC#AUTO GGC#BIND GGC#CARD GGC#CHKR GGC#CL GGC#CL64 GGC#CL7 GGC#CL8 GGC#CLLS GGC#CMTS GGC#CNTL GGC#CPM GGC#CPNT GGC#CPOL GGC#DB2V GGC#DSAF GGC#DSPL GGC#DYNL GGC#ENCR GGC#ENQS GGC#ENVF GGC#EPRI GGC#ERSH GGC#ERSI GGC#FCPY GGC#ICAI GGC#ICAL GGC#ICCC GGC#ICCI GGC#IDCF GGC#IDSA GGC#IERR GGC#IHSA GGC#IKPL GGC#IKPN GGC#ILGP GGC#ILRA GGC#ILRS GGC#ILSA GGC#INIT GGC#IOPF GGC#IPIE GGC#IPPB GGC#IPPC GGC#IPPD GGC#IPPH GGC#IPPL GGC#IPPN GGC#IPPS GGC#IRPL GGC#ISNA GGC#JPRI GGC#LGAA GGC#LGAC GGC#LGAF GGC#LGAI GGC#LGAP GGC#LOGR GGC#LRD6 GGC#MAIN GGC#MDRV GGC#MLOG GGC#MMGR GGC#MPRI GGC#MREP GGC#MTIO GGC#OBRP GGC#OPCL GGC#OPRI GGC#OS GGC#PRF5 GGC#PRNG GGC#QSAM GGC#RANG GGC#RESM GGC#RH GGC#RH10 GGC#RM24 GGC#RPRP GGC#RUNT GGC#STAT GGC#SUBD GGC#SUBX GGC#SYSC GGC#TB GGC#TB7 GGC#TB8 GGC#TP GGC#TP10 GGC#TSS GGC#TSSA GGC#TUTL GGC#UPRI GGC#URDT GGC#UTLS GGC#UTOP GGC#VERS GGC#VSM GGC#WRIT GGC#XMLD GGC#XMLI GGC#XMLJ GGC#XMLS GGC#XMLU GGC$ACCS GGC$ACES GGC$BDSN GGC$BJBC GGC$BMSG GGC$BUTJ GGC$CALL GGC$CTCM GGC$DCVT GGC$DS GGC$DSN GGC$ETRG GGC$EXCP GGC$OPVS GGC$OPVV GGC$PRFD GGC$PRFR GGC$RCTL GGC$URDT GGC$ZPAR GGC3MEPI GGC3MEPL GGCALLZT GGCAPOST GGCBLNKT GGCCAPST GGCCHART GGCCOMAT GGCDOTT GGCDSNXT GGCEQUAL GGCFTRT GGCHEXT GGCIENQS GGCLGRD GGCLVALT GGCMMGR GGCNBLKT GGCNNUMT GGCPARET GGCPERIT GGCRPART GGCS99 GGCXAS31 GGCXAS64 GGCXASMS GGCXASPR GGCXDDM GGCXEXPM GGCXPDS GGCXUTLS GGCZPEXT
Fix information
Fixed component name
DB2 CHANGE ACCU
Fixed component ID
5655F5500
Applicable component levels
R310 PSY UI72899
UP20/12/07 P F012
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]
Document Information
Modified date:
05 January 2021