Space Manager QSA has been installed manually using the server-specific installer. QSA has been installed and started successfully but the client GUI is showing that the Quest Server Agent Status is not installed. Reinstalling the QSA yields the same issue.
'quest_exec' package and package body is also installed on another schema aside from the specified Space Manager owner.
RESOLUTION:
Run the following SQL to ensure that QSA objects have been installed on the specified schema.
select PRODUCT_ID,PRODUCT_NAME,INSTALL_USER,PRODUCT_VERSION,INSTALLED_BY from quest_com_products where product_id in ('35', '61');
Sample results:
PRODUCT_ID PRODUCT_NAME INSTALL_USER PRODUCT_VERSION INSTALLED_BY
---------- ------------------------------ --------------------- -------------------- ------------------------------
61 Quest Server Agent LIVE 6.6.0 LIVE
35 Space Manager LIVE 6.6.0 LIVE
Now run the following SQL to check if 'quest_exec' package is installed on another schema aside from the specified owner (e.g. LIVE).
select owner, object_type from dba_objects where object_name=upper('quest_exec');
Sample results:
OWNER OBJECT_TYPE
------------------------------ ------------------
PUBLIC SYNONYM
SYSTEM PACKAGE
SYSTEM PACKAGE BODY
LIVE PACKAGE
LIVE PACKAGE BODY
The above result shows that 'quest_exec' package and package body is also installed on SYSTEM schema. This is normally a mistake during installation, where the user incorrectly specifies SYSTEM to install the objects. Drop the quest_exec package and package body from the wrong schema (in this example SYSTEM).
Restart the QSA agent and client GUI.
