IBM Support

IT06067: FEDERATION: IMPORT ON NICKNAME FAILS WITH SQL27999N REASON CODE = "14".

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An import on a Nickname will fail with SQL27999N -  Reason code
    14 If the server name is created as a string with double quota.
    This problem exists for any Federated Server wrappers.
    
    Example
    create server "s1" type mssqlserver version 2008 wrapper
    MSSQLODBC3 options(node 'mssql2008csdl2', dbname 'mssql2008db2')
    DB20000I  The SQL command completed successfully.
    
    create user mapping for user server "s1" options(remote_authid
    'j15user1', remote_password 'XXX')
    DB20000I  The SQL command completed successfully.
    
    create nickname n1 for "s1".j15user1.t11
    DB20000I  The SQL command completed successfully.
    
    Import from 1.ixf OF ixf ALLOW WRITE ACCESS COMMITCOUNT 10000
    MESSAGES 1.import.msg INSERT into n1
    
    Number of rows read         = 0
    Number of rows skipped      = 0
    Number of rows inserted     = 0
    Number of rows updated      = 0
    Number of rows rejected     = 0
    Number of rows committed    = 0
    
    The error message in 1.import.msg
    SQL27999N  The requested IMPORT operation into a remote target
    (nickname)
    cannot be performed.  Reason code = "14".
    

Local fix

  • Create the server without "" - create server s1 , which will
    effectively store the Servername in capitals in the Catalog.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 10.1 and Fix Pack 5                   *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 Version 10.1 and Fix Pack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06067

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-12

  • Closed date

    2015-07-13

  • Last modified date

    2015-07-13

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

    JR51984

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 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":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 July 2015