Friday, December 28, 2012 4:17 PM
This is a general question; I'm not asking for help on a specific error.
Our SQL 2008 R2 jobs occasionally run into OLE DB errors. Regardless of the error code, the message always includes "An OLE DB record is available." Where is this OLE DB record that's supposedly available?
The reason I ask is because we occasionally run into DB2 OLE DB driver errors that returns very cryptic messages. If there was a log for the driver itself--which I'm assuming this "available record" is residing--I might be able to get more specific error info.
Wednesday, January 02, 2013 2:49 PM
You did not mention what type of SQL Server 2008 R2 jobs you are running. One common job type is to run an SSIS package. Is that what you are doing? Are you running on a 64-bit server? If so, the following might be helpful:
Wednesday, January 02, 2013 10:39 PM
Thanks, Russel. Yes, our Jobs are running SSIS packages. They run other steps as well, but the errors we get are with the SSIS packages only. Yes, it's a 64-bit server.
The reason for my question was not for help with the often-occurring OLE DB error itself. We've got Microsoft Support working on it, and so far they're telling us to upgrade to the DB2 OLE DB driver version 4 for SQL Server 2012 SP1. I don't know if we'll go that route yet, especially since our step retry configuration seems to be a worthwhile workaround for our particular error. (For some reason, waiting 5 minutes and re-executing the SSIS package circumvents the OLE DB error.)
Our particular error message is not found in the link you provided, and that's fine because I wasn't looking for help with our error message; I was only asking about the info in the error message that "an OLE DB record is available." Could it be that our error messages are being logged somewhere other than the Job log and the SSIS package log?
Thanks for your help,
Thursday, January 03, 2013 1:29 AM
Yes, though the "B" case in the link I gave you did include that message "An OLE DB record is available". It laid the problem at the doorstep of a provider that did not have a 64-bit version. Since you are working between SQL Server and DB2, the possibility of incompatible drivers seemed none zero. :)
However, if it works sometimes, that makes it more mysterious.
I have never seen anything useful provided by "An OLE DB record is available" just for what it is worth. If it is not in your application or system logs, then I have no suggestion.
- Marked As Answer by SQL Server dude Friday, January 04, 2013 8:57 PM
Friday, January 04, 2013 8:59 PMThanks for your input, Russell. I hope to post the answer here myself, eventually.