Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Dbvisit Replicate can replicate on different levels. It can replicate:

  • 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 is only supported for if the target is an Oracle database.

Dbvisit Replicate does NOT replicate:

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

 

1

PL/SQL replication works as follows:

  • Dbvisit Replicate does not support creating the initial copy of the PL/SQL code.
  • Dbvisit Replicate replicates all create/alter/drop procedure/function/package/package body commands. Dbvisit Replicate does not replicate the actual code, Dbvisit Replicate replicates all DDLs for it.
  • Dbvisit Replicate currently does not replicate triggers, java, types, objects, synonyms, indextypes, mining models, editions, assemblies, flashback archives.

Excluded 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.

 

  • No labels