Re: Reducing REDO log churing

In addition, you can use create index ... nologging or create index .. unrecoverable, respectively.

Pascal Glauser

In article <L8Lp4.12834$VJ1.24388_at_newsfeeds.bigpond.com>,   "Graeme Farmer" <g_farmer_at_halas.com.au> wrote:
> Gregory,
> You shouldn't need to put the table in a separate tablespace.
 NOLOGGING
> in Oracle 8 can be enabled at the table level.
> alter table <table_name> nologging;
>
> If you are dropping and recreating the table from another table then
 you can
> use:
>
> create table <new_table>
> nologging
> as select * from <old_table>
>
> If you are using Oracle 7.x.x you can use (this also works in ORACLE8
 for
> backwards compatability)
>
> create table <new_table>
> unrecoverable
> as select * from <old_table>
>
> This will greatly increase the performance of your data copy and
 reduce the
> hits on your redo logs.
>
> Graeme.
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Mon Feb 14 2000 - 00:00:00 CST