e2e _troubleshootingguideehp1

Download E2E _TroubleShootingGuideEhP1

Post on 28-Mar-2015

326 views

Category:

Documents

3 download

Embed Size (px)

TRANSCRIPT

SAP Solution Manager 7.0 EhP1

End-to-End DiagnosticsVersion 1.1, December 2009

Trouble Shooting Guide missing data in service session from BI/CCDB

END-TO-END DIAGNOSTICSTROUBLE SHOOTING GUIDE MISSING DATA IN SERVICE SESSION FROM BI/CCDB

Typographic ConventionsType Style 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 textEXAMPLE TEXT

IconsIcon Meaning Caution Example Note Recommendation Syntax

Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text

EXAMPLE TEXT

END-TO-END DIAGNOSTICSTROUBLE SHOOTING GUIDE MISSING DATA IN SERVICE SESSION FROM BI/CCDB

Contents1 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

4

11.1

IntroductionHow to Use this document

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

Required Software Components

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

5

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

6

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.

2.1

Checking Workload Data

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.

2.1.1 E2E Workload Analysis applicationIn the Root Cause Analysis Work Center (which is assigned with role SAP_SMWORK_DIAG) choose: 1. End-To-End Analysis 2. Your POWL Query or predefined Query (like Java Systems) 3. The relevant System 4. The Button 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 ListcubeIf 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 sessio