Can Profiler catch OLEDB events from an SSIS package? RRS feed

  • Question

  • Hi All,

    We have an SSIS package on a SQL 2008 R2 box that connects to a remote DB2 data source using the DB2 OLEDB version 4.0 driver.  We've scheduled the package to run daily using a SQL Agent job.  For some reason, the job step that runs the SSIS package fails every Sunday, and we can see the error in the Job history:

    Error: 2012-12-09 05:00:48.38     Code: 0xC0202009     Source: Customers OLESRC Terminals [1]     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E14.  An OLE DB record is available.  Source: "Microsoft DB2 OLE DB Provider"  Hresult: 0x80040E14  Description: "An internal network library error has occurred. A network level syntax error has occurred. SQLSTATE: HY000, SQLCODE: -379".  End Error

    Before we contact the DB2 admins and ask what they're doing every Sunday, we want to ensure the problem is on the DB2 side and not ours.  I set up a server-side trace to catch OLEDB events while the SSIS package runs, but the results contain no OLEDB events.  I ran the trace again and manually executed the package, but still no OLEDB events.  I ran the trace again and executed "INSERT INTO dbo.Customers SELECT * FROM DB2.DB2.Customers" from Management Studio and I can see all of the OLEDB events in the trace results that I would normally expect.

    I'm not an expert Profiler user, but it seems like 1) the OLEDB calls from SSIS aren't available to the SQL Server engine, and 2) Profiler can only catch SQL Server engine events.  Could somebody set me straight on this?

    Also, the above error message includes "an OLEDB record is available."  Where can I find this record of the error?


    Wednesday, December 19, 2012 6:39 PM