Version 21c

General Information
Library Note Morgan's Library Page Header
Which has the higher priority in your organization: Deploying a new database or securing the ones you already have? Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
Purpose These procedures are called during migration of V7.3.x to V8.0.2 using the export/import utilities: the import utility will call it
They are private functions to be released in PL/SQL binary form and are shared by a snapshot and master partitions.

Why they are still hanging around in version 20c is a total mystery given that every other piece of Advanced Replication has been dropped from the product.
STANDARD (only)    
Documented No
First Available Not known
Security Model Owned by SYS with EXECUTE granted to the IMP_FULL_DATABASE role
Source {ORACLE_HOME}/rdbms/admin/dbmshrmg.sql
After a V8 import, this procedure is called to clean up any V7 replication objects (mlog$_%, triggers) that require modification

Overload 1
dbms_repcat_mig.cleanup_import(dump_version IN NUMBER);
exec dbms_repcat_mig.cleanup_import(19.5);

PL/SQL procedure successfully completed.
After a full replicated db import, this routine is invoked to perform any necessary cleanup

Overload 2
dbms_repcat_mig.cleanup_import(expseal IN VARCHAR2);
Called after doing a full import of a database with replicated data dbms_repcat_mig.post_import;
exec dbms_repcat_mig.post_import;

PL/SQL procedure successfully completed.
Called before doing a full import of a database with replicated data dbms_repcat_mig.pre_import;
exec dbms_repcat_mig.pre_import;

PL/SQL procedure successfully completed.

Related Topics
Built-in Functions
Built-in Packages
What's New In 19c
What's New In 20c-21c

Morgan's Library Page Footer
This site is maintained by Dan Morgan. Last Updated: This site is protected by copyright and trademark laws under U.S. and International law. © 1998-2019 Daniel A. Morgan All Rights Reserved