Database Tuning (MOSC)

MOSC Banner

Actual execution plan different from Explain plan, always.

edited Jan 29, 2009 12:11AM in Database Tuning (MOSC) 3 commentsAnswered
Hello,

We have a slow running print job, from 10043 trace,  Oracle dose full table scans for a SQL like this:

SELECT  *  FROM PRODDTA.F4211

WHERE  ( SDDOC = :KEY1 AND SDDCT = :KEY2 ) 

ORDER BY SDDOCO ASC,SDDCTO ASC,SDKCOO ASC,SDLNID ASC

Both columns are indexed in a single index. From explain plans for both bind variable and value version, the access path is by index. The index is used when SQL is submitted in SQL*Plus, fetching is very fast.

The problem is in a custom JDEdware print job. The SQL is generated by print job process, no SQL hint can be given. Full table scan always happen.

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