Oracle High Performance Tuning for 9i and 10g
This text covers the three parts of tuning an Oracle database: data modeling, SQL code tuning, and physical database configuration, and explains both problem detection and resolution.
TABLE OF CONTENTS Oracle High Performance Tuning for 9i and 10g
Chapter 13: Object Tuning
Overview
There are two layers to object physical tuning. The first layer allows for special behavior applied to objects such as tables and indexes. These special behaviors will be covered in this chapter. The second layer is explicit block and extent level tuning within objects. Explicit block and extent level tuning is what I like to call low-level architecture and will be covered in Chapter 14.
This chapter looks at object-level physical tuning. What is object-level physical tuning? This subject encompasses changes to an object, such as a table, which involve changing the underlying physical structure without necessarily affecting block structure. This chapter is split into the different objects such as tables, indexes, and sequences. Much of the detail for many object types is covered in the first section on tables. Each subsequent section is expanded to cater for details specific to the different object types.
13.1 Tables
So what can be done with table objects?
13.1.1 Caching
This option is much like the keep and recycle buffer pools from a previous version of Oracle Database and applies to full table scans only. Caching will allow forcing of small static tables into MRU (most recently used) cache and large seldom used tables into LRU (least recently used) cache.
For my Accounts schema I could do something like that shown as follows. The GeneralLedger and StockMovement tables are large and I would like to force any full table scans on very large tables out of cache as soon as possible. Small...
Copyright Elsevier Inc. 2004 under license agreement with Books24x7
