IBM Support

JR26744: JDBC CALL DATABASEMETADATA.GETMAXCOLUMNNAMELENGTH() IS RETURNING 128 WHEN IT SHOULD RETURN 30.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JDBC call DatabaseMetaData.getMaxColumnNameLength() is returning
    128 when it should return 30.
    
    This was introduced to DB2 Version 9 FixPak 2 by the JCC 3.3.x
    driver which was shipped with fp2.
    

Local fix

  • No workaround is avaiable.
    

Problem summary

  • JDBC CALL DATABASEMETADATA.GETMAXCOLUMNNAMELENGTH() IS RETURNING
    128 WHEN IT SHOULD RETURN 30.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR26744

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-05-31

  • Closed date

    2009-09-29

  • Last modified date

    2009-09-29

  • 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 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R910 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
07 October 2021