Skip to main content

Qlik Replicate

Discussion board for collaboration on Qlik Replicate.

Announcements
QlikWorld 2023, a live, in-person thrill ride. Save $300 before February 6: REGISTER NOW!
cancel
Showing results for 
Search instead for 
Did you mean: 
Attunity_user01
Contributor
Contributor

Db2 connection timeout error

We are trying t replicate data from SAP ECC system with full and CDC load from some of the huge tables.

After about 22 hours of processing we get the connection terminated with error below

RetCode: SQL_ERROR  SqlState: 08001 NativeError: -30081 Message: [IBM][CLI Driver] SQL30081N  A communication error has been detected. Communication protocol being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location where the error was detected: "IP Address".  Communication function detecting the error: "recv".  Protocol specific error code(s): "10054", "*", "0".  SQLSTATE=08001

or 

Error at 'Reading log records': A communication error has been detected. Original SQLCODE -30081: ' message SQL30081N A communication error has been detected. Communication protocol

 

What could be the issue? Db2 11.1 on AIX and Attunity  6.5.0.354

Thank you in advance.

 

 

 

2 Solutions

Accepted Solutions
Ted_Manka
Support
Support

Hello,

The "Communication error" indicates a problem in the network or some disconnection from the DB2/Mainframe.  Anytime you see "Native" error is means that Replicate is passing through an error from something it depends on.  See here for more information: https://www.ibm.com/support/pages/sql30081n-tcpip-communication-errors

Thank you,

Ted Manka

View solution in original post

Barb_Fill21
Support
Support

Hello @Attunity_user01 

First I can HIGHLY recommend that you need to upgrade to May 2022 Release. 

There have been many fixes related to communication errors.  But I am suspecting that DB2 is disconnecting due to a time-out.  

Please consider putting in the Source DB2 Endpoint definition  - Advanced Tab, Internal parameters, 

Parameter                       Value
executeTimeout            5400

SAVE the endpoint.

reload your task. 

See if it helps.

Sincerely,

Barb

View solution in original post

3 Replies
Ted_Manka
Support
Support

Hello,

The "Communication error" indicates a problem in the network or some disconnection from the DB2/Mainframe.  Anytime you see "Native" error is means that Replicate is passing through an error from something it depends on.  See here for more information: https://www.ibm.com/support/pages/sql30081n-tcpip-communication-errors

Thank you,

Ted Manka

Barb_Fill21
Support
Support

Hello @Attunity_user01 

First I can HIGHLY recommend that you need to upgrade to May 2022 Release. 

There have been many fixes related to communication errors.  But I am suspecting that DB2 is disconnecting due to a time-out.  

Please consider putting in the Source DB2 Endpoint definition  - Advanced Tab, Internal parameters, 

Parameter                       Value
executeTimeout            5400

SAVE the endpoint.

reload your task. 

See if it helps.

Sincerely,

Barb

Barb_Fill21
Support
Support

The other possible reason is that during CDC, the mainframe DB2 or even just the table may have been encountering Maintenance.

If so, please stop your Replicate Db2Z tasks about 30 minutes before DB2 z/OS maintenance occurs and resume all tasks after DB2 is back up. 

 

Hope this helps!

 

Sincerely

Barb