Accelerator Customer Upgrade fails with error 'Invalid object name'
Article ID: 100034120
Updated On:
Description
Error Message
Invalid object name
Cause
Part of the upgrade process is to review the existing objects in the database in preparation for the upgrade. Examples of database objects include tables, views, stored procedures, functions, indexes or statistics. If custom, non-factory objects have been added to the database or existing objects have been modified beyond factory settings to meet a particular business need, the review will advise as such using a generic error as listed above. The specific customised object names may not be listed in the error.
Resolution
The database will need to be reverted to factory specifications to allow an upgrade to be completed successfully. This may include reverting any customised objects to factory specifications and/or removing any added custom objects.
It is the customer's responsibility to track any such custom database objects (tables, views, stored procedures, functions, etc.) and revert any such customisations prior to an upgrade so the upgrade may be completed successfully. If there is a business need for customised 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 object(s) for a review of the custom object(s), an upgrade of the custom object(s) as needed and re-implementation post upgrade. This will need to be performed at each upgrade.
Note: If there is a specific business need that is not currently included in the product that prompted the creation of a custom database object (tables, views, stored procedures, functions, etc.), it is recommended an enhancement request be entered for the business need. Please see the Related Articles section for the steps to enter an enhancement request.
It is the customer's responsibility to track any such custom database objects (tables, views, stored procedures, functions, etc.) and revert any such customisations prior to an upgrade so the upgrade may be completed successfully. If there is a business need for customised 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 object(s) for a review of the custom object(s), an upgrade of the custom object(s) as needed and re-implementation post upgrade. This will need to be performed at each upgrade.
Note: If there is a specific business need that is not currently included in the product that prompted the creation of a custom database object (tables, views, stored procedures, functions, etc.), it is recommended an enhancement request be entered for the business need. Please see the Related Articles section for the steps to enter an enhancement request.
Issue/Introduction
Upgrading an Enterprise Vault (EV) Compliance Accelerator / Veritas Advanced Supervision (CA/VAS) or Discovery Accelerator (DA) database results in the error listed below. The upgrade does not complete and re-running the upgrade results in the same error.
Was this article helpful?
Yes
No
Powered by
