Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2006
    Posts
    4

    Unanswered: Materialized view refresh

    After upgrading to 10g, the following is
    happening:

    BEGIN
    dbms_refresh.REFRESH('REFGRP_PROFILE_MV_CEEMEA');
    END;
    Gives the following error

    ORA-12048: error encountered while refreshing materialized view "CRI_CEEMEA_ADMIN"."USER_ROLE_TITLE"
    ORA-02068: following severe error from CEEMEA_DBLINK_CRI
    ORA-03113: end-of-file on communication channel
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line


    2461

    BEGIN
    dbms_mview.REFRESH('USER_ROLE_TITLE');
    END;

    Gives the following error

    ORA-12008: error in materialized view refresh path
    ORA-02068: following severe error from CEEMEA_DBLINK_CRI
    ORA-03113: end-of-file on communication channel
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430

  2. #2
    Join Date
    Jan 2004
    Location
    Croatia, Europe
    Posts
    4,094
    Provided Answers: 4
    A blind guess? A materialized view query uses a function which works with a table in another database, or you used a synonym to a materialized view (instead of the MV itself).

    First example suggests that you have created a refresh group (REFGRP_PROFILE...).

    Here is the DBMS_REFRESH documentation page, so you may check it.

    As of your second example: it says
    following severe error from CEEMEA_DBLINK_CRI
    DBLINK suggests that it has something to do with the database link. If so, well, make sure materialized view is located in your local database. Otherwise, you can not refresh it.

    This is the DBMS_VIEW documentation page; perhaps you'd want to check what it says.

  3. #3
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    Also what database version is the CEEMEA_DBLINK_CRI link pointing to. When we upgraded a bunch of our databases from 8i to 10gr2, MVIEWS on the 10GR2 database always failed when trying to get data from the remaining 8i machine. This is a know problem and there is no work around.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •