Poor Performance for Query with ROWNUM predicate and NESTED LOOPS.
Last updated on JANUARY 25, 2018
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.1]
Information in this document applies to any platform.
- Queries which include a ROWNUM predicate may get a suboptimal plan, typically including an expensive NESTED LOOPS join.
- Explain plan shows a join to a subquery or view which has incorrectly assumed that the cardinality returned will be that of the rownum predicate.
- Users might see a nested loop join in the plan when the query has a rownum predicate and contains a view.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms