Re: Disable logging in tablespace vs using hidden parameter _disable_logging
- From: "Jonathan Lewis" <jonathan@xxxxxxxxxxxxxxxxxx>
- To: <juancarlosreyesp@xxxxxxxxx>
- Date: Thu, 2 Feb 2006 20:53:47 -0000
For a large import, the point I was making about
commits is pretty irrelevant. I was only thinking
about the usual potential for latch collision and
redo wastage for highly concurrent systems, and
'row at a time' batch processing.
Everything that could normally cause a redo-related
problem still can cause a problem with _disable_logging
set to true apart from one little detail, which is the
log file write time.
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/appearances.html
Public Appearances - schedule updated 10th Jan 2006
----- Original Message -----
From: "Juan Carlos Reyes Pacheco" <juancarlosreyesp@xxxxxxxxx>
To: <jonathan@xxxxxxxxxxxxxxxxxx>
Cc: <oracle-l@xxxxxxxxxxxxx>
Sent: Thursday, February 02, 2006 8:02 PM
Subject: Re: Disable logging in tablespace vs using hidden parameter
_disable_logging
Thank you Jonathan, can you please extend your explanation about the
and avoid
commits.
How important is to set commit=N in an import?
Sorry for this questions, but I asked my boss to giveme a server(a
normal 500U$ computer) to run some optimizations test, but he denied,
so I can't do as much test as I would like and have to be guessing and
asking.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
