March 28, 2007 at 12:56 pm
Hi Guys,
Normally I don't post questions and prefer to research the info myself online. This time I'm stumped and cant seem to find any info online that helps.
I'm hoping one of you guys can assist me.
Having an issue in one of the environments I'm responsible for. 3 Servers using MS SQL Server 2005, all run enterprise edition and are using sp1 (DEV, QA and LIVE) each server has a linked server to a corresponding DB2 server. I'm using microsofts OLE DB2 provider (version 7.0.2413.0).
The linked server is used to write data to DB2 and also read data from DB2 to update our MS SQL system.
My responsibility is in the realm of SQL Server the DB2 boxes are managed by our client. Its basically an integration process residing on the data tier which enables synchronization between different systems used by different departments.
For the most part the linked server on my side works fine but at least once a day the linked server acts up and stops working, this occurs most notably on the LIVE box which also happens to be the most busy box.
The following error is returned in SQL Agent (All processes are stored procedures executed by Agent) :
OLE DB provider "DB2OLEDB" for linked server "DB2Srv" returned message "". [SQLSTATE 01000] (Error 7412). The step failed.
The only way to remedy this situation at present is to restart the SQL Service on the box. This is obviously not the best way to remedy the situation and has only gone unnoticed thus far by the powers that be due to us still being in a pilot phase in terms of the project.
If anyone can offer some insight into the problem it would be greatly appreciated.
November 1, 2013 at 11:42 am
I am having the same issue:
OLE DB provider "DB2OLEDB" for linked server "sqlserver01" returned message "An internal network library error has occurred. A network level conversational protocol error has occurred. SQLSTATE: HY000, SQLCODE: -343".
Msg 7330, Level 16, State 2, Line 1
Cannot fetch a row from OLE DB provider "DB2OLEDB" for linked server "sqlserver01".
I have read rights to most of the DB2 tables. Then I requested read rights to 3 more tables. Now I see this error just for those 3 tables.
There is an exception to every rule, except this one...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply