Solution Manager: EarlyWatch Alert - Fix for Common Timeout Error on Remote System

Scenario
Encounter timeout error on remote system that caused by the data collection of EarlyWatch Alert.

Relevant SAP Note
1247198 - /SDF.RSORADLD_NEW timeout
984955 - Timeout with selection of V$-Views
838725 - Oracle dictionary statistics and system statistics

Error found on the remote system
1) Sample error from "ST22"

2) Double click to view the details

3) To further investigate the error with "ST11" and locate the trace log that within the time range of the error occur

4) Double click to view the details and search for the activities that occur on the specific time frame

Solution:
1) Prerequisite to ensure the BRTools version: SAP BRTools Release 7.00 Build 15 onwards.

2) To check the BRTools version and update it if required

3) Execute BRCONNECT command to create Oracle dictionary statistics - BRCONNECT internally calls the two procedures GATHER_DICTIONARY_STATS and GATHER_FIXEC_OBJECTS_STATS.

Login with user: ORA<SID> and execute the command below and wait until it complete. It will take couple of minutes depends on the system resources. (brconnect -u / -c -f stats -t oradict_stats)

4) Monitor the process with OS command: "top" with another putty session

5)  Creating Oracle system statistics (NOWORKLOAD) using BRCONNECT
     (brconnect -u / -c -f stats -t system_stats)

6) Creating Oracle system statistics (WORKLOAD) using BRCONNECT
    (brconnect -u / -c -f stats -t system_stats -i <minutes>) - example of 1 minutes

7) That's all, observe the task next cycle or day to determine the error been resolve.

Authorization: Example of Resolving Solution Manager Monitoring Error - RFC_NO_AUTHORITY

Scenario
Encounter authorization error on remote system after setting up of Solution Manager system monitoring.

System used
1) Remote system that been monitor: QAS client: 688

Error found on the QAS
1) TCODE: ST22 showing the list of error

2) Double click for further details

3) Locate the user that been used for the RFC connection

Solution
1) Execute TCODE: ST01 to trace the missing authorization for the user used for the RFC connection.

2) Execute TCODE: SUIM to find the role that required additional settings and select Roles by Complex Selection Criteria

3) Select the relevant user and the filtering object: S_RFC

4) Sample role found and double click to modify the authorization data

5) Click the change button

6) Add the missing authorization

7) That's all and observe the log of the next cycle or day to confirm the RFC error no longer appear.