IT26343: LOAD ERROR: "OPEN LOCFILE FOR WRITE FAILED!" IF A LOAD QUERY TABLE IS EXECUTED IN PARALLEL

APAR status

• Closed as program error.

Error description

• There might be a race condition for a parallel LOAD of a CDE
  table and the load monitoring with LOAD QUERY TABLE or
  db2LoadQuery API for the same table.
  This may cause concurrent access to the LOC file that is used by
  LOAD internally. In rare cases this might abort the LOAD with
  the following message in db2diag.log:
  
  You will typically see two different application handles
  reporting errors, here for the LOAD QUERY (0-107) it reports:
  
  2018-08-17-22.44.23.781278+120 I91762883A551        LEVEL: Error
  PID     : 3539446              TID : 59887          PROC :
  db2sysc 0
  INSTANCE: db2sample        NODE : 000           DB   : SAMPLE
  APPHDL  : 0-107                APPID:
  199.199.199.199.62727.180817161433
  AUTHID  : SAPSR3               HOSTNAME: localhost
  EDUID   : 59887                EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
  probe:0
  MESSAGE : locfile data corrupt! (0 byte length) , 0, 0, Detected
  in
            file:sqlulocf.C, Line:430
  
  whereas the LOAD (0-90) itself reports:
  
  2018-08-17-22.44.23.781288+120 I91763435A613        LEVEL: Error
  PID     : 3539446              TID : 55775          PROC :
  db2sysc 0
  INSTANCE: db2sample        NODE : 000           DB   : SAMPLE
  APPHDL  : 0-90                 APPID:
  199.199.199.199.62710.180817161433
  AUTHID  : SAPSR3               HOSTNAME: localhost
  EDUID   : 55775                EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
  probe:0
  DATA #1 : String, 138 bytes
  LOADID: 55775.2018-08-17-22.44.23.765956.0 (18;974)
  open locfile for write failed! , -2029060074, 0, Detected in
  file:sqlulocf.C, Line:205
  ...
  
  2018-08-17-22.44.23.782967+120 I91765127A646        LEVEL: Error
  PID     : 3539446              TID : 55775          PROC :
  db2sysc 0
  INSTANCE: db2sample        NODE : 000           DB   : SAMPLE
  APPHDL  : 0-90                 APPID:
  199.199.199.199.62710.180817161433
  AUTHID  : SAPSR3               HOSTNAME: localhost
  EDUID   : 55775                EDUNAME: db2agent (SAMPLE) 0
  FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
  probe:0
  DATA #1 : String, 171 bytes
  LOADID: 55775.2018-08-17-22.44.23.765956.0 (18;974)
  /db2/SAMPLE/db2sample/NODE0000/SQL00001/load/DB200012.PID/DB2003
  CE.OID/load.loc , 0, 0, Detected in file:sqlulocf.C, Line:206
  

Local fix

Problem summary

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

Problem conclusion

• 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