Manage Database Replication Definitions

A table, a function, a transaction, DDL, or a system stored procedure can be a replicated object. A database replication definition specifies filters for replicated objects—either including or excluding the same or entire replicated object from replication.

For example, to create a database replication definition:

create database replication definition rep_1C
  with primary at PDS.pdb
    replicate tables in (table1, table2)
    not replicate functions in (fc_a)
    not replicate system procedures
    replicate transactions
    replicate DDL

In this example, we are replicating:

table1 and table2
All functions except fc_a
All transactions
Supported DDL commands

We are not replicating:

Any database tables except table1 and table2
Function fc_a
Any system procedures

See Replication Server Reference Manual > create database replication definition for complete syntax and usage information.

Note: Database replication definitions do not support the options send-standby-all-columns, send-standby-all-parameters, and send_standby_repdef_cols. Where a database replication definition exists, Replication Server sends all columns or parameters.

Altering Database Replication Definitions
Use alter database replication definition to change a database replication definition.
Drop Database Replication Definitions
You can drop a database replication definition, but you must first have dropped all associated database subscriptions.
Database Replication Filters
Learn how replication filters work.

Parent topic: Manage Replicated Objects Using Multisite Availability