We use BO Data Integrator 11.7 to connect MS SQL Server 2005 and got this message from time to time.
ODBC data source error message for operation : <[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()).>.
The protocols we used for SQL Server are: TCP/IP and Shared Memory. It sometimes happens when we have large volumn of data but sometimes not. The connections don’t seem busy all the time so we cannot understand why. We hope to figure out how can fix it.
It comes from either the source or target database. I appreciate it if you could be more specific what symptons I can tell it’s under-powered and how I can keep up with the load. It happens to different data flow in different time of the day and the network traffic or database load usually is not very heavy so I need some measures to watch and find out the root cause to fix.
If you’re using Shared Memory (as the error message indicates), you must already have the DI job server installed on the same machine as the source and/or target database, correct?
Shared Memory connections are only usable when the application talking to the database is on the same physical machine as the database.
You could try configuring SQL Server to only allow TCP/IP connections, to see if that makes a difference.
Our DI is installed on the AP server which is different from the DB server. Thank you for reminding and we change it accordingly. We’ve tried to use only TCP/IP but it doesn’t make a difference. We get the same error with either TCP/IP only or other connections. Other than the ConnectionRead or ConnectionWrite error, we also get the Timeout expired error from time to time and these really cause us big trouble. Let me know what else we can try to fix it.
Initialization ODBC call for data source failed: [Microsoft][ODBC SQL Server Driver] Timeout expired
(BOB member since 2007-07-06)
(BOB member since 2004-01-30)