RE: Please a parameter to disable undo, like _disable_logging

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.

Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----

From: Juan Carlos Reyes Pacheco [mailto:jreyes_at_dazasoftware.com]=20 Sent: Tuesday, October 05, 2004 8:23 PM
To: oracle-l_at_freelists.org
Subject: RE: Please a parameter to disable undo, like _disable_logging

thanks

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
Juan Carlos Reyes Pacheco
OCP
--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Wed Oct 06 2004 - 08:58:53 CDT