SQL Performance (MOSC)

MOSC Banner

Optimizer Refusing to Use Seemingly Obvious Index

edited May 23, 2013 12:48AM in SQL Performance (MOSC) 11 commentsAnswered
I hope I am including everything it makes sense to without including too much extra information.
The system:

We are running Oracle 11.2.0.1. No purchased add-ons. Running on Oracle Unbreakable Linux 5.5.

There is 48 GB of RAM dedicated to our production instance where the following issue/concern is occurring.

The entities:

parent_table (
   primary_key number,
   client_id   number,
   data_point  number(10)
   attribution varchar2(500));

There are actually a great many additional attributes. I just listed all attribution as a single large varchar2 to suggest that each row can fill a fair chunk of space.

150,908 total rows
133,594 selected rows (client_id 58)
 11,239 blocks

create unique index idx_parent_data_point

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center