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

AFTER UPGRADING TO DB2 V11.5.4, IT IS POSSIBLE TO SEE SQL901 ERRORS AND
ENGINE CRASHES

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The known errors are
- SQL0901N Reason "Non-SYSTEM tenant for
3rd part name is not supported"
- SQL0901N Reason "SYSSEQUENCES
is missing row for identity column"
- SQL1224 and a trap file
from JITS where the top of the stack
shows:_ZN12JitsServices17policyAllowsTableEjmm
This can only
occur if your database was originally created prior to Db2 10.1
GA and you have upgraded this database through subsequent Db2
releases to Db2 11.5.
The error occurs because an internal
field in the table packed descriptor was not properly
initialized in versions prior to Db2 10.1 GA.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5.5.0 or higher                            *
****************************************************************
Local Fix:
If you already upgraded to Db2 v11.5.4.0 and hitting the issue,
download and run special version of db2cat tool to fix the
issue.
Please refer to the following Technote for instructions
and download links:
https://www.ibm.com/support/pages/node/6246049
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.07.2020
20.11.2020
20.11.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)