IT25927: PADIAGLOGCOLL::PARSEFILTERPARMS SHOWS UP IN DB2DIAG.LOG FREQUENTLY.

Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• PADiagLogColl::parseFilterParms shows up in db2diag.log with
  message "START TIMESTAMP and END TIMESTAMP" as following sample
  shows when application invoke PD_GET_DIAG_HIST() table function
  with invalid parameters where starttime > endtime, but no error
  return to the application.
  
  
  2018-03-30-17.51.04.291464+540 E559724A1376         LEVEL: Error
  PID     : 12345678             TID : 1234           PROC :
  db2sysc 0
  INSTANCE: db2inst1             NODE : 000           DB   :
  SAMPLE
  APPHDL  : 0-32                 APPID:
  *LOCAL.DB2.180330085039
  AUTHID  : XXXXX              HOSTNAME: <host>
  EDUID   : 3343                 EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, RAS/PD component,
  PADiagLogColl::parseFilterParms, probe:20
  MESSAGE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
            Invalid parameter
  DATA #1 : String, 42 bytes
  START TIMESTAMP greater than END TIMESTAMP
  DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
  0x0000000110FDCEC0 : 0000 0000 0000 0000 0000 0000 FFFF F810
  ................
  0x0000000110FDCED0 : 0021 5354 4152 5420 5449 4D45 5354 414D
  .!START TIMESTAM
  0x0000000110FDCEE0 : 5020 616E 6420 454E 4420 5449 4D45 5354
  P and END TIMEST
  0x0000000110FDCEF0 : 414D 5000 0000 0000 0000 0000 0000 0000
  AMP.............
  0x0000000110FDCF00 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x0000000110FDCF10 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x0000000110FDCF20 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x0000000110FDCF30 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x0000000110FDCF40 : 0000 0000 0000 0000
  ........
  
  2018-03-30-17.51.04.292095+540 I561101A626          LEVEL:
  Warning
  PID     : 12345678             TID : 1234           PROC :
  db2sysc 0
  INSTANCE: DB2              NODE : 000           DB   :
  SAMPLE
  APPHDL  : 0-32                 APPID:
  *LOCAL.DB2.180330085039
  AUTHID  : XXXX              HOSTNAME: <host>
  EDUID   : 3343                 EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, WLM, sqlrwGetPDDiagHist_v10fp3, probe:200
  MESSAGE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
            Invalid parameter
  DATA #1 : String, 75 bytes
  Error initializing the diag log collector. Not able to access
  the diag log.
  
  
  Local bypass:
  Make sure starttime is less than endtime when invoke
  PD_GET_DIAG_HIST()
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 4 Fixpack 4
  

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:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP