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

DB2 MOVE WITH COPY OPTION FROM V9.5/V9.1 TO V9.7 GIVES SQL0206N

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
V9.7 FP1 - database sourcedb and targetdb 
 
1) db2 connect to sourcedb 
 
2) create table schem1.table1(col1 integer) 
 
3) db2 connect reset 
 
4) db2move sourcedb copy -sn schem1  -co target_db targetdb 
schema_map 
 "((SCHEM1, SCHEM1))" -u userid -p password 
 
(this is invoked on the DB2 instance that hosts targetdb) 
 
5)  table schem1.table1 is copied into database targetdb 
 
This also works if both the sourcedb and targetdb are V9.5. 
 
 
When sourcedb is V9.5 or V9.1, and targetdb is V9.7, this does 
not work. 
 
- No *.err file created. 
In command line, we can see this : 
 
--------------------------------------------- 
 
Error Message : sqlcode -206:select objschema, objname, type, 
subtype, generated_cols, 
 
db2move failed with -1 (debuginfo:220). 
 
-----------------------------------------------
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All db2 users below V9.7 FP3.                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 move with copy option from v9.5/v9.1 to v9.7 gives       * 
* SQL0206N                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users should move to V9.7 FP3 or above.                      * 
****************************************************************
Local Fix:
NA
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fix included in V9.7 FP3 and above.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69806 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.07.2010
28.09.2010
28.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList