IBM Support

JR29393: EXTRA ERROR IN DB2DIAG.LOG DURING DB2STOP ON NT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We got extra  error message in db2diag.log during db2stop.  The
    message is like that.
    2008-01-22-12.20.19.875000-480 E9128H418          LEVEL: Error
    (OS)
    PID     : 2572                 TID  : 2816        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000
    EDUID   : 2816                 EDUNAME: db2pclnr (SOURCE)
    FUNCTION: DB2 UDB, oper system services, sqloLioDestroyPort,
    probe:1
    MESSAGE : ZRC=0x83000006=-2097151994
    CALLED  : OS, -, CloseHandle
    OSERR   : 6 "The handle is invalid."
    
    The problem only happen on NT.
    
    we add the code to close the iocp port when shutdown the page
    cleaner. But we should only do that on AIX because on AIX each
    page cleaner  will try to collect the IO itself. But for NT, db2
    got a collecter thread to collect all the IO. So the page
    cleaner don't need to close the IOCP port.
    
    LOCAL FIX: None
    
    It will be fixed in future releases.
    

Local fix

  • None.
    
    Will be fixed in future releases.
    

Problem summary

  • ERROR DESCRIPTION:
    We got extra  error message in db2diag.log during db2stop.  The
    message is like that.
    2008-01-22-12.20.19.875000-480 E9128H418          LEVEL: Error
    (OS)
    PID     : 2572                 TID  : 2816        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000
    EDUID   : 2816                 EDUNAME: db2pclnr (SOURCE)
    FUNCTION: DB2 UDB, oper system services, sqloLioDestroyPort,
    probe:1
    MESSAGE : ZRC=0x83000006=-2097151994
    CALLED  : OS, -, CloseHandle
    OSERR   : 6 "The handle is invalid."
    
    The problem only happen on NT.
    
    we add the code to close the iocp port when shutdown the page
    cleaner. But we should only do that on AIX because on AIX each
    page cleaner  will try to collect the IO itself. But for NT, db2
    got a collecter thread to collect all the IO. So the page
    cleaner don't need to close the IOCP port.
    

Problem conclusion

  • LOCAL FIX: None
    
    It will be fixed in future releases.
    
    LOCAL FIX:
    None.
    
    The checking is fixed in v95 fp2
    

Temporary fix

  • LOCAL FIX: None
    
    It will be fixed in future releases.
    
    LOCAL FIX:
    None.
    
    fixed in v95 fp2
    

Comments

APAR Information

  • APAR number

    JR29393

  • Reported component name

    DB2 UDB WSE WIN

  • Reported component ID

    5765F3501

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-05-26

  • Closed date

    2008-11-10

  • Last modified date

    2008-11-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • engn
    

Fix information

  • Fixed component name

    DB2 UDB WSE WIN

  • Fixed component ID

    5765F3501

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 November 2008