DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
neeraj
Participant



Joined: 24 May 2005
Posts: 106

Points: 1443

Post Posted: Thu Feb 14, 2019 8:40 am Reply with quote    Back to top    

DataStage® Release: 11x
Job Type: Parallel
OS: Unix
Additional info: [ODBC SQL Server Wire Protocol driver]Socket closed.
Hello,

I am using DataStage to read from Azure SQL Server and Writing into Azure Sql Server. During the process of reading and writing using ODBC connector Job is performing the CDC .

For the High Data volume jobs, if the job runs for more than 30 minutes, I get this error message

ODBC_Target,5: ODBC function "SQLEndTran(SQL_COMMIT)" reported: SQLSTATE = 08S01: Native Error Code = 0: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Socket closed.
ODBC function "SQLEndTran(SQL_COMMIT)" reported: SQLSTATE = 08S01: Native Error Code = 0: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]SSL I/O Error.
ODBC function "SQLEndTran(SQL_COMMIT)" reported: SQLSTATE = HY000: Native Error Code = 5: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]01006 (CC_OdbcConnection::commit, file CC_OdbcConnection.cpp, line 1,241)

I tried to work with IBM and Data Direct but could not find any solution.

Have anyone faced this issue and aware about the solution.

Regards
Neeraj
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54519
Location: Sydney, Australia
Points: 295643

Post Posted: Thu Feb 14, 2019 4:14 pm Reply with quote    Back to top    

"Socket closed" suggests a problem with your network software. Involve your network administrator. Perhaps boost the "keep alive" setting.

_________________
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Rate this response:  
Not yet rated
qt_ky



Group memberships:
Premium Members

Joined: 03 Aug 2011
Posts: 2861
Location: USA
Points: 21756

Post Posted: Fri Feb 15, 2019 12:42 am Reply with quote    Back to top    

Along those lines, it could be a keep alive or connection timeout setting in a firewall. We ran into that before with a different type of database connection.

_________________
Choose a job you love, and you will never have to work a day in your life. - Confucius
Rate this response:  
Not yet rated
chulett

Premium Poster


since January 2006

Group memberships:
Premium Members, Inner Circle, Server to Parallel Transition Group

Joined: 12 Nov 2002
Posts: 42969
Location: Denver, CO
Points: 221612

Post Posted: Fri Feb 15, 2019 2:54 am Reply with quote    Back to top    

Was thinking the same thing, especially if you meant "if the job runs for more than 30 minutes before it starts returning data". Now, if data is actively flowing through the job for those 30 minutes then something else is going on.

_________________
-craig

Now I've got that feeling once again, I can't explain; you would not understand
this is now who I am. I have become comfortably numb.
Rate this response:  
Not yet rated
neeraj
Participant



Joined: 24 May 2005
Posts: 106

Points: 1443

Post Posted: Mon Feb 18, 2019 6:03 am Reply with quote    Back to top    

Hello,

Thanks for the reply.

We have added keepAlive variable in odbc.ini file but still getting the problem and involved the network team, they are not saying any connection break during the process.

What change you performed to mitigate the issue?

Regards
Neeraj
Rate this response:  
Not yet rated
qt_ky



Group memberships:
Premium Members

Joined: 03 Aug 2011
Posts: 2861
Location: USA
Points: 21756

Post Posted: Tue Feb 19, 2019 1:00 am Reply with quote    Back to top    

In my situation I did not have to change any settings on Information Server. I had to request the firewall team to change the "extended session timeout" firewall settings. But like Craig said, that usually depends on idleness, so if your job was actively transferring data, then maybe a different setting is needed or it has a different cause. Any chance the database server has a hard limit on connection time?

_________________
Choose a job you love, and you will never have to work a day in your life. - Confucius
Rate this response:  
Not yet rated
chulett

Premium Poster


since January 2006

Group memberships:
Premium Members, Inner Circle, Server to Parallel Transition Group

Joined: 12 Nov 2002
Posts: 42969
Location: Denver, CO
Points: 221612

Post Posted: Tue Feb 19, 2019 2:54 am Reply with quote    Back to top    

You still need to clarify exactly what's going on when it fails.

_________________
-craig

Now I've got that feeling once again, I can't explain; you would not understand
this is now who I am. I have become comfortably numb.
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours