Select the product you need help with
PRB: DTS Transfer From SQL Server to Oracle Through OLE DB Provider Shows Ongoing Private Bytes ConsumptionArticle ID: 293320 - View products that this article applies to. This article was previously published under Q293320 On This PageSYMPTOMS
When you use Dtsrun.exe to transfer a large table from SQL Server to Oracle by using the Microsoft OLE DB Provider for Oracle, or the Oracle OLE DB Provider for Oracle, during the transfer you may see that the private bytes of Dtsrun.exe continue to increase during the entire transfer. For the transfer of a large enough number of rows, the computer memory may be stressed, which causes this error message to occur:
DTSRun OnProgress: Copy Data from document_field_default to
"DATA_CONVERT"."DOCUMENT_FIELD_DEFAULT" Step; 3050000 Rows have been
transformed or copied.; PercentComplete = 0; ProgressCount = 3050000 DTSRun OnError: Copy Data from document_field_default to
"DATA_CONVERT"."DOCUMENT_FIELD_DEFAULT" Step, Error = -2147024882 (8007000E) Error string: Error at Destination for Row number 3050982. Errors encountered so far in this task: 1. Error source: DTS Data Pump Help file: Help context: 0 Error Detail Records: Error: -2147024882 (8007000E); Provider Error: 0 (0) Error string: There is insufficient available memory. Error source: Microsoft Cursor Engine
RESOLUTION
To work around the high consumption of private bytes, use the Microsoft ODBC Driver for Oracle or the Oracle ODBC Driver for Oracle. Neither of these drivers consume as much private bytes during large row transfers from Microsoft SQL Server to Oracle.
STATUS
This behavior is by design.
MORE INFORMATIONSteps to Reproduce Behavior
PropertiesArticle ID: 293320 - Last Review: October 31, 2003 - Revision: 3.2
|


Back to the top








