| Author |
Message |
neeraj
Participant
Joined: 24 May 2005
Posts: 105
Points: 1413
|
|
| 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
Participant
Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group
Joined: 23 Oct 2002
Posts: 54501
Location: Sydney, Australia
Points: 295558
|
|
|
|
|
|
|
"Socket closed" suggests a problem with your network software. Involve your network administrator. Perhaps boost the "keep alive" setting.
|
_________________
RXP Services Ltd
Melbourne | Canberra | Sydney | Hong Kong | Hobart | Brisbane |
|
|
|
|
qt_ky
Group memberships:
Premium Members
Joined: 03 Aug 2011
Posts: 2855
Location: USA
Points: 21702
|
|
|
|
|
|
|
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
|
|
|
|
|
chulett
since January 2006
Group memberships:
Premium Members, Inner Circle, Server to Parallel Transition Group
Joined: 12 Nov 2002
Posts: 42926
Location: Denver, CO
Points: 221381
|
|
|
|
|
|
|
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
The Old Ones were, the Old Ones are, and the Old Ones shall be. Not in the spaces we know, but between them. They walk serene and primal, undimensioned and to us unseen.
|
|
|
|
|
neeraj
Participant
Joined: 24 May 2005
Posts: 105
Points: 1413
|
|
|
|
|
|
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
|
|
|
|
|
|
qt_ky
Group memberships:
Premium Members
Joined: 03 Aug 2011
Posts: 2855
Location: USA
Points: 21702
|
|
|
|
|
|
|
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
|
|
|
|
|
chulett
since January 2006
Group memberships:
Premium Members, Inner Circle, Server to Parallel Transition Group
Joined: 12 Nov 2002
Posts: 42926
Location: Denver, CO
Points: 221381
|
|
|
|
|
|
|
You still need to clarify exactly what's going on when it fails.
|
_________________
-craig
The Old Ones were, the Old Ones are, and the Old Ones shall be. Not in the spaces we know, but between them. They walk serene and primal, undimensioned and to us unseen.
|
|
|
|
|
|
|
