Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Way to much log switching!!!
Use direct-path INSERTs for loading, then use NOLOGGING to reduce redo
generation from that. Then, use RMAN incremental backups to backup the
just-loaded data to make it recoverable. Or not.
If you are unable to use direct-path INSERTs for loading, then something is wrong with the design of the data warehouse. Non-volatile time-variant data in partitioned tables is ideally suited for loads using direct-path INSERTs. In Oracle9iR2, direct-path INSERTs also enable the possibility of using table compression.
on 6/30/04 2:50 PM, Barbara Baker at barbarabbaker_at_yahoo.com wrote:
>
> Brings up a question that we are facing.
>
> If we turn on archive logging in our warehouse, we
> generate tons of archive logs during dataloads that we
> probably do not need.
>
> If we do not turn on archive logging, our options for
> using RMAN are less attractive.
>
> What are other sites doing about this dilemma??
>
> Barb
>
>
> --- DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM> wrote:
>> Mark >> Do you mean that you are filling logs every 1-2 >> minutes every hour of the >> day and night, or is this some type of peak that >> occurs for a few minutes >> each day? Some sites operate their ODS in >> noarchivelogmode. Have you >> considered that?
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Wed Jun 30 2004 - 23:07:45 CDT