Question & Answer
Question
The db2 update db cfg command returned the SQL5133N error after upgrading to DB2® 10.5 Fix Pack 4. How can this behavior be solved?
Cause
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.
You see the following entry in your db2diag.log:
FUNCTION: DB2 UDB, config/install, sqlfdbchk, probe:3331
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 : SQL10054
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:
Answer
There are two methods that can be used to solve this problem:
1. reset db cfg.
db2 reset db cfg
for database will update nchar_mapping value to zero.
2. Use an attachment program.
We prepared the program to change nchar_mapping value to zero.
IT04571 -v databasename
: display current nchar_mapping value
IT04571 -u databasename
: update current nchar_mapping value
For example:
Created database sample with non-unicode database.
Display current nchar_mapping value
$ /TMP/tsutoo/IT04571/IT04571_AIX64 -v sample
Get DB Config. fields for the "sample" database:
NCHAR_MAPPING = 16
Update current nchar_mapping value
$ IT04571 -u sample
Set DB Config. fields for the "sample" database:
NCHAR_MAPPING = 0
Verify current nchar_mapping value
$ IT04571 -v sample
Get DB Config. fields for the "sample" database:
NCHAR_MAPPING = 0
Download and compile IT04571.c.
For Windows 64bit, use IT04571.exe.
For other platforms, see the attachment.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21686677