Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Run Oracle without transactions?

Re: Run Oracle without transactions?

From: Anita Krishnamurthy <anita_at_cls.uob.com.sg>
Date: Thu, 08 Jul 1999 17:56:50 +0800
Message-ID: <378475E2.734866B9@cls.uob.com.sg>


So do I conclude that there is no way I can turn transactions off on the database? I was told that this is how Oracle runs when loading is done using SQL Loader. I was wondering if there is a way for us to do it. This would be a solution for us.

Jonathan Lewis wrote:

> I suspect that there is no cheap fix for your
> problem, too many black-boxes with the
> potential for complicated twiddly bits.
>
> You ought to have an option to commit
> one object at a time within your loading
> front-end. This will save the massive
> rollback, though it could drive the redo
> log wastage (hence I/O) up quite a bit.
> (If there isn't an option to commit for
> each object, there should be).
>
> You could look at the option for producing
> a second loader, using common code to
> generate flat files corresponding to the
> relational tables that would be loaded, and
> then use a fast loader to pump the flat
> files into the database.
>
> To get an insight into what the black boxes
> are doing, you could send a sql_trace call
> to the process that gets the data into the
> database - it might give you some clues
> on a least expensive strategy.
>
> -
Received on Thu Jul 08 1999 - 04:56:50 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US