Professional Documents
Culture Documents
Trouble Shooting Guide Missing Data in Service Session From BI CCDB
Trouble Shooting Guide Missing Data in Service Session From BI CCDB
0 EhP1
End-to-End Diagnostics
END-TO-END DIAGNOSTICS
TROUBLE SHOOTING GUIDE MISSING
DATA IN SERVICE SESSION FROM BI/CCDB
Typographic Conventions
Icons
Type Style
Icon
Example
Text
Represents
Words or characters quoted
from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.
Cross-references to other
documentation.
Example
text
Emphasized words or
phrases in body text, graphic
titles, and table titles.
EXAMPLE
TEXT
Example
text
Example
text
<Example
text>
EXAMPLE
TEXT
Meaning
Caution
Example
Note
Recommendation
Syntax
END-TO-END DIAGNOSTICS
TROUBLE SHOOTING GUIDE MISSING
DATA IN SERVICE SESSION FROM BI/CCDB
Contents
1
Introduction ......................................................................................................................................... 4
1.1 How to Use this document ........................................................................................................... 4
1.2 Technical Infrastructure ............................................................................................................... 4
1.3 Required Software Components .................................................................................................. 4
1.4 Technical Infrastructure ............................................................................................................... 5
2
Trouble Shooting ................................................................................................................................. 6
2.1 Checking Workload Data .............................................................................................................. 6
2.1.1
E2E Workload Analysis application .......................................................................................... 6
2.1.2
Listcube ................................................................................................................................... 6
2.2 Checking Configuration Data ....................................................................................................... 8
2.3 General checks ........................................................................................................................... 10
2.3.1
Extractor Framework Administration ...................................................................................... 10
2.3.2
Diagnostics Setup Wizard and results .................................................................................... 11
2.3.3
Landscape Browser ............................................................................................................... 11
2.3.4
Selfcheck ............................................................................................................................... 12
2.4 Step by Step analysis ................................................................................................................. 13
2.4.1
Retrieving the correct LongSid ............................................................................................... 13
2.4.2
Retrieving the time frame ....................................................................................................... 14
2.4.3
Retrieving the BI RFC Destination and the User .................................................................... 14
2.4.4
Required Authorizations ......................................................................................................... 14
2.4.5
Missing configuration data...................................................................................................... 14
2.4.6
Missing performance data ...................................................................................................... 16
3
Known Issues .................................................................................................................................... 18
3.1 Service Session........................................................................................................................... 18
3.1.1
Missing JDK information......................................................................................................... 18
3.1.2
Incomplete Instance name for double stack systems ............................................................. 18
3.1.3
Authorization Problem ............................................................................................................ 18
3.1.4
Multiple entries with no aggregated data ................................................................................ 19
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
Introduction
1.1
The purpose of this document is to help you with the troubleshooting of automatic service sessions like EarlyWatch
Alert (EWA) in the Solution Manager and the Solution Manager Diagnostics.
1.2
Technical Infrastructure
In order to generate an EarlyWatch Alert (EWA) for non-ABAP components, Solution Manager 7.01 is required.
Solution Manager comprises of both an ABAP and a Java stack. On the Java stack of the Solution Manager, Solution
Manager Diagnostics (SMD) is installed, which is used to collect centrally data of all managed non-ABAP systems.
Several other service sessions like EarlyWatch, GoingLive Analysis or GoingLive Verification use the same technique.
The ABAP stack is used as:
- Persistency for configuration data in the configuration and change DB (CCDB)
- Persistency for performance data in the Solution Manager BI
- Extractor Framework(EFWK), that schedules and triggers several extractors
- Service Session Workbench to generate the Service Report
Within the SMD several extractors exist that call several SMD Agent Applications (Agelets) or reading data from the
Wily Introscope Enterprise Manager (IS EM). The SMD Agelets in turn can collect data either from file system (FS)
or directly from managed system.
The EWA Session is usually scheduled on a weekly basis and reading the data from CCDB and BI if the session is
processed either in transaction DSA or by the job 'SM:EXEC SERVCICES'. Other sessions read the data during
initialization of the session or when a check is processed.
1.3
Resulting from the technical scenario described above, the software components are required for sessions for nonABAP components as described in and the referenced notes of the Solution Manager release of note 1010428. For
EhP1 for example it is note 1274287.
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
1.4
Technical Infrastructure
There is no special setup step required for EWA but the following requirements must be fulfilled:
The setup of the managing system (SAP Solution Manger) has to be executed successfully
(Transaction SOLMAN_SETUP).
The setup steps for the managed systems have to be executed successfully and they have to report their data
correctly to SMD and Introscope as described in the setup guide of SMD that can be found in the Service
Marketplace http://service.sap.com/diagnostics -> Installation and Configuration -> End-to-End Root Cause Analysis
System Landscape Setup Guide
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
Trouble Shooting
In this chapter it is described how to check some settings for a managed J2EE Engine. It would be similar for other
software components.
2.1
The E2E Workload Analysis application reads also data from BI therefore it is a good starting point to check if
performance data for a system is available in the E2E Workload Analysis.
In the E2E Workload Analysis Application open the tab strip for the main instance and choose the appropriate time
frame from the Service Session (see also 2.4.2Retrieving the time frame).
When data can be displayed in the E2E Workload Analysis Application but not in the service session something with
the RFC connection is wrong (RFC Destination does not work, RFC User does not have enough authorizations...).
2.1.2 Listcube
If no HTTP connection is possible one can also check the content of the BI with transaction LISTCUBE. Performance
data is available in Infocube 0SMD_PE2H (for hourly values) and 0SMD_PE2D (for daily aggregations). First all
metrics will be written into the hour cube 0SMD_PE2H and are aggregated by housekeeping job into day cube
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
0SMD_PE2D.
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
Data is available in Infocube 0SMD_PE2H with the same selection. If data is just missing in infocube 0SMD_PE2D
then something with the house keeping job is wrong. Check the job logs and spool output of job
E2E_HK_CONTROLLER.
Introscope extractors are scheduled (see chapter 2.4.6Missing performance data)
Data is available in Introscope at all.
When data can is available in the Infocubes but not in the service session something with the RFC connection is
wrong (RFC Destination does not work, RFC User does not have enough authorizations...).
2.2
The Change Reporting application reads also data from CCDB therefore it is a good starting point to check if
configuration data for a system is available in the Change Reporting.
In the Root Cause Analysis Work Center (which is assigned with role SAP_SMWORK_DIAG) choose:
1. System Analysis
2. Your POWL Query or predefined Query (like Java Systems)
3. The relevant System
4. The Button Change Reporting
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
Below the system there are different levels where configuration data is collected (Main Instance, Host, Instance,..).
If there is no data available follow chapter 2.4.3 But when data can be displayed in the Change Reporting but not in the
service session something with the RFC connection is wrong (RFC Destination does not work, RFC User does not
have enough authorizations...).
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
2.3
10
General checks
This part contains several checks that can be executed when no performance data or configuration data is available.
The most important entries in the RCA Workcenter are:
- Extractor Framework Administration
- Diagnostics Setup
- System Browsing
- Diagnostics Self-Check
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
SAP AG 2008
11
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
2.3.4 Selfcheck
With the self check you can check the status and settings of the managing system as well as the managed system.
Each self check has a status and a short explanation what to do in case of an error.
SAP AG 2008
12
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
2.4
13
This chapter describes step by step what can be done if no performance or configuration data for NON-ABAP systems
like J2EE engine is available.
Open the attribute editor in the service session (Goto-> Technical Functions-> Attribute Editor) and choose the correct
context and the context instance (e.g J2EESYSTEM for J2EE Engine). The long sid is stored in the attribute LSID:
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
14
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
15
http://service.sap.com/diagnostics -> More documents -> Media Library -> E2E Change Analysis Troubleshooting
Guide
Checking CCDB Extractors
If no entries are returned repeat the setup of the managed system (2.3.2Diagnostics Setup Wizard and results).
In case no HTTP connection is possible check in transaction SE16 in table E2E_ACTIVE_WLI if CCDB Extractors are
scheduled for the managed system. Use these selection criteria:
EVENT_TYPE_ID
SID
<LSID>
INSTNO
PRPPMSID
MIPPMSID
PPPMSID
CVPPMSID
MAINEXTRACTOR
EXTRACTOR
E*CCDB*
If no entries are returned repeat the setup of the managed system (2.3.2Diagnostics Setup Wizard and results).
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
SAP AG 2008
16
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
17
Start application Extractor FWK Administration from the RCA work center:
If no entries are returned repeat the setup of the managed system (2.3.2Diagnostics Setup Wizard and results).
Select one extractor and display the log.
In case no HTTP connection is possible check in transaction SE16 in table E2E_ACTIVE_WLI if Introscope Extractors
are scheduled for the managed system. Use these selection criteria:
EVENT_TYPE_ID
SID
<LSID>
INSTNO
PRPPMSID
MIPPMSID
PPPMSID
CVPPMSID
MAINEXTRACTOR
EXTRACTOR
E2E_JAVA_EXTRACTOR_IF
If no entries are returned repeat the setup of the managed system (2.3.1Diagnostics Setup Wizard and results). At
least two entries for a J2EE engine should be returned (one for host specific data where no PPMSID field is filled and
one for the J2EE engine where field CVPPMSID is not empty see also screenshot above).
If table E2E_ACTIVE_WLI contains all the required extractors you can check in SE16 for table E2E_EFWK_STATUS
how many records have been read for the last execution. Use the same selection criteria as for table 2E_ACTIVE_WLI.
Example of a result:
EXTRACTOR
E2E_JAVA_EXTRACTOR_IF
EXTRACTORCLASS
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
METRIC
TIMESTART
20081215064546
TIMESTOP
20081215064548
COLLECT
STATUS
PRIORITY
0
RC
00
MESSAGE
LASTRUNTIME
1
LASTRECORDS
36
The field LASTRECORDS contains the number of retrieved metrics.
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
18
Known Issues
3.1
Service Session
The E2E Workload Analysis application reads also data from BI therefore it is a good starting point to check if
performance data for a system is available in the E2E Workload Analysis.
3.1.1
In Check 56 (Support Package Maintenance) of group SMD_J2EE the JDK information is not displayed although the
configuration could be read.
Reason: The Store type has been changed.
Solution: The problem is fixed with ST-SER 2008_2 SP3.
SAP AG 2008
End-to-End Diagnostics
Trouble Shooting Guide missing data in service session from BI/CCDB
19
Solution:
Note 1392762 has to be applied in the Solution Manager BI for the info provider 0SMD_PE2D.
SAP AG 2008