Create a New Vault

Review the following information if you plan to use a Oracle database for your vault.

• Unlike the Hypertrieve and SQL Server database engines, the Oracle database engine requires that an Oracle instance already exist before a vault can be created. An existing instance can be used but we recommend that you can create a new instance dedicated to Meridian. Use the Oracle Database Configuration Assistant to create a new instance according to your preferences. Meridian functionality and performance is independent of most instance initialization parameters. If multiple vaults will be hosted by Oracle, we recommend that you create a separate instance for each vault. This is to limit the Oracle database size in the event that vaults are deleted or when the Vault Consistency Wizard is used.

• We recommend that you use only eight characters for the name of an Oracle vault. The reason is that the Oracle table representing the vault only uses the first eight characters of the vault name, and if the difference between different vault names occurs after the first eight characters, then the vaults will appear to have the same name.

• After you create an Oracle instance, the EDM Server service account needs to be created in the database using DBA Studio or SQL Plus. The account name must be MERIDIAN (upper case) and the initial password must be MANAGER (upper case) in order to create the first vault. For information on the requirements for this account, see EDM Server Service Account Requirements For Oracle. You can change the EDM Server service to use a different account later as described in Configure the Oracle Account Used By Meridian.

To create a new vault:

1. In the Meridian Enterprise Administrator, click EDM Server in the left pane.

   The active vaults are listed in the right pane.

2. Click Next.

   The Vault Name and Database Engine Type page appears.

3. Type a name for the new vault.

   Do not use spaces in the name.

4. Make a selection from Database engine.

   The available database engine types are those that were selected when Meridian was installed on the server and that have registered licenses.

   For Meridian, the supported database engines are Hypertrieve, SQL Server, and Oracle. Additional choices among the database engine types may be present for backward compatibility. For more information about each engine type, see Hypertrieve Database Engine, How Meridian Works With SQL Server, and How Meridian Works With Oracle.

5. Click Next.

   The How to Initialize the Vault page appears.

6. Click options or type values using the descriptions in the following table.

   Vault initialization options

   Option	Description
   Create empty vault	Creates an empty vault containing no documents or configuration information. Select this option if you will be importing an existing vault configuration file or will configure the vault manually. For more information on configuring an empty vault, see Configure Vault Settings.
   Maintain history	Retains all revisions of documents. Otherwise, only the latest revision will reside in the vault. This option uses more disk space. To remove unused revisions, they can be archived as described in Archive Documents or removed as described in Remove Vault History.
   Import contents of another vault	Imports the documents and configuration settings from an existing vault into the new vault. Select this option if you want to create a replica of an existing vault for testing, development, or similar purposes. Note: This option cannot be used to import a vault from an earlier version. The recommended workaround is described in Move a Vault. After the vault has been created, restart the Accruent EDM Server service to load the contents into HyperCache.
   Source vault	Select the source vault to import into the new vault. To exclude specific properties from the source vault, see Exclude Existing Property Values When Importing a Vault.
   Copy stream files	Copies the document files of the source vault to the new vault. This makes the new vault an independent replica of the source vault. Be sure adequate free disk space exists to duplicate all of the source vault's files.
   Use existing stream files	Causes the new vault to use the existing document files of the source vault instead of copies. This makes the source vault and the new vault both dependent on the same document files. Select this option only if the source vault will be abandoned. Do not select this option if the source vault will continue to be used. Otherwise, revision conflicts will occur between revisions made in both vaults.

7. Click Next.

8. If the Create empty vault option is enabled, click options or type values using the descriptions in the following table.

   Otherwise, skip to step 9.

   Configuration import options

   Option	Description
   Do not import configuration data into the new vault	Select this option to leave the configuration of the new vault empty so that you can begin manual configuration.
   Import configuration data from a template	Imports an existing vault configuration (.MET) file during vault creation. Vault configuration files are exported from the Meridian Enterprise Configurator as described in Meridian Enterprise Configurator.
   Path to configuration file	Type the path to an existing vault configuration file or click Browse and select a file.

9. Click Next.

   The Configure Database Engine page appears.

10. Click options or type values using the descriptions in the following table.

    Database engine options

    Option	Description
    Path for database files	This option appears only if the HyperTrieve database engine is selected. Type a path where the files created by the database engine should be stored or click Browse and select a folder. This location must have adequate free space for all of the metadata that will be created during the import, plus future growth. For guidelines on estimating the space required and location options, see Document Storage Space Requirements.
    Computer running SQL Server, OR Instance of Oracle server	These options appear only if the SQL Server or Oracle database engines were selected in step 4. Type the name of the SQL Server computer or Oracle instance. If this is the same computer as the Meridian application server, leave this option blank. The database files will be controlled by the selected database engine. For more information on using a separate database server, see Deployment Strategies.
    Path for content (stream) files	Type a path where the files created by the database engine should be stored, or click Browse and select a folder. This location must have adequate free space for all of the document files that will be created during the import and their future revisions, plus space for future growth. For guidelines on estimating the space required and location options, see Document Storage Space Requirements. The content (stream) files may be located on a separate file server or network storage device by specifying a UNC path. For more information on using a separate storage location, see Deployment Strategies. Note: If content indexing will be enabled for the vault, storing content files at a UNC location requires that the indexing service reside on the Meridian Enterprise application server and a registry value modified as described in Configure Content Indexing.
    Location for EDM server local files	Type a path on the local computer where temporary and backup files created by the database engine should be stored, or click Browse and select a folder.

11. Click Next.

    The next Configure Database Engine page appears. If the SQL Server or Oracle database engines were selected in step 4, a page appears listing additional database engine options.

    Click options or type values using the descriptions in the following table. Otherwise, skip to step 12.

    Database file options

    Option	Description
    Path for database files	Type an existing path where the data files created by the database engine should be stored. If a remote SQL Server instance is specified in Computer running SQL Server, type the path on the remote server. If the database is hosted on the local computer, click Browse and select a folder. This location must have adequate free space for all of the metadata that will be created during the import, plus future growth. For guidelines on estimating the space required and location options, see Document Storage Space Requirements. For additional folder requirements, see Integrate With a Separate SQL Server Computer.
    Path for index files	Type an existing path where the index files created by the database engine should be stored. If a remote SQL Server instance is specified in Computer running SQL Server, type the path on the remote server. If the database is hosted on the local computer, click Browse and select a folder. This location must have adequate free space for all of the index data that will be created during the import, plus future growth. For guidelines on estimating the space required and location options, see Document Storage Space Requirements.
    Path for log files	Type an existing path where the transaction log files created by the database engine should be stored. If a remote SQL Server instance is specified in Computer running SQL Server, type the path on the remote server. If the database is hosted on the local computer, click Browse and select a folder. This location must have adequate free space for all of the log files that will be created during the import plus space for future growth. For guidelines on estimating the space required and location options, see Document Storage Space Requirements.
    Database exists	Enable this option if the SQL Server database to store this vault's data already exists as described in Create the Vault Database Manually.
    Disk configuration scenario	Select the option that best describes the database server that will be used by this vault, which will enable the corresponding path options on this page.

12. Click Next.

    The next Configure Database Engine page appears.

13. Select database cache size values using the descriptions in the following table.

    These settings can be adjusted later. For more information on optimizing vault performance, see Optimize Performance.

    Database cache options

    Option	Description
    Relative cache size	Type a percentage of the total database size that should be held in cache memory. Larger numbers generally result in better performance. This setting will ensure that an optimum amount of data is cached as the vault grows over time.
    Maximum cache size	Type the maximum amount of cache memory to be allocated to this vault. This setting limits the size of the vault cache so that it does not consume too much of the server's memory.
    Use HyperCache	Enables (default) HyperCache configuration as described in Hypercache.

14. Click Next.

    If the SQL Server or Oracle database engines were selected in step 4, skip to step 15.

15. Select database configuration settings using the descriptions in the following table.

    Hypertrieve database options

    Option	Description
    Maximum size of the database log	Accept the default unless an existing vault will be imported, in which case type a larger value or increase the value of Minimum time between snapshots so that snapshots are not performed during the import, which can delay import completion.
    Minimum time between snapshots (minutes)	Accept the default or type a larger interval so that snapshots are not performed during large imports or during production hours, if necessary.

16. Click Next.

    The next Completing the New Vault Wizard page appears.

17. Confirm the settings that are shown and click Finish to begin vault creation.

    Depending on the options selected, vault creation can take several minutes or many hours.

18. If the SQL Server database engine was selected in step 4, continue with the task described in Integrate With a Separate SQL Server Computer.

If the synchronization between Meridian and Meridian Explorer fails inconsistently:

1. Check the SQL logs.

2. If an error is found, take corrective action such as increase the temporary database size.

3. Restart the EDM Server.

4. Restart Meridian Enterprise Server.

5. Retry the synchronization.