myexport problem

IDS 12.10.FC12 Solaris 10 1/13 I am attempting to try myexport/myimport in hopes of getting faster export/import times, compared to dbexport/dbimport. I ran 'myexport -ss <database> -E >out 2>err'. But, it does not run to completion. Stops (although seems to be waiting for input) with the following in the err file: informix@ifmx-prod-jnu>tail err.myexport "informix".em_service_plan_cd "informix".pretrial_query_tables "informix".pretrial_case_reporting_extract "informix".bopp_calendar "informix".bopp_cal_appt "informix".bopp_hrng_waitlist "informix".bopp_cal_holidays "informix".omp_lsi_staging Waiting for data exports to complete...ksh[2698]: 6673 Segmentation Fault(coredump) ksh[2718]: 6683 Bus Error(coredump) informix@ifmx-prod-jnu> The dbexport command 'dbexport -ss <database> >out 2>err' completes successfully. (Running myexport without the -E option behaves the same way.) Might anyone have any suggestions? Thank you. DG

Oops, I was ambiguous. WHen I said myexport without -E ran the same way, I meant it also failed-- NOT that it ran the same way as dbexport (which succeeds). DG

I found a work-around (if not a solution). It was just one table that tripped it up every time. After consulting with the developer who created that table, I learned that it really was of transitory use only. It is created any time it is needed. So, I simply DROP it before exporting that database. Then myexport works like a charm. Interesting that I also had problems with dbexport/dbimport with respect to that table. However, in this case, dbexport works just fine... it is dbimport that crashes. Solution is basically the same. Edit the <database>.sql file produced by dbexport to remove the code that imports the screwy table. Weird, but unless something else crops up, I don't have time to figure it out. The table DDL appears quite ordinary. Plain vanilla table, with plain vanilla data types. Sigh, DG