November 23, 2011 at 11:23 pm
Hi
We have SQL Server 2008 EE 64bit SP3, with 16 logical processor and 64GB RAM on Windows 2008R2 x64.
Ocassionally we are facing one issue(once in a week) while running SQL job which contain SSIS package which imports millions of data from ORACLE.
most of the times this process completes flawlessly(average time is 4hrs), but once in week its run for 6hrs after that also it get failed. with below error:
Started: 3:17:23 PM Error: 2011-11-22 15:33:40.69
Code: 0xC0202009
Source: TDS Ends OLE DB Source [1]
Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005
Description: "[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.".
End Error Error: 2011-11-22 15:33:40.98 Code: 0xC0047038
Source: TDS Ends SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.
The PrimeOutput method on component "OLE DB Source" (1) 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.
End Error Error: 2011-11-22 15:33:49.71 Code: 0xC0202009 Source: INT_ADM OLE DB Destination [148]
Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server"
Hresult: 0x80004005
Description: "[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.".
End Error Error: 2011-11-22 15:33:49.74
Code: 0xC0202009
Source: RENO OLE DB Destination [16]
Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005
Description: "[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.".
End Error Error: 2011-11-22 15:33:50.00
Code: 0xC0209029
Source: INT_ADM OLE DB Destination [148]
Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "input "OLE DB Destination Input" (161)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (161)" specifies failure on error.
An error occurred on the specified object of the specified component.
There may be error messages posted before this with more information about the failure.
End Error Error: 2011-11-22 15:33:50.03 Code: 0xC0209029 Source: RENO OLE DB Destination [16]
Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "input "OLE DB Destination Input" (29)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (29)" specifies failure on error.
An error occurred on the specified object of the specified component.
There may be error messages posted before this with more information about the failure.
End Error Error: 2011-11-22 15:33:50.35
Code: 0xC0047022
Source: INT_ADM SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.
The ProcessInput method on component "OLE DB Destination" (148) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (161).
The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
There may be error messages posted before this with more information about the failure. End Error Error: 2011-11-22 15:33:50.39
Code: 0xC0047022
Source: RENO SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.
The ProcessInput method on component "OLE DB Destination" (16) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (29). The identified component returned a... The package execution fa... The step failed.
Plz help
हेमडब्या
November 24, 2011 at 6:27 am
It might be helpful...
Error message when an application connects to SQL Server on a server that is running Windows Server 2003: "General Network error," "Communication link failure," or "A transport-level error"
November 24, 2011 at 10:18 am
thanks but we have already applied the said settings but no use
हेमडब्या
November 24, 2011 at 10:19 am
thanks but we have already applied the said settings but no use
हेमडब्या
December 6, 2011 at 9:02 pm
hey guys at least give some hint from where i can start troubleshooting
हेमडब्या
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply