DB2 FOR LUW / DB2FORLUW / A10 - DB2

Set DB2_COMPATIBILITY_VECTOR to enable local federated DB2 
database and disable DB2 compatibility features against DRDA 
database. 
ALTER NICKNAME does not work to map remote DATE to local 
TIMESTAMP(0). 
 
For example: 
 
db2set DB2_COMPATIBILITY_VECTOR=ORA 
 
db2 create db testora 
 
connect to testora 
 
CREATE WRAPPER drda 
 
create server <server_name> type db2/udb version 9.7 wrapper 
drda authorization <user_id> password <password> OPTIONS(dbname 
<dbname>, password 'Y') 
 
create user mapping for user server <server_name> options( 
remote_authid <user_id>, remote_password <password>) 
 
set passthru <server_name> 
 
create table ltab (c1 int, c2 date) 
 
set passthru reset 
 
create nickname nck1 for <server_name>.<user_id>.ltab 
 
 
ALTER NICKNAME <user_id>.nck1 ALTER COLUMN C2 LOCAL TYPE 
TIMESTAMP(0) 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0604N  The length, precision, or scale attribute for column, 
distinct type, 
structured type, array type, attribute of structured type, 
routine, cast 
target type, type mapping, or global variable "DATE" is not 
valid. 
SQLSTATE=42611 
 
The mapping rule refers to 
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2 
Fcom.ibm.swg.im.iis.db.found.conn.fw.dtm.doc%2Ftopics%2Fiiynwdtm 
dlf.html

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALTER NICKNAME IN ORA COMPATIBLE MODE, FAILED TO MAP REMOTE  * 
* DATE TO LOCAL TIMESTAMP(0)                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 fixpack 3.                           * 
****************************************************************

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
 

This is fixed in version 10.1 fixpack 3.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

25.09.2013
30.10.2013
30.10.2013