November 28, 2012 at 7:54 am
I get a package that fails sometimes with the following error. The package queries a view that is converting xml data and creates a flat file. Has any one ever seen this?
Started: 8:40:00 AM Error: 2012-11-28 08:40:27.00 Code: 0xC0202009 Source: Data Flow Task OLE DB Source [118] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. End Error Error: 2012-11-28 08:40:27.00 Code: 0xC02020E8 Source: Data Flow Task OLE DB Source [118] Description: Opening a rowset for "[dbo].[vwAutofillUpdate]" failed. Check that the object exists in the database. End Error Error: 2012-11-28 08:40:27.00 Code: 0xC004706B Source: Data Flow Task SSIS.Pipeline Description: "component "OLE DB Source" (118)" failed validation and returned validation status "VS_ISBROKEN".
November 28, 2012 at 8:20 am
jdbrown239 (11/28/2012)
I get a package that fails sometimes with the following error. The package queries a view that is converting xml data and creates a flat file. Has any one ever seen this?Started: 8:40:00 AM Error: 2012-11-28 08:40:27.00 Code: 0xC0202009 Source: Data Flow Task OLE DB Source [118] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. End Error Error: 2012-11-28 08:40:27.00 Code: 0xC02020E8 Source: Data Flow Task OLE DB Source [118] Description: Opening a rowset for "[dbo].[vwAutofillUpdate]" failed. Check that the object exists in the database. End Error Error: 2012-11-28 08:40:27.00 Code: 0xC004706B Source: Data Flow Task SSIS.Pipeline Description: "component "OLE DB Source" (118)" failed validation and returned validation status "VS_ISBROKEN".
I've seen this error and can recreate the error by changing the DDL underneath a SSIS package. For example, I've got a SSIS package running in production that accesses the dbo.Employees table. A column gets added to the Employees table. The next time the scheduled production job runs that SSIS package, it will fail with the VS_ISBROKEN error. The good news is that it's easily fixed by opening the .dtsx file in BIDs / VS and updating the metadata.
I don't know if this the issue in your situation; but I hope this helps.
Rob
November 28, 2012 at 9:23 am
What metadata am I updating and why?
November 28, 2012 at 11:48 am
jdbrown239 (11/28/2012)
What metadata am I updating and why?
The datasource is linked directly to the schema of the table. When the schema changes, anything that connects to it must be updated for the changed schema. Simply open the package and doubleclick on the datasource. It'll walk you through the metadata update.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply