Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: NOLOGGING Option on Create Table
"Marc Blum" <marc_at_marcblum.de> wrote in message
news:3cb045d8.1516190_at_news.online.de...
> On 6 Apr 2002 11:17:49 -0800, Thomas Kyte <tkyte_at_oracle.com> wrote:
>
> >I see people say things like "and *I* will never need to recover them".
That is
> >wrong. You will need to recover that many times in your lifecycle.
> >
>
> Hi Tom,
>
> I would be interested in your opinion concerning data warehousing /
> DSS / Analytic Databases which are used for querying only and say
> completely rebuild each night. I that case I tend to avoid archiving,
> logging etc. If the database crashes, well, users will be unhappy for
> not being able to work on it today, but 'til tomorrow it's fixed and
> NO data is lost.
I'm not Tom <g>, but I agree with you The difference is of course that your scenario is a read-only DSS system not a transaction processing system. The OP had transactions going through this table as part of the application logic. This has to be protected by redo.
-- Niall Litchfield Oracle DBA Audit Commission UKReceived on Sun Apr 07 2002 - 14:07:40 CDT