Oninit cdi / Archive
Talk to an expert →

dbexport/dbimport corrupting BLOBs?

Posted in 1998

Topics: Storage & Space Management, Connectivity: ESQL/C, 4GL & Embedded SQL, Data Types & Schema Design, Migration, Import/Export & Data Conversion, Platform-Specific Issues, Versions, Editions & End-of-Life

Evans_Russell@doh.state.fl.us — — source: Informix-list mailing list archive (1991-1998)

A vendor that is building a 4gl application for us is having trouble with BLOBs being corrupted. It seems to happen when data is exported then imported on our system (IDS 7.24 UC4, Solaris 2.6). The data is being stored as byte data type, and is not being flagged as corrupted after the import. (Informix will retrieve the data without complaint, but the data is not what it was before exporting). Informix tech support is researching the problem, but I wondered if anyone here has run across this problem. I have some tables with large numbers of extents that I need to export/drop/create/import to clean up, but am wary of doing this until I find the cause. How does dbexport/dbimport handle the binary data in BLOBS when it converts it to ASCII? Does it use the standard UNIX UUEncode/UUDecode algorithm? I'd like to be able to verify the accuracy of the data after export to see if it is happening on export or import. Russ Evans Division of Information Resource Management The Alexander Building 2020 Capital Circle SE, Room 2407 Tallahassee, FL 32399-1733 (850)413-8490 S/C 293-8490

Glossary