0 EhP1
End-to-End Diagnostics
Trouble Shooting Guide missing data in
service session from BI/CCDB
Version 1.1, December 2009
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 4
Trouble Shooting Guide missing data in service session from BI/CCDB
1 Introduction
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.
©SAP AG 2008
End-to-End Diagnostics 5
Trouble Shooting Guide missing data in service session from BI/CCDB
©SAP AG 2008
End-to-End Diagnostics 6
Trouble Shooting Guide missing data in service session from BI/CCDB
2 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.
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 7
Trouble Shooting Guide missing data in service session from BI/CCDB
0SMD_PE2D.
©SAP AG 2008
End-to-End Diagnostics 8
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...).
©SAP AG 2008
End-to-End Diagnostics 9
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 10
Trouble Shooting Guide missing data in service session from BI/CCDB
©SAP AG 2008
End-to-End Diagnostics 11
Trouble Shooting Guide missing data in service session from BI/CCDB
©SAP AG 2008
End-to-End Diagnostics 12
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
End-to-End Diagnostics 13
Trouble Shooting Guide missing data in service session from BI/CCDB
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 14
Trouble Shooting Guide missing data in service session from BI/CCDB
Performance data is read from the BI via an RFC Destination. The destination is maintained during setup and can be
identified with SE16 in table E2E_WA_CONFIG for the entry TYPE = SAP_BID_M.
Take the value from the field String and check the destination in transaction SM59.
Authorizations in BI Client
Performance data is read from the BI via an RFC Destination. The user in the RFC Destination is entered during the
setup and needs the role SAP_BI_E2E.
©SAP AG 2008
End-to-End Diagnostics 15
Trouble Shooting Guide missing data in service session from BI/CCDB
http://service.sap.com/diagnostics -> More documents -> Media Library -> E2E Change Analysis Troubleshooting
Guide
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 16
Trouble Shooting Guide missing data in service session from BI/CCDB
©SAP AG 2008
End-to-End Diagnostics 17
Trouble Shooting Guide missing data in service session from BI/CCDB
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
©SAP AG 2008
End-to-End Diagnostics 18
Trouble Shooting Guide missing data in service session from BI/CCDB
3 Known Issues
©SAP AG 2008
End-to-End Diagnostics 19
Trouble Shooting Guide missing data in service session from BI/CCDB
Solution:
Note 1392762 has to be applied in the Solution Manager BI for the info provider 0SMD_PE2D.
©SAP AG 2008