Versions Compared

Old Version 1

changes.mady.by.user Arjen Visser

Saved on

compared with

New Version Current

changes.mady.by.user Jan Suchanek (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Whole database (except sys and system objects).
  • Whole schemas.
  • Individual tables.
  • Partial tables.  Filtering can be done by row level.
  • Partial tables.  Certain columns can be excluded.
  • PL/SQL1

Dbvisit Replicate replicates both:

  • DML (data changes)
  • DDL Not all DDL is supported. For example create tablespace is not supported. DDL  DDL is only supported for when the target is an Oracle target database.(structure changes)

Dbvisit Replicate does NOT replicate:

  • Triggers
  • Global Temporary Tables
  • Constraints
  • Sequences
  • Database structure
  • ALTER DATABASE commands
  • ALTER SYSTEM commands

 

Note
title1

PL/SQL replication works as follows:

  • Dbvisit Replicate does not support creating the initial copy of the PL/SQL code. The initial copy must be manually exported from the source database and imported to the target altogether with instantiated data. You may use DataPump or legacy Exp/Imp.
  • Dbvisit Replicate replicates all alter/drop procedure/function/package/package body commands. Dbvisit Replicate does not replicate the actual code, Dbvisit Replicate replicates all of the DDLs for it.
  • Dbvisit Replicate currently does not replicate triggers, java, types, objects, synonyms, indextypes, mining models, editions, assemblies, flashback archives.
Note
titleExcluded Objects

By default certain objects are excluded. The Oracle Compression Advisor creates tables with name like DBMS_TABCOMP_TEMP_CMP . These tables are automatically excluded from replication.
Oracle scheduler creates tables with name like SCHEDULER$_. These tables are automatically excluded from replication.