Dbexport / Dbimport Bugs?

Hi, We seem to be having a problem running a dbexport/dbimport on our SE databases. The error -100 appears when we run our dbexport or dbimport which is basically a duplicate value error. We checked the problem and we found that we do not have any duplication. I noted that informix has quite a few open cases in this regards! We get these errors on various platforms. Sometime they work, other times they don't. This also occurs for any database that we try to dump or import. Does informix have problems with these utilties that they are fixing. When we drop the problem tables and indexes we can dump and import everything fine. The only problem is that there is not duplication within the database or in the system files and indexes that we can find. We used update statistics and we did an secheck and none of them return any error messages. Any ideas? Does anyone have another work around that they have found handy to use for this error? Thanks in advance, Lloyd.

This also happens on 7.30.TC6 and 7.31.TC2 on NT. It works always if you use IECC, but with the DBEXPORT utility you get often primary key violations when you use DBIMPORT, because in some VARCHAR or CHAR columns values the last charcter is cut (!!!). This is strange because IECC also uses DBEXPORT. The bug is not in the engine or DBIMPORT, but in DBEXPORT. You can see the duplicate values if you import the unload file to Excel or or Access and sort them. Axel Weitermann

We also had a problem exporting / importing data. The export would say there were X number of rows unloaded but this did not match the number in the table export file. To solve this our sysadmin ran a perl script which would find these errors before the import so that he had a chance to fix them. Also , it seems to help if an update statistics; is run before the export.