|
Problem IC99276
|
Status: Closed |
DATABASE UPGRADE TO DB2 V10.X DOES NOT DELETE THE PRE-V10 DB2TSCHG.HIS FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
After migration from DB2 v9.7 to DB2 v10.1 the DBPATH gets
converted from the old style to the new pureScale like layout.
For example within the old (pre-V10) directory layout, You can
find DB2TSCHG.HIS in
~/<instance>/NODE0000/SQL00001
and in the new layout under:
~/<instance>/NODE0000/SQL00001/MEMBER0000
Once database upgrade is finished you may end up with two
different versions of the DB2TSCHG.HIS file because the v97 file
does still exist.
If you use db2logsForRfwd from DB2 10.1 against the pre-V10 file
version of DB2TSCHG.HIS you will get unpredictable results, like
core dump, no output etc ...
With this APAR we will delete the pre-V10 DB2TSCHG.HIS file
during the
database upgrade step. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
remove the v.9x DB2TSCHG.HIS manually |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.02.2014
09.09.2014
09.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
