Hi!
I am currently encountering an error of testing an SSIS package in the server.
The package runs fine on my laptop, but not in the server.
I appreciate it for any of your input, comments, and suggestions.
The package is to populate records (150k rows) from a DB2 table and insert them into
another DB2 table (12,754,715 rows).
The server,
Windows Server 2003 Enterprise
SQL server 2005 sp1
8 CPUs
6 GB RAM
Native OLE DB\IBM OLE DB Provider for DB2
My laptop,
Windows 2000 Professional
SQL server 2005 sp1
2 CPUs
2 GB RAM
Native OLE DB\IBM OLE DB Provider for DB2
It fails on the insertion part (see the error message at the bottom). I have been playing with "DefaultBufferMaxRows" and "DefaultBufferSize" properties, but still no luck so far.
For the testing purpose, I even only select 2 rows from the source table, but it still fails with the same error message. And strangely, it still takes a very long time to process (for just two rows). In my laptop, it only takes few second to finish.
I have been really pulling my head to try to figure it out. Any of your help/input is highly appreciated! Thanks!
======================
Error Message
[POLICY [1683]] 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.".
Strange...
Check the available memory with task manager...
check If datasource has indexes in database
Avoid using transforms like union all, aggregate, ...
but in your example importing only 2 rows is to strange.. :-(
give me more details...
Regards.
|||Thanks for your reply.
All information came from Task Manager, (I am not good at monitoring system performance and resources by any mean)
Before the process ran,
Memory Usage: 0.9 GB (~5.1+ GB physical memory available)
Right before the process failed,
Memory Usage: 3.1 GB (~2.5+ GB physical memory available)
DefaultBufferMaxRows: 100
DefaultBufferSize: 1048576
Both tables (source and destination) have indexes.
The data transformation is very straight forward. OLEDB source to OLEDB destination (table to table).
For any further information for diagnosing this issue, please let me know.
Thanks.
No comments:
Post a Comment