July 27, 2014 at 6:17 am
Hi Guys,
I have a Simple Package that Loads Data from Oracle Table to Sql Server Table.
For Source Connection i have used (Oracle Connection) : ORACLE PROVIDER FOR OLEDB
and Destination: SQL SERVER NATIVE CLIENT 10.0
It just a Plain Insert of Record without any Transformation. But While executing , After Inserting "323750"
records , package gets failed at OLEDB SOURCE.
Error is as Follows:
1) SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
2) SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (200) returned error code 0xC0202009. 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. There may be error messages posted before this with more information about the failure.
I tried running package many times but after "323750" records it gets Failed. The Source (oracle) Table has around 20 Lakh reocrds.
July 27, 2014 at 11:27 pm
Anyone with updates on This ??
July 28, 2014 at 12:34 am
Anything special at row 323750?
Do you use a select statement at the source?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 28, 2014 at 1:20 am
Nothing Special with Source Data.
and Yes, i m using a Select Statement for Source.
July 28, 2014 at 1:30 am
If you only have the source component in the dataflow (and maybe just a multicast after the source), can you run the package without error?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 28, 2014 at 1:39 am
I ran the package with Source and Multicast . Package Executed but containers were not marked Red/Green. Got these Warning.
1. [OLE DB Source 1 [2261]] Warning: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.
2. [SSIS.Pipeline] Warning: Component "OLE DB Source 1" (2261) has been removed from the Data Flow task because its output is not used and its inputs either have no side effects or are not connected to outputs of other components. If the component is required, then the HasSideEffects property on at least one of its inputs should be set to true, or its output should be connected to something.
3. [SSIS.Pipeline] Warning: Component "Multicast" (2750) has been removed from the Data Flow task because its output is not used and its inputs either have no side effects or are not connected to outputs of other components. If the component is required, then the HasSideEffects property on at least one of its inputs should be set to true, or its output should be connected to something.
July 28, 2014 at 1:46 am
SSIS realized the data flow didn't do anything actually useful, so it removed the source and multicast at runtime (you did connect them together, right?). You can avoid this by setting RunInOptimizedMode to false on the data flow.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 28, 2014 at 1:51 am
Hi,
Can U please Explain This Point to me:
[OLE DB Source 1 [2261]] Warning: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.
I See some problem with the CodePage Here.
It will be really Helpful if you can share something with codepage.
July 28, 2014 at 2:00 am
It took me 10 seconds of Googling to find the answer for the default code page warning (which is a warning, so it will not crash your package):
http://consultingblogs.emc.com/jamiethomson/archive/2005/10/25/SSIS_3A00_-Connect-to-Oracle.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 28, 2014 at 2:50 am
This is not helping.
Same Problem.
July 28, 2014 at 2:53 am
Does the select run succesfully on Oracle?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply