IBM Support

LI74394: THE UNIVERSAL JDBC DRIVER (JCC) DOES NOT RETURN METADATA WHEN RUNNING A JAVA ROUTINE WHICH RETURNS EMPTY RESULTSET

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Universal JDBC Driver (JCC) does not return metadata along
    with the result code, when the JCC driver is used to run a
    Java stored procedure, which results in empty resultset.
    The same Java stored procedure executed using legacy JDBC driver
    returns the metadata correctly.
    
    Incorrect JCC driver output:
    ============================
    
    db2 call EMPTYRS
    
      Return Status = 0
    
    Expected legacy JDBC driver output:
    ==================================
    
    db2 call EMPTYRS
    Result set 1
      --------------
    
      COL1
      ---------
    
      0 record(s) selected.
    
      Return Status = 0
    

Local fix

  • Use legacy JDBC driver for running the Java stored procedures:
    
    db2set DB2_USE_DB2JCCT2_JROUTINE=OFF
    <restart instance>
    

Problem summary

  • USERS AFFECTED:
    Users running Java routines.
    
    PROBLEM DESCRIPTION:
    The Universal JDBC Driver (JCC) does not return metadata
    along with the result code, when the JCC driver is used to run a
    Java stored procedure.
    
    PROBLEM SUMMARY:
    The Universal JDBC Driver (JCC) does not return metadata when
    running a stored procedure, which results in empty resultset.
    
    Incorrect JCC driver output:
    ============================
    
    db2 call EMPTYRS
    
      Return Status = 0
    
    Expected output:
    ================
    
    db2 call EMPTYRS
    Result set 1
      --------------
    
      COL1
      ---------
    
      0 record(s) selected.
    
      Return Status = 0
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 5 (s091123).
    

Temporary fix

  • Use legacy JDBC driver for running the Java stored procedures:
    db2set DB2_USE_DB2JCCT2_JROUTINE=OFF
    <restart instance>
    

Comments

APAR Information

  • APAR number

    LI74394

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-31

  • Closed date

    2009-12-16

  • Last modified date

    2009-12-16

  • 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 UDE ESE LIN

  • Fixed component ID

    5765F4104

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:
16 December 2009