Move database from IDS 7.30 to IDS 9.40

Hello list. For the the moment I prepare to move a database from an old IDS 7.30 to 9.40 I'm using dbexport here, because we want change the codepage from codpage 437 to De_de.8859-1 The dbexport works with some problems. After transfering the files to new server (ftp, binary mode) I changed all brackets to Umlaute. The settings in .profile are the same. On dbimport the import stops with this message: Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Load file has different number of columns than table Import data is corrupted! revoke all on "informix".ehrung_key from "public"; create unique index "informix".ix317_1 on "informix".ehrung_key (ehrung_nr); { TABLE "informix".ehrung2 row size = 339 number of columns = 13 index size = 40 } { unload file name = ehrun00323.unl number of rows = 7125 } create table "informix".ehrung2 ( adr_nr integer, ehrung_key integer, vereins_nr char(7), beantragt_von char(50), beantragt_am date, status integer, begruendung_status char(100), verleihung_soll date, verleihung_ist date, verleihung_von char(50), entzogen integer, entzogen_am date, grund_entzogen char(100) ); Load file has different number of columns than table *** put loadcur 1213 - Character to numeric conversion error informix@mega:~> I checked all data in the numeric fields. There are characters in the original table. Any ideas? Thanks in advance for your help. Best regards from Hannover, Germany. Dirk Emmermacher

Am Di, 13.03.2007, 09:00, schrieb emmermacher@hotmail.com: > Hello list. > > For the the moment I prepare to move a database from an old IDS 7.30 > to 9.40 > I'm using dbexport here, because we want change the codepage from > codpage 437 to De_de.8859-1 > The dbexport works with some problems. > After transfering the files to new server (ftp, binary mode) I changed > all brackets to Umlaute. > The settings in .profile are the same. > > On dbimport the import stops with this message: > Load file has different number of columns than table > > Load file has different number of columns than table >..... many more errors... > Load file has different number of columns than table > > Import data is corrupted! > > revoke all on "informix".ehrung_key from "public";> > create unique index "informix".ix317_1 on "informix".ehrung_key > (ehrung_nr); > { TABLE "informix".ehrung2 row size = 339 number of columns = 13 index > size = 40 > } > { unload file name = ehrun00323.unl number of rows = 7125 } > > create table "informix".ehrung2 > ( > adr_nr integer, > ehrung_key integer, > vereins_nr char(7), > beantragt_von char(50), > beantragt_am date, > status integer, > begruendung_status char(100), > verleihung_soll date, > verleihung_ist date, > verleihung_von char(50), > entzogen integer, > entzogen_am date, > grund_entzogen char(100) > ); > Load file has different number of columns than table > > *** put loadcur > 1213 - Character to numeric conversion error > > informix@mega:~> > > I checked all data in the numeric fields. There are characters in the > original table. > Any ideas? > > Thanks in advance for your help. > > Best regards from Hannover, Germany. > > Dirk Emmermacher > First: Can you run the import without changing Umlaut and Codepage? Second: DBDATE is set? (DBCENTURY too?) Third: Compare two lines (from original and changed file) of data, where is the first mismatch with a field value? Mit freundlichen Grüßen Joerg Volz http://www.it-volz.de

emmermacher@hotmail.com wrote: > Hello list. > > For the the moment I prepare to move a database from an old IDS 7.30 > to 9.40 > I'm using dbexport here, because we want change the codepage from > codpage 437 to De_de.8859-1 > The dbexport works with some problems. What problems do you see from dbexport ? > After transfering the files to new server (ftp, binary mode) Since exported files (*.unl and *.sql) are all ascii, you should use ftp character mode. Do you ftp between unix/linux and windows? > I changed all brackets to Umlaute. What is your delimiter set to? If I guesses right, then in codepage 437 '''''''' replaces standard '{|}[\\]', so might have replaced the field delimiter (default |). > The settings in .profile are the same. Don't compare the content of .profile, compare the output of 'env' [snip] > > Dirk Emmermacher >

Hello Jörg. Thanks for your reply. > > First: Can you run the import without changing Umlaut and Codepage? With this test I don't tested it, but generally its possible. > Second: DBDATE is set? (DBCENTURY too?) DBDATE is set to DMY4. on both machines. DBCENTURY isn't set. Best regards. Dirk > Third: Compare two lines (from original and changed file) of data, where > is the first mismatch with a field value? > > Mit freundlichen Grüßen > > Joerg Volz > > http://www.it-volz.de

Hello Claus. Thanks for your answer. > What problems do you see from dbexport ? The dbexport has problems with the permissions. Its runs after some time out of memory. I had a look for old users and revoke them from system. Tomorrow I will try a new run with dbexport. > > > After transfering the files to new server (ftp, binary mode) > > Since exported files (*.unl and *.sql) are all ascii, you should use ftp character mode. Do you ftp between unix/linux > and windows? > > > I changed all brackets to Umlaute. > > What is your delimiter set to? If I guesses right, then in codepage 437 'äöüÄÖÜ' replaces standard '{|}[\\]', so might > have replaced the field delimiter (default |). DBDELIMITER is set to "#" . > > > The settings in .profile are the same. > > Don't compare the content of .profile, compare the output of 'env' > There are differences in TERM. The old machine ist set to VT100 (HP-UX 10.20), the new to xterm (Suse Linux 8.2) because I use different terminal emulations. > [snip] Best regards. Dirk > > > > > Dirk Emmermacher