Skip to main content

​
Troubleshooting

​
Workflow Deployment Error

If there were any errors during the workflow deployment process, the Ingestion Pipeline Entity will still be created, but no workflow will be present in the Ingestion container.
  • You can then Edit the Ingestion Pipeline and Deploy it again.
  • From the Connection tab, you can also Edit the Service if needed.

​
Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in Collate. Below are some of the most frequently observed troubleshooting scenarios.

​
How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in Collate:
  1. Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the Collate UI.
  2. Select a Service Choose the specific service for which you want to enable debug logging.
  3. Access Ingestion Tab Go to the Ingestion tab and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.
  4. Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
  5. Schedule and Submit Configure the schedule if needed and click Submit to apply the changes.

​
Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

​
SAP BW/4HANA-Specific Issues

​
Permission Denied on ABAP Catalog Tables

Symptom: Test connection step GetInfoAreas, GetADSOs, GetCompositeProviders, or GetBExQueries fails with a permission error. Cause: The HANA user does not have SELECT access on one or more BW ABAP catalog tables in the configured abapSchema. Resolution: Grant the required permissions listed in the Requirements section. Verify the correct schema name by running:

​
Wrong ABAP Schema

Symptom: Test connection passes (CheckAccess succeeds) but GetInfoAreas returns 0 results or fails. Cause: The abapSchema field is set to the default (SAPHANADB) but your system uses a different schema name. Resolution: Run the following query on your HANA system and use the returned schema name in the abapSchema field:

​
No Lineage Edges Produced

Symptom: Metadata ingestion works but the lineage workflow produces no edges. Cause: The HANA user may be missing SELECT on the lineage-specific tables (RSTRAN, RSTRANRULE, RSTRANFIELD, SYS.OBJECT_DEPENDENCIES), or your BW system has no active transformations between ADSOs. Resolution: Verify the lineage permissions from the Requirements section. Confirm that transformation objects exist in your BW/4HANA system by checking RSTRAN.

​
HANA Port Not Reachable

Symptom: CheckAccess test step fails with a connection timeout or refused error. Cause: The hostPort may point to the wrong port, or the HANA SQL port (default 30015) is not accessible from the ingestion host. Resolution: Confirm the correct HANA instance SQL port. For multi-tenant systems, the tenant port may differ (e.g. 30041 for tenant 41). Ensure your network allows TCP connectivity from the ingestion runner to the HANA host on that port.