Database Tuning (MOSC)

MOSC Banner

How to avoid full table scan?

edited Nov 11, 2010 4:31AM in Database Tuning (MOSC) 7 commentsAnswered
 Hi

I have a query with 4 tables in which two tables are

XLA_AE_HEADERS (AE_HEADER_ID,APPLICATION_ID)--->unique index

XLA_AE_LINES (AE_HEADER_ID,EVENT_ID,APPLICATION_ID)--->unique index

. in join these two i have written as

XH.AE_HEADER_ID=XL.AE_HEADER_ID

and XH.APPLICATION_ID=XL.APPLICATION_ ID

but Plan shows full table scan on Lines table.

Any clue to avoid full table scan and improve performance.

regards

Hina

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center