BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

   
Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





   

 

 

 

Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation

 

 


 

 

 

 

   
 


Oracle Unrecoverable Table Option

Oracle Tips by Burleson Consulting
Using Oracle’s UNRECOVERABLE Option

Please note that the UNRECOVERABLE option has been deprecated and replaced with the NOLOGGING option.

* Create index . . . unrecoverable--This is the most common use of the unrecoverable clause, and certainly the one that makes the most sense from an Oracle perspective. Regardless of any transaction failures, an index can always be re-created by dropping and redefining the index, so having an incomplete or corrupt index would never be a problem.

* Alter table . . . add constraint . . . unrecoverable--As we know, when a referential integrity constraint is added to a table, the Oracle software will sometimes create an index to enforce the constraint. Primary key, foreign key, and unique constraints may cause Oracle to create an index, which is built in unrecoverable mode.

* SQL*Loader--SQL*Loader is generally used when initially populating Oracle tables from external flat files. For very large numbers of inserts, it is best to leave the default. We already know that in the unlikely event of an abnormal termination, the incomplete tables must be dropped and SQL*Loader run again.

This is an excerpt from "High Performance Data Warehousing", copyright 1997. To learn more about Oracle, try "Oracle Tuning: The Definitive Reference", by Donald K. Burleson.  You can buy it direct from the publisher at 30% off here:

http://www.rampant-books.com/book_1002_oracle_tuning_definitive_reference_2nd_ed.htm

|

 

Remote DBA Service
 

Oracle Tuning Book

 

Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software

 

 

 

 

 

 

BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.