Out of Memory Error when loading into ORACLE db

Question

Hi All,
I have few SSIS packages that were running fine until a windows security patch was applied. Since then they are failing with an error " log on denied" after researching it said to run the package as 32 bit, which worked to an extent as now it is failing with the following error
[OLE DB Destination [311]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8007000E.
An OLE DB record is available. Source: "Microsoft Cursor Engine" Hresult: 0x8007000E Description: "Out of memory.".
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (311) failed with error code 0xC0202009 while processing input "OLE DB Destination Input" (324). 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.

Please advice i am not sure how these were running for months w/o any issues when running as 64 bit. Please advice.
Also when i chose in the connection manager drop down "TABLE OR VIEW FAST LOAD" i get error message that Object doesn't exist in the DB or i do not have the permissions, but when i select "Table or View" i do not get the error message but load is very very slow.
Thanks

Answer 1

Hi @bk ,

Based on error message, the issue should be caused by insufficient memory for the package execution.

For a 32-bit SSIS on a 32-bit platform, each DTExec process can consume up to 2GB memory. For a 32-bit DTExec process on a 64-bit Operating System, it can consume up to 4GB memory. If the platform is 64-bit and there are sufficient memory available on the server, and the 64-bit driver required is installed on the server, while the package runs in 32-bit runtime, then we can run the package in 64-bit runtime by setting Run64BitRuntime property to “True” of the package project to resolve this issue.

server-memory-server-configuration-options

Additional, the issue can also be caused by the oracle provider used in data flow task. Please use “Microsoft OLEDB provider Oracle” or “Oracle provider for OLEDB” to test again.

Regards，

Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October