Time based chunks error - WORKLOAD ANALYSIS (INTROSCOPE DATA)

Hi All,
I'm getting time based chunks error for WORKLOAD ANALYSIS (INTROSCOPE DATA) extractor repeatedly. None of the extractor run is successful. I'm using Solution Manager 7.1 SP10.
Any kind advise is most welcome.
Regards,
Pragadees

Hi Pragadees,
the string "... time based chuncks ..." indicates that you have a backlog which is processed by the EFWK currently. Normal process is indeed to improve the resource capacity of SolMan (as Roland suggested) or at the managed system.
Please have a look at the link below for further explanation.
EFWK_TROUBLESHOOTING - Technical Operations - SCN Wiki
Best regards, Alexander

Similar Messages

  • 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,

  • TDMS time based reduction method has no end date

    Hello TDMS experts,
    I am in the process of configuring the 'Time based reduction' method of TDMS. In the package, I am in phase "System Analysis"->"Analyze and specify'from date'".
    Here it gives me the option to specify the start/from date only. If I want to transfer data for only  a month in the past lets say april of 2007, then how can I specify the from and to dates.
    Please advise.
    Thank you,
    kind regards,
    Zaheer Shaikh

    Hi Pankaj,
    Thanks for the reply.
    In the phase "maintain Table Reduction" I have chosen SAP standard reduction, that means the table reduction is handled by SAP itself. Since my sender system database is 4 Terabytes, my question is if I select the 'from date' as 10th April 2009 (present date is 20 April 2009), will the TDMS still copy the whole tables for which I have not manually defined any reduction?
    Please advice.
    Thank you,
    Kind regards,
    Zaheer Shaikh

  • 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.

  • Wrong date format when creating a universe based on a MS Analysis cube

    Hi,
    When creating a universe based on a MS Analysis 2008 cube the date objects from the cube are created in the universe with CHAR format when it should be DATE format
    I have tried to resolve the issue by modifying the date object in the universe with MDX but with little success.
    I wonder if it is an error in the cube and that it actually should be possible to get the correct date format from the cube when creating the universe automatically in the universe design tool.
    The date object is organised in a hierarchy.
    Any ideas? - both to resolve the issue by using MDX in the universe object properties or in the cube.
    The universe design tool is version 4.0 SP2 patch 5
    /Kim

    Oh I knew I was missing something. Ok version 2.
    I think in general this approach would work. I assumed you are starting from 1 and resetting to 1.
    There should be error handling and so forth that is not here. Probably some details need to be tweaked.
    So the key thing here AFAIK is to put the sequence reset in an autonomous procedure. Exactly how to do that may need to be modified.
    PS this version has a bug. After the reset needs to change the increment of the sequence back to 1.
    and I left that out. oops!
    /* testtrigger */
    /* previously:
    create table mytable (
    myprimary_key number(10) primary key,
    column1 number(2)
    create sequence mysequence
    start with 1
    increment by 1
    maxvalue 99
    nocache;
    create table mylastdate (lastdate date);
    insert into mylastdate(lastdate) values (trunc(sysdate));
    create or replace procedure reset_mysequence (in_correction number) is
    pragma autonomous_transaction;
    begin
    execute immediate 'alter sequence mysequence INCREMENT BY ' || in_correction || ' MINVALUE 1';
    update mylastdate set lastdate = trunc(sysdate);
    commit;
    end;
    show errors;
    create or replace trigger mytrigger
    before insert on mytable for each row
    declare
    tmpdate number(8) := null;
    lastdate_used number(8) := null;
    correction number := null;
    lastseq number(2) := null;
    begin
    if INSERTING then
    tmpdate := to_number(to_char(sysdate,'YYYYMMDD'));
    select to_number(to_char(lastdate,'YYYYMMDD')) into lastdate_used
    from mylastdate;
    select mysequence.currval into lastseq from dual;
    /* when this displays in the forum it shows lt gt as nothing on the screen
    so this should be lastdate not equal to tmpdate */
    if lastdate_used <> tmpdate and lastseq > 1 then
    correction := -(lastseq - 1);
    reset_mysequence(correction);
    end if;
    :new.myprimary_key := (tmpdate * 100) + mysequence.nextval;
    end if;
    end;
    show errors;
    Edited by: lake on Nov 30, 2010 10:39 AM
    Edited by: lake on Nov 30, 2010 10:52 AM

  • 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

  • Error in computing time based on TimeZones on a server

    I have a piece of code that generates timestamps based on US TimeZones such as Pacific, Central and Eastern. I get correct results when I run this code locally (EST) but get results an hour off when I run the same code on a server running in US central time. See the results below and the code that I run.
    Results from running the code on Dev Server:
    ts: 2007-11-05 10:39:03.19 ���� ������� (Default time)
    tsEST: 2007-11-05 10:39:03.019� ������� (EST based on TimeZone String America/New_York, should be 11:39)
    tsCST: 2007-11-05 09:39:03.019� ������� (Central time based on TimeZone String US/Central, should be 10:39)
    tsPST: 2007-11-05 07:39:03.019� ������� (Pacific time based on TimeZone String America/Los_Angeles, should be 8:39)
    Results from running the same code on Local machine:
    tsEST: 2007-11-05 11:39:01.272� (Eastern Time based on TimeZone String America/New_York)
    tsCST: 2007-11-05 10:39:01.272� (Central time based on TimeZone String US/Central)
    tsPST: 2007-11-05 08:39:01.272� (Pacific time based on TimeZone String America/Los_Angeles)
    Below is the code that I ran.
         Timestamp ts = new Timestamp(Calendar.getInstance().getTime().getTime());
    DateFormat df1 = new SimpleDateFormat( "yyyy-MM-dd HH:mm:ss.SS" );
    GregorianCalendar cal1 = new GregorianCalendar();
    Timestamp tsNow = new Timestamp(cal1.getTimeInMillis());
    TimeZone tsEST = TimeZone.getTimeZone("America/New_York");
    String inPattern = "yyyy-MM-dd HH:mm:ss.SS";
    DateFormat df = new SimpleDateFormat(inPattern);
    df.setTimeZone(tsEST);
    Date date = df.parse(tsNow.toString());
    df.setTimeZone(tsEST);
    ts = new Timestamp( df1.parse( df.format(date) ).getTime() );
    System.out.println("tsEST: " + ts.toString());
    DateFormat df2 = new SimpleDateFormat(inPattern);
    TimeZone tsCST = TimeZone.getTimeZone("US/Central");
    df2.setTimeZone(tsCST);
    ts = new Timestamp( df1.parse( df2.format(date) ).getTime() );
    System.out.println("tsCST: " + ts.toString());
    TimeZone tsPST = TimeZone.getTimeZone("America/Los_Angeles");
    df.setTimeZone(tsPST);
    ts = new Timestamp( df1.parse( df.format(date) ).getTime() );
    System.out.println("tsPST: " + ts.toString());

    Actually, I did try a complete removal and re-install with the same results. On the desktop machine on which the Ctime client is working, Ctime was installed on an earlier system version and was working before the upgrade to the current system. The client continued to work. This at least indicates an initial setup problem on 10.2.4 and may indeed relate to the product not yet being ready for the latest system.

  • 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

  • ***URGENT*** Time Based Work Flow ERROR/PROBLEM

    Knowing that the PRE() function doesn't work smoothly with the wait function. We went ahead and added it in the conditions statement and disabled the reeval check box, but the problem is it appears that it is still checking the condition. Anyone have this problem or possible solution?
    Edited by: 783027 on Jul 26, 2010 3:49 PM

    See answer to your previous post.
              Jai wrote:
              > Hi ,, I am trying to use time based delivery of message in WLServer7.0. After going
              > through the various posts I figured this is the snippet required to send time-based
              > messages. But i havent had any luck on it as yet. Can someone please point out
              > where am I going wrong in this or send a snippet of code which does this.
              >
              > here is snippet of code ....
              >
              > /*initialization */
              >
              > qconfactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
              > qcon = qconfactory.createQueueConnection();
              > qsession=qcon.createQueueSession (false,Session.AUTO_ACKNOWLEDGE);
              > queue = (Queue) ctx.lookup (QUEUE);
              > qsender = qsession.createSender(queue);
              > msg = qsession.createTextMessage();
              > qcon.start();
              >
              > /* actual bit which does sending */
              > Date later = new Date();
              > long now = System.currentTimeMillis();
              > GregorianCalendar cal = new GregorianCalendar();
              > cal.getTime().toLocaleString();
              > System.out.println("The current time is: " + cal.getTime().toLocaleString());
              > now += 10*1000; later.setTime(now); cal.setTime(later);
              >
              > msg.setText(message);
              > ((WLMessage)msg).setJMSDeliveryTime(cal.getTime().getTime()); ((weblogic.jms.extensions.WLMessageProducer)
              > qsender).setTimeToDeliver(cal.getTime().getTime());
              > qsender.send(msg);
              >
              > Many Many thanks for your swift response ...
              

  • Error messages when sending date-time stamp to Oracle Database

      I have a complex application that communicates with an Oracle database.  One of the table values that gets written to the table is a date-time stamp.  Until recently, the user only required a date, and this was never an error. (The format String used was %d-%b-%Y)  Now they need a time-stamp as well, so I attempted to edit the format string input of the format date/time string function to include the time. I have tried numerous format strings, each of which returns an error on execution.  Depending on which format I use, I get one of 3 different error messages.  The really odd thing is that both the date and time always get stored in Oracle without any problem (regardless of what date-time I use, as long as I include the date and any part of a time stamp - I get the entire timestamp even if I only include %I for the hour).  The only issue is that LabVIEW generates an ODBC error if I try to include the time to the date-time stamp.  In other words, teh date/time stamp writes to the Oracle database, but an ODBC error occurs every time.  I've included a word doc with screen captures of the format strings used, the resultant date/time stamps written to Oracle and the error messages generated within LabVIEW. Any advice would be most appreciated.
    Attachments:
    Summary of ODBC Error messages related to date-time stamp.doc ‏65 KB

    Oracle has a standard date format: 12-Mar-2009 that it accepts as a string, but if you want more than that, you need to use the todate() function. I used this string going into the standard LabVIEW ''Format date/time sting vi' 
    to_date('%d-%b-%Y %H:%M:%S', 'DD-MON-YYYY HH24:MIS') to create the value needed for Oracle.
    Then I use standard format string to create SQL: insert into mytable (mydate) values(%s) and select * from my table where mydate = %s using the string above for %s.
    I think you can also define a global format for all time strings but I haven't bothered figuring that out.

  • Workload Analysis and Exception Analysys   Overview data n/a

    Hello,
    About Root cause analysis.
    In Workload Analysis and Exception Analysys, the KPI data, in right pane of overview tab,
    is always n/a.
    In the other tab, e.g.  ABAP and Java instance tab, the data is diplayed.
    So I think data could be properly stored in BI.
    Please give me some advice what setup is missing.
    Regards

    SAPNote1032461

  • I got this error while my mac was backing up to time machine: he backup disk image "/Volumes/Data/Sanjeev's iMac.sparsebundle" could not be created (error (null)). Please could someone help

    I got this error while my mac was backing up to time machine: he backup disk image “/Volumes/Data/Sanjeev’s iMac.sparsebundle” could not be created (error (null)). Please could someone help

    Has the backup been working ok??
    If that is the case simply reboot the TC.. or if that fails, reboot the whole network, restarting in correct order..
    modem.. wait 2min
    TC.. wait 2min

  • 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.

  • Hi when I open each application for mac office, the app closes and it pops up the following error: Microsoft Error Reporting log version: 2.0  Error Signature: Exception: EXC_BAD_ACCESS Date/Time: 2014-03-27 14:14:52 +0000 Application Name: Microsoft Exce

    Microsoft Error Reporting log version: 2.0
    Error Signature:
    Exception: EXC_BAD_ACCESS
    Date/Time: 2014-03-27 14:14:52 +0000
    Application Name: Microsoft Excel
    Application Bundle ID: com.microsoft.Excel
    Application Signature: XCEL
    Application Version: 14.1.4.111121
    Crashed Module Name: libTIFF.dylib
    Crashed Module Version: unknown
    Crashed Module Offset: 0x000078ae
    Blame Module Name: MicrosoftComponentPlugin
    Blame Module Version: 14.1.4.111121
    Blame Module Offset: 0x0000d9fc
    Application LCID: 1040
    Extra app info: Reg=en Loc=0x0410
    Crashed thread: 0

    Hi mattiaprodomo,
    If you are having issues with an app that unexpectedly closes on launch, you may find the following article helpful:
    OS X Mavericks: If an app freezes or quits unexpectedly
    http://support.apple.com/kb/PH13975
    Regards,
    - Brenden

  • My Microsoft Office won't work! Here is the error report. Microsoft Error Reporting log version: 2.0  Error Signature: Exception: EXC_BAD_ACCESS Date/Time: 2015-03-04 12:04:03  0000 Application Name: Microsoft Word Application Bundle ID: com.microsoft

    My Microsoft Office won't work after upgrading to the newest OS from Apple! HELP!!!!!!
    Microsoft Error Reporting log version: 2.0
    Error Signature:
    Exception: EXC_BAD_ACCESS
    Date/Time: 2015-03-04 12:04:03 +0000
    Application Name: Microsoft Word
    Application Bundle ID: com.microsoft.Word
    Application Signature: MSWD
    Application Version: 14.4.8.150116
    Crashed Module Name: unknown
    Crashed Module Version: unknown
    Crashed Module Offset: unknown
    Blame Module Name: MSXML
    Blame Module Version: 14.4.8.150116
    Blame Module Offset: 0x00003125
    Application LCID: 1033
    Extra app info: Reg=en Loc=0x0409
    Crashed thread: 0

    If your startup disk says it is full, you need to remove some of your stuff.
    Either move some documents/movies/pictures to an external drive (if you want to keep them), or delete them from your startup drive. Then, empty the Trash.
    If you move them to an external, you will still have to delete them from the internal drive.
    That won't fix Office (I don't think), but it will make everything run better. You need a minimum of 10GB free (more would be better).
    You might need to reinstall Office. It should work without problem (well, at least as little problem as Office can muster).

Maybe you are looking for

  • How do I know if I had gotten hacked?

    I got home and discovered that my OS X 10.2.8 servers (webserver and fileserver) powered OFF. I had left them on when I left the house. These servers are behind multiple firewalls: a Netgear router that lets inbound only on ports 22 and 80 and forwar

  • VOFM Condition base value not updating(Urgent)

    Hi All, I have created a Condition Base Value 901 for Sales Order in Transaction VOFM. Following is the code when I enter the Sorce text. FORM FRM_KOND_BASIS_901. *{   INSERT         DEVK901384                                        1 DATA: XXKOMV TY

  • Migrating Webview Reports to CUIC

    Hello, Everyone is running around with this problem since cisco stops the webview , the CUIC is a great reporting solution but the only thing CUIC  is weak with is the stock reports , not only they don't include all the  reports mostly needed but the

  • I changed computers and I get an error code 131:4     I need to know what to do to get access to my CS4.

    I just transferred my Adobe CS4 from a macbook pro to an imac and I can't fire up any of the programs.  I get an error code  131:4   Does anyone know what that is?

  • Officejet 8000 VS Deskjets ink quality? Which is better?

    Which uses better ink quality?  Officejet Pro 8000 or Deskjets?   Officejet Pro 8000 uses pigments and the Deskjets uses dye.  Pigment inks are supposed to be better than dye inks. However, the inks for the Officejet Pro 8000 (HP 940) are so much che