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

UPGRADE TO FEDERATION SERVER V97 FAILED DUE TO UNEXPECTED
'REMOTE_COLUMN_SCALE' COLUMN OPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If there is 'REMOTE_COLUMN_SCALE' column option for nickname's 
TIMESTAMP/DATETIME data type column, the upgrade to federation 
server version 9.7 will fail. 
 
The error message is: 
SQL0902C  A system error (reason code = "SYSCOLOPTIONS Migration 
DMS  rc=80090005: <nickname>") occurred.  Subsequent SQL 
statements cannot be  processed.  SQLSTATE=58005 
 
And you will also find the following log in db2diag.log file: 
 
2011-04-01-13.28.12.978838-300 I396271A749        LEVEL: Severe 
PID     : 557076               TID  : 1544        PROC : db2sysc 
0 
INSTANCE: djinst1              NODE : 000         DB   : DB2DJA 
APPHDL  : 0-7                  APPID: 
*LOCAL.djinst1.110401182805 
AUTHID  : DJINST1 
EDUID   : 1544                 EDUNAME: db2agent (DB2DJA  ) 0 
FUNCTION: DB2 UDB, catalog migration, sqlrlm_95toCobra_djpd, 
probe:10922 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
CALLED  : DB2 UDB, catalog migration, sqlrlmLogErr 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String with size, 61 bytes 
SYSSERVERS Migration DMS rc=801a006d: upgrade remote table pd
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as Error Description.                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
Drop the related nickname and try to upgrade again.
available fix packs:
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
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
N/A
Comment
N/A
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.05.2011
03.10.2011
03.10.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList