IT31384: IN PURESCALE UNNECESSARY SQLB_EAT_OBJ_TYPE_NOT_FOUND MESSAGES MAY BE WRITTEN INTO DB2DIAG.LOG

APAR status

• Closed as program error.

Error description

• Here are sample unnecessary messages in db2diag.log:
  -----
  2019-12-11-13.06.20.023441+540 I43865676A1384       LEVEL:
  Severe
    omit
  FUNCTION: DB2 UDB, buffer pool services, sqlbpfAddToQ, probe:821
  MESSAGE : ZRC=0x8002045A=-2147351462=SQLB_EAT_OBJ_TYPE_NOT_FOUND
            "Requested object type could not be found in the
  Extent Anchor Table for the table space."
  DATA #1 : String, 65 bytes
  Failed to setup the extent anchor table for this prefetch
  request
  DATA #2 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 104 bytes
    omit
  
  2019-12-11-13.06.20.024414+540 I43867061A1461       LEVEL:
  Severe
    omit
  FUNCTION: DB2 UDB, buffer pool services, sqlbServiceLeafRequest,
  probe:3791
  MESSAGE : ZRC=0x8002045A=-2147351462=SQLB_EAT_OBJ_TYPE_NOT_FOUND
            "Requested object type could not be found in the
  Extent Anchor Table for the table space."
  DATA #1 : String, 7 bytes
  req_ptr
  DATA #2 : Prefetcher SQLB_pfRequest structure,
  PD_TYPE_SQLB_PFREQUEST, 1000 bytes
    omit
  
  2018-11-08-23.20.20.658960-300 I5164711A7025        LEVEL:
  Warning
    omit
  FUNCTION: DB2 UDB, buffer pool services,
  sqlbLoadExtentAnchorFromObjTable, probe:1736
  MESSAGE : ZRC=0x8002045A=-2147351462=SQLB_EAT_OBJ_TYPE_NOT_FOUND
            "Requested object type could not be found in the
  Extent Anchor Table for the table space."
  DATA #1 : String, 98 bytes
  OT record skipped load into EAT due to one of the table's
  objects being in SQLD_OBJ_PARTIAL state.
  -----
  
  DB2DUMP and/or ALT_DB2DUMP will have the associated dump.bin
  files and may impact disk space.
  
  These messages may be written unexpectedly.  It can be ignored
  and the associated dump.bin files also can be deleted.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Db2 Version 11.1                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 Version 11.1 Mod 4 Fix Pack 6.                *
  ****************************************************************
  

Problem conclusion

• Problem was first fixed in Db2 Version 11.1 Mod 4 Fix Pack 6.
  

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