|
Problem IC73357
|
Status: Closed |
DATABASE UPGRADE FAILS IF TIMESTAMP TYPE MAPPING IS CREATED FOR SERVER TYPE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The database upgrade to v9.7 fails if timestamp type mapping
created for server type existing in the database.
For example, if the upgrading database has a type mapping
created by below DDL:
CREATE TYPE MAPPING "TYPEMAP_DRDA_TIMESTAMP" FROM LOCAL TYPE
TIMESTAMP TO SERVER TYPE DB2/UDB REMOTE TYPE "TIMESTAMP";
The database upgrade command will return the error message
below:
SQL2519N The database was restored but the restored database
was not upgraded
to the current release. Error "-902" with tokens "SYSSERVERS
Migration DMS
rc=80040001: " is returned.
The following shows a sample callstack:
0x00002B9100BF0A47 sqlrrSqlCode + 0x02ef
(/home2/iidev22/sqllib/lib64/libdb2e.so.1)
0x00002B9101442047 _Z12sqlrlmLogErrP8sqlrr_cbjmilPcm + 0x0239
(/home2/iidev22/sqllib/lib64/libdb2e.so.1)
0x00002B910144658B
_Z20sqlrlm_find_wrapnameP8sqlrr_cbtP8sqlr_tidPcjPhPi + 0x051b
(/home2/iidev22/sqllib/lib64/libdb2e.so.1)
0x00002B9101320DF1
_Z32sqlrlm_95toCobra_systypemappingsP8sqeAgenttP10SQLD_VALUEP8sq
lr_tidPcPS5_PlPbS8_
+ 0x0457
(/home2/iidev22/sqllib/lib64/libdb2e.so.1)
0x00002B910144119A
_Z19sqlrlm_catalogFixupP8sqlrr_cbtllm17sqlrlm_catChangesPc8sqlr_
tidPS3_P18sqlrlm_runstatsCmd
+ 0x1432
In the db2diag.log there will be a message like the following:
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 38
sqlerrmc: SYSSERVERS Migration DMS rc=80040001:
sqlerrp : SQLRM00E
sqlerrd : (1) 0x00000001 (2) 0x00000001 (3)
0x00000000
(4) 0x00000003 (5) 0xFFFFF429 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* SERVERNAME is a nullable column and this was not taken into *
* account. This issue is specific only to remote TIMESTAMP *
* types. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 and Fix pack 4. *
**************************************************************** |
| Local Fix: |
Drop type maps that are timestamps: db2 drop type mapping
TYPEMAP_DRDA_TIMESTAMP |
| available fix packs: |
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 |
Problem was first fixed in DB2 version 9.7 and Fix pack 4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73433
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.12.2010
28.04.2011
28.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
