-
Título
Installing Performance Analysis repository the error: "Scenario initialization fault" occurs -
Descripción
While installing the Performance Analysis (PA) repository the following error occurs:
The repository operation failed.
Connection Details
...
Generated the following error:
ERROR: Scenario initialization fault
Location:
Error Code: -81000
Installation without repository works fine. -
Causa
CAUSE 1: Invalid Performance Analysis database objects in the monitored instance. To diagnose run the following query as PA user in the monitored database:
Select object_name, object_type, status from user_objects where status = INVALID;CAUSE 2: Corrupt history collection on the middleware. If you are connecting to the instance with the PA client you will get and error message stating: "History collection is not configured".
CAUSE 3: Not enough space available in the repository. This can be diagnosed by examining the repository log under <install dir>/agents/StealthCollect/7.0/<HOST-INSTANCE>quest_sc_rep/var/stderr.quest_sc_rep
For example for Oracle you will see:Wed May 11 15:18:38 2016: ERROR: sc_rep_mngr:db_utils.cxx:24: <DATABASE ERROR> Code: 1653; Message: ORA-01653: unable to extend table QUEST.QUEST_SC_WAIT_EVENT# by 128 in tablespace TOOLS; SQL Text: INSERT INTO QUEST_SC_WAIT_EVENT# (INSTANCE_KEY, QUEST_EVENT_ID, WAIT_EVENT_NAME, CATEGORY_NAME, PARAM_COUNT, RES1, RES2) VALUES (:instance_key , :quest_event_id , :event_name , :category_name , :param_count , :res1 , :res2 ); VAR Info: </DATABASE ERROR> -
Resolución
RESOLUTION 1:(Oracle Only)1. Stop the PA services on monitored host and middleware host.2. Drop the monitored instance schema using the following steps:a) Go to: <install dir>/agents/StealthCollect/7.0/data/b) Login to the monitored instance as the Performance Analysis user using sqlplus.c) Run the script quest_pa_drop_mon.sql3. Re-create the monitored instance schema by following the instructions in readme.txt which is located in the same directory as above. (Refer to the first section, "I. To install the Performance Analysis objects on the monitored instance")4. Restart the PA services on monitored host and middleware host.NOTE: For SQL Server there are no objects installed in the monitored instance.RESOLUTION 2:(Oracle or SQL Server)If the history collection is not configured, remove the corrupted installation and reinstall PA. Make sure that you can connect (ping, tnsping and connect via SQL*Plus) from the middleware server to the database server and vice versa.RESOLUTION 3:(Oracle or SQL Server)Allocate more space for the repository.For Oracle PA needs about 2.2 GB per monitored instance (1.2 GB for data and 1.0 GB for index)For SQL Server PA needs about 2.5 GB per monitored instance (2.0 GB for the data file and 500MB for the log file)