Symptom
Required Cloud Connector information for Datasphere cases troubleshooting.
- Screen-shots
- Log files
Environment
SAP Datasphere
Resolution
Part 1: Screen-shots of Cloud Connector configuration information.
Please take the follow screen-shots and upload into the case.
- Datasphere subaccount details, similar like below:
- Could Connector -> Cloud To On-Premise - Access Control tab, please select the corresponding mapping entry so that to show the resources of it.
- Could Connector -> Cloud To On-Premise - Access Control tab -> Mapping details
Part 2: SAP Cloud Connector log
Please record Cloud Connector log according to below steps:
-
In the SAP Cloud Connector, increase the Cloud Connector Loggers to Debug, switch on CPIC trace (RFC trace level = 3), set Other Loggers as Information per KBA 2452568 - Log and Trace files for SAP Cloud Connector
Turn off other loggers like SSL Trace.
- Reproduce the issue. (For example, validate the connection in Datasphere, run Data Flow in Datasphere etc).
- Save the SAP Cloud Connector logs (by clicking on the Download all button) - it should contain the "ljs_trace.log (<2.17)/scc_core.trc* (>=2.17)"and scc_about files.
- Take screenshot of the error including the timestamp.
- Please save all the files to one zip file and attach (so that we will not have too much attachments in one case).
See Also
KBA 2452568 - Log and Trace files for SAP Cloud Connector
Keywords
SCC, Datasphere , KBA , DS-DI-CON , Connections , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , DS-DI-DF , Data Flows , DS-DI-RF , Replication Flows , Problem
Product
Attachments
Pasted image.png |