In this case, I think it is because the original database is defined as
UTF-8. Even though db2move can move data between different platform, but
it can't move data between database with different character set (I didn't
do any test to approve this, it is just my thought).

Regards,




"pavan" <db2udbdba-ezmlmshield-x48989570.[Email address protected]
07/27/2006 05:27 PM


To: "LazyDBA Discussion" <[Email address protected]
cc:
Subject: Re: db2move - import - FORCEIN error -- URGENT !!


Thank you. It works!!
But, can you explain in simple words why does UTF-8 solve the problem ?
I did my research but could not get the big picture of the problem.
Thanks a bunch !

> Hi,
>
> You need to create your database using UTF-8 character set.
>
> Regards,
>
>
>
>
> "pavan" <db2udbdba-ezmlmshield-x85942687.[Email address protected]
> 07/27/2006 04:31 PM
>
>
> To: "LazyDBA Discussion" <[Email address protected]
> cc:
> Subject: db2move - import - FORCEIN error -- URGENT !!
>
>
> All,
> I am in the process of replicating a database onto a windows server.
> I do not have db2look.sql of the original database. I have been supplied
> with only db2move output.
> when i use
>>>db2move gort import -io replace_create
> I get the following error. Can somebody guide me how to use FORCEIN
> What is the mistake that I am doing here.
> FORCEIN is a filetype modifier in "db2 import". How can I use this along
> with db2move ????
>
> ***** DB2MOVE *****
> Action: IMPORT
> Start time: Thu Jul 27 14:52:22 2006
> Connecting to database GORT ... successful! Server: DB2 Common Server
> V8.2.1
> * IMPORT: table "GORT "."GENDER_LOOKUP"
> ***ERROR -3309. Check message file tab1.msg!
> *** SQLCODE: -3309 - SQLSTATE:
> *** SQL3309N Column " dÚ " in the PC/IXF file is defined as a
> graphic column. The FORCEIN parameter was not specified.
>
>>>D:\DB2\NODE0000\gort>more tab1.msg
>
> SQL3150N The H record in the PC/IXF file has product "DB2 02.00", date
> "20040119", and time "155902".
>
> SQL3153N The T record in the PC/IXF file has name "tab1.ixf", qualifier
> "",
> and source " ".
>
> SQL3309N Column " dÚ " in the PC/IXF file is defined as a graphic
> column.
> The FORCEIN parameter was not specified.
>
> SQL3110N The utility has completed processing. "0" rows were read from
the
> input file.
>
> SQL3150N The H record in the PC/IXF file has product "DB2 02.00", date
> "20040119", and time "155902".
>
> SQL3153N The T record in the PC/IXF file has name "tab1.ixf", qualifier
> "",
> and source " ".
>
> SQL3309N Column " dÚ " in the PC/IXF file is defined as a graphic
> column.
> The FORCEIN parameter was not specified.
>
> SQL3110N The utility has completed processing. "0" rows were read from
the
> input file.
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
> --
>
>



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




DB2 & UDB email list listserv db2-l LazyDBA home page