Here’s a little gem from the OTN database forum – why should the CPU usage of querying an “interval partitioned” table depend on the size of something that’s missing ?
(The most significant symptom is identified in a reply I wrote to the thread – but that’s only a step in the right direction).
