Re: long to clob conversion redo size and new table size

From: joel garry <joel-garry_at_home.com>
Date: Mon, 27 Jul 2009 13:29:51 -0700 (PDT)
Message-ID: <1c4c35a5-6d9e-4a60-9774-a01ff0c6ad2a_at_x25g2000prf.googlegroups.com>

On Jul 27, 12:16 pm, Grzegorz <grzegor..._at_interia.pl> wrote:
> Mark D Powell pisze:
>
>
>
> > On Jul 27, 12:19 pm, Grzegorz <grzegor..._at_interia.pl> wrote:
> >> Hi,
> >>         I've got 300GB table t1 with 2 columns:
>
> >> id number primary key,
> >> some_data long
>
> >> currently 70 mln rows.
> >> When I'm doing to_lob conversion via:
>
> >> insert /*+ APPEND NOLOGGING */ into t2 select id, to_lob(some_data)
> >> some_data from t1 where id between 1 and 2222222;
>
> >> table t2 clob is defined as 8kb chunk in MSSM tablespace (uniform size 1M)
>
> >> a 63MB redolog is switched every 18 seconds.
> >> My question is what is in redo ?
> >> The only think which comes to my mind is lob index maintenance but
> >> is that true ? Database is 9.2.0.8 and NOARCHOVELPG mode.
> >> Second question :
> >> How to minimize ne wtable (t2) size (table is insert/select only).
>
> >> Regards.
> >> Grzegorz
>
> > LOB data is forward recoverable just like any other data.  The LOB
> > inserts are being logged.
>
> Even with NOLOGGING hint ?
> How to minimize redo size in that case ?

Oh I forgot to add, you can set the index unusable and alter session skip_unusable_indexes to true, unless it is unique.

Google dump oracle redo log to see how to do that dump.

jg

--
_at_home.com is bogus.
The watched watch the watchers.
http://www.chicagotribune.com/features/columnists/advice/chi-0707-ask-amyjul07,0,2095115.column

Received on Mon Jul 27 2009 - 15:29:51 CDT