Updating a Materialized View.

Question

Hi,
I'm using Oracle 9.2.0.6.
We have a materialized view with this definition.
SET DEFINE OFF;
DROP SYNONYM APPSRO.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D;
DROP SYNONYM APPS.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D;
DROP MATERIALIZED VIEW FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D;
CREATE MATERIALIZED VIEW FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D
TABLESPACE APPS_TS_SUMMARY
NOCACHE
NOLOGGING
NOPARALLEL
BUILD DEFERRED
REFRESH FORCE ON DEMAND
WITH PRIMARY KEY
AS
SELECT
                         a.*
FROM
                         apps.ftbv_qt_esr_to_1st_esc_dtl_v a;
COMMENT ON TABLE FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D IS 'snapshot table for snapshot FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D';
GRANT ALTER, DELETE, INDEX, INSERT, REFERENCES, SELECT, UPDATE, ON COMMIT REFRESH, QUERY REWRITE, DEBUG, FLASHBACK ON  FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D TO APPS WITH GRANT OPTION;
GRANT SELECT ON  FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D TO APPSRO;
GRANT SELECT ON  FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D TO FTBV_REPORTING;
CREATE SYNONYM APPSRO.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D FOR FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D;
CREATE SYNONYM APPS.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D FOR FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D;We've updated the view that it's reading by adding a column 'CUSTOMER_NAME'. It looks like this.
CREATE OR REPLACE VIEW FTBV_QT_ESR_TO_1ST_ESC_DTL_V
(RESPONSE_TEAM, RESPONSE_COMMENTS, SALES_MGR, SALES_REP, DEAL_ID,
REQUEST_SUBMIT_DATE, RESPONSE_1ST_SUBMIT_DATE, ELAPSED_HRS, RESPONSE_1ST_SUBMIT_YYYY_MM, CUSTOMER_NAME)
AS
SELECT
          resp_1.team                                       AS response_team
        , resp_2.response_comments                          AS response_comments
        , user_r.sales_mgr_last                             AS sales_mgr
        , SUBSTR  ( deal.sales_rep_user_id, 2 )             AS sales_rep
        , TO_CHAR ( req.deal_id,'999999'      )             AS deal_id
        , req.submit_date                                   AS request_submit_date
        , resp_1.min_submit_date                            AS response_1st_submit_date
        , ROUND
            ( ftbv_om_ord_util.get_datetime_interval_char ( req.submit_date,resp_1.min_submit_date, 'dd', 'Y') * 24 ) +
            ( ftbv_om_ord_util.get_datetime_interval_char ( req.submit_date,resp_1.min_submit_date, 'hh', 'Y')      ) +
            ( ftbv_om_ord_util.get_datetime_interval_char ( req.submit_date,resp_1.min_submit_date, 'mi', 'Y') / 60 )
          , 2
          )                                                 AS elapsed_hrs
        , TO_CHAR ( resp_1.min_submit_date, 'YYYY-MM' )     AS response_1st_submit_yyyy_mm
        , cust.customer_name                                as customer_name
FROM      (
          SELECT    /*+ no_merge */
                    deal_id                                           AS deal_id
                  , team                                              AS team
                  , MIN ( submit_date )                               AS min_submit_date
          FROM
                    op_esc_prod
          GROUP BY
                    deal_id
                  , team
                                                               resp_1
          SELECT    deal_id                                           AS deal_id
                  , version_number                                    AS version_number
                  , team                                              AS team
                  , submit_date                                       AS submit_date
                  , CASE WHEN UPPER ( comments ) LIKE '%HI%TOUCH%'
                         THEN'High Touch'
                         WHEN UPPER ( comments ) LIKE 'HT%'
                         THEN'High Touch'
                         WHEN UPPER ( comments ) LIKE '%LO%TOUCH%'
                         THEN'Low Touch'
                         WHEN UPPER ( comments ) LIKE 'LT%'
                         THEN'Low Touch'
                         ELSE NULL
                    END                                               AS response_comments
          FROM
                    op_esc_prod
          )                                                    resp_2
          op_esr                                               req
          op_deal                                              deal
          op_customers                                         cust
          SELECT     user_id                                          AS user_id
                   , SUBSTR ( relation_id, 2 )                        AS sales_mgr_last
          FROM       op_user_relationship
          WHERE      relation                                          = 'SLSMGR'
                                                               user_r
WHERE
          resp_2.deal_id                                     = resp_1.deal_id         AND
          resp_2.team                                        = resp_1.team            AND
          resp_2.submit_date                                 = resp_1.min_submit_date
AND       req.deal_id                                        = resp_2.deal_id         AND
          req.version_number                                 = resp_2.version_number
AND       deal.deal_id                                       = req.deal_id
AND       user_r.user_id                                     = deal.sales_rep_user_id
AND       cust.op_customer_id                                = deal.op_customer_id
GROUP BY
          resp_1.team
        , resp_2.response_comments
        , user_r.sales_mgr_last
        , SUBSTR  ( deal.sales_rep_user_id, 2 )
        , TO_CHAR ( req.deal_id,'999999'      )
        , req.submit_date
        , resp_1.min_submit_date
        , TO_CHAR ( resp_1.min_submit_date, 'YYYY-MM' )
        , cust.customer_nameWhen we run the refresh we get the following error messages.
BEGIN dbms_snapshot.refresh('FTBV.FTBV_QT_ESR_TO_1ST_ESC_DTL_1D','C'); END;
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-00913: too many values
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
ORA-06512: at line 1I don't believe we're creating table for this MView I think we're just defining an MView and then populating it. For some reason it's not picking up the new column. Is there a reason why? What do I need to do?
Thanks

Answer 1

When you create an MV, Oracle automatically does create an underlying table with the same name. That is how it is a "materialized" view -- physical storage of the result set from the query defining the MV.
When you created this particular MV "FTBV_QT_ESR_TO_1ST_ESC_DTL_1D" ,
the "SELECT A.* FROM apps.ftbv_qt_esr_to_1st_esc_dtl_v a;"
was automatically translated to the specific columns in ftbv_qt_esr_to_1st_esc_dtl_v.
An table called FTBV_QT_ESR_TO_1ST_ESC_DTL_1D was actually created to store the results of the query. Therefore, it has the actual column names as well.
In fact, even if you created a View, the view gets created with the actual column names.
See :
SQL> create table a_1_t (col_1 number not null primary key, col_2 varchar2(5));
Table created.
SQL> insert into a_1_t values (1,'a');
1 row created.
SQL> commit;
Commit complete.
SQL> create view a_1_v as select * from a_1_t;
View created.
SQL> desc a_1_v
Name                                                                     Null?    Type
COL_1                                                                    NOT NULL NUMBER
COL_2                                                                             VARCHAR2(5)
SQL> create materialized view a_1_mv as select * from a_1_t;
Materialized view created.
SQL> desc a_1_mv
Name                                                                     Null?    Type
COL_1                                                                    NOT NULL NUMBER
COL_2                                                                             VARCHAR2(5)
SQL> select * from a_1_mv;
     COL_1 COL_2
         1 a
SQL> alter table a_1_t add (col_3 varchar2(10));
Table altered.
SQL> select * from a_1_v;
     COL_1 COL_2
         1 a
SQL> select * from a_1_mv;
     COL_1 COL_2
         1 a
SQL> exec dbms_mview.refresh(a_1_mv);
BEGIN dbms_mview.refresh(a_1_mv); END;
ERROR at line 1:
ORA-06550: line 1, column 26:
PLS-00357: Table,View Or Sequence reference 'A_1_MV' not allowed in this context
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
SQL> select col_1, col_2, col_3 from a_1_t;
     COL_1 COL_2 COL_3
         1 a
SQL> select col_1, col_2, col_3 from a_1_v;
select col_1, col_2, col_3 from a_1_v
ERROR at line 1:
ORA-00904: "COL_3": invalid identifier
SQL>I can still do a SELECT * from both the view A_1_V and the materialized view a_1_mv.
But I cannot see the 3rd column in either of them. (Note : This means that the view also wouldn't show the new column !!).
I cannot refresh the MV because there is physical storage of the columns.
Hemant K Chitale
http://hemantoracledba.blogspot.com