R
Rob Fitzpatrick
Guest
As we know, an object added to a DB without an area assignment will go into the schema area. As we also know, no application objects should go there. So the price of keeping the Schema Area clean is eternal vigilance. There is no way to prevent future mistakes that can cause objects being put in Type I storage. However in 11.x MT databases we have the concept of a default table area, a default index area, and a default LOB area for a tenant. My request is to extend this notion (for non-MT databases) to allow DBAs to designate a given Type II area as the default area for future tables (or indexes, or LOBs), database-wide. Then if an object is added without an area assignment it will go into the designated Type II area, if it exists, else fall back to the existing behaviour and put it in the Schema Area. If an object is added with an area assignment, then of course use the existing behaviour and put it where it has been assigned. And if, someday, you make the Schema Area a Type II area that would be nice too. But I won't hold my breath. And even if it did happen it wouldn't completely remove the need for the above enhancement.
Continue reading...
Continue reading...