RE: Please a parameter to disable undo, like _disable_logging

Juan,

If you just want to create table from DBA_OBJECTS, use nologging, as
Connor already pointed out.


Mark J. Bobak
Oracle DBA
ProQuest Company
Ann Arbor, MI

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Juan Carlos Reyes
Pacheco
Sent: Wednesday, October 06, 2004 10:17 AM
To: DGoulet@xxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Please a parameter to disable undo, like _disable_logging


Hi Dick,
In my home computer took 2 hour to create a 100,000,000 records from
dba_objects, so I t hink is a good idea to=20
find a better way , obviously this is not to use in production database,
and
is not to save microseconds.

=20
Juan Carlos Reyes Pacheco
OCP
-------Original Message-------
=20
From: DGoulet@xxxxxxxx
Date: 10/06/04 10:05:52
To: jreyes@xxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Please a parameter to disable undo, like _disable_logging
=20
There are some things like this that I believe should not be done, even
in test. The reason is that now you've crippled a significant item for
database recovery for the purpose of shaving a couple of microseconds
off of the execution time. Problem with that is that when the same
application starts to run in production it will run slower than in test
& damanagement will want the same performance/crippled database in
production. Then when, not if, all hell breaks loose you're the one
trying to explain why the database can't be recovered. I personally
like having my test environment, not development, in a similar
configuration so that all of the background delays play out just like in
production.
=20
=20
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Juan Carlos Reyes Pacheco [mailto:jreyes@xxxxxxxxxxxxxxxx]=3D20
Sent: Tuesday, October 05, 2004 8:23 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Please a parameter to disable undo, like _disable_logging
=20
thanks
=20
but /*+ append */ too bypasses undo, and if you set _disable_logging you
run the same risk, if you have a problem.
I think for a test database could be acceptable. For example I'm trying
to create a 10 000 000 records in my home for testing purposes, so this
will be greatly welcome.
I bet there should be a way.
=20
=3D20
Juan Carlos Reyes Pacheco
OCP
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l

Other related posts: