Transportable Tablespace Using Datapump Does Not Create RUPD$ Tables of the Materialized View Log
(Doc ID 753471.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 188.8.131.52 [Release 10.1 to 11.1]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Using transportable tablespaces (TTS) via data pump to export the tablespace that contains the materialized view log, does not create the internal RUPD$_<tablename> tables upon import.
An updatable materialized view is one you can use to insert, update, or delete base table rows (master table). It is created with the FOR UPDATE clause and used in conjunction with Oracle Advanced Replication. An updatable materialized view should not be confused with a read-only materialized view; read-only materialized views do not update the base table rows (master table).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document