JR30834: DB2 EXPORT SESSION JUST HANGS IF DESTINATION FILE SYSTEM IS FULL.

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• "db2 export to ... " command to filesystem, which is almost
  full, hangs. This problem is intermittent. Only the session
  which issues this command hangs. Rest of the sessions run
  perfectly fine.
  
  During hang situation, db2diag.log gets filled up with following
  messages continuously :
  
  2008-09-22-10.56.48.109000+330 I169893255H447     LEVEL: Error
  (Origin)
  PID     : 3380                 TID  : 6040        PROC :
  db2bp.exe
  INSTANCE: DB2                  NODE : 000
  APPID   : *LOCAL.DB2.080922042054
  FUNCTION: DB2 UDB, database utilities, sqluMoveFileContents,
  probe:2189
  MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
            DIA8312C Disk was full.
  DATA #1 : String, 29 bytes
  Not enough space for new file
  
  2008-09-22-10.56.48.109000+330 E169893704H477     LEVEL: Info
  (OS)
  PID     : 3380                 TID  : 6040        PROC :
  db2bp.exe
  INSTANCE: DB2                  NODE : 000
  APPID   : *LOCAL.DB2.080922042054
  FUNCTION: DB2 UDB, oper system services, sqlonewsize, probe:120
  MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
            DIA8312C Disk was full.
  CALLED  : OS, -, unspecified_system_function
  OSERR   : 112 "There is not enough space on the disk."
  
  Even after killing hang session, db2diag.log gets flooded with
  above entries. To get rid of these messages, we need to kill
  the db2bp.exe backend process (PID 3380).
  

Local fix

• Try to avoid running EXPORT against file system which is almost
  full.
  

Problem summary

• "db2 export to ... " command to filesystem, which is almost
  full, hangs. This problem is intermittent. Only the session
  which issues this command hangs. Rest of the sessions run
  perfectly fine.
  

Problem conclusion

• Users affected: ALL.
  
  Problem is first fixed in DB2 V91 FP 7.
  

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:

  JR30901

Fix information

• Fixed component name

  DB2 UDB WSE WIN

• Fixed component ID

  5765F3501

Applicable component levels

• R910 PSY

     UP