Re: Allocating memory for Bulk Inserts
Date: Thu, 8 Jan 2004 08:31:23 +0100
Message-ID: <btj15q$7mnkd$1_at_ID-152732.news.uni-berlin.de>
"oidba" <oidba_at_yahoo.com> schrieb im Newsbeitrag
news:e61db2dc.0401072138.7294c1d0_at_posting.google.com...
> > > SQL*LOADER is not an option
> >
> > I am sorry: Why not ?
>
> We're talking zero room for error in this situation. This is a
> telecomm call charging application. Unless Oracle provides a C/C++
> SQL*LOADER API, I would not bet too much on SQL*LOADER to provide the
> appropriate error handling and transaction control needed. How do you
> suppose I rollback a transaction once SQL*LOADER has loaded the table.
The question is _which_ table, that is why I suggested to laod all the raw
> I would not want to depend on the return value from a "system()" or
> "popen()" to handle the errors. Should one file be incorrectly
> processed, a tedious and time consuming task of batch cleaning would
> have to take place to manually rollback.
Received on Thu Jan 08 2004 - 08:31:23 CET