IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    JR30834

  • Reported component name

    DB2 UDB WSE WIN

  • Reported component ID

    5765F3501

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-20

  • Closed date

    2009-05-03

  • Last modified date

    2009-05-03

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
06 October 2021