Migrating a Hypertrieve vault to Oracle

To migrate an existing Hypertrieve vault to Oracle:

  1. Create a new vault as described in Creating a new vault using the options described in the following table.
  2. Confirm that the migration was successful by checking the new vault for:
    • Total number of documents equal to the source vault
    • Existence of prior revisions
    • Correct status of work in progress documents
    • Documents are visible in the Meridian viewer
    • Custom configuration items
  3. To prevent users from accessing the old Hypertrieve vault instead of the new Oracle vault, delete the Hypertrieve vault in Meridian Administrator.
Vault migration options
Option Value

Database engine

Oracle

Import contents from another vault

Enable

Source Vault

Select the Hypertrieve vault

Copy stream files

Enable

Oracle instance name

Type an Oracle instance name

After the migration is done, the new vault is ready for use.

The migration can take a significant amount of time, depending on the size of the Hypertrieve database and the number and size of the stream files. The size of the resulting Oracle database will be about 2.5 times the size of the source Hypertrieve database and can be seen in Windows Explorer in the location specified for the Path for database files property of the vault.

Related concepts

Integrating Meridian with Oracle

Understanding how Meridian works with Oracle

Understanding ORAIO

Understanding vault cache memory

Understanding Oracle vault backups

Understanding the EDM Server service account requirements for Oracle

Related tasks

Configuring the Oracle account used by Meridian

Restoring an Oracle vault to another server