Oppolzer - Informatik / Blog

Once again I would like to mention my transfer (or migration) tool,
which allows you to specify individual translation tables
for every transfer (or one common translation table for
all transfers) to handle such issues.

Please ask for details offline, if you are interested.

Kind regards

Bernd



Am 06.10.2014 15:48, schrieb D.S.:
Hello:

Thanks for the responses.

Just to give further clarification, I'm all set with loading. I'm currently
working on validation by comparing data from both the databases.

I agree that the process should work fine but the business partners would still
like to see the data being validated due to the sensitive nature of it.

Now that I found A way of comparing & validating the data, I found a few issues.
Here's another question to the experts.

Unreadable characters are not converted in their original form from EBCIDIC to
ASCII, for example In Mainframe DB2...
^

Gets converted to Oracle like below...
¬

Besides, square brackets (which seem to be a popular issue during conversion)
don't get converted correctly. Below is the example.

From (Mainframe/DB2)
[RACK MOUNT]

To (Oracle)
ÝRACK MOUNT¨

People who worked on such tasks, do you have any idea if there's a way (without
making it a big project) to fix this? Or is this something everybody should live
with (as some people seem to be doing)? This is happening in description fields
(CHAR)

Thanks,
-D.