Well it starts off as a simple export/import of an UTF-8 database from AIX to Windows. I have an UTF-8 database on an AIX box and I created a UTF-8 database on the windows to replicate the setup on AIX with
db2 create db MYUTFDB codeset UTF-8 territory US
and did the following to export the schema and the data from the AIX box
db2look -d MYUTFDB -ea -o mydbddl.sql
db2move AMUTF export
and on the windows box did this to import it on my newly created UTF-8 DB.
db2 -tvf mydbddl.sql
db2move MYUTFDB IMPORT
Now comes the time for a 2 day long struggle to find out why the utf-8 data inside the tables are all messed up, and all I could see are characters looking like "–>–>". When i opened up the ixf file for the imported tables using Notepad++ Instead of seeing actual characters (ex: in Japanese) i could only find "SUB" (Hex: 1A1A). To keep the long story short this is what i used to solve the problem
db2set DB2CODEPAGE=1208
db2 terminate
db2 force applications all
db2stop
db2start
I did this both on the AIX and Windows box.
The reason being, for some reason the db2move export on the AIX box, always exported the IXF files in the codepage 819 instead of 1208, eventhough my database was set to codepage 1208. Hence problem solved!
World Peace!