Gaps in the GUI - collector does not collect data (39684)

We have gaps in the GUI and the collector does not collect data.

CAUSE 1
Conflicting PA configuration settings on the database server and middleware server.
During several PA upgrades and support cases changes at the configuration settings have been done. Now these changes  are conflicting and causing errors.

CAUSE 2:
Two middleware installations try to access the same collector, for example an old middleware test installation is still active.

CAUSE 3:
After upgrade to Performance Analysis 6.5 some files in the short term repository were corrupted

RESOLUTION 1:
Restore the original/default configuration files:
<install dir>/<port>/agents/StealthCollect/6.0/<hostname-SID>/quest_sc_mw/config
collector_ext_config.cfg
ext_config.cfg

To get the original/default configuration files contact Quest Support.

RESOLUTION 2:
Remove/Stop the not needed middleware installation.
For details have a look at the attached document "Multiple_MW_addressing_the_same_Collector.pdf"

RESOLUTION 3:
On the middleware server:
1. stop the PA processes (quest_launcher_daemon shutdown)
2. go to <install dir>/pa_agent/<port>/agents/StealthCollect/6.0/<host-SID>/quest_sc_mw/data.
3. rename Syntax_ID.data and Syntax_ID.indx
4. start PA processes (quest_launcher_daemon start)

The two files will be correctly rebuild while restarting the PA processes

DIAGNOSE 1:
- status of the collector is running, but no data is collected.
- middleware processes crashed every now and then.
- after restarting the installation everything is working fine for about 1-2 hours.

DIAGNOSE 2:
- on monitored host open <install dir>/agent/log/activity.log

You will find entries like this:
StealthCollect@6.0@quest_sc_collector@Collector1-Instance1 (2211972) killed by quest (USER1@MW1)
StealthCollect@6.0@quest_sc_collector@Collector1-Instance1 started
StealthCollect@6.0@quest_sc_collector@Collector1-Instance1 (1999062) killed by quest (USER2@MW2)