SAP HANA unable to run the sync

[dheerendra43-afk]

Topic

Sync job is failing for memory issue

Relevant information

Hi Team,

One of my Airbyte sync is failing when loading data from SAP HANA to Snowflake. Attached the error.

sap_hana___new___snowflake_logs_34366_txt.txt

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will help with initial triage.

I'll review your issue and:

• Ask clarifying questions if needed
• Provide immediate guidance if available
• Escalate to the appropriate team if this requires engineering attention

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/4daa49d915534cd1abd4f8dcc9f2a185

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi @dheerendra43-afk, thank you for reporting this issue!

I can see from the logs that you are running Airbyte OSS v1.6.3 with the SAP HANA Enterprise source connector (v0.0.16) syncing to Snowflake. The logs show a successful connection check, but I notice the sync logs are incomplete - they end at "START REPLICATION" without showing the actual error that caused the failure.

Key observation from the logs:

The platform is limiting your connector resources:

Invalid resource requirements detected, requested 4 while limit is 1, falling back to requesting 1.
Invalid resource requirements detected, requested 8Gi while limit is 2Gi, falling back to requesting 2Gi.

The SAP HANA connector requested 4 CPUs and 8GB memory, but your deployment is limiting it to 1 CPU and 2GB memory. Given that your SAP HANA instance has 2,875 tables and 42,659 columns, this resource constraint is likely causing the memory issue you mentioned.

To help diagnose further, could you please provide:

1. The complete sync logs including the actual error message (the attached logs end before showing the failure)
2. How many streams/tables are you trying to sync in this connection?

Recommended workaround:

You can increase the resource limits for your Airbyte deployment. In your values.yaml file, add or modify:

Helm Configuration for Resource Limits

global:
  jobs:
    resources:
      limits:
        cpu: "4"
        memory: "8Gi"
      requests:
        cpu: "2"
        memory: "4Gi"

Alternatively, you can set environment variables:

• JOB_MAIN_CONTAINER_CPU_LIMIT
• JOB_MAIN_CONTAINER_MEMORY_LIMIT
• JOB_MAIN_CONTAINER_CPU_REQUEST
• JOB_MAIN_CONTAINER_MEMORY_REQUEST

For more details, see the documentation on Configuring Connector Resources.

If increasing resources does not resolve the issue, please share the complete error logs and we can investigate further.

---

This message is generated from Devin.ai (internal session link).

[dheerendra43-afk]

++ Nanditha from our Admin team.

…

On Thu, Jan 29, 2026 at 12:18 PM devin-ai-integration[bot] < ***@***.***> wrote: *devin-ai-integration[bot]* left a comment (airbytehq/airbyte#72457) <#72457 (comment)> Hi @dheerendra43-afk <https://github.com/dheerendra43-afk>, thank you for reporting this issue! I can see from the logs that you are running Airbyte OSS v1.6.3 with the SAP HANA Enterprise source connector (v0.0.16) syncing to Snowflake. The logs show a successful connection check, but I notice the sync logs are incomplete - they end at "START REPLICATION" without showing the actual error that caused the failure. *Key observation from the logs:* The platform is limiting your connector resources: Invalid resource requirements detected, requested 4 while limit is 1, falling back to requesting 1. Invalid resource requirements detected, requested 8Gi while limit is 2Gi, falling back to requesting 2Gi. The SAP HANA connector requested 4 CPUs and 8GB memory, but your deployment is limiting it to 1 CPU and 2GB memory. Given that your SAP HANA instance has *2,875 tables and 42,659 columns*, this resource constraint is likely causing the memory issue you mentioned. *To help diagnose further, could you please provide:* 1. The complete sync logs including the actual error message (the attached logs end before showing the failure) 2. How many streams/tables are you trying to sync in this connection? *Recommended workaround:* You can increase the resource limits for your Airbyte deployment. In your values.yaml file, add or modify: Helm Configuration for Resource Limits global: jobs: resources: limits: cpu: "4" memory: "8Gi" requests: cpu: "2" memory: "4Gi" Alternatively, you can set environment variables: - JOB_MAIN_CONTAINER_CPU_LIMIT - JOB_MAIN_CONTAINER_MEMORY_LIMIT - JOB_MAIN_CONTAINER_CPU_REQUEST - JOB_MAIN_CONTAINER_MEMORY_REQUEST For more details, see the documentation on Configuring Connector Resources <https://docs.airbyte.com/platform/operator-guides/configuring-connector-resources> . If increasing resources does not resolve the issue, please share the complete error logs and we can investigate further. ------------------------------ This message is generated from Devin.ai (internal session link <https://app.devin.ai/sessions/4daa49d915534cd1abd4f8dcc9f2a185>). — Reply to this email directly, view it on GitHub <#72457 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B44PIMHHX2HEYSTNL45Y5OT4JI6FBAVCNFSM6AAAAACTKY57T6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMJZGEYDKMBSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Best Regards Dheerendra kumar Pandey