Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6282A.06A64003"
Subject: RE: Disable logging in tablespace vs using hidden parameter _disable_logging
Date: Thu, 2 Feb 2006 13:53:37 -0500
Message-ID: <AA29A27627F842409E1D18FB19CDCF2706A3A0E7@AABO-EXCHANGE02.bos.il.pqe>
Thread-Topic: Disable logging in tablespace vs using hidden parameter _disable_logging
Thread-Index: AcYoKDXuLW21AgJySHCxbwjXqAaymQAAMBQQ
From: "Bobak, Mark" <Mark.Bobak@il.proquest.com>
To: <juancarlosreyesp@gmail.com>,
 "Li-Shan Cheng" <exriscer@gmail.com>
Cc: <oracle-l@freelists.org>
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: Mark.Bobak@il.proquest.com
------_=_NextPart_001_01C6282A.06A64003
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Juan,

Setting NOLOGGING on a tablespace does not, in and of itself, do
anything.  That setting becomes the default for any segments created in
the tablespace.  Further, NOLOGGING does not have an effect on all
operations.  Actually, it's quite a small subset of operations that
NOLOGGING will have an effect on.  Some of these include:  index
creation, index rebuild, insert /*+ APPEND */, just to name a few.  It's
important to understand NOLOGGING and how it works, so that you may
understand the recovery implications.  Blocks loaded using NOLOGGING
will NOT be recoverable till a backup is taken after the NOLOGGING
operation is complete.  More details on NOLOGGING can be found at:
http://www.jlcomp.demon.co.uk/faq/nologging.html

_disable_logging, on the other hand, says "I don't care about this
database, don't do any logging, if the database crashes, it's worthless,
game reset, start over."  This is quite different from, and far more
dangerous than, NOLOGGING operations.

Hope that helps,

-Mark

--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning

"There are 10 types of people in the world:  Those who understand
binary, and those who don't."

-----Original Message-----
From: oracle-l-bounce@freelists.org
[mailto:oracle-l-bounce@freelists.org] On Behalf Of Juan Carlos Reyes
Pacheco
Sent: Thursday, February 02, 2006 1:40 PM
To: Li-Shan Cheng
Cc: oracle-l@freelists.org
Subject: Re: Disable logging in tablespace vs using hidden parameter
_disable_logging

HI Li, thanks I know that, I RTFM,

It is an open question about how to get the _disable_logging effect
without using that parameter.

What I'm asking is  about applying no logging to all tablespaces before
import?
Compared to setting _disable_logging?
I don't know if some one knows about improvements.
For example
"setting nologgin to all tablespace I saved 1% of time, but I set this
other parameter too, etc.."
And any other comment about reducing logging activity without using the
_disable_logging parameter.
:)
--
http://www.freelists.org/webpage/oracle-l


------_=_NextPart_001_01C6282A.06A64003
Content-Type: text/x-vcard; name="Bobak, Mark.vcf"
Content-Transfer-Encoding: base64
Content-Description: Bobak, Mark.vcf
Content-Disposition: attachment;
 filename="Bobak, Mark.vcf"

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkJvYmFrO01hcmsNCkZOOkJvYmFrLCBNYXJrDQpP
Ukc6UHJvUXVlc3QgSW5mb3JtYXRpb24gYW5kIExlYXJuaW5nO0RhdGFiYXNlIEdyb3VwDQpUSVRM
RTpTb2Z0d2FyZSBBcmNoaXRlY3QsIFNyLVRQRA0KVEVMO1dPUks7Vk9JQ0U6NzM0Ljk3NS42MDg2
DQpBRFI7V09SSzo7RUNDNC1OMDFFMDQ7MTQwMCBFaXNlbmhvd2VyIFBhcmt3YXkNCkxBQkVMO1dP
Uks7RU5DT0RJTkc9UVVPVEVELVBSSU5UQUJMRTpFQ0M0LU4wMUUwND0wRD0wQTE0MDAgRWlzZW5o
b3dlciBQYXJrd2F5DQpFTUFJTDtQUkVGO0lOVEVSTkVUOk1hcmsuQm9iYWtAaWwucHJvcXVlc3Qu
Y29tDQpSRVY6MjAwNTEyMTNUMjIzNjU0Wg0KRU5EOlZDQVJEDQo=

------_=_NextPart_001_01C6282A.06A64003--
--
http://www.freelists.org/webpage/oracle-l