IT32515: FODC_TRAP GENERATED DURING MON_GET_CONNECTION PROCESSING AN APPLICATION

APAR status

• Closed as program error.

Error description

• During MON_GET_CONNECTION processing it is possible that an
  application to be reported on is found
  to be missing control blocks and MON_GET_CONNECTION
  processing traps.  The db2diag.log would show probes such
  as the following:
  
  2020-03-31-22.46.10.718000-240 I1794257F634         LEVEL: Error
  PID     : 2952                 TID : 8012           PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000           DB   :
  SAMPLE
  APPHDL  : 0-17591              APPID: 123456789
  UOWID   : 2                    ACTID: 1
  AUTHID  : DB2ADMIN             HOSTNAME: LOCALHOST
  EDUID   : 8012                 EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, WLM,
  sqlrwFilteredApplicationIterator::execute, probe:11656
  DATA #1 : String, 20 bytes
  rds App CB not valid
  DATA #2 : String, 35 bytes
  appHandle: 0-17601 appStatus: 0x802
  
  2020-03-31-22.46.10.718000-240 I1794893F178       LEVEL: Severe
  PID:2952 TID:8012 NODE:000 Title: sqeApplication
  Dump File:C:\PROGRA~1\IBM\SQLLIB~1\DB2\2952.8012.000.dump.bin
  
  2020-03-31-22.46.10.999000-240 I1795073F671         LEVEL:
  Severe
  PID     : 2952                 TID : 8012           PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000           DB   :
  SAMPLE
  APPHDL  : 0-17591              APPID: 123456789
  UOWID   : 2                    ACTID: 1
  AUTHID  : DB2ADMIN             HOSTNAME: LOCALHOST
  EDUID   : 8012                 EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, RAS/PD component,
  pdResilienceIsSafeToSustain, probe:800
  DATA #1 : String, 37 bytes
  Trap Sustainability Criteria Checking
  DATA #2 : Hex integer, 8 bytes
  0x0000000400041040
  DATA #3 : Boolean, 1 bytes
  false
  b
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply  v11.1 Mod 4 Fixpack 6 to DB2 server                   *
  ****************************************************************
  

Problem conclusion

• First fixed in v11.1 Mod 4 Fixpack 6
  

Temporary fix

•  See LOCAL 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