Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Change Database Locale

429 views
Skip to first unread message

Daniela Lemm

unread,
May 11, 1998, 3:00:00 AM5/11/98
to
Hey,

we are working with Informix 7.22. My Problem is that the Locale of the
Database is incorrect and I have to change it.
I' ve tried this with Backup and Restore but it didn't work, after
changing the Locale Keys in the Windowsregistry.

Can I set the Locale in an another way?

Thanks

Dani Lemm

vcard.vcf

Claus Samuelsen

unread,
May 13, 1998, 3:00:00 AM5/13/98
to Daniela Lemm
The official way is to dbexport the database,
then set DB_LOCALE and CLIENT_LOCALE,
then dbimport your database again.

Be carefull about dates and decimal point. Usually you can set DBDATE
and DBMONEY before you export to be sure that dates and decimal point
correspond to the locale you want to import under.

If you don't set CLIENT_LOCALE and DB_LOCALE your database will be
localized to en_us.8859-1.

You can look it up with SELECT * FROM systables WHERE tabid in (90, 91);

The unofficial way (be very carefull) is to directly update the
systables table, with something like
UPDATE systables
SET site = 'de_de.819'
WHERE tabid in (90, 91);
After this you must rebuild indexes on NCHAR and NVARCHAR columns.

regards

claus samuelsen

Daniela Lemm wrote:

> -------------------------------------------------------------------------------------------------------------
>
> Daniela Lemm <lemm...@sni.de>
> Siemens Nixdorf Business Services
>
> Daniela Lemm
> Siemens Nixdorf Business Services <lemm...@sni.de>
> Colonia Allee 3 Work: 0221/679-2134
> Köln Fax: 0221/679-1772
> 51067 Home: 02304/70601
> Germany Netscape Conference Address
> Netscape Conference DLS Server
> Additional Information:
> Last Name Lemm
> First Name Daniela
> Version 2.1


vcard.vcf

Nils Myklebust

unread,
May 14, 1998, 3:00:00 AM5/14/98
to

You have to use dbexport or onunload to export the data.
Then set your new locale and import the data again with dbimport or
onload respectively.


On Mon, 11 May 1998 18:48:39 +0200, Daniela Lemm <lemm...@sni.de>
wrote:

>Hey,
>
>we are working with Informix 7.22. My Problem is that the Locale of the
>Database is incorrect and I have to change it.
>I' ve tried this with Backup and Restore but it didn't work, after
>changing the Locale Keys in the Windowsregistry.
>
>Can I set the Locale in an another way?
>
>Thanks
>
>Dani Lemm

Nils Myklebust
NM Data AS
Norway
E-mail: Nils.My...@nmdata.com
FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html
(Now with ODBC info under "Third party products".)

F.PALMITJAVILA

unread,
May 21, 1998, 3:00:00 AM5/21/98
to

> I have the same problem.
>
> the only way is export the database without set dblocale and clientlocale.
> (if the actual locale is the default (en_us.819 or 8859-1 is the same).
> Then set the clientlocale='en_us.819 and dblocale='new locale'.(or the
> reverse? I don't remember..try it with an littlle table)
>
> Import the database.
>
> This is the best way, because informix translate the codes betwen actual to
> news, and is not nessesari to set dbmoney or others.
>
> After this , your database is in new locale, but you can configure clients
> with some others locales whit set BDLOCALE='locale of database' and
> CLIENTLOCALE= 'the locale that client wants to use'. Informix translate the
> codes.
>
> Don't forget that each time you create a database, he takes the locale you
> have set in your DBLOCALE or CLIENTLOCALE. if not set, he take the default
> en_us.819.
>
> Don`t try to modify dirctly the codes in the systables tabid 90-91, this may
> cause an coruption of database, and after this you can't drop it.I have testet
> this, and the only way to drop the corupted database is to edit directly the
> database to correct the codes.
>
> Remember the 7.X informix uses GLS. the olds variables (dbmoney, nls, dblang )
> function well but hare not nessesaris.You can work only with
> DBLOCALE,CLIENTLOCALE.


0 new messages