Oninit cdi / Archive
Talk to an expert →

Re: Optimizing a BaaN installation

Posted in 2005

Topics: Installation, Setup & Upgrades, Migration, Import/Export & Data Conversion

david@smooth1.co.uk — — source: Usenet: comp.databases.informix

What does unloading and loading tables cause problems? Surely you put back the same data that you have before? If not what unsupported crap are Baan doing? I should add this to the FAQ!

↪ replying to david@smooth1.co.uk
Claus Samuelsen — — source: Usenet: comp.databases.informix

david@smooth1.co.uk wrote: > What does unloading and loading tables cause problems? > > Surely you put back the same data that you have before? > > If not what unsupported crap are Baan doing? > > I should add this to the FAQ! > When using level 1 driver BAAN calculates hash keys. These key values are stored as binary data in char columns, so unloading/loading these values are not safe. dbexport/dbimport has a -X option which treats binary data in char columns as hex representation. Using 'unload to'/'load from' will most likely change the hash key values. BAAN has tools for unloading/loading tables. It's slower than the informix unload/load, but BAAN recalculates the hash key values!

↪ replying to david@smooth1.co.uk
Jaime Casanova — — source: Usenet: comp.databases.informix

the problem that for "compatibility with other databases" (mostly their own flat-file based) BaaN doesn't use the informix's index system instead it appends columns at the end of the table with a hash of the index column... there values in those hashes that are not valid so dbimport/dbexport simply falls down for them... :(