Error Message

Example from the Information field of a DA customer database's properties page:

The statistics 'VaultId' is dependent on column 'SearchItemID'.

The error example above lists the object name, a statistic in this example, causing the error, and then lists the column on which the statistic is dependent. This object is not a part of the database's schema at installation and is a manually created user object. If the upgrade process attempts to make a change to this column, such as to its data type, the upgrade fails as a dependency on this column exists.

CA/VAS and DA customer databases are expected to have only objects that are part of the database schema when installed or upgraded. When user-added objects are present, such as the statistic in the example above, the upgrade will fail. This is because the upgrade process is only aware of specific database objects and dependencies, and will, thus, log an error when an unexpected, user-added object or dependency is encountered.

It is the customer's responsibility to track any such user-added database objects (tables, views, stored procedures, functions, statistics, etc.) and revert any such customizations prior to an upgrade so the upgrade may be completed successfully. If there is a business need for customized database objects and that business need is not fulfilled by the upgraded product, it is also the customer's responsibility to consult the entity responsible for the original creation and implementation of the custom objects for a review of the custom objects, an upgrade and/or removal of the custom objects as needed and re-implementation post upgrade as needed. This will need to be performed at each upgrade.

For the example error above, follow these steps resolve the issue:

1. Ensure a current backup of the database exists in the event the changes must be reverted.
2. Stop the Enterprise Vault Accelerator Manager Service (EVAMS) on the Accelerator server.
3. Identify the affected table. This can be done by looking through the database schema for all tables using the column to be altered.
4. In SQL Server Management Studio:
   1. Expand the database and its Tables folder.
   2. Locate and expand the affected table's Statistics folder.
   3. Refer to the errors to identify the statistics object(s) causing the failure.
   4. Right click on the statistics object to be dropped and select the Script Statistic as | DROP To | New Query Editor Window options.
   5. Execute the contents of the new query window to drop the unexpected statistics object.
   6. Repeat Steps 3 through 5 for each unexpected statistics object.
5. Start the EVAMS.
6. In the EVBAAdmin web page, click on the customer in the left panel under the Accelerator server name to see its Properties in the right panel.
7. Right click on the customer to see the available options.
8. Select the Properties option to open the customer's Properties page.
9. Click the Retry button.
10. Monitor the Information dialog box in the properties to see if the upgrade is completed successfully.