DB2 - Problembeschreibung
Problem IT02591 | Status: Geschlossen |
RECEIVE SQL0901N WITH ERROR MESSAGE "MSSQL3 UNKNOWN VERSION" WHEN INSERTING NICKNAME FOR 2012 SQL SERVER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * MSSQL server 2012 user * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix * * Pack 4) or higher * **************************************************************** | |
Local-Fix: | |
Use 2008 version number as work around like below: - db2 "alter server <your_server_name> version 2008" | |
Lösung | |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.06.2014 18.05.2017 18.05.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |