Locale Check before DB Export - Import
A user asked whether dbexporting a German-locale database from IDS 9.40 on Linux and dbimporting it into an en_us.819 IDS 11.10 instance on Solaris would cause problems. Art Kagel warned about date formats, decimal commas vs periods, and accented/special characters (umlauts, es-zett) that don't exist in the target locale, and confirmed dbexport/dbimport handle one database at a time. Others advised setting DBDATE/DBMONEY consistently and considering 8859-15 or UTF-8; one poster reported that mismatched DB_LOCALE and CLIENT_LOCALE corrupted CP1252 characters, so keeping them identical fixed it. No confirmation of the original poster's outcome is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Dear all,
We are planning to take a dbexport from IDS 9.40.UC8W7 on RHLE with db locale
set to de and importing it on IDS 11.10.FC2W1 on solaris with db locale
en_us.819.
Can this factor can cause a issue .
Do we have to take the dbexport seperately for every database created in our
server and import them seperately.
Please let me know what all such db related Prerequisites that we have to take
care of before going for dbexport - import
Thanking you in advance.
Regards,
vikas
VIKAS HIVARKAR wrote:
> Dear all,
>
> We are planning to take a dbexport from IDS 9.40.UC8W7 on RHLE with db locale
> set to de and importing it on IDS 11.10.FC2W1 on solaris with db locale
> en_us.819.
> Can this factor can cause a issue .
>
It may cause you problems and it may not. You have to be careful of
things like date formats. Dbexport will be exporting dates in the
current locale which may not load correctly, if at all, in the target
locale. Similarly for floating point numbers where commas in the de
locale need to be periods in the us locale. Then there are accented
(umlauts for example) letters and non-standard (es-zett for example)
characters which may not exist in the target locale (the en_us locale
has no native accented letters).
> Do we have to take the dbexport seperately for every database created in our
> server and import them seperately.
>
If you are using dbexport/dbimport, yes, these are single database
migration tools.
> Please let me know what all such db related Prerequisites that we have to
take
> care of before going for dbexport - import
>
> Thanking you in advance.
>
> Regards,
> vikas
>
Art S. Kagel
Oninit
================================================================================
===========
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.oninit.com/home/disclaimer.php
================================================================================
===========
If you are bored can you look at setting up OAT at Cargotel, the software is
informix home utils directory and need to be installed on db1p
Cheers
Paul
Paul Watson
Tel: +1 913-400-2620
Mob: +1 913-387-7529
Web: www.oninit.com
Failure is not as frightening as regret.
If you want to improve, be content to be thought foolish and stupid.
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Art S. Kagel (Oninit)
> Sent: 19 March 2008 12:55
> To: ids@iiug.org
> Subject: Re: Locale Check before DB Export - Import [11675]
>
> VIKAS HIVARKAR wrote:
> > Dear all,
> >
> > We are planning to take a dbexport from IDS 9.40.UC8W7 on RHLE with
> db
> locale
> > set to de and importing it on IDS 11.10.FC2W1 on solaris with db
> locale
> > en_us.819.
> > Can this factor can cause a issue .
> >
>
> It may cause you problems and it may not. You have to be careful of
> things like date formats. Dbexport will be exporting dates in the
> current locale which may not load correctly, if at all, in the target
> locale. Similarly for floating point numbers where commas in the de
> locale need to be periods in the us locale. Then there are accented
> (umlauts for example) letters and non-standard (es-zett for example)
> characters which may not exist in the target locale (the en_us locale
> has no native accented letters).
>
> > Do we have to take the dbexport seperately for every database created
> in our
> > server and import them seperately.
> >
>
> If you are using dbexport/dbimport, yes, these are single database
> migration tools.
>
> > Please let me know what all such db related Prerequisites that we
> have to
> take
> > care of before going for dbexport - import
> >
> > Thanking you in advance.
> >
> > Regards,
> > vikas
> >
>
> Art S. Kagel
> Oninit
>
>
> =======================================================================
> ====================
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
>
> http://www.oninit.com/home/disclaimer.php
>
>
> =======================================================================
> ====================
>
>
> ***********************************************************************
> ********
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> See you at the IIUG Informix 2008 Conference
> The Power Conference for Informix Professionals
> April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas
> http://www.iiug.org/conf
> Registration Now Open!!
>
> =======================================================================
> ====================
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
>
> http://www.oninit.com/home/disclaimer.php
>
> =======================================================================
> ====================
================================================================================
===========
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.oninit.com/home/disclaimer.php
================================================================================
===========
Paul Watson wrote: > If you are bored can you look at setting up OAT at Cargotel, the software is > informix home utils directory and need to be installed on db1p > > Cheers > Paul Oops, I think that was meant for me, not this list. Please ignore. Art S. Kagel Oninit ================================================================================ =========== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ================================================================================ ===========
Why are you taking a German locale database to en_us.819.
I guess it is not a real issue as neither of these locales have support
for the euro char, but just curious.
Just wondering if you considered 8859-15 or utf8?
on export and import set DBDATE and DBMONEY constantly.
not sure where you got the de locale for Linux, as I didn't think that
Informix provided this.
"VIKAS HIVARKAR" <vikashivarkar3@gmail.com>
Sent by: ids-bounces@iiug.org
03/19/2008 12:28 PM
Please respond to
ids@iiug.org
To
ids@iiug.org
cc
Subject
Locale Check before DB Export - Import [11674]
Dear all,
We are planning to take a dbexport from IDS 9.40.UC8W7 on RHLE with db
locale
set to de and importing it on IDS 11.10.FC2W1 on solaris with db locale
en_us.819.
Can this factor can cause a issue .
Do we have to take the dbexport seperately for every database created in
our
server and import them seperately.
Please let me know what all such db related Prerequisites that we have to
take
care of before going for dbexport - import
Thanking you in advance.
Regards,
vikas
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
See you at the IIUG Informix 2008 Conference
The Power Conference for Informix Professionals
April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas
http://www.iiug.org/conf
Registration Now Open!!
OK so I'm an idiot - all together now - Harsh but Fair :-) Sorry peeps Paul Watson Tel: +1 913-400-2620 Mob: +1 913-387-7529 Web: www.oninit.com Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Art S. Kagel (Oninit) > Sent: 19 March 2008 13:18 > To: ids@iiug.org > Subject: Re: Locale Check before DB Export - Import [11677] > > Paul Watson wrote: > > If you are bored can you look at setting up OAT at Cargotel, the > software is > > informix home utils directory and need to be installed on db1p > > > > Cheers > > Paul > Oops, I think that was meant for me, not this list. Please ignore. > > Art S. Kagel > Oninit > > > ======================================================================= > ==================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > > http://www.oninit.com/home/disclaimer.php > > > ======================================================================= > ==================== > > > *********************************************************************** > ******** > Forum Note: Use "Reply" to post a response in the discussion forum. > > See you at the IIUG Informix 2008 Conference > The Power Conference for Informix Professionals > April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas > http://www.iiug.org/conf > Registration Now Open!! > > ======================================================================= > ==================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > > http://www.oninit.com/home/disclaimer.php > > ======================================================================= > ====================
That's nothing. Yesterday, I accidentally hit "reply all" when I sending out my picks for the College Basketball Ladder Championship. All I can hope now is that it encouraged more people to enter, bringing in more funds for me to win (or now share) at the end of it all. Take care. Clifton M. Bean Informix DBA / AIX System Admin Currency Technics & Metrics Phone: (972) 812-1411 x244 -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Paul Watson Sent: Wednesday, March 19, 2008 7:58 PM To: ids@iiug.org Subject: RE: Locale Check before DB Export - Import [11681] OK so I'm an idiot - all together now - Harsh but Fair :-) Sorry peeps Paul Watson Tel: +1 913-400-2620 Mob: +1 913-387-7529 Web: www.oninit.com Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Art S. Kagel (Oninit) > Sent: 19 March 2008 13:18 > To: ids@iiug.org > Subject: Re: Locale Check before DB Export - Import [11677] > > Paul Watson wrote: > > If you are bored can you look at setting up OAT at Cargotel, the > software is > > informix home utils directory and need to be installed on db1p > > > > Cheers > > Paul > Oops, I think that was meant for me, not this list. Please ignore. > > Art S. Kagel > Oninit > > > ======================================================================= > ==================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > > http://www.oninit.com/home/disclaimer.php > > > ======================================================================= > ==================== > > > *********************************************************************** > ******** > Forum Note: Use "Reply" to post a response in the discussion forum. > > See you at the IIUG Informix 2008 Conference > The Power Conference for Informix Professionals > April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas > http://www.iiug.org/conf > Registration Now Open!! > > ======================================================================= > ==================== > Please access the attached hyperlink for an important electronic > communications disclaimer: > > http://www.oninit.com/home/disclaimer.php > > ======================================================================= > ==================== **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!
I just finished an export/import exercise using HPL (going from 7.31 to
10.00), but these comments should apply to dbexport/dbimport as well:
* we ended up using en_US.CP1252 to cover western european characters
including the euro sign.
* actually, even though the source db was en_US.819 it did contain CP1252 only
characters (like the euro). This caused a problem during export when I noticed
that these characters were changed to ASCII 127 (DEL) by dbexport/onpload.
Found that this was caused by CLIENT_LOCALE being set to en_US.CP1252...by
making sure both DB_LOCALE and CLIENT_LOCALE were the same all characters came
out as they were stored.
Using HPL involved some extra work, but moving a 120+ GB database was
completed in < 8 hours including building indexes. This was originally planned
as a 24 hour exercise, so the gain was definitely worth the effort.
/Johan