IBM Support

JR28519: DB2 ON WINDOWS EXECUTING AN UDF WITH AN EXTERNAL NAME USING AN UNC PATH FAILS WITH SQL0444N

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With DB2 V9.5 on Windows an UDF's which is using a Windows UNC
    Path as external name fails with SQL0444N Reason code: "4".
    
    Suppose a stored procedure (UDF) is created that way:
    
    CREATE PROCEDURE OUT_LANGUAGE (OUT language CHAR(8))
    ..
    EXTERNAL NAME '\\<machine>\<path>\proc.dll!OutLanguage'
    
    In this example EXTERNAL NAME is pointing to a Windows UNC
    (Unified Naming Convention) path. The stored procedure can be
    created but if it is executed fails with SQL0444N.
    
    The SQLCA structure which is dumped in db2diag.log shows:
    
    2008-02-20-17.33.37.995000+060 I57060H892         LEVEL: Info
    PID     : 4812                 TID  : 5224        PROC :
    db2syscs.exe
    INSTANCE: DB2_02               NODE : 000         DB   : SAMPLE
    APPHDL  : 0-145                APPID: *LOCAL.DB2_02.080220163336
    AUTHID  : DB2ADMIN
    EDUID   : 5224                 EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -444   sqlerrml: 57
     sqlerrmc: DB2ADMIN.OUT_LANGUAGE C_OUT_LANGUAGE \proc
    

Local fix

Problem summary

  • Users Affected: ALL
    
    Problem Description:
    
    With DB2 V9.5 on Windows an UDF's which is using a Windows UNC
    Path as external name fails with SQL0444N Reason code: "4".
    
    Suppose a stored procedure (UDF) is created that way:
    
    CREATE PROCEDURE OUT_LANGUAGE (OUT language CHAR(8))
    ..
    EXTERNAL NAME '\\<machine>\<path>\proc.dll!OutLanguage'
    
    In this example EXTERNAL NAME is pointing to a Windows UNC
    (Unified Naming Convention) path. The stored procedure can be
    created but if it is executed fails with SQL0444N.
    
    The SQLCA structure which is dumped in db2diag.log shows:
    
    2008-02-20-17.33.37.995000+060 I57060H892         LEVEL: Info
    PID     : 4812                 TID  : 5224        PROC :
    db2syscs.exe
    INSTANCE: DB2_02               NODE : 000         DB   : SAMPLE
    APPHDL  : 0-145                APPID: *LOCAL.DB2_02.080220163336
    AUTHID  : DB2ADMIN
    EDUID   : 5224                 EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -444   sqlerrml: 57
     sqlerrmc: DB2ADMIN.OUT_LANGUAGE C_OUT_LANGUAGE \proc
    
    Problem Summary:
    
    With DB2 V9.5 on Windows an UDF's which is using a Windows UNC
    Path as external name fails with SQL0444N Reason code: "4".
    
    Suppose a stored procedure (UDF) is created that way:
    
    CREATE PROCEDURE OUT_LANGUAGE (OUT language CHAR(8))
    ..
    EXTERNAL NAME '\\<machine>\<path>\proc.dll!OutLanguage'
    
    In this example EXTERNAL NAME is pointing to a Windows UNC
    (Unified Naming Convention) path. The stored procedure can be
    created but if it is executed fails with SQL0444N.
    
    The SQLCA structure which is dumped in db2diag.log shows:
    
    2008-02-20-17.33.37.995000+060 I57060H892         LEVEL: Info
    PID     : 4812                 TID  : 5224        PROC :
    db2syscs.exe
    INSTANCE: DB2_02               NODE : 000         DB   : SAMPLE
    APPHDL  : 0-145                APPID: *LOCAL.DB2_02.080220163336
    AUTHID  : DB2ADMIN
    EDUID   : 5224                 EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -444   sqlerrml: 57
     sqlerrmc: DB2ADMIN.OUT_LANGUAGE C_OUT_LANGUAGE \proc
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 2 (build s080811)
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR28519

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-02-20

  • Closed date

    2008-08-27

  • Last modified date

    2008-08-27

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

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

    JR30122

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       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:
27 August 2008