| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Informatica Bulk Mode behavior
First guess - they're using direct load, and still loading one row at a time, so you get one row per block (or worse).
Since you've got the v$sql entry, check
executions against rows processed and see
if that gives you a clue.
Second guess - is your tablespaces using
auto segment space management: (e.g a
9.2 database with tablespaces created by
DBCA with default settings). If so, check
a few blocks from each extent - there are
a couple of bugs in ASSM that could lead
to massive space wastage (like only using
3 blocks per extent before allocating a new
extent).
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
April 2004 Iceland http://www.index.is/oracleday.php June 2004 UK - Optimising Oracle Seminar July 2004 USA West Coast, Optimising Oracle Seminar August 2004 Charlotte NC, Optimising Oracle Seminar September 2004 USA East Coast, Optimising Oracle Seminar September2004 UK - Optimising Oracle Seminar
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.
 |
 |