November 25, 2014 at 12:59 pm
I was able to run huge queries through SQL*Plus from both my computer and our SQL Server box. This rules out a network issue and an issue with Oracle. The issue appears to be coming from SQL Server and the linked server. I've tried deleting and recreating the linked server, messing with the provider settings, restarting the service, everything I can think or find through Google. Nothing seems to be working, but I have narrowed it down to a SQL Server linked server issue.
December 3, 2014 at 10:11 am
The issue ended up being a firewall problem. I found it accidentally, but maybe the steps I took will help someone else solve a similar problem:
I decided to try using ODBC for the linked server instead of OLEDB. It's a roundabout way of doing things that you wouldn't normally do, but I was just trying to get some reports working again any ways I could. When I ran above query through the ODBC linked server, the results where very similar. I returned some of the rows and then threw an error. The big difference was that the error message was different. OLEDB gave a basically useless error message, but for some reason the error message through ODBC was actually useful. In our instance, the error message was 'bad packet'. I gave the error to our network admin, and he was able to find a solution within minutes.
So, if you run into this error, consider running the linked server through ODBC and see if it gives a different error message.
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply