Re: imp commit=n and rbs

On 24 Apr 2003 16:47:27 -0700, joel-garry_at_home.com (Joel Garry) wrote:

>So what is it that makes the rbs orders of magnitude larger than the
>data on an import with commit=n? Freshly bounced db, one user, hpux
>11, oracle 8.1.7.2, default imp buffer, 8K db buffers, single 520M
>table truncated in single extent (yeah, I know, I know, no LMT on this
>ts), 5 indices (one insane, 420M) pctfree 10%, no odd datatypes, no
>optimal, single rbs extended to 3.8G is not big enough.
>
>Works just fine with commit=y, doesn't even stress the minimal (400M)
>rbs. Just curious what's the deal with commit=n. Even if it were
>screwy enough to have a table image for each index plus each index
>that's only 3.2G...
>
>jg

As defined in the manual, commit=n commits only *once* per table.

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Thu Apr 24 2003 - 23:44:20 CDT