My Oracle Support Banner

How to Avoid Capturing changes made by EXP/IMP Session (Doc ID 788906.1)

Last updated on JANUARY 02, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.2 [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
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
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 12.1.0.2


Goal

Generally streams would capture all the changes made by an export/import (expdp/impdp) session based on the capture rules created (TABLE level, SCHEMA level or GLOBAL rules). Sometimes it would necessary to resynchorize few of these tables; all of these table or may be the whole schema itself by export and import may not be required to capture and replicate. The changes made by the export and import should be applied only to a single database. This document explains how to avoid capturing changes which are made by an import session.

Solution

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
Goal
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.