| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT07707 | Status: Closed |
THE DB2 UPDATE DB CFG FAILS WITH SQL5133N ERROR AFTER UPDATING FROM DB2 10.5 FIX PACK 4 TO NEWER LEVEL | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
Since DB2 10.5 Fix Pack 3, nchar_mapping was stored 16 even if
database code page is non-unicode. In DB2 10.5 Fix Pack 4,
nchar_mapping was stored 0, if database code page is
non-unicode. The change causes APAR IT04571 and SQL5133N error
on updating database configuration after the database migration
from v10.5 fp4 to newer.
You see the following entry in your db2diag.log:
FUNCTION: DB2 UDB, config/install, sqlfdbchk, probe:3354
MESSAGE : ZRC=0xFFFFEBF3=-5133
SQL5133N The configuration parameter was not updated
because the
specified value is not valid. Specified value: "".
Configuration
parameter name: "". Set of valid values: "".
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -5133 sqlerrml:
18
sqlerrmc: 16 nchar_mapping
sqlerrp : SQL10055
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See SYSROUTE APARs to see where this APAR is addressed * **************************************************************** | |
| Local Fix: | |
Please see following TechNote on how to fix this issue http://www.ibm.com/support/docview.wss?uid=swg21686677 | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.03.2015 09.05.2017 09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.7 |
|