0 Replies Latest reply: Aug 3, 2012 9:05 AM by 675346 RSS

    Materialized view logs in cloned database

    675346
      Hi all!

      We have materlialized views and materlialized view logs in two separate databases which are connected with a database link. The MV logs are in DB1_PROD, which is the database being cloned. The database link goes from DB2_PROD (where the MVs are located) to DB1_PROD:

      DB2_PROD (materialized views) ----DB link---> DB1_PROD (materialized view logs)

      When cloning DB1_PROD to DB3_DEV, the MV logs still have a reference to DB2_PROD. However, there is no connection between DB3_DEV and DB2_PROD.

      In my opinion this is not harmful, but I would like to know if any of you can see any problems with this.

      In summary;
      DB1_PROD: Materialized view logs
      DB3_DEV: Materialized view logs. Clone of DB1_PROD
      DB2_PROD: Materialized views.
      DB1_PROD and DB3_DEV:
      select * from v$version;
      
      Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
      PL/SQL Release 10.2.0.4.0 - Production
      CORE     10.2.0.4.0     Production
      TNS for Linux: Version 10.2.0.4.0 - Production
      NLSRTL Version 10.2.0.4.0 - Production
      DB2_PROD:
      select * from v$version;
      
      
      Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
      PL/SQL Release 11.2.0.3.0 - Production
      CORE     11.2.0.3.0     Production
      TNS for Linux: Version 11.2.0.3.0 - Production
      NLSRTL Version 11.2.0.3.0 - Production
      Please let me know if you need further information.