Hi together,

last weekend we migrated to a new baan server. The old one with BAAN IVc4, porting set 6.1c.06.02, Oracle 8.1.7.4.1 and Windows NT4.0 SP6, the new one with BAANIVc4, porting set 6.1c.07.02, Oracle 9.2.0.4.0 and Windows 2003 Server Standard Edition. BaaN and Oracle were installed and $BSE\application and $BSE\tools were copied from the old server. Data was moved with oracle export/import. Here are both script params:

*** export params ****
set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
set EXP_DIR=L:\ORADATA\BAAN\EXP
set EXP_PARAMS=BUFFER=32635 FULL=YES CONSISTENT=YES COMPRESS=YES


*** imp params ***
set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
imp system/manager
BUFFER=10000000
FULL=YES
commit=YES

###################################


PARAMETER VALUE *** OLD SERVER ***
-------------------- --------------------------------------------------
NLS_CHARACTERSET WE8ISO8859P1
NLS_LANGUAGE GERMAN
NLS_TERRITORY GERMANY


PARAMETER VALUE *** NEW SERVER ***
-------------------- -------------
NLS_CHARACTERSET WE8MSWIN1252
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA

####################################

Now we get problems with the layout of some reports specially after compile like
¿¿¿¿¿
instead of
---------------
When we export the report on the old machine and then import on the new one the layout is correct, also after compile. Now we aren't sure if there more problems, perhabs in more/all reports, sessions ?
Which possibilities do we have ? Imp/exp all reports ? Standard/Customized ?
Is it possible to change NLS_CHARACTERSET at the moment or only with a new oracle exp/imp ?
Is it enough to make an entry in db_resource like
nls_lang:american_america.we8iso8859p1

Thanks a lot !

you would need to set the db_resource parameter to be
american_america.WE8MSWIN1252

Not we8iso8859p1..

or, ideally, change your DB character set to be we8iso8859p1

Dave

Hi Dave,

you think setting db_resource param is enough ? Or must we do something more?
The other way - changing DB character set by exp/imp or by converting the db character set ? Do you have experience with this ?

Ingo

Hi Ingo,

It looks like imp translated your data to WE8MSWIN1252,
so if you tell baan that you are using that character set, you
should be fine.

if you have your old DB still out there, the best bet is to use
baan to bdbpre those 3 layout tables out.

Dave

Hi Dave,

that's it. It's the same solution/way BaaN Support tolds us on friday.
We made a baan dump of ttadv304, 335 and 364 on our old server with command set of nls_characterset to WE8ISO8859P1 in the bw-configuration. Next we made a create table from sequential dump with these dumps and nls_characterset to WE8MSWIN1252 on the new server. We also put this new character set to tabledef6.1
Now we can compile reports in a correct way.

Thanks a lot Dave.

Best regrads
Ingo

I think, you could not solve this Problem by setting the character set in baan, because the report layout tables (and also the form layout tables !) contains binary data in char fileds and the imp utility converts it to the new character set.
(i have had the same problem after setting up a database with east europe character set and importing an existing company) The only way to solve this problem is, as dave described by bdbpre/bdbpost the these tables from the old environment to the new database.

martin

@ingo
if you had some more questions, send me a pm, so we could discussed it in german.

I think it all depends on how that binary data is stored..

For example, if you're using Oracle export from a we8iso8859p1 DB and importing to WE8MSWIN1252. The binary data will
be converted to WE8MSWIN1252.

Now if you set nls_lang:american_america.we8iso8859p1 in your db_resource, baan will give you the weird corrupt results becuase the code page isn't translating correctly..

Now if you set nls_lang:american_america.we8mswin1252
baan should be able to translate the code page correctly and
read the data.. So first step should be to try setting the environment variables correctly.. second step is to go back to the old DB and export/import...

Dave