Database DataWarehousing (MOSC)

MOSC Banner

materialized view usage

edited Jan 14, 2010 1:14AM in Database DataWarehousing (MOSC) 5 commentsAnswered
  We have 2 materialized views which are basically the same but partitioned differently.  Reports are either by posted date or transaction date.  We created the two separate materialized views in hopes that Oracle would choose the appropriate materialized view at query time dependent on if the query written against the base tables was by posted date or transaction date to take advantage of partition pruning.

In testing this I have found this not to be the case.  The query in question is based on posted date however Oracle is choosing to use the materialized view partitioned by transaction date.  When using the rewrite hint and hinting the materialized view on posted date the query has a much smaller cost, prunes as expected, and resolves much faster. 

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