DB2 - Problem description
Problem IT06067 | Status: Closed |
FEDERATION: IMPORT ON NICKNAME FAILS WITH SQL27999N REASON CODE = "14". | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem 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". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 and Fix Pack 5 * **************************************************************** | |
Local Fix: | |
Create the server without "" - create server s1 , which will effectively store the Servername in capitals in the Catalog. | |
Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.12.2014 13.07.2015 13.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |