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

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 9.7 and Fix Pack 11                   *
  ****************************************************************
  

Problem conclusion

• Problem was first fixed in DB2 Version 9.7 and Fix Pack 11
  

Temporary fix

Comments

APAR Information

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

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

  IT06067 IT06581

Fix information

• Fixed component name

  MSSQL WRAPPER

• Fixed component ID

  5724N9705

Applicable component levels

• R970 PSN

     UP