Old obsolete tables, indexes, and views remain after upgrading Harvest
Article ID: 109646
Updated On:
Products
Issue/Introduction
We have a "Prod" Harvest environment and a "Test" Harvest environment. After recently upgrading Harvest in our "Test" environment we ran into problems on our database upgrade, requiring us to delete the "Test" database and install the database again from scratch, using the HDBSETUP install feature. After successful install of the database to the new version of Harvest, our Oracle DB team identified to us a huge difference between our "Prod" and "Test" databases. This concerns us, as it indicates that the CA Harvest database upgrade script does not clean up obsolete tables, index, grants, views etc in the Harvest database. Why is this happening?
Environment
CA Harvest SCM all versions and platforms.
Resolution
When upgrading the SCM database you will find that data tables which are obsolete in the new version remain in the database after the upgrade. This is because deleting those tables could potentially delete user data and this is something we try to avoid. After confirming which tables are obsolete under the new version, these can be manually dropped from your SCM database if you prefer.
To get a list of tables and columns in a Harvest database, see this article: Database table descriptions
Additional Information
More information on the HDBSetup utility is found here: The hdbsetup Database Configuration Utility
Feedback
