IS ORACLE HELPLESS IN REFRESHING COMPLEX MVIEW FAST??

Question

I have a mview with a complicated query.But I need to refresh it fast on commit.I would be grateful if you people could solve this prob anyway.My mview script is given below..
SELECT TAS.ANSWER_SET_ID ALGORITHM_ID,
          TAS2.ANSWER_SET_ID RULE_ID, TAS2.CODEVAL1 SEQUENCE_NO,
     DE.EFFECTIVE_FROM_DATE EFFECTIVE_DATE,
          DE.ALPHANUMERIC_CODE_VALUE STATUS,
     MN1.MESSAGE_TEXT STAT_CODE,
          MN2.MESSAGE_TEXT CREDIT_PERCENTAGE,
          MN3.MESSAGE_TEXT DEBIT_PERCENTAGE,
     MN4.MESSAGE_TEXT CREDIT_DOLLAR,
          MN5.MESSAGE_TEXT DEBIT_DOLLAR,
          MN6.MESSAGE_TEXT ELEMENT_INCLUDED_IN,
     MN7.MESSAGE_TEXT PREMIUM_BASED_ON,
          MN8.MESSAGE_TEXT PREM_RATING_ELEMENT,
     EXP1.MESSAGE_TEXT EXPIARY_DATE
FROM T_RULE_CONTEXT RC,
          T_ANSWER_SET TAS,
          T_ANSWER_SET TAS1,
     T_ANSWER_SET TAS2,
     T_DECISION_PARAMETER DP,
          T_DECISION_EXPRESSION DE,
     T_DECISION_MESSAGE DM1,
          T_DECISION_MESSAGE DM2,
          T_DECISION_MESSAGE DM3,
     T_DECISION_MESSAGE DM4,
          T_DECISION_MESSAGE DM5,
          T_DECISION_MESSAGE DM6,
     T_DECISION_MESSAGE DM7,
          T_DECISION_MESSAGE DM8,
     (SELECT MESSAGE_NOTE_ID, DM4.ANSWER_SET_ID FROM T_DECISION_MESSAGE DM4, T_ANSWER_SET TAS2 WHERE DM4.ANSWER_SET_ID = TAS2.ANSWER_SET_ID AND MESSAGE_NAME='EXPIARY_DATE') EXP,
     T_MESSAGE_NOTE MN1,
          T_MESSAGE_NOTE MN2,
          T_MESSAGE_NOTE MN3,
     T_MESSAGE_NOTE MN4,
          T_MESSAGE_NOTE MN5,
          T_MESSAGE_NOTE MN6,
          T_MESSAGE_NOTE MN7,
          T_MESSAGE_NOTE MN8,
     (SELECT DM5.MESSAGE_NOTE_ID A, DM5.ANSWER_SET_ID, MN4.MESSAGE_NOTE_ID B, MESSAGE_TEXT FROM T_DECISION_MESSAGE DM5, T_ANSWER_SET TAS3, T_MESSAGE_NOTE MN4 WHERE DM5.ANSWER_SET_ID = TAS3.ANSWER_SET_ID AND DM5.MESSAGE_NAME='EXPIARY_DATE' AND DM5.MESSAGE_NOTE_ID = MN4.MESSAGE_NOTE_ID(+)) EXP1
WHERE      RC.CONTEXT_NAME = 'ALGORITHMS'
AND      RC.QUESTION_SET_ID = TAS.QUESTION_SET_ID_PARENT
AND      TAS1.CODEVAL1 = 'NO'
AND      TAS1.QUESTION_SET_ID_PARENT(+) = TAS.QUESTION_SET_ID_CHILD
AND      TAS1.QUESTION_SET_ID_PARENT IN
                         (SELECT QUESTION_SET_ID_CHILD
                         FROM T_RULE_CONTEXT , T_ANSWER_SET
                         WHERE RC.CONTEXT_NAME = 'ALGORITHMS'
                         AND QUESTION_SET_ID = QUESTION_SET_ID_PARENT)
AND      TAS2.QUESTION_SET_ID_PARENT = TAS1.QUESTION_SET_ID_CHILD
AND      DP.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DE.DECISION_PARAMETER_ID = DP.DECISION_PARAMETER_ID
AND      DM1.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM2.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM3.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM4.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM5.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM6.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM7.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM8.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      TAS2.ANSWER_SET_ID = EXP.ANSWER_SET_ID(+)
AND      DM1.MESSAGE_NAME = 'STAT_CODE'
AND      DM2.MESSAGE_NAME = 'CREDIT_PERCENTAGE'
AND      DM3.MESSAGE_NAME = 'DEBIT_PERCENTAGE'
AND      DM4.MESSAGE_NAME = 'CREDIT_DOLLAR'
AND      DM5.MESSAGE_NAME = 'DEBIT_DOLLAR'
AND      DM6.MESSAGE_NAME = 'ELEMENT_INCLUDED_IN'
AND      DM7.MESSAGE_NAME = 'PREMIUM_BASED_ON'
AND      DM8.MESSAGE_NAME = 'PREM_RATING_ELEMENT'
AND      MN1.MESSAGE_NOTE_ID = DM1.MESSAGE_NOTE_ID
AND      MN2.MESSAGE_NOTE_ID = DM2.MESSAGE_NOTE_ID
AND      MN3.MESSAGE_NOTE_ID = DM3.MESSAGE_NOTE_ID
AND      MN4.MESSAGE_NOTE_ID = DM4.MESSAGE_NOTE_ID
AND      MN5.MESSAGE_NOTE_ID = DM5.MESSAGE_NOTE_ID
AND      MN6.MESSAGE_NOTE_ID = DM6.MESSAGE_NOTE_ID
AND      MN7.MESSAGE_NOTE_ID = DM7.MESSAGE_NOTE_ID
AND      MN8.MESSAGE_NOTE_ID = DM8.MESSAGE_NOTE_ID
AND      EXP.MESSAGE_NOTE_ID = EXP1.A(+)
IS THERE ANY WAY TO DO THIS OR ITS A LIMITATION OF ORACLE??

Answer 1

Hi,
Take a look on restrictions applied on fast refresh of materialized views:
General Restrictions:
1.) The materialized view must not contain references to non-repeating expressions like SYSDATE and ROWNUM.
2.) The materialized view must not contain references to RAW or LONG RAW data types.
Restrictions on Fast Refresh on Materialized Views with Joins Only:
1.) All restrictions from "General Restrictions on Fast Refresh".
2.) They cannot have GROUP BY clauses or aggregates.
3.) If the WHERE clause of the query contains outer joins, then unique constraints must exist on the join columns of the inner join table.
4.) If there are no outer joins, you can have arbitrary selections and joins in the WHERE clause. However, if there are outer joins, the WHERE clause cannot have any selections. Furthermore, if there are outer joins, all the joins must be connected by ANDs and must use the equality (=) operator.
5.) Materialized view logs must exist with rowids for all the base tables in the FROM list of the query.
In your case look on point 3 and 4. This might cause problems. Sort out issues relating to point 3 & 4. Then i hope that fast refreshing should work with your view.