|
Home > Archive > SQL Anywhere database > May 2005 > Convert of collation from 1252Latin1 to utf8
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Convert of collation from 1252Latin1 to utf8
|
|
| Peter Stojkovic 2005-05-24, 7:23 am |
| ASA 9.02 last Build 3124
I have a database with 1252Latin1 Collation.
I have done an UNLOAD.
Than i have created a new database with collation UTF8
When i try to LOAD my data with reload.SQL the problems a char-columns
with german ö or ü or ä.
Then i get the errormessage primary key would not be unique.
But these columns are not part of the primary key.
I think it happens when it first-time sees the ö or ü or ä.
What is the correct way to do the work ??
| |
|
| Hi Peter,
I don't know a particular reason for the error you're seeing... but the
general procedure to do a char set conversion is:
use internal unload, external reload (main difference is input into
statements vs. load table statements-- load table does not do a charset
translation, input into does)
dbunload -ix...
when loading the new database start dbisqlc !!! (dbisql uses a different
parameter) and specify the char set the data you want to input is in.
dbisqlc -c "uid=...;pwd=...;cs=cp1252"
Make sure server charset translation is enabled (default) (dbsrv9 -ct+)
HTH
Guido
"Peter Stojkovic" <Peter.Stojkovic@gmx.net> wrote in message
news:42930d3e$1@foru
ms-1-dub...
> ASA 9.02 last Build 3124
>
> I have a database with 1252Latin1 Collation.
> I have done an UNLOAD.
> Than i have created a new database with collation UTF8
>
>
> When i try to LOAD my data with reload.SQL the problems a char-columns
> with german ö or ü or ä.
>
> Then i get the errormessage primary key would not be unique.
> But these columns are not part of the primary key.
> I think it happens when it first-time sees the ö or ü or ä.
>
> What is the correct way to do the work ??
>
>
>
>
>
>
|
|
|
|
|