-
Title
An entry for a repository has been found in Quest tables located on database <alias> But no -
Description
When using the Repository Wizard it generates the following message:
An entry for a repository has been found in Quest tables located on database <alias>
But, no repository was found.
The application cannot connect to <alias> -
Cause
The database once had a repository installed (under a separate username than other quest products) and the repository objects have since been dropped.
A entry remains in a common Quest table which records the fact that a repository was installed. -
Resolution
In the situation where the repository objects have been dropped, it is possible to clean-up the database so that it appears as though a repository does not exist.
In a SQL*Plus session to the database, confirm that no Capacity Manager repository objects exist:
SQL> select owner,object_name,object_type from dba_objects where object_name like 'QUEST_CMO_%';
no rows selected
Provided there are no rows returned, then the next step is to check QUEST_COM_PRODUCTS:
SQL> select product_id,product_name from quest_com_products;
PRODUCT_ID PRODUCT_NAME
---------- ------------------------------
9999 Quest Common Schema
311 Instance Analyze Trace Objects
36 Capacity Manager for Oracle
The data returned may vary depending on the products installed. The Capacity Manager for Oracle entry is the one that prevents a new repository from being installed. It can be deleted:
SQL> delete from quest_com_products where product_id = 36;
SQL> commit;
Then, the Repository Wizard will run normally.
NOTE: If the user is dropped with cascade (to drop the repository objects), the user needs to be created (with dba rights) as part of the Repository Wizard's pre-install checklist, otherwise it will not be able to install the repository objects.