Re: Rollback segment sizing on Ora7 vs. Ora8

There was a thread about this type of problem some time ago - I forget the resolution.

One thing to check for with SQL*Load, though is the REPLACE/TRUNCATE option if you
are using direct path loads.

I believe some earlier versions of Oracle allowed direct path loading to take place with the REPLACE keyword used to delete the existing data, but later versions require the TRUNCATE keyword, and switch to normal path loading (with rollback on a massive delete) if they see the REPLACE keyword.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Michael J. Loeffler wrote in message <37a6178f.6180216_at_news.albany.net>...
>
>I have Oracle on one system, let's call it SYS1. The version of
>Oracle is 7.0.16 and it has a rollback segment size of 80M. Most of
>the things I have to do with Oracle are importing flat files using
>SQL*LOAD. Typical import size file is several hundred MB. All works
>fine, Oracle does it loads properly. Great.
>

>I'm turning over a new system, let's call it SYS2. The version of
>Oracle is 8.0.5. I used the EXACT same database creation scripts.
>I am testing imports in SQL*LOAD using the EXACT same files that
>already work properly above in SYS1. Yet, on SYS2 - I keep running
>messages about unable to extend rollback segments. I've tried
>increasing the size of my rollback segment to 700M so far, and still
>same problem.
>The problem occurs on the 2nd trial run of the same file import
>(obviously, when table is empty, the import works). The 2nd import
>(when table has data in it) is when it fails.
>
Received on Tue Aug 03 1999 - 03:14:47 CDT