home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC88678 Status: Closed

SQL0180N IS REPORTED WHEN CREATE MSSQL NICKNAME

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2 => create wrapper mssql_wrap library 'libdb2mssql3.so' 
db2 => create server mssql2008_serv type mssqlserver version 
2008 wrapper mssql_wrap options(node '*', dbname '*') 
db2 => create user mapping for user server mssql2008_serv 
options(remote_authid '*', remote_password '*') 
db2 => set passthru mssql2008_serv 
db2 => create table test3 (c1 date, c2 char) 
db2 => insert into test3 values ('2012-01-01','a') 
db2 => insert into test3 values ('2012-01-02','b') 
db2 => insert into test3 values ('2012-01-03','c') 
db2 => insert into test3 values ('2012-01-04','d') 
db2 => set passthru reset 
 
From SQL Server Management Studio, run 
EXEC sp_createstats 
 
After that, create nickname will fail: 
db2 => create nickname mssql_test3 for mssql2008_serv.*.test3 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0180N  The syntax of the string representation of a datetime 
value is 
incorrect.  SQLSTATE=22007
Problem Summary:
User affected: 
  Users who of  in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was fistly fixed in Version 10, FixPak 2. This 
fix should be applied on the federation Server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2012
04.01.2013
04.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList