Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • As we learned from today's Oracle Tuning class, disabling Automatic Storage Management (ASM) could potentially fix our index problems
  • Change Oracle's statistics gathering function to run between 03:00 - 04:00 instead at 22:00
    • Oracle assumes to be the only active user during stats gathering
    • All the tables, indexes, views need to be created in the same order via scripts
  • Switch to RBO (Rule Based Optimizer) for certain views
    • Eventual deterministic/stable performance after queries have been tuned
    • Need to be careful that we're not joining these non-analyzed tables to analyzed ones
    • We may need to switch our OPTIMIZER_MODE setting over to CHOOSE?
  • Keep in mind after rebuilding the CM tables there are only 2 tables and 2 queries that run into trouble regularly.  We should be careful not to implement DB wide strategies to attack these 2 problems.   We need to understand why they differ and see if they can be tuned. (KA)

Activity Log

Friday 10-12-2007

  • 15:57 (Patrick) The way things are currently configured on caje, the 5 tables will be switched at 6am and 6pm each
    day. The autostats window is now set for 5am Monday-Friday. That means the tables will have stats on them for at
    most one hour.

Thursday 10-11-2007

  • 06:07 (Patrick) Recreated 5 CM tables

...