IBM Support

JR52153: CREATE NICKNAME FAILS WITH SQL0901N "INVALID NICKNAME COLUMN LENGTH" WHEN USING ORACLE RDB ODBC DRIVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When connecting to an Oracle Rdb database via DB2 nicknames and
    the Federated ODBC Wrapper, a nickname could fail with the
    following error:
    
    CREATE NICKNAME TESTODBC.T1 FOR RDB.T1
    DB21034E  The command was processed as an SQL statement because
    it was not a
    valid Command Line Processor command.  During SQL processing it
    returned:
    SQL0901N  The SQL statement failed because of a non-severe
    system error.
    Subsequent SQL statements can be processed.  (Reason "Invalid
    nickname column
    length".)  SQLSTATE=58004
    
    This could happen if the data length of the CHAR field is
    greater than or equal to 255.
    
    
    Updating the column could result in an SQL3324N error as
    follows:
    
    update TESTODBC.T1 set AFTER_TEXT = 'testing' where id = 12345
    DB21034E  The command was processed as an SQL statement because
    it was not a valid Command Line Processor command.  During SQL
    processing it returned:
    SQL3324N  Column "AFTER_TEXT" has a type of "CHAR" which is not
    recognized.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 10.5, Fix pack 7                      *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 10.5, Fix pack 7
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR52153

  • Reported component name

    FEDERATION SERV

  • Reported component ID

    5724N9700

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-12-26

  • Closed date

    2016-01-29

  • Last modified date

    2016-01-29

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

    JR52149

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

Fix information

  • Fixed component name

    FEDERATION SERV

  • Fixed component ID

    5724N9700

Applicable component levels

  • RA50 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCAVPY","label":"General Issues"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 January 2016