|
Problem IT04571
|
Status: Closed |
RESTORE ON FP4 MAY FAIL WITH SQL5133N ERROR IF THE DATABASE WAS CREATED AND BACKED UP BETWEEN 10.5GA AND FP3 |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Restore command on FP4 may fail with SQL5133N error if the
non-unicode database was created and backed up on release
between 10.5GA and FP3. This problem does not occur on UNICODE
database. The db2diag.log will show following error:
2014-09-12-17.56.51.733498+540 I11210E1118 LEVEL:
Warning
PID : 23240 TID : 140231734978896 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-21 APPID:
*LOCAL.db2inst1.140912085647
AUTHID : DB2INST1 HOSTNAME: sles11
EDUID : 334 EDUNAME: db2agent (SAMPLE) 0
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: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using non-unicode MBCS database *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Please see following TechNote on how to fix this issue
http://www.ibm.com/support/docview.wss?uid=swg21686677 |
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.09.2014
25.03.2015
25.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
