This question was LOCKED with a PROPOSED ANSWER and awaits your decision today. Once a question is LOCKED with a Proposed Answer, few new experts will step in to help on that question, since the assumption is, you've been helped. If the Proposed Answer helped you, please accept it and award that expert. If it did not help you, please reject it and add comments as to status and what else is needed.
If you wish to award multiple experts, just comment here with detail, I'll respond as soon as possible. As it stands today, you asked the question, got help and not one expert was awarded for the contribution(s) made. Your response is needed. I'll monitor through month end, and if you've not returned to complete this, we'll need to decide. Expert input is welcome (as always) to determine the outcome here if the Asker does not respond.
Your response in finalizing this (and ALL) your question(s) is appreciated.
Moondancer
Community Support Moderator @ Experts Exchange
Main Topics
Browse All Topics





by: dbalaskiPosted on 2001-02-11 at 18:44:57ID: 5833408
I think you hit the following bug:
NT() if the column is not aliased.
BUG 814851
Description: If a materialized view is created with an aggregate as a column,
such as sum(b), then a failure can occur during refresh with
DBMS_MVIEW.REFRESH_DEPENDE
Workaround: Provide an alias for such columns.
example:
create materialized view PURCHASETOTAL
......
select id, sum(itemcost) SUMCOST
from purchases.......
I had the same problem -- this seems to have fixed it...
hope this solves it for you...
dBalaski