How to Improve Local Index Performance ??

Question

I need to store telecom CDR Data, which having following fields
CDR_DATE => Date
Telephone_Num=> Varchar2(20)
A=> Varchar2(40)
B=> Varchar2(10)
The Input Data volume is very High.. At Present 100 Million/Day
So i created the Oracle Partition Table with Date Range Partition.
The application will run always one type query
select * from CDR where Telephone_Num='&TNUM' AND CDR_DATE between JAN09 AND MAR09;
Question1
what will be Best way to create Index? Which can provide best performance and not degrade Daily Loading of Data.
Question2- For this I created the LOCAL Index
Create Index ABC ON CDR (CDR_DATE,Telephone_Num) LOCAL;
The Data fetching is using the index but I can see in Trace, the count of CONSISTENT GETS & PHYSICAL READS are very High.
So please suggest, Creating LOCAL INDEX is wise decision or not. Or any other way.
Thanks in advance.
Sumit
Edited by: Sumit2 on Jul 31, 2010 6:27 PM

Answer 1

Sumit2 wrote:
The Input Data volume is very High.. At Present 100 Million/Day
So i created the Oracle Partition Table with Date Range Partition.
The application will run always one type query
select * from CDR where Telephone_Num='&TNUM' AND CDR_DATE between JAN09 AND MAR09;
Question1
what will be Best way to create Index? Which can provide best performance and not degrade Daily Loading of Data.
Question2- For this I created the LOCAL Index
Create Index ABC ON CDR (CDR_DATE,Telephone_Num) LOCAL;
The Data fetching is using the index but I can see in Trace, the count of CONSISTENT GETS & PHYSICAL READS are very High.
You've created the index with the columns in the wrong order - your equality condition is on telephone number and the range-based condition is on the date, so you need the telephone number first in the index.
In fact, if your query is always going to be for whole days, you might as well exclude the date column from the index because it adds no precision to the query.
Another option to consider is to create the table as an index-organized table that starts with a primary key that (telephone number, cdr_date) so that all the data for a given telephone number is contained within a very small number of index leaf blocks. (However, if you rarely have more than a couple of calls per number per day then the supporting strategies for this approach will cost more than the benefit you get from building the data structure to match the query requirements.)
As far as data loading is concerned, your best strategy is to look at playing games with local indexes and partition exchange.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
There is a +"Preview"+ tab at the top of the text entry panel. Use this to check what your message will look like before you post the message. If it looks a complete mess you're unlikely to get a response. (Click on the +"Plain text"+ tab if you want to edit the text to tidy it up.)
+"Science is more than a body of knowledge; it is a way of thinking"+
+Carl Sagan+