Informatica Bulk Mode behavior

From: Thomas Jeff <jeff.thomas_at_thomson.net>
Date: Thu, 22 Apr 2004 09:32:44 -0500
Message-ID: <358728A276824E419580403633AABFD0021F6148@INDYSMAIL03.am.thmulti.com>

List,
Is anyone familiar with how Informatica's bulk mode works?

We have a situation where I created a 4GB tablespace for a new and simple
truncate/load operation from Informatica, around 7 million rows estimated
to take up 1.5GB.

Using bulk mode, which appears to be a direct load (in the SQL cache, the
INSERT statement has a hint that I've never seen before: SYS_DL_CURSOR which
I assume stands for Direct Load), they run out of space in the tablespace after
about 200K rows have been inserted.

If I then manually rebuild the table, the 200K rows gets compressed back down
to one extent.

So there's a lot of either empty or preallocated space. Thinking somehow
the high-water mark was the culprit, I manually truncated the table before
they reran their job.

Still the same problem.

If the job runs in 'normal' mode, which is row-by-row processing, it runs fine,
although of course, performance is quite poor.

Any ideas/experience as to how this bulk mode operates?

Thanks.

Jeffery D Thomas
DBA
Thomson Information Services
Thomson, Inc.

Email: jeff.thomas_at_thomson.net

Indy DBA Master Documentation available at: http://gkmqp.tce.com/tis_dba

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html


-----------------------------------------------------------------

Received on Thu Apr 22 2004 - 10:22:44 CDT