I know that this has been discussed before, but I am curious to know if there are any "new" features to people running on 10.2B (preferably on SP04)
Have an opportunity to redesign the database layout and was considering the following:
1) all large or heavy I/O tables to have their own area
2) All indices relating to #1 to have their own area
3) all other tables to be in a "data" area
4) All indices relating to #3 to have their own "index" area
for #1, is 64 rows per block still the "best" rough guide ?
for #2, is there any advantage to putting each index into it's own area, rather than putting all indices for a table into 1 area
for #2 and #4, what is the optimal or "best" rough guide to rpb ?
most of the #1 tables are write-once, read many or have a very high proportion of reads vs writes
are there any more "new" startup parameters relating to tuning ?
-B2 secondary buffer pool ?
Specific create and toss limits for individual Tables in the same Type II Storage Area as opposed to the default values in order to achieve better compaction for example on fields that grow over time as they are continually updated (eg a Comment, where you'd want that Toss limit to be higher and the create limit lower based on the minimum and maximum record size of the entry).
For a good primer on database storage design considerations, have a look at Tom Bascom's presentation Storage Optimization Strategies.
Slide deck: dbappraise.com/.../sos.pptx
Video (Tom at Progress Exchange Online 2010):
To address your questions:
If 128 is good then 256 is better...