ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
UNICODE-tables not handled correctly
Article ID: 104062
Updated On:
Products
RC Compare for DB2 for z/OS
Database Analyzer for DB2 for z/OS
Fast Unload for DB2 for z/OS
Fast Check for DB2 for z/OS
Fast Index for DB2 for z/OS
Fast Load for DB2 for z/OS
Rapid Reorg for DB2 for z/OS
Issue/Introduction
We want to migrate a table with CCSID UNICODE to another system into a table, which has also CCSID UNICODE.
We want to migrate a table with CCSID UNICODE to another system into a table, which has also CCSID UNICODE. The data is unloaded in EDCDIC, which is in my opinion wrong, because the table can contain data, which can't be represented in EBCDIC and the subsequent load fails with conversion error, because
1. UNICODE is specifiede, although input-dataset is EBCDIC
2.Field-specifications are wrong (if input-dataset is EBCDIC I will send generated strategy.
How do we resolve this
We want to migrate a table with CCSID UNICODE to another system into a table, which has also CCSID UNICODE. The data is unloaded in EDCDIC, which is in my opinion wrong, because the table can contain data, which can't be represented in EBCDIC and the subsequent load fails with conversion error, because
1. UNICODE is specifiede, although input-dataset is EBCDIC
2.Field-specifications are wrong (if input-dataset is EBCDIC I will send generated strategy.
How do we resolve this
Environment
z/os db2
Resolution
This is specifiable through the utility model that you are using. You should add the symbol UNICODE to your UNLOAD utility with a value of UNICODE. Additionally, it seems you wish to LOAD to a UNICODE table also, so you may also want to specify the same symbol/value combination in the LOAD utility.
Feedback
Yes
No
Powered by
