140 likes | 418 Vues
Chapter 3 - OFA. Database Processing. Chapter 3. Logical Database Layouts. Chapter 3 - OFA. Optimal Flexible Architecture. image source: http://www.iprimus.ca/~mariolam/flexibility.html. Chapter 3 - OFA. OFA.
E N D
Chapter 3 - OFA Database Processing Chapter 3 Logical Database Layouts
Chapter 3 - OFA Optimal Flexible Architecture image source: http://www.iprimus.ca/~mariolam/flexibility.html
Chapter 3 - OFA OFA • The OFA standard is a set of configuration guidelines for fast, reliable Oracle databases that require little maintenance. • At the highest level, it is designed to logically separate objects by object type and activity type. • It is the structure you get if you create a default database
Chapter 3 - OFA System tablespace • At a minimum you have to have a SYSTEM tablespace • It would be a very poor design to put all objects into one tablespace. • Data dictionary should be isolated
Chapter 3 - OFA Data tablespaces • Our author suggests that data tablespaces should be organized by application • The data for each application should isolated from the system tables and other tablespaces • For example, human resources, accounting, sales, inventory management • One database, many applications
Chapter 3 - OFA Index tablespaces • Because of concurrent I/O, indexes should be stored separately from their associated tables. • In my installation, my assumption was that the indexes would be in the indx01.dbf file • I queried the dba_indexes view and found...
Chapter 3 - OFA Index tablespaces Primary Key indexes in User tablespace
Chapter 3 - OFA Index tablespaces USER tablespace is in the USERS01.DBF file.
Chapter 3 - OFA Index tablespaces So I moved it...
Chapter 3 - OFA Index tablespaces And now it’s in the index data file
Chapter 3 - OFA Tools tablespaces • Used to store tables created by Oracle or 3rd party tools (applications) that create tables owned by the SYSTEM account
Chapter 3 - OFA User tablespaces • For development projects • All other tables should be created by the DBA
Chapter 3 - OFA Other tablespaces • RBS • Temp
Chapter 3 - OFA OFA • Further divide the previous tablespaces into pairs of high/low usage tablespaces • Common-sense Logical Layouts • Segment types that are used in the same way should be stored together • The system should be designed for standard usage • Separate areas should exist for exceptions • Contention among tablespaces should be minimized • The data dictionary should be isolated