LOB Conversion from Windows to AIX Problem - HELP!

[cpressley2]

Hi all,

I am doing a db converison from windows v7 to aix v8. The db contains
many LOBs. I did an export specifying the LOB option, compressed the
data (using tar and gzip for windows) , ftp the data, and decompressed
the data. I then ran the import using the same LOB option and the
output from the import command says that the data was loaded with no
issues.

However when the application tries to view the data, it complains about
the tables that have the LOBs stating that the database is corrupt.

The database is not corrupt but I think the LOB data got 'lost in
translation' . I know that this is not a new thing. Am I missing
something? Do I need a fixpak ??

Thanks,

Celestine

[Mark A]

<cp********@yahoo.com> wrote in message
news:11*********************@g43g2000cwa.googlegro ups.com...

Hi all,

I am doing a db converison from windows v7 to aix v8. The db contains
many LOBs. I did an export specifying the LOB option, compressed the
data (using tar and gzip for windows) , ftp the data, and decompressed
the data. I then ran the import using the same LOB option and the
output from the import command says that the data was loaded with no
issues.

However when the application tries to view the data, it complains about
the tables that have the LOBs stating that the database is corrupt.

The database is not corrupt but I think the LOB data got 'lost in
translation' . I know that this is not a new thing. Am I missing
something? Do I need a fixpak ??

Thanks,

Celestine

What fixpack are you on? I would recommend FP11, or at the very least FP10.

Try using db2move utility to export and load replace the data. If you don't
want to load all the tables, you can edit the db2move.lst file before you do
the load replace.

[Serge Rielau]

cp********@yahoo.com wrote:

Hi all,

I am doing a db converison from windows v7 to aix v8. The db contains
many LOBs. I did an export specifying the LOB option, compressed the
data (using tar and gzip for windows) , ftp the data, and decompressed
the data. I then ran the import using the same LOB option and the
output from the import command says that the data was loaded with no
issues.

However when the application tries to view the data, it complains about
the tables that have the LOBs stating that the database is corrupt.

The database is not corrupt but I think the LOB data got 'lost in
translation' . I know that this is not a new thing. Am I missing
something? Do I need a fixpak ??

Is this message raised by application code or DB2?
Could it be that you have numeric data (like INTEGER) embedded in the
LOB. Intel processors use a different endian-nes than power processors.
So any numbers embedded inside the LOB would be byte reversed.
Your application code that composes/reads the LOB will have to be
conscious about that. There is nothing DB2 can do since LOB's are
black-box.

Also if you have text data you might get in trouble with codepage
conversions if you use BLOB (binary) since it BLOBs don't have it.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

[cpressley2]

Thanks Serge. This error message was raised by the application. Since
posting this SOS, I have learned that the data was copied over
correctly. We are able to compare the data to the Windows version and
it matches. Of course it is hard to read the Clobs/lobs without the app
but everything else looks good.

I'll express your points to the application group.

Thanks.
Celestine