Skip to main content


The MVIMPORT is the preferred mechanism for moving data from other MultiValue implementations to Caché. At present, MVIMPORT accepts supports backups created by UniVerse, jBASE, D3, Reality and MVBase. The features of MVIMPORT vary according to the type of backup being restoreD. The detailed description of MVIMPORT is located in the MultiValue Commands Reference.

MVIMPORT is designed as a migration aid. Thus,

  • It will only recognize programs and data when performing its task. Any indices present in the import file will be ignored; native Caché facilities for indexing will be used instead.

  • It will not create any of the underlying Caché classes needed by running programs. These will be created as needed when the programs are prepared for execution.

  • It is not designed for general-purpose backup; only for restore (migration to Caché). Once the information has been migrated, administrators should use the Caché operator commands to save and restore data.

At the end of MVIMPORT (for all backups except UniVerse),

  1. Caché displays a summary of the number of errors and warnings. The detail of these errors and warnings and general restore statistics are saved to an external file and this filename is displayed to the user.

  2. When MVIMPORT fails to create a namespace and/or a database, it now displays an informative error message.

  3. All items found in the backup are now restored to the VOC unless they already exist in the VOC.

  4. The file IMPORTED.VOC contains all the original VOC, regardless of whether or not the items were restored to the VOC. This allows a customer to see what the VOC looked like on their original system before MVIMPORT made decisions on whether or not to apply the items to the VOC.

  5. MVIMPORT looks for object code in D3 backups. While this is discarded on Caché because it cannot be used, its presence indicates which files contain compiled code. This fact is used to mark the file as BASIC source for use with Studio.

FeedbackOpens in a new tab