- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- SMD on SP15: no data for E2E Workload Analysis are...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
SMD on SP15: no data for E2E Workload Analysis are shown
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 04-14-2008 4:19 PM
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
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Thom Heinemann,
I am also facing the same issue. Workload analysis and other extractor based applications in diagnostics are not displaying any data.
Could you pls share your experience regarding issue. It will b helpful
regards
Naveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Please check the functioning of RFC (TCP/IP)
MDX PARSER.
Hope this helps you.
Feel free to revert back.
--Ragu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Thom.
Even if it looks a stupid advice, check the Solman RFC connections (user/password), because this kind of errors does not appear in the extractor log.
Also, check if RFC is defined in RZ21 for your managed system, if not it means you missed to flag the RFC for Monitoring option in SMSY.
Hope it helps!!
Regards,
Fermín.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
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.
- Capture Your Own Workload Statistics in the ABAP Environment in the Cloud in Technology Blogs by SAP
- Sneak Peek in to SAP Analytics Cloud release for Q2 2024 in Technology Blogs by SAP
- Value Unlocked! How customers benefit from SAP HANA Cloud in Technology Blogs by SAP
- Workload Analysis for HANA Platform Series - 3. Identify the Memory Consumption in Technology Blogs by SAP
- Installation of Sales cube (0SD_C03) in BW 7.5 version in Technology Blogs by Members
| User | Count |
|---|---|
| 98 | |
| 11 | |
| 11 | |
| 10 | |
| 10 | |
| 8 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.