Unload in ASCII or Binary Format
When unloading a database, you should unload the files in ASCII format unless you are copying the database to another instance on the same machine or to a binary-compatible machine. In these cases, use binary format.
If you are not sure, use ASCII format.
Unloading in ASCII format allows you to:
• Move databases to an instance with a different machine architecture
• Edit the data files before reloading them into a database
To unload the database files in ASCII format, specify the -c option (create printable data files) on the copydb command. (In VDBA, use the Create Printable Data Files option in the Generate copy.in and copy.out dialog.)
To unload the database files in binary format, do not specify the -c option.
Note: Copying between releases of Ingres with different major release identifiers can cause problems if new columns were added to a later release to support new features. If you have made use of these new features in the later release and attempt to unload and reload into an earlier release that did not support the new feature, the reload produces an error. To avoid this error, simply edit the reload scripts to avoid loading the non-existent columns.
Caution! If you unload the files in binary format, do not edit them. Editing prevents you from reloading them.