When to use _disable_logging on Oracle 10g Release 2
- From: Juan Carlos Reyes Pacheco <juancarlosreyesp@xxxxxxxxx>
- To: oracle list <Oracle-L@xxxxxxxxxxxxx>
- Date: Tue, 11 Oct 2005 13:11:03 -0400
Hi,
Well after a stress tests, and other test, in the previous days,
losing a test database because redo logs corruption.
using the parameter _disable_logging on Oracle 10g Release 2 and
thanks to several comments in this list I can say.
You can get useful improvements using this paramters, but...
1)
The behavior of this parameter is not as stable as it could seem,
additionally the fact this is not support by Oracle.
2)
The only reason I found feasible to use it is when you have to import
urgently (for example for a presentation) in 0:30 or tomorrow.
Otherwise you can end losing your database.
3)
Anyway if you want to use it don't forget do normal shutdown, and
never abort, and always avoid use immedaite.
4)
And you must know the difference between undo data and redo data,
obviously. To know how much improve you are expecting.
This parameter can be useful, but expect the unexpected, even if you
are carefull.
Thanks to every one who answered to the previos thread.
--
Oracle Certified Profesional 9i 10g
Orace Certified Professional Developer 6i
8 years of experience in Oracle 7,8i,9i,10g and developer 6i
--
//www.freelists.org/webpage/oracle-l
Other related posts:
