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 IT02597 Status: Closed

RECEIVE SQL0901N WITH ERROR MESSAGE "MSSQL3 UNKNOWN VERSION" WHEN
INSERTING NICKNAME FOR 2012 SQL SERVER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Here is a sample reproducing flow. 
 
- create wrapper MSSQLODBC3 
- create server <your_server_name> type MSSQLSERVER version 2012 
wrapper MSSQLODBC3 options (DB2_IUD_ENABLE 'Y', node 
'<your_2012_dsn>', dbname '<your_dbname>') 
- create user mapping for user server <your_server_name> options 
(remote_authid '<user>', remote_password '<password>') 
- create nickname TN for <your_server_name>."<user>"."T1" 
- insert into TN values(2) 
  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 or command failed because of a 
database system error. (Reason "MSSQL3 Unknown version ".) 
SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* MSSQL server 2012 user                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Release 10.1.0.5 (also known as v10.1 Fix     * 
* Pack 5) or higher                                            * 
****************************************************************
Local Fix:
Use 2008 version number as work around like below: 
- db2 "alter server <your_server_name> version 2008"
Solution
Fixed in DB2 Release 10.1.0.5 (also known as v10.1 Fix Pack 5)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.06.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 FixList