0001827116

8/10/2019 0001827116

http://slidepdf.com/reader/full/0001827116 1/12

SAP Knowledge Base Article

Symptom

In SAP EarlyWatch Alert (EWA) the rating is not determined (grey rating):

Environment

l SAP Solution Manager 7.0 EHP1l SAP Solution Manager 7.1

Reproducing the Issue

1. Open transaction SM_WORKCENTER

2. Go to tab Technical Monitoring 3. Click Generated Documents

4. Click button EarlyWatch Alert

1827116 - Rating not determined (Grey) at SAP EarlyWatch Alert

Version 17 Validity: 08.08.2013 - active Language English

Section 1 Service Summary of the document shows message:

Some essential service data for the EarlyWatch Alert session is missing. Therefore, no rating is assigned.Check the details in the "Service Preparation and Service Data Quality" section.

8/10/2019 0001827116


5. Select solution and click button Search

6. Check EWA report with grey rating

7. Open document with button Generate Word Report

8. In section 1 Service Summary look for message:

9. In section 3.1 or3.4 Quality of Service Data in Solution Manager Diagnostics - BW look for messages:

Some essential service data for the EarlyWatch Alert session is missing.Therefore, no rating is assigned. Check the details in the

Check the details in the "Service Preparation and Service Data Quality" section.

Performance of <SID>

No performance data is returned fromBW InfoCube. Infocube: 0SMD_PE2D ,metric type: APPLICATION THREADS ,metric name: ACTIVETHREADSCOUNT / metric type:JAVA MEMORY USAGE , metric name:FULLGC FRACTION (%) used insection 'Java System Data for <SID>'.

8/10/2019 0001827116


8/10/2019 0001827116


For more information check SAP note 1801236.

Resolution

1. In case the SAP Solution Manager is on release 7.0 EHP1 please follow the attached guide to SAP note1332428 2. For Solution Manager 7.1: As first step always check the correct maintenance of the product in the Landscape Management Database (LMD

page: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape In case the product is not maintained correctly in LMDB not all relevant extractors (like of type J2EE) will be scheduled.

3. Please verify that the Introscope Enterprise Manager is up and running according to check point from SCN pagehttp://wiki.sdn.sap.com/wiki/display/SMSETUP/SMS_CHECK_10

4. Check for End-to-End Analysis Workload Analysis data for the affected managed system, the EWA time frame and granularity day:

1. Go to tab Root Cause Analysis

2. Click End-to-End Analysis in the left-hand panel3. Select system and push button Workload Analysis

4. In the E2E Workload Analysis check for the EWA report time frame (timeframe custom selection) if you have data for granularity day (clictab J2EE Engine

In case the EWA report contains message:

No performance data is returned from BW InfoCube.Infocube: 0SMD_PE2D , metric type: JAVA MEMORY USAGE , metric name: FULLGC FRACTION (%) used in section 'Java System Da

check for Workload Analysis related data in sub tab Java Memory Usage for the report time frame:

No performance data is returned from BW Infocube. Infocube: 0SMD_PE2D , metric type: APPLICATION THREADS , metric name: ACTIVETHREADSCOUNT used in section 'Java System

check for Workload Analysis related data in sub tab J2EE Thread Usage for the report time frame:

8/10/2019 0001827116


In case there are data available J2EE Thread Usage on granularity day, please follow recommendations from SAP note 1835894 (The isa Service Content Update which was released on 19th March 2013).

If there are no data for J2EE Thread Usage on granularity day:

1. Log on to Wily Enterprise Manager (EM) (→ how to log on to Wily EM is described further down)2. Go to tab Console and select View Netweaver Portal Triage 3. Check for data in chart Application Threads (Active and Max)

Set the Console Lense option for the affected Host and Process (use SAP Netweaver as process) and click button Apply:

8/10/2019 0001827116


Check again for data in chart Application Threads (Active and Max).In case you have no data for that chart for Application Threads, check if Introscope Byte Code Adpater is up and running according t

5. If you have no workload analysis data for granularity day but for granularity hour like below:

Check according section 2.1.2 Listcube in the guide attached to SAP note 1332428 if the job E2E BI HOUSEKEEPING is running on a dailySM37:

Select under area Job status all options, as Job start condition set last week until today and click button Execute:

Check for a daily running E2E BI HOUSEKEEPING job with Status Finished.

8/10/2019 0001827116


If this is not the case please create a customer ticket on component SV-SMG-INS-DIA and mention that there is a problem with the E2E BI HO

6. If you have no data for granularity hour either for the EWA time frame for Java Memory Usage

1. Open transaction E2E_EXTRACTOR_FWK 2. Select filter similar to below example (you need to check for extractors like WORKLOAD ANALYSIS (INTROSCOPE DATA) of type JAV

system)

The relevant target cube can be found in tab Extractor Detail → Configuration

If the last status of the extractor is Red LED; stop; errors, please check the message from tab Extractor Log and follow the recommendatimessage:

8/10/2019 0001827116


In case you cannot find such JAVA WORKLOAD ANALYSIS related extractors for your managed system:

1. Open transaction SOLMAN_SETUP 2. Go to Managed Systems Configuration 3. Select Technical System

4. Go to step Configure Automatically and click Edit 5. Select Activity Extractors Setup and click Execute Selected

6. Open transaction SOLMAN_SETUP 7. Go to Managed Systems Setup

8. Select Technical System

9. Go to step Configure Automatically 10. The following two activities must be in green status (=Activity performed)

n Introscope Host Adapter

n Byte Code Adapter Installation

8/10/2019 0001827116


11. If the activities are not shown in green, redo the activity setup steps:

1. Click button Edit 2. Select activities:

n Introscope Host Adapter

n Byte Code Adapter Installation 3. Click Execute Selected

4. If one of the activities from section Configure Automatically keeps failing check the detailed log messages in the log grid:

Important remark on the Byte Cod e Adapter (ISAGENT) :

The byte code agent pushes JAVA related data every 15 seconds to Introscope EM. If isagent setup was not completed succwill not contain J2EE related data (like JAVA APPLICATION THREADS).

For Byte Code Adapter setup therefore check the manual ISAdmin setup results under:

http://<host>:<port>/smd/ISAdmin → Select J2EE system ID → check IS Agent State:

8/10/2019 0001827116


If the IS Agent State is not Running check the detailed error message in section Last Operation Results.If the J2EE Nodes are missing for the JAVA system as shown below:

check the system landscape definition according to step 2 of this KBA. The J2EE nodes must also be found in the Landscape Browser under Technical Systems → Search for <SID> → check for ebelow the instance:

Attention: In case your IS Agent Version is on ISAGENT.8.2.4.0-2012-01-27 (patch 0) please upgrade to ISAgent Release I

8/10/2019 0001827116


06-26 (patch 1) as described under SAP note 1273028.Please also check: For the Byte Code Adapter installation also check that not only a few standard Introscope metrics are disdescribed under SCN page: http://wiki.sdn.sap.com/wiki/display/SMSETUP/SMS_CHECK_44

Important remark: Regarding IS Agent setup please also consider SAP notes 1793553 and 1796399.

This can be checked in Introscope Starter :

1. Use direct linkhttps://<host>:<port>/webdynpro/dispatcher/sap.com/tc~smd~navigation/WilySelectorApp?INTROSCOPE_MODE=W

2. Click button Start Introscope

3. Log on to Wily Webview with user Admin (the default password of user Admin is Admin89)

4. Open tab Investigator and expand *SuperDomain5. Select host6. Check for specific metrics like SAP J2EE or JMX

Keywords

Ursachenanalyse, Transaktion, Systemlastanalyse, ACTIVETHREADSCOUNT / metric type: JAVA MEMORY USAGE , metric name:

8/10/2019 0001827116


EFFECTIVE OLD SPACE USAGE (%) / metric type: JAVA MEMORY USAGE , metricname: FULLGC FRACTION (%) used in section 'Java System Data for WRP'.

Metrik

Header Data

Product

This document is not restricted to a product or product version

References

This document refers to:

CSS SAP Notes

Released On 08.08.2013 08:35:52

Release Status Released to Customer

Component SV-SMG-DIA-APP-WA Workload Analysis

SV-SMG-INS-DIA Configuration of Root Cause Analysis related infrastructure

Priority Normal

Category Problem

1835894 False Warning About APPLICATION THREADS Data Missing In EWA

1801236 Rating Rules: Grey Rating of an Alert Based Session

1777750 How To Resolve Missing Service Data In CCDB on 7.0

1686987 Self-Diagnosis: Transfer to SAP ( active by default )

1332428 Missing data in service sessions from BW/CCDB

1273028 Introscope 8 Release Notes

69455 Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12)

Other Components

0001827116

Documents

Transcript of 0001827116