Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Unveils New Agentic Capabilities Across Analytics, Data Engineering, and Trust: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
SushCNX
Contributor
Contributor

Connection Closed Unexpectedly

Hi Team

We have observed frequent disconnections for all PostgreSQL targets connected to the Qlik Replicate server after the recent psql version upgrade on the replicate server from 10 to 15.3

This issue is impacting full load operations across all Postgres targets. The connections are getting closed unexpectedly, causing full load failures. Additionally, during CDC operations, we are observing multiple events where the connection is getting lost.

Below is the error encountered:

[TARGET_LOAD]
RetCode: SQL_ERROR
SqlState: 08001
NativeError: 101
Message: server closed the connection unexpectedly
This probably means the server terminated abnormally.

Based on our observation, this issue is occurring for all PostgreSQL target connections.

We have also addded additional connection properties internal parameter ; KeepaliveTime= 60 And KeepaliveInterval = 10

Please help us in resolving the issue.

Regards,

Sushant

1 Solution

Accepted Solutions
DesmondWOO
Support
Support

Hi @SushCNX ,

To determine whether the issue is related to psql, you can enable TRACE level logging on both TARGET_LOAD and TARGET_APPLY. If the connection error occurs after loading the CSV file into the attrep_changes table, then it is unlikely to be caused by the psql version.

As Naren mentioned, if the issue persists or you are still unsure about the cause of the connection error, please open a support ticket for further assistance.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

2 Replies
narendersarva
Support
Support

Hi @SushCNX 

We need to review the complete logs to properly understand the issue. Since this appears to be related to a network interruption, it is possible that the task recovered automatically once connectivity was restored.

If the issue is still occurring, please open a support ticket and attach the full task logs and diagnostic package. One of our support team members will review the logs in detail and assist you further.

 

Thanks
Naren

DesmondWOO
Support
Support

Hi @SushCNX ,

To determine whether the issue is related to psql, you can enable TRACE level logging on both TARGET_LOAD and TARGET_APPLY. If the connection error occurs after loading the CSV file into the attrep_changes table, then it is unlikely to be caused by the psql version.

As Naren mentioned, if the issue persists or you are still unsure about the cause of the connection error, please open a support ticket for further assistance.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!