SMD E2E Trace analysis - Urgent!!

Hi,
I have configured Root cause analysis for r/3 system. Everything is working but unable to enable the system in Trace analysis. Its says, Trace status could not be evalutated.
The system meets all the prerequisites in note 1061383 and Exeption,Configuration analysis are working fine for it.
Please help
Ajay Kande

Make sure your RFC destinations in java in monitored system to the SLD are working correctly, ie VA > Server > Services > SLD Data Supplier.
Do a "trigger" to make sure you can pass info to the SLD.

Similar Messages

  • SMD E2E Trace Anaysis Fails

    Hi
    On Clicking on SMD E2E Trace Analysis the following message is shown on the UI
    "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"
    SMD SP 12
    LMSERVICE SP 12
    Any Ideas?
    -Log file--
    #1#com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: 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.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:377)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:322)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:181)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 61 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 71 more
    Caused by: java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4AppServerJCODestination(JCOClientConnection.java:704)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:478)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
    Regards,
    Vikram

    Hi Paula,
    Thanks for the speedy response.
    No I don't think I have performed any step to create JCO connections on SLD. Do you have any details on the steps?
    Do you think it would be wise to wait for SP13? Wonder why have SAP is forcing customers to buy the SMD Starter Pack.
    Regards,
    Vikram

  • E2E trace analysis in Solman

    Dear all,
    I have some question about the E2E trace analysis on solman. Hope you can help me!~
    1. We are using Solman 7.1 SP6 and we will upgrade to SP10 or SP11 in recent months. We want to use solman RCA trace analysis to trace ERP ABAP program. Could anyone can told me how to do this? I can do the HTTP trace in solman with RCA trace analysis but I don't know whether we can also nalysis the ABAP trace in solman.
    2. We have many printers in our PRD systems and all printers connected to a SPRINTER server. Now we need some suggestion on how we can monitoring these printers with solman. Also we hope to use the RCA tools to nalaysis the problem on printer such as the printer are offline/dead halt/printing very slowly and so on.
    Is this possible?

    Hi Yushuai,
    1. Using E2E in SolMan you can capture the movement of request and response to any JAVA and ABAP system. It will show you that what ABAP program has been called but It will not tell you what happening inside ABAP program.
    Regards,
    Ravi Maheshwari

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

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

  • 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

  • Error while accessing E2E Change Analysis via SMD

    Hi All,
    I am having below mentioned error while accessing E2E Change Analysis via SMD.
    Error loading template 0TPL_0SMD_CA01_Q0001 
    Notification Number BRAIN 276 
    Let me know if you are aware about the solution.
    Regards,
    Vinit Pagaria

    Is the Queries and templates activated completely in BI-content/Client?
    Please check the same and if needed activate the queries again by running report :CCMSBI_SETUP_E2E
    Also refer to the SAP Note 1342231 - ST: Manual actvtn. of BI Content for E2E diagnostics SP18-22.
    Revert for any issues pls.
    Thanks,
    Jagan

  • Urgent : How to do the SQL trace analysis

    Hi Floks,
    How to do the SQL  Trace analysis and any another tools is there to test abap programming then this tools runtime analysis,extended Programming Checking,Code inspector .How to utilize that tools .please forward me
    thanks
    suresh

    HI,
    <b>SQL Trace Use:</b>
    The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.
    <b>
    Features</b>
    The SQL Trace is especially useful for:
    Development
    SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.
    1.      Performance analysis
    Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.
    <b>Activities</b>
    Typically, you should use the SQL Trace when you need to check the behavior of a particular application. This is the following scenario:
    Look at the below links, you will get the idea
    http://help.sap.com/saphelp_erp2005/helpdata/en/d1/801f89454211d189710000e8322d00/content.htm
    Re: Runtime Analysis vs SQL Trace
    http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html

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

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

  • E2E Exception Analysis

    Hi All,
    I have configured SMD (Solution Manager Diagnostics) on SM 4.0 SP12 and I also have setup IntroScope agent and EP agent succesfully.
    When trying to run the program E2E Exception Analysis I get the next message:
    "This application is not yet configured. Please refer to the E2E post-installation steps". Unfortunately I cannot find any documentation about these post installation steps.
    Can you please help me out?
    Regards,
    Koen

    Hi Koen,
    E2E functionalities are very difficult to setup manualy.
    In SPS12, you should order a E2E Diagnotics starter pack.
    General availability of E2E tools is SPS13 (automatic setup).
    Regards,
    Xavier Picquart

  • Trace Analysis

    Where can I obtain the details and "interpretations" of a trace, i.e., what does ringmode=1 mean?; what does CallState=1 mean? Where can I get whatever all the trace headings, messages, etc.??????? If anything, we don't have any CCM plugins, and we don't have Trace Analysis tool configured nor installed on our cluster. Thank you in advance for your assistance.

    Though a little old now, there is a book out there written by Paul Giralt which talks in detail about CCM traces.  Its titled "Troubleshooting Cisco IP Telephony."  This covers CCM 4.x, but the basics of traces haven't changed much since then... just won't include a lot of the newer 5.x and later features.  Will do a good job of covering media and call flow however.
    ISBN-10: 1587050757
    ISBN-13: 978-1587050756
    I have been in TAC supporting CUCM for more than 5 years and I still refer to Paul's book from time to time.
    --Matt

  • Performance Tunned Trace/ Analysis tool

    Hi,
           I am seraching for any tool / utility provided by SAP in the ABAP Development workbench to trace/analyse the perofrmace of DB Accesses , Internal table operations in programs so I could analyse the inefficient ABAP code and could replace the same with efficient.
    thanks and regards,
    Avakash.

    Hi Avakash,
    Check this info.
    You can use ST05 to find the performance of each select.
    u can use SE30 - runtime analysis to find which part of your code is taking more time.
    using ST05:
    activate the trace --> execute the program --> deactivate the trace --> display trace.
    then go to Trace list --> Summarize trace by SQL statements.
    here u can analyze performance of all the selects.
    If you want to compare the duration by the selects in your program itself then use: GET RUNTIME statement.
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

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

Maybe you are looking for

  • OAM View-Only Access in 11.5.10.2?

    Is there any way to give a user view-only, or inquiry, access to OAM? Or is there any way to give a user any access (view-only or not) to OAM without granting that user the "System Administrator" responsibility? We are on 11.5.10.2 (CU2). For SOX com

  • HELP: CONVERSION FROM ASCII TO LABVIEW

    I am degitiging 4 chanels biomedical data by POWERLAB. I can save that file into ASCII format or POWERLAB format. Recently I am using a software to analyzed those data that need a file like labview format or HP Vee FORMAT. I DO NOT KNOW THE TYPE OF T

  • Real Time kernel questions

    I decided to compile myself a new kernel using a PKGBUILD from AUR, which contains Ingo Molnar's real time patch. I know that there are some entries int the wiki about this (Kernel Compilation with ABS, Custom Kernel Compilation with ABS, Kernel Patc

  • Can we please get some assistance for the Tap Chat product??

    This is my second post about this matter, and yet no response at all. I bought the tap chat in hopes that it would actually work. But when I press it down, it opens up my task manager, as if I just pressed ctrl + delete. It will not work with vent, i

  • Character recognition using java

    Hi guys, I have a fairly complex problem that I need to solve. Basically I am reading a set of pixel colours from a 3rd party client. I need to take this pixel data and recognize the characters used in it. Does anybody know of any good character reco