Only after performing the steps described in Prepare the Meridian Server and Vault Configuration are you ready to run the Vault Consistency Wizard (VCW).
Run the VCW after business hours, such as on a weekend.
Run the Wizard
To run the VCW:
-
Open Windows Explorer and navigate to the folder containing the Meridian executable programs.
By default, the folder is located at C:\Program Files\BC-Meridian\Program.
-
Run AMVltCons.exe.
The Vault Consistency Wizard appears.
-
Click Next.
The What to Repair page appears.
-
Click Browse.
-
Select the vault to be repaired.
-
For most vaults, the VCW will run acceptably with the default options.
Enable or disable options using the descriptions in the following table only if necessary or instructed by Accruent Technical Support.
-
Click Next.
The final wizard page appears.
-
Click Finish.
A progress bar shows the processing progress. When the operation is finished, a dialog box will appear that shows a brief summary of what was found. If inconsistencies are shown, you can view the log file for more details.
Important!Remember to reverse the server and vault preparation changes described in Prepare the Meridian Server and Vault Configuration after the VCW has completed.
-
To restore user access to the vault after running the Vault Consistency Wizard:
-
Open the Local Users and Groups Microsoft Management Console.
-
Navigate to Groups > Windows Local Groups > Distributed COM Users.
-
Re-enable access for Authenticated Users.
-
| Option | Description |
|---|---|
|
Check only |
Performs a check of the vault database but does not make any changes to it unless the following option is enabled. |
|
Clean up deleted static collections after successful check |
Removes orphaned references from documents to static collections that have been deleted with the LargeSelectionThreshold registry value set as described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\OML. |
|
Check, Repair and Compact |
After the database checks have been performed, any inconsistencies found are repaired, and the database is compacted to reclaim unused disk space. |
|
Optimize database cache memory (large vault) |
Enables automatic configuration of memory used by the database cache while the VCW runs to prevent out of memory errors. Enabled by default. |
|
Analysis options |
Each option indicates a potential check that the VCW can perform on the vault. Accept the default options unless directed by Accruent technical support.
|
Logs
When the VCW runs, it logs its activities to the file Check.txt similar to the following example. By default, the file is located in the vault folder. Additional information can be found in the Windows application event log. Review them for any inconsistencies in the vault status values and keep them in case you have further problems and need to send them to Accruent Technical Support.
It is normal for the quantities of items to be different between when the index is rebuilt before and after repairs are made. This is the expected result of purging useless data and compressing the vault database.
Ideally, the six numbers that are reported for the vault status should be 0 after running the VCW check/repair/compact operation. The numbers of documents and versions should be identical before and after running the VCW (17422 documents and 23883 versions in the preceding example). That indicates that the vault is in excellent condition.
Single digit numbers greater than zero that appear in the Windows application event log before running the VCW are not cause for alarm. Run the VCW and they should change to 0. If any of the numbers are not 0 after running a VCW check/repair/compact operation or any of the numbers of the vault status consistently increases from one backup to another, contact Accruent Technical Support.
For more information about the status numbers, see the AutoManager OML source in Review the Application Event Log.
The log file might contain lines with the message "time effectivity ZERO interval". The background for this is that the Hypertrieve database supports versioning through "time effectivity". Each record in the database contains fields indicating the time interval during which the record is valid. A database query is always made for a particular point in time, and all records which are not valid for that time are filtered out.
A record is valid when the start of the record’s time interval is equal to or less than the point in time specified in the query, and the end of the interval is greater than the query time point. Records for which start and end of the interval are equal will always be filtered out. Other than taking up some space in the database file, these records do not affect Meridian functionality.
The existence of these "zero-interval" records is related to the unique time and context-versioned nature of Meridian transactions. Generally, their generation is difficult to avoid. When seeing these messages, you can assume that the reported database records have no consequence for the Meridian functionality.
=========== ht5ora.dll =========== 0 - Before Check&repair Number of documents: 13700 Vault status for Datastore TEST, Section TEST: 0, 0, 0, 0, 0, 0. Docs: 17422, Vers: 23883 1 - Chek&Rep Database Check of Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\TEST\CompoundItemService at 5/11/2016 7:53:32 PM RebuildIndex(ObjectSet): started. Values in ID Domain: 133079; Last Location Index = 16635. Repairs committed. End Database Check of Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\TEST\CompoundItemService at 5/11/2016 7:56:04 PM ----------------------------------------------- Import started at 5/11/2016 7:56:08 PM Import ended at 5/11/2016 8:18:03 PM ; Success. 2 - After Check&Repair Number of documents: 13700 Vault status for Datastore TEST, Section TEST: 0, 0, 0, 0, 0, 0. Docs: 17422, Vers: 23883 3 - Check Only Database Check of Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\TEST\CompoundItemService at 5/12/2016 11:18:59 AM RebuildIndex(ObjectSet): started for 81393 objects in 10175 locations. No errors found. End Database Check of Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\TEST\CompoundItemService at 5/12/2016 11:21:25 AM 4 - After Check Only Number of documents: 13700 Vault status for Datastore TEST, Section TEST: 0, 0, 0, 0, 0, 0. Docs: 17422, Vers: 23883
