PH12726: POSSIBLE RC=02 WITH "NO DATA TO REPORT" OR MISSING DATA WHEN LEAP SECOND ARE SET IN THE SYSTEM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When the product determines if the log file is needed for
  processing it is comparing the local (requested time) with
  GMT adjustment to UTC time (which is GMT + leap seconds).
  This could lead to the problem when actual log with needed
  data is skipped. The change needs to be done to ALAGEND to
  convert the correct LRSN (in UTC) to the BPSDATE/BPSTIME so
  this values (in UTC) will be checked with the UTC
  date/time from the BSDS for the log.
  

Local fix

• In order to overcome the issue the user will need to adjust the
  end time by the leap seconds value.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. The ALABSQL was trying to find the   *
  *                         LOB/XML IDs for null locator.        *
  *                      2. The IDMAP report can improperly show *
  *                         the data for the tablespace when     *
  *                         SEGSIZE of 1024K. We will need to    *
  *                         adjust the print line beyond header  *
  *                         line.                                *
  *                      3. Possible RC=02 with "No data to      *
  *                         report" as a result of incorrect     *
  *                         leap seconds processing.             *
  *                      4. CATFILE lookup error occurs in       *
  *                         ALAGLOAD if LOB and XML columns      *
  *                         present in reported tables.          *
  *                      5. LAT falls with S0C4 in ALACLDEL      *
  *                         because of the absence of EXTFILE    *
  *                         and other DDs.                       *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  .
  

Problem conclusion

• Apply the PTF
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI64258

Modules/Macros

• ALABSQL  ALACLDEL ALAGEND  ALAIDRP  ALALLB
  

Fix information

• Fixed component name

  DB2 LOG ANALYSI

• Fixed component ID

  5655E6601

Applicable component levels

• R350 PSY UI64258

     UP19/07/19 P F907

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.