im trying to migrate a db2 udb v7.1 to db2 v9.0 both on linux, using the db2move statement.
on server with db2 v9 to create database use command:

db2 create database prueba using code set ISO8859-1 territory US

this command use with the 2 version,

but have not to import, using the command

db2move prueba import or db2move prueba load

get message:

Application code page not determined, using ANSI codepage 1208

Error opening report file. Terminating ...
**Error occured while opening a file.

End time: Thu Apr 12 18:56:35 2007

Hi,
it looks like you are trying to export from UTF-8 code page database into US code page. I don't think this is supported. UTF-8 can have stored characters that are not supported by US code page.

Why do you need to "migrate" from UTF-8 to US code page? If you would like to use XML functionalities there are only available in UTF-8 code page system.

If you need migration from UTF-8 to US code page, there I can't imagine anything else except "export to file of del select * from table".

BTW, if you don't need to move from UTF-8 to US code page then just try to make a backup of old database on v7 system and restore into v9 system. It is possible I will be required to execute command "db2migrate"

Hope this helps,
Grofaty

Grofat, Thank you for answering.
The mistake that I have is from the exportation, I have db2 V7.1 on Linux ERH of 64 bits. My database has 331 tables.
The command: db2move control export
generates only 5 lines in the file db2move.lst, but exports 331 ixf and 331 msg files.
From the exportation I obtain messages of mistake and then I cannot import or load the information in the version 9.0

db2move control export

***** DB2MOVE *****
Action: EXPORT
Start time: Sun Apr 15 13:33:08 2007
Connecting to database CONTROL ... successful! Server: DB2 Common Server V7.1.0

*** Table "DB2ADMIN"."TARJETA": ERROR 3107. Check message file tab1.msg!
*** SQL Warning! SQLCODE is 3107
*** SQL3107W There is at least one warning message in the message file.


The file db2move.lst only has:
!"DB2ADMIN"."SPI_3"!tab89.ixf!tab89.msg!
!"DB2ADMIN"."TASA_COMISION_CREDITO"!tab93.ixf!tab9 3.msg!
!"DB2ADMIN"."INDICADOR_POR_PROYECTO"!tab142.ixf!ta b142.msg!
!"DB2ADMIN"."PLANTILLA_INDICADOR"!tab150.ixf!tab15 0.msg!
!"DB2ADMIN"."PLANTILLA_ORGANIZACION"!tab151.ixf!ta b151.msg!

This one is an example of a msg file:
SQL3104N The Export utility is beginning to export data to file "tab1.ixf".

SQL3132W The character data in column "EMPLEADO_ID" will be truncated to size
"10".

SQL3132W The character data in column "MOTIVO_NO_LABORA" will be truncated to size "40".

SQL3132W The character data in column "FERIADO_LABORADO" will be truncated to size "1".

SQL3132W The character data in column "COMENTARIO" will be truncated to size "250".

SQL3105N The Export utility has finished exporting "67262" rows.

Hi,
it looks like there is a problem with export of the table on db v7. This is not db v9 problem at all.

Have you tried to export manually (export to file.ixf of ixf select * from table)?

My suggestion is:
1. backup the database v7
2. restore the database to db v9
3. user "db2move db export" command from db v9
4. create db in v9 with desired code page
5. use "db2move db load/import" command to db v9

If this doesn't helps then is another option:
1. "export to file.del of del select * from table" on db v7
2. "import" del file into db v9

Hope this helps,
Grofaty