Probably should have posted the docs url for "alter table" instead of
"create table", but the impact still seems to be basically the same - a lot
more impact than just to loads. Of course, this "lot more impact" would be
good in your case, right.
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/statem2a.htm#2054899
--
"Burt Peltier" <burttemp1REMOVETHIS_at_bellsouth.net> wrote in message
news:2JBFc.3283$o62.929_at_bignews2.bellsouth.net...
> The impact of "ALTER TABLE NOLOGGING" looks different to me, just from
> reading the docs at:
>
>
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/statem3e.htm#2061078
>
> I think it impacts a LOT more than just bulk-loads :)
>
> --
>
> "Chloe Crowder" <chloe.crowder_at_bl.uk> wrote in message
> news:f27559a3.0407020039.292cbdb3_at_posting.google.com...
> > Hi
> >
> > is there any way (in 8.1.7) of switching off logging on specific
> > tables? We have a system where the redo log IO rate is of concern
> > (lots of log file sync waits being caused). A significant amount of
> > the logging is on tables which are only used to store "session" data,
> > which would not be of use or interest in the event of a recovery being
> > required. The business has agreed that these tables are not required
> > to be recovered (they are in fact cleared out on a regular basis
> > anyway).
> >
> > Looking at the ALTER TABLE NOLOGGING command, this only seems to
> > impact bulk-load type operations.
> >
> > Unfortunately the system is a third-party application, so I have no
> > control over how the application operates, but any other bright ideas
> > would be appreciated.
> >
> > Chloe Crowder
>
>
Received on Sat Jul 03 2004 - 12:35:38 CDT
