February 19, 2008 at 7:13 am
Hi,
I have an error that keeps appearing, seemingly randomly, when loading a data warehouse for a customer. There is a schedueled job that runs once during the night and 3 times during the day. Usually it works as it should but then sometimes it doesn't. When trying to run the job manually it might fail a couple of times and then it completes sucessfully.
The job step is to run an SSIS package that in turn loads data into the warehouse with help from a view that in turn is using a second view that contains a pivot function to return data.
The error message that I get is the following, and as others have commented, the view of course exists in the database. Can anyone advice on what the real problem might be and how to solve it, and it would make my month.
Thanks in advance!
/Per
Error Message
Executed as user: XXX ...for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:00:00 PM Error: 2008-02-15 15:03:34.80 Code: 0xC0202009 Source: Data Flow Task vwRotRouteLegLoading OLE DB Source [1088] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E57. End Error Error: 2008-02-15 15:03:35.14 Code: 0xC02020E8 Source: Data Flow Task vwRotRouteLegLoading OLE DB Source [1088] Description: Opening a rowset for "[bi].[vwRotRouteLegLoading]" failed. Check that the object exists in the database. End Error Error: 2008-02-15 15:03:35.50 Code: 0xC004701A Source: Data Flow Task vwRotRouteLegLoading DTS.Pipeline Description: component "OLE DB Source" (1088) failed the pre-execute phase and returned error code 0xC02020E8. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:00:00 PM Finished... The package execution fa... The step failed.
February 19, 2008 at 8:22 am
I am guessing here. I was confused when you said it worked fine everytime but then sometimes it fails. Then when I reviewed your error, there is something that it is asking you to check if it exist. Which is some object in the database. So, I think whenever the package fails, something that is embedded within the package could not find the proper object that it is related to. Only then it fails. Otherwise, if it is there, it goes on smoothly. The evidence is when you mentioned that it does the same sometimes when you try to execute it manually. Please go back to the error and find where your package is needing something that is not there. Hope this helps!
[font="Verdana"]Imagination is more important than knowledge-Albert Einstein[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply