E2E Workload Analysis for BI

Hi All,
Currently we are searching for BI - IP workload analysis tools. I come to know that SolMan Diagnostic tool E2E Workload Analysis for BI useful somewhat to measure the work load. Kindly anybody can tell me
1. Is this tool works for JAVA environment or not
2. How it is useful for BI-IP workload analysis
3. Is there any tools like SolMan diagnostic tool.
4. If we install this tool in SolMan what is the impact.
Thxs,
KVA

This is what I get from Application log (slg1) when I try to drill down on system BIJ (java system) and the page under Workload Analysis do not display (WA-Overview) is ok:
SELECT { [Measures].[0SMD_AVG], [Measures].[0SMD_MAX], [Measures].[0SMD_EXS
] } ON 0, NON EMPTY [0SMD_METY].MEMBERS ON 1 FROM [0SMD_MPEH/0SMD_MPEH_WA_Q
0008_H] SAP VARIABLES [0SMD_V_SID] INCLUDING "BIJ_2" [0SMD_V_TIHMFROM] INCL
UDING >= "201008270000" [0SMD_V_TIHMTO] INCLUDING <= "201008272359" [0SMD_V
INFOPR] INCLUDING "0SMDPERH" [0SMD_V_INFOPR] INCLUDING "0SMD_PE2H" [0SMD_
V_MTYPEM] INCLUDING "IVIEWS" [0SMD_V_MTYPEM] INCLUDING "BI RUNTIME SERVICE"
Value "BIJ_2" for variable "E2E SID Variable" is invalid
Type:E, Id:BRAIN, Number:643, System:SMDCLNT001
I applied the note Note 1301656  even if we are already sp23.  I also regenerated the query 0SMD* in bi client.
What does Value "BIJ_2" for variable "E2E SID Variable" is invalid mean and how to correct this?

Similar Messages

  • After BI 4.1 configuration in SOLMAN - error message "The systems you selected do not contain any software components currently supported by E2E Workload Analysis"

    Hi All,
    I'm trying configure E2E monitoring. I configured all necessary steps, I can see my BI 4.1 system in SLD, also in SOLMAN, all “lights” are green. But if I start Root Cause Analysis>> Ent-to End Analysis>> My system>> Workload Analysis, I see this error "The systems you selected do not contain any software components currently supported by E2E Workload Analysis".

    It would be better if you can raise the question at Remote Supportability and Monitoring Tools
    and or comment in the blog post How to generate and consume an E2E trace with BI4.x (for non-SolMan landscapes)
    created by Toby Johnston
    Do go through the note 1871260 - The systems you selected do not contain any software
    components currently supported by E2E Workload analysis for SAP HANA
    Hope they help.

  • SMD on SP15: no data for E2E Workload Analysis are shown

    Hello!
    I have successfully run Setup Wizard for the satellite solution "EP Portal on 6.40".
    Unfortunately no data for E2E Workload Analysis are shown since more than one month.
    I use SAP Solution Manager with SP 15, BI CONT 9
    I have implemented the following SAP notes:
    1088163, 1107804, 110782, 1119766
    The jobs E2E_EXTRACTOR_CONTROLLER are running without errors.
    Enclosed one of those for portal solution:
    09.04.2008 E2E: Extractor Controller 1
    EC: 09.04.2008 13:05:52 UTC Extractor Controller started for SID B11
    EC: 09.04.2008 15:05:52 CET Installation Number 0020198811
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component
    EC: 13:05:52 UTC Calling ME.
    EC: Read Destination SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:05:52 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 13:05:52 UTC Receiving return code 0 from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 13:05:54 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence: 0
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor /SDF/APPLOG_EXTRACTOR
    EC: Extractorclass
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: 13:05:54 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
    ME: 13:05:54 UTC Calling Extractor /SDF/APPLOG_EXTRACTOR ,
    Extractor Class:
    ME: 13:05:54 UTC Receiving return code 98 from
    /SDF/APPLOG_EXTRACTOR
    ME: Error:
    ME: Error - No RFC Destination maintained for remote execution.
    EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor /SDF/DUMP_EXTRACTOR
    EC: Extractorclass
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: 13:05:54 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
    09.04.2008 E2E: Extractor Controller 2
    ME: 13:05:54 UTC Calling Extractor /SDF/DUMP_EXTRACTOR ,
    Extractor Class:
    ME: 13:05:54 UTC Receiving return code 98 from
    /SDF/DUMP_EXTRACTOR
    ME: Error:
    ME: Error - No RFC Destination maintained for remote execution.
    EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor /SDF/SYSLOG_EXTRACTOR
    EC: Extractorclass
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: 13:05:54 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
    ME: 13:05:54 UTC Calling Extractor /SDF/SYSLOG_EXTRACTOR ,
    Extractor Class:
    ME: 13:05:54 UTC Receiving return code 98 from
    /SDF/SYSLOG_EXTRACTOR
    ME: Error:
    ME: Error - No RFC Destination maintained for remote execution.
    EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor /SDF/UPDATE_EXTRACTOR
    EC: Extractorclass
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: 13:05:54 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
    ME: 13:05:54 UTC Calling Extractor /SDF/UPDATE_EXTRACTOR ,
    Extractor Class:
    ME: 13:05:54 UTC Receiving return code 98 from
    /SDF/UPDATE_EXTRACTOR
    ME: Error:
    ME: Error - No RFC Destination maintained for remote execution.
    EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: 13:05:54 UTC Calling ME.
    EC: Read Destination SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    09.04.2008 E2E: Extractor Controller 3
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:05:54 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 13:05:55 UTC Receiving return code 0 from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 13:05:55 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence: 0
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eEAExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200006685
    EC: 13:05:56 UTC Calling ME.
    EC: Read Destination SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
    ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eEAExtractor
    ME: 13:05:56 UTC Receiving return code 6 from
    E2E_JAVA_EXTRACTOR_IF
    ME: Error:
    DATA_RETRIEVAL_EXCEPTION
    EC: 13:05:56 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200006685
    EC: 13:05:56 UTC Calling ME.
    EC: Read Destination SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 13:05:57 UTC Receiving return code 0 from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 13:05:57 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence: 0
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR
    09.04.2008 E2E: Extractor Controller 4
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: 13:05:58 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 08.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type b) detected: From 08.04.2008 12 h to 09.04.2008 11 h
    RR: Interval (Type c) detected: From 08.04.2008 12 h to 09.04.2008 12 h
    ME: 13:05:58 UTC Calling Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR ,
    Extractor Class:
    ME: 13:05:58 UTC Receiving return code 98 from
    /SDF/IDOC_THROUGHPUT_EXTRACTOR
    ME: Error:
    ME: Error - No RFC Destination maintained for remote execution.
    EC: 13:05:58 UTC Main Extractor raises exception. No Data returned by extractor.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_CA_CS_EXTRACTOR
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: No action - TSL parameter detected.
    EC: This extractor is not allowed to run outside time frame:
    EC: From 03 h to 05 h CET
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F60_XI_E2E_PROXY_STATS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: 13:05:58 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:05:58 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
    ME: No Data Found.
    ME: 13:06:00 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F90_CA_C_TRANSPORTS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:01 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:01 UTC Calling Extractor F90_CA_C_TRANSPORTS
    09.04.2008 E2E: Extractor Controller 5
    ME: No Data Found.
    ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F90_CA_NOTES
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:01 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:01 UTC Calling Extractor F90_CA_NOTES
    ME: No Data Found.
    ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F90_CA_W_TRANSPORTS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 1
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:01 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:01 UTC Calling Extractor F90_CA_W_TRANSPORTS
    ME: No Data Found.
    ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_CA_CS_EXTRACTOR
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: No action - TSL parameter detected.
    EC: This extractor is not allowed to run outside time frame:
    EC: From 03 h to 05 h CET
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: 13:06:01 UTC Calling ME.
    EC: Read Destination SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:01 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
    09.04.2008 E2E: Extractor Controller 6
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 13:06:02 UTC Receiving return code 0 from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 13:06:02 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence: 0
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F55_XI_IDOC_ADAPTER
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: 13:06:02 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:02 UTC Calling Extractor F55_XI_IDOC_ADAPTER
    ME: No Data Found.
    ME: 13:06:02 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F60_XI_E2E_PROXY_STATS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component
    EC: 13:06:03 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:03 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
    ME: No Data Found.
    ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Invalidating MDX Cache.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F90_CA_C_TRANSPORTS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:03 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:03 UTC Calling Extractor F90_CA_C_TRANSPORTS
    ME: No Data Found.
    ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_ST_API
    09.04.2008 E2E: Extractor Controller 7
    EC: Extractor F90_CA_NOTES
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:03 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:03 UTC Calling Extractor F90_CA_NOTES
    ME: No Data Found.
    ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_ST_API
    EC: Extractor F90_CA_W_TRANSPORTS
    EC: Extractorclass
    EC: Product 01200314690900000192
    EC: Main Instance (1) 9
    EC: Main Instance (2) 01200314690800000134
    EC: Component 01200615320200005507
    EC: 13:06:03 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_ST_API Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:03 UTC Calling Extractor F90_CA_W_TRANSPORTS
    ME: No Data Found.
    ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
    EC: Main Extractor E2E_ME_RFC
    EC: Extractor E2E_SSR_EXTRACTOR_IF
    EC: Extractorclass
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component 01200615320200005507
    EC: Local Execution of Extractor.
    EC: ME called in Multi-Mode.
    EC: 13:06:03 UTC Calling ME.
    EC: Read Destination
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
    RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
    ME: 13:06:03 UTC Calling Extractor E2E_SSR_EXTRACTOR_IF ,
    Extractor Class:
    E2E_SSR_EXTRACTOR_0CCMSATPH
    ME: 13:06:06 UTC Receiving return code 0 from
    E2E_SSR_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 13:06:06 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence: 0
    EC: Invalidating MDX Cache.
    Any helpful information will be appreciated
    regards
    Thom

    Same problem being observed in our Solman system (SP15). Below are the errors observed in the spool output of E2E framework jobs,
    1] ME: Data Loader Error occurred.
       EC: 21:05:44 UTC Main Extractor raises exception. No Data returned by extractor.
    2] No action - TSL parameter detected.
       This extractor is not allowed to run outside time frame
    3] ME: 21:05:45 UTC Receiving return code    98   from
       /SDF/UPDATE_EXTRACTOR
       ME: Error:
       ME: Error - No RFC Destination maintained for remote execution.
       EC: 21:05:45 UTC Main Extractor raises exception. No Data returned by extractor.
    4] ME: Error:
       DATA_RETRIEVAL_EXCEPTION
       EC: 21:05:46 UTC Main Extractor raises exception. No Data returned by extractor.
    Tried referring E2E workload analysis guide...no use..the issues have not been covered in that.

  • E2E Workload analysis-Conditions tab

    Hello,
    While cheking the E2E workload analysis, I could see three expandable (drill down) tabs in the workload analysis section. 1. Conditions 2. Navigation 3.Metric Data Display. Here I am not abe to understand the functionality of 'Conditions'.  Could you please tell me the use of this and how we can use this?
    Regards,
    Rajeev

    duplicate post

  • SMD: no data for E2E Workload Analysis are shown

    Hello,
    I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
    The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
    Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
    The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
    16.04.2008                  E2E: Extractor Controller                          1
    EC: 16.04.2008 14:05:11 UTC    Extractor Controller started for SID  E11
    EC: 16.04.2008 16:05:11 CET    Installation Number                   0020198811
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component
    EC: 14:05:11 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:11 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:12 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eEAExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component           01200615320200006685
    EC: 14:05:14 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  16.04.2008 01 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:14 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eEAExtractor
    ME: 14:05:16 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component           01200615320200006685
    EC: 14:05:16 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    16.04.2008                  E2E: Extractor Controller                          2
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:16 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:18 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_CA_CS_EXTRACTOR
    EC: Extractorclass
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: No action - TSL parameter detected.
    EC: This extractor is not allowed to run outside time frame:
    EC: From  03 h to  05 h  CET
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eEAExtractor
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: 14:05:18 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  16.04.2008 01 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:18 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eEAExtractor
    ME: 14:05:20 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: 14:05:20 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:20 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    16.04.2008                  E2E: Extractor Controller                          3
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:21 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    Can some one help to solve this problem.
    Thank you very much
    regards
    Thom

    Hello,
    I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
    The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
    Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
    The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
    16.04.2008                  E2E: Extractor Controller                          1
    EC: 16.04.2008 14:05:11 UTC    Extractor Controller started for SID  E11
    EC: 16.04.2008 16:05:11 CET    Installation Number                   0020198811
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component
    EC: 14:05:11 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:11 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:12 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eEAExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component           01200615320200006685
    EC: 14:05:14 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  16.04.2008 01 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:14 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eEAExtractor
    ME: 14:05:16 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product
    EC: Main Instance (1)
    EC: Main Instance (2)
    EC: Component           01200615320200006685
    EC: 14:05:16 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    16.04.2008                  E2E: Extractor Controller                          2
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:16 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:18 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_CA_CS_EXTRACTOR
    EC: Extractorclass
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: No action - TSL parameter detected.
    EC: This extractor is not allowed to run outside time frame:
    EC: From  03 h to  05 h  CET
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eEAExtractor
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: 14:05:18 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  16.04.2008 01 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:18 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    com.sap.sup.admin.bwextract.E2eEAExtractor
    ME: 14:05:20 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    EC: Main Extractor      E2E_ME_RFC
    EC: Extractor           E2E_JAVA_EXTRACTOR_IF
    EC: Extractorclass
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    EC: Product             01200314690900000192
    EC: Main Instance (1)   7
    EC: Main Instance (2)   01200314690800000134
    EC: Component
    EC: 14:05:20 UTC Calling ME.
    EC: Read Destination  SOLMANDIAG
    ME: E2E_ME_RFC Main Extractor Run started.
    RR: Calculating Required Records.
    RR: Scanned Interval:            From  09.04.2008 13 h to  16.04.2008 13 h
    RR: Interval (Type e) detected:  From  16.04.2008 13 h to  16.04.2008 13 h
    ME: 14:05:20 UTC Calling Extractor  E2E_JAVA_EXTRACTOR_IF          ,
    Extractor Class:
    16.04.2008                  E2E: Extractor Controller                          3
    com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
    ME: 14:05:21 UTC Receiving return code     0   from
    E2E_JAVA_EXTRACTOR_IF
    ME: No Data returned by Extractor with no Error detected.
    ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
    ME: Number of records written to persistence:           0
    EC: Invalidating MDX Cache.
    Can some one help to solve this problem.
    Thank you very much
    regards
    Thom

  • SMD on SP15: no data for E2E Workload Analysis is visible

    Hello,
    I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 4) and would set up the SMD functionality for SAP EP 6.40 SP19.
    The Set up Wizards runs without any errors but I could see the data in  the tabs (E2E Workload, E2E Change Analysis)
    The E2E_EXTRACTOR_CONTROLLER job runs without errors.
    Which actions should be done to solve the problem?
    Thank you!
    regards
    Thom

    Tom,
    Make sure that when you ran SMD setup wizard, job CCMSBISETUP completed successfully. Check this in SM37.
    Check ABAP runtime errors in ST22.
    If you are getting RAISE_EXCEPTION error, apply note 1119766.
    Make sure that MultiProvider 0SMD_MPIH is activated. In BI client run  transaction RSA1, Modeling, InfoProvider- check if 0SMD_MPIH is active.
    If above doesn’t solve the issue, try to do Manual activation of BI Content for E2E Diagnostics.  (note 1110013)
    Hope this helps.
    Thanks,
    Labinot

  • No data in Workload Analysis overview in E2E Analysis for TREX

    Hi,
    I'm not getting any data in E2e Workload analysis Overview screen for TREX system. Data is available in all other screens and extractors are running fine. I'm using Solution Manager 7.1 SP10. Kindly help me.
    Regards,
    Pragadees

    Hi Pragadeesh,
    Your system landscape definition in SMSY seems to be wrong. The products selected at the Setup Wizard for the managed system must exist in SMSY in order to run the extractos correctly.
    Please refer to the Root Cause Analysis Landscape Guide available
    at http://service.sap.com/diagnostics -> media library for additional information.
    1) Upgrade CIM model according to note 669669.
    2) Download the latest version of note 1468591 and apply it using SNOTE
    3) Check note 1259109, download the latest configuration file and apply it
    Additionally, it is highly recommended to patch your LM-SERVICE SP09
    with the latest patch (1) according to note 1599627.
    Thanks
    Vikram

  • End-to-End Workload Analysis: Architecture

    Hi there,
    I have read in training material about E2E Workload Analysis (from SAP) the following statement:
    "On ABAP-based components, the workload related data is extracted from statistical files and is written in BI"
    The picture in the training material shows, that e.g. Java and .Net needs a Diagnostics Agent. But for ABAP-based components only a RFC Interface is necessary.
    Is it possible to use the E2E Workload Analysis without installing any Agent on the ABAP-System?
    And are there any jobs which must be scheduled on the ABAP-System alternatively on the Solution Manager?
    If I start the Workload Analysis and chose a ABAP-System, there are no statistical data.
    Thanks for your reply!
    Best regards,
    Andreas

    Hi there,
    The ABAP systems connect using RFC, but it is just one of the required connections that are maintained among satellite and managing system. (this is actually established in the managed system configuration, step 1).
    The actual data is collected by SMD Agent, that pools several other services in the sattelite system itself, such as SAPOSCOL and SAP CCMS.
    There's a PDF attached to SAP note 1332428 called TroubleShootingGuideEhP1.pdf, go to page 4. The picture in this page is  great to show how everything works. There you can see all the connections.
    The answer to your question is no, unfortunately. Make sure you follow the "Managed System Configuration" in the solman_setup, this will ensure you have everything that is needed for workload analysis, including SMD Agent.
    Please refer to note 1435043 to address what is needed for Workload Analsysis. Managed system configuration fits in item 5 of this note.
    I hope this is helpful for you.
    Best regards,
    Guilherme Balbinot

  • SMD E2E: Configuration Analysis

    Hi!
    I can already see the data for E2E Workload Analysis.
    Unfortunately I cannot see the data under the tab "E2E Configuration".
    Can some one tel me how to proceed with with errors/warnings?
    No SID found for value 'E11 0020198811012003146909000001927' of characteristic 0SMD_FSRC
    Invalid filter on 0SMD_FSRC: Filter changed
    Characteristic 0SMD_CSAL was changed in InfoCube 0SMD_CA01. Adjust the query
    What I have already done
    tcode RSRT --> Gen. query directly --> "0SMD*"
    tcode CCMSBISETUP --> Sceanrio "E2E"
    Any helpful information will be appreciated
    regards
    Thom

    Hi,
    I'm trying to setup E2E. Diagnostics server (BI client in solman) & Managed system setup was done.
    I don't see any graphs(at least plain) in solman. I observed that extractor jobs are failing, also i dont see any info objects under solman diagnostics in TC - RSA1.
    Please guide.
    Thanks in advance.

  • WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection

    Hi all SDNers,
    Help is needed on error "WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection".
    This error occured on RCA -> Extractor FWK administration and go to managed system (PI) and from the log, i can see some extraction failed due to error message " Error when opening an RFC connection"
    consequently, JAVA performance data is not appearing in RCA -> workload analysis but work fine for ABAP and adapter engine.
    I've followed below notes and perform the troubleshooting step by step by still to no avail:
    Note 1332428 - Missing data in service sessions from BI/CCDB
    Note 1257308 - FAQ: Using EarlyWatch Alert
    Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP27
    Note 1265070 - Diagnostics - Setup of Managed Systems
    Note 1010428 - End-to-End Diagnostics
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/WorkloadAnalysis-Noapplicabledatafound
    steps that have performed:
    restarted agent
    enlarge RFC resource cap for solmandiag and none
    delete entire SID in SMSY and pull again from SLD, re-setup managed system
    restart PI system
    i've spent 2 days on troubleshooting this issue but lack of information in SMP and SDN, even in google.
    in table E2E_EFWK_STATUS and extractor E2E_JAVA_EXTRACTOR_IF, i see all WLI_ID ended with RC 96, MESSAGE = Error when  opening an RFC connection and LASTRECORDS = 0
    I strongly believe this is the issue that causing no applicable data found for JAVA data.
    fyi, we are on SOLMAN EHP1 SPS27.
    Any kind advise is most welcome.
    Thanks,
    Nicholas Chang

    Gosh! at last i found the solution!!
    I appreciate those who tried to help and i''m sharing the solution as i believe this is the purpose of SDN Forum and help others Netweaver Chap who facing the same problem:
    Problem faced:
    Extractor failed intermittently for WORKLOAD ANALYSIS (Introscope Data) due to error message "Error when opening an RFC connection"
    Due to the above error, performance data is not available in RCA workload analysis for J2EE engine.
    Possible Solution:
    1) Ensure both webadmin & SOLMANDIAG RFC working fine -> SM59 -> TCP/IP
    2) go to SE16 -> E2E_RESOURCES and change the resourcecap to 10 for SOLMANDIAG
    3) go to /smd/services -> Diagnostic System -> Advanced Setup -> Abap connectivity -> Connection Configuration and change server count to 10
    4) Restart webadmin (step 3 & 4 can perform in VA too)
    5) set gw/keepalive &  gw/reg_keepalive to value 0 in RZ11 (without reboot of instance)
    5) again go to SM59 -> TCP/IP -> SOLMANDIAG and put in the gateway host and gateway service correctly, don't leave this empty!!!! -
    > This is the main solution to solve intermittent failed RFC for extractor.
    Now, go back and monitor the extractor log and you should see no RFC error anymore and wait for 1 hour for the data to populate.
    Thanks!
    Nicholas Chang,

  • No data in RunSAP workload analysis

    Hi Experts,
    I've installed solution manager 7.0 EHP1 and configured to execute End-to-End Analysis.
    And I can use Wily Introscope Workstation to display realtime data and history data.
    But in solution manager workcenter, I can't get any data from workload analysis.
    I've used t-code CCMSBISETUP to setup BI and everything looks fine.
    What other things should I check?
    Thanks!

    Hello,
    Please make sure that your system fulfills all the pre-requisites. The following note will point you to the right one depending on the release level of your system:
        1274287 End-to-End Diagnostics
    Make sure your systems are well defined, as of EHP1 is mandatory the use of SLD. Please check the following document:
       http://service.sap.com/diagnostics
         Media Library...
             SAP Solution Manager Landscape Setup Guide
    Further information can be found ate SAP Note 1435043.
       1435043 E2E Workload Analysis - No applicable data found
    Regards,
    Allam Drebes

  • Workload Analysis tab is missing  in E2E Anaysis

    Hi Guru,
    I am in process of generating EWA reports for portal ,below are the steps I have completed successfully.
    1. SMD agent installation on portal.
    2. Defined portal system in SMSY.
    3. completed SOLMAN_SETUP.
    4. Completed Setup Wizard for managed system.
    5. Deploy IS agent via SDM in Solman.
    6. Introscope agent setup done for managed system
    7. Managed system data is visible in IS Enterprise Manager.
    When I checked t code solman_workcenter->RCAtab-> E2E Anaysis->selected  the portal system i cant find Workload Analysis tab i.e Workload Analysis tab is missing could you please help me to resolve this issue.
    System Configuratoi: SAP EHP 1 for SAP Solution Manager 7.0 and portal is netweaver 7.0
    Thanks
    Abullais

    Hi,
    Kindly check security guide for RCA authorization,
    https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718044&_SCENARIO=01100035870000000202
    It may be due to authorization issue.
    Regards,
    Karthik

  • What is the table name for Workload analysis?

    Hi All TechGurus,
    We need to create an ABAP program in which it displays some information of Transaction (STO3n), Report for the same (SAPWL_ST03N)
    We want  to create an ABAP program to get the output in excel format?
    What is the table name for Workload analysis?
    Many thanks in advance!!

    Hi  Keshav,
    Thank you for your reply.
    As per my requirement, i want to create an ABAP program in which it displays some information of Transaction (STO3n) and want to send the output in excel format. however I don't understand how to start with it.
    Below are the conditions -
    1. display data for today's date
    2 .In transaction profile,  task should be Dialogue.
    from where should i fetch data which is getting displyed after executing t.code ST03n?
    Please help me with your suggessions...
    Thanks

  • E2E Change Analysis

    I am unable to see E2E change analysis tab in SMD. I can see E2E exeption,trace and workload analysis but not Change analysis....Can anyone of you please let me know if i need to do any configuration for this....
    REWARD POINTS FOR ALL USEFUL ANSWERS...
    Thanks,
    Ajay Kande

    Thnx  a lot Frederic.
    Can you tell me regarding the following error:
    type com.sap.sup.admin.e2e.trace.wd.model.types.Syuzeit could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
    I am getting this error when i try to execute E2E Trace Analysis....

  • Diagnostics Workload Analysis - Java Memory Usage gives BI query input

    Dears
    I have set up diagnostics (aka root cause analysis) at a customer side and I'm bumping into the problem that on the Java Memory Usage tab in Workload analyis the BI query input overview is given
    Sol Man 7.0 EHP1 SPS20 (ST component SP19)
    Wily Introscope 8.2.3.5
    Introscope Agent 8.2.3.5
    Diagnostics Agent 7.20
    When I click on the check button there I get the following:
    Value "JAVA MEMORY USAGE" for variable "E2E Metric Type Variable" is invalid
    I already checked multiple SAP Notes like the implementation of the latest EWA EA WA xml file for the Sol Man stack version.
    I already reactivated BI content using report CCMS_BI_SETUP_E2E and it gave no errors.
    The content is getting filled in Wily Introscope, extractors on Solution Manager are running and capturing records (>0).
    Did anyone come accross this issue already?
    ERROR MESSAGE:
    Diagnosis
    Characteristic value "JAVA MEMORY USAGE" is not valid for variable E2E Metric Type Variable.
    Procedure
    Enter a valid value for the characteristic. The value help, for example, provides you with suggestions. If no information is available here, then perhaps no characteristic values exist for the characteristic.
    If the variable for 0DATE or 0CALDAY has been created and is being used as a key date for a hierarchy, check whether the hierarchies used are valid for this characteristic. The same is valid for variables that refer to the hierarchy version.
      Notification Number BRAIN 643 
    Kind regards
    Tom
    Edited by: Tom Cenens on Mar 10, 2011 2:30 PM

    Hello Paul
    I checked the guide earlier on today. I also asked someone with more BI knowledge to take a look with me but it seems the root cause analysis data fetching isn't really the same as what is normally done in BI with BI cubes so it's hard to determine why the data fetch is not working properly.
    The extractors are running fine, I couldn't find any more errors in the diagnostics agent log files (in debug mode) and I don't find other errors for the SAP system.
    I tried reactivating the BI content but it seems to be fine (no errors). I reran the managed system setup which also works.
    One of the problems I did notice is the fact that the managed SAP systems are half virtualized. They aren't completely virtualized (no seperate ip address) but they are using virtual hostnames which also causes issues with Root Cause Analysis as I cannot install only one agent because I cannot assign it to the managed systems and when I install one agent per SAP system I have the message that there are already agents reporting to the Enterprise Manager residing on the same host. I don't know if this could influence the data extractor. I doubt it because in Wily the data is being fetched fine.
    The only thing that it not working at the moment is the workload analysis - java memory analysis tab. It holds the Key Performance Indicators for the J2EE engine (garbage collection %). I can see them in Wily Introscope where they are available and fine.
    When I looked at the infocubes together with a BI team member, it seemed the infocube for daily stats on performance was getting filled properly (through RSA1) but the infocube for hourly stats wasn't getting filled properly. This is also visible in the workload analysis, data from yesterday displays fine in workload analysis overview for example but data from an hour ago doesn't.
    I do have to state the Solution Manager doesn't match the prerequisites (post processing notes are not present after SP-stack update, SLD content is not up to date) but I could not push through those changes within a short timeframe as the Solution Manager is also used for other scenarios and it would be too disruptive at this moment.
    If I can't fix it I will have to explain to the customer why some parts are not working and request them to handle the missing items so the prerequisites are met.
    One of the notes I found described a similar issue and noted it could be caused due to an old XML file structure so I updated the XML file to the latest version.
    The SAPOscol also throwed errors in the beginning strange enough. I had the Host Agent installed and updated and the SAPOscol service was running properly through the Host Agent as a service. The diagnostics agent tries to start SAPOscol in /usr/sap/<SID>/SMDA<instance number>/exe which does not hold the SAPOscol executable. I suppose it's a bug from SAP? After copying the SAPOscol from the Host Agent to the location of the SMD Agent the error disappeared. Instead the agent tries to start SAPOscol but then notices SAPOscol is already running and writes in the log that SAPOscol is already running properly and a startup is not neccesary.
    To me it comes down the point where I have little faith in the scenario if the Solution Manager and the managed SAP systems are not maintained and up to date 100%. I could open a customer message but the first advice will be to patch the Solution Manager and meet the prerequisites.
    Another pain point is the fact that if the managed SAP systems are not 100% correct in transaction SMSY it also causes heaps of issues. Changing the SAP system there isn't a fast operation as it can be included in numerous logical components, projects, scenario's (CHARM) and it causes disruption to daily work.
    All in all I have mixed feelings about the implementation, I want to deliver a fully working scenario but it's near impossible due to the fact that the prerequisites are not met. I hope the customer will still be happy with what is delivered.
    I sure do hope some of these issues are handled in Solution Manager 7.1. I will certainly mail my concerns to the development team and hope they can handle some or all of them.
    Kind regards
    Tom

Maybe you are looking for

  • Can a friend and I share one license for Photoshop Elements 12 on separate computers?

    A friend and I want to pitch-in to get a license for Elements, but we'd like to see if we can each use it on our respective computers before we decide to buy. Also, if I decide that I want my license to change from my laptop (which will use the softw

  • Speakers not working correctly

    I have a hp laptop, under a year old, my speakers only work when i have my earphones plugged  in.  But I can sometimes click on the speaker icon and I will get sound for a second or two and then shuts off again.

  • Tolerance for Tax Amount difference

    Dear All, In certain cases the tax amount given in the invoice is different from the tax calculated by the system. Please help me, where to make the configuration so as to accept a difference of 0.05 INR between the calculated tax amount and the tax

  • Insert script

    I have a table called table1 Table1 INTID MonthNo Month Year QuarterName ID TRANS_GRP Email 1 11 November 2014 Q4 11111 1742 [email protected] 2 12 December 2013 Q4 22222 1772 [email protected] 3 12 December 2014 Q3 33333 1472 [email protected] I wou

  • Deletion of Order(Suborder,WIP order) and notification number

    Hi, Is there any function module or BAPI to delete the WIP Order (IW32) and Suborder(IW36) and Notifcation number(IW22). Please let me know!!!! Thanks for ur time, Sowmmya.B