Re: Problem with dbexport

Never had this problem in the 12 years using Informix products. I've moved applications from HP-UX to Solaris to SCO OpenServer using 'd bexport'. After recompiling forms and reports, everything ran fine. Check what options you used the first and second time you did the export. You may also want to ask Informix yourself (have a contract?) if the version you were using had any kind of problems. Usually, they're isolated to a platform. MoJo Risin -- In article <7uf9u0$ib6$1@nnrp1.deja.com>, Ravi Krishna <srkrishna@yahoo.com> wrote: > Hi, > > For some reasons we had to take the dbexport of the database, to be > dbimported later. The dbexport went off smoothly, or so we thought. > When he had to dbimport back it ran into problems, as mentioned below:- > > 1.{ unload file name = area_00100.unl number of rows = 120 } > > The "number of rows" mentioned above is critical for dbimport, bcos it > matches it with the .unl file. In our case we found that while the .unl > file has correct # of rows, the number of rows mentoned above was > incorrect. It was much less than the actual # of rows. Consequently > dbimport died with error message "dbimport data corrputed". > > 2. One table had a field missing in the table definition but that field > was present in the .unl file. As a result dbimport died with an error > message "no of fields do not match no of columns". > > 3. Some of the stored procedures weren't up to date. It was reflecting > the older version. > > We were forced to reload data from the tape and take dbexport again. But > this time it was successful. > > Version: Informix IDS 7.30UC8 > Hardware: IBM RS6000 running AIX 4.3.2 > > Has anyone experienced this problem before. Is dbexport unreliable. > > Ravi. > > Sent via Deja.com http://www.deja.com/ > Before you buy. > Sent via Deja.com http://www.deja.com/ Before you buy.