SAP Knowledge Base Article - Public

2630653 - HOW-TO: Collect traces to help troubleshoot errors and issues when importing data from on-premise data sources in SAP Analytics Cloud (SAC) ***Master KBA ***

Symptom

  • You are using SAP Analytics Cloud (SAC) and want to connect to data stored on your network and import that data into a model or dataset in SAP Analytics Cloud.
    • SAP Business Warehouse (BW),
    • SAP BW/4HANA,
    • SAP S/4HANA,
    • SAP HANA,
    • Universes,
    • SQL Server databases etc.
    • Note: All supported data sources are listed here: Data Connectivity – Import.
  • What tracing and logging information is needed to help troubleshoot errors and issues?
  • For live connections, see 2589761 and the product documentation: Live Data Connection.

Environment

  • SAP Analytics Cloud (Enterprise)

Resolution

In the workflow of importing data from on-premise data sources into SAC, the following applications/products are involved where different traces could be collected:

  • SAP Analytics Cloud (SAC)
  • SAP BTP Cloud Connector (SCC)
  • SAP Analytics Cloud Agent (SAC Agent)
  • On-Premise Data sources

Trace on SAP Analytics Cloud (SAC)

  • Leverage browser-side tracing (Chrome Developer Tools / HTTP Archive Files (HAR)) for troubleshooting page loading performance and obtaining request / response information.
  • Refer to SAP KBA  2280022 - How to collect HAR files in SAP Analytics Cloud
  • In the network panel, detailed action log and resource information for each request can be seen by reviewing the Header, Preview, Response, Cookies, and Timing sections.
    • Header: The Request Payload is important to get the detail action log and resource information
    • Preview: In preview tab, we can also find the detail data source information.
    • Response: In response tab, we can find the status information for the request resource data.
    • Timing: Timing information is helpful when troubleshooting the performance issue. In the timing tab, we can know how the time is distributed for each request, especially for the request time and waiting time.
  • Also refer to SAP KBA: 2413393 - How to record timelines in Chrome Developer Tools in case of SAP Analytics Cloud performance issues

Trace on SAP BTP Cloud Connector (SCC)

  • The folllowing trace files are required to be collected from SCC:
    • Cloud Connector Loggers: ljs_trace.log
    • Paylod trace (or calling Traffic trace): traffic_trace_<account id>_on_<landscapehost>.trc
      => Note: <Subaccount_ID> and <Region> would be customer specific.
  • Logging and Tracing on Cloud Connector documentation can be found at: Cloud Connector > Administration > Troubleshooting.
  • See also SAP KBA 2452568 - Log and Trace files for SAP Cloud Connector.
  • Note: Once you enable the payload trace, please let the issue happen a few times and provide the trace file for further troubleshooting.

Trace on SAP Analytics Cloud Agent (SAC Agent)

  • SAP Analytics Cloud Agent is a web application (C4A_AGENT) which is deployed in the Apache Tomcat webserver to handle the connectivity between SAP Analytics Cloud and on-premise data sources after the Cloud Connector has successfully established the secure tunnel.
    • SAC Agent is only required for non-HTTP-based data source like BW, ERP, SQL databased, etc.
    • For HTTP-based data source like S/4HANA, OData, etc., the HTTP request from SAC could be transferred to data source directly via Cloud Connector, so SAC agent is not required.
  • The following trace/log information could be collected with SAC Agent and used to troubleshoot errors between SAP Analytics Cloud Agent and Data Source
    • The Tomcat error log: <Tomcat_Install_Dir>/logs/tomcat-stderr.<DATE>.log   (for example "tomcat7-stderr.2018-04-09.log")
    • The Tomcat catalina log <Tomcat_Install_Dir>/logs/catalina.<DATE>.log   (for example "catalina.2018-04-09.log")
  • See detail from SAP KBA 3406144 - HOW-TO: Collecting Trace on SAP Analytics Cloud Agent when importing data from on-premise data sources in SAP Analytics Cloud (SAC)
  • Note: please let the issue happen a few times and provide the trace files for further troubleshooting.

Traces on various data sources

Required Traces for different scenaiors

Check Configuration Create/Edit Connection Create model/dataset Run Import Jobs
Trace on SAC 〇 〇 〇
Trace on SCC 〇 〇 〇 〇
Trace on SAC Agent 〇 △ △ △
Trace on Data source 〇 〇 〇

〇: Reuqired
△: Trace on SAC agent are only required for non-HTTP-based data source like BW and ERP, but not required for HTTP-based data source like S/4HANA and OData.

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

EPM, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, EPM-ODS, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics, Import, Acquired, Acquire, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, Troubleshoot, Troubleshooting, bp, bps, T-shooting SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud, https://hcs.cloud.sap, https://hanacloudservices.cloud.sap, https://cloudanalytics.accounts.ondemand.com, https://hanacloudservices-us.accounts.ondemand.com, https://www.sap.com, https://help.sap.com, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software epm, business intelligence, , KBA , sap sac load failures , sactroubleshooting saw sactroubleshootin , sactroubleshooting sac troubleshooting , load failures , loading dataloads data loads , import connection , sac model creation failing intermittentl , bw note checkig tool sac , checking , failing intermittently , best practices bp bps , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , LOD-ANA-ML-DI , Data Integration, Data Export API, Data Import API , LOD-ANA-PL-PLI , Planning Integration (BPC import/export/writeback) , Problem

Product

SAP Analytics Cloud 1.0