suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT29561 Status: Closed

SQL27999N REASON CODE 14 ERROR RETURNED WHEN ISSUING AN IMPORT AGAINST A
NICKNAME FEDERATED TO SQL SERVER 2012 AND 2014

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Issuing an import against a nickname returns the error below:

SQL27999N The requested IMPORT operation into a remote target
(nickname) cannot be performed. Reason code = "14".

The following message is displayed on db2diag.log:

2019-06-17-14.33.47.873628-240 I5069715A457         LEVEL: Error
PID     : 25231368             TID : 1              PROC :
db2fmp (39644) 0
INSTANCE: db2inst1             NODE : 000           DB   :
SAMPLE
APPID   : *N0.db2inst1.1234567890
HOSTNAME: localhost
EDUID   : 1                    EDUNAME: db2fmp (39644) 0
FUNCTION: DB2 UDB, Query Gateway, SQLQG_DSPROC_NICKNAMEINFO,
probe:45
MESSAGE : Unsupported mssql version
DATA #1 : String, 4 bytes
2014

This message appears even using a driver which supports SQL
Server 2012 and 2014.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 11 or higher                    *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.06.2019
25.02.2020
25.02.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)