HI, I HAVE A NEW PROBLEM...HOPE SOMEONE KNOWS WHAT THE $#%#$ IS HAPPENING. HERE IT′S THE THING: I′M USING A DATA FLOW TASK TO READ DATA FROM AN ORACLE SERVER AND TRANSFER THE INFO TO MY SQL 2005 SERVER, THE SOURCE IS AVAILABLE AND THE CONNECTION IS WORKING, I'M USING A DATA READER SOURCE TO CONNECT AND EXTRACT. I′VE PUT THIS DTS IN A JOB AND IT WAS OK, IT HAD BEEN RUNNING OK FOR ALMOST A MONTH BUT SUDDENLY HIS MORNING IT FAILED WITH THE FOLLOWING ERROR:
SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" starting.
Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Extrae SAZ_GranoO_New, DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Extrae SAZ_GranoO_New, DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Extrae SAZ_GranoO_New, DTS.Pipeline: Execute phase is beginning.
Error: 0xC0047062 at Extrae SAZ_GranoO_New, SAZ_GranoONew [421]: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)
Error: 0xC0047038 at Extrae SAZ_GranoO_New, DTS.Pipeline: The PrimeOutput method on component "SAZ_GranoONew" (421) returned error code 0x80004003. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Error: 0xC0047021 at Extrae SAZ_GranoO_New, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.
Information: 0x402090DF at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has started.
Information: 0x402090E0 at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has ended.
Information: 0x40043008 at Extrae SAZ_GranoO_New, DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at Extrae SAZ_GranoO_New, DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at Extrae SAZ_GranoO_New, DTS.Pipeline: "component "OLE DB Destination" (1022)" wrote 19522 rows.
Task failed: Extrae SAZ_GranoO_New
Warning: 0x80019002 at SAZSIE_CargaVentasSeguros: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" finished: Failure.
THE DATA HAS BEEN COPIED INTO MY DESTINATION TABLE, BUT THE PACKAGE ENDS IN AN ERROR, WHAT IS THE PROBLEM WITH THIS?
PLASE SOMEONE !!!!
THANKS!!!!!!!
the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...|||take it easy|||ruk_walled wrote:
the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...
Hence you should always use a SQL statement rather than referencing a table by name!
-Jamie
|||it′s exactly what i did... after the error of course ;)
thanks for your advice!!!
|||Interesting. I just ran into this same problem, with the same cause - source table structure changed.However, the query I was using to retrieve from it was of the form "select * from <blah>".
It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?|||
It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?
Any component in a dataflow that acceses something external to the package has something called the ExternalMetadata collection which is information about what that external thing "looks" like. If that external thing doesn't look like what the SSIS package is expecting - you'll get problems.
-Jamie
No comments:
Post a Comment