For ASE: Primary database initialization (command pdb_init) verifies the database, and it will be configured with command sp_reptostandby pdb,'ALL'. This automatically marks all tables for replication, as well as all DDL commands.
For ASE only, individual tables can not be marked or
unmarked when the primary database is configured with sp_reptostandby (which
is the default ASE setting for a Mirror Activator environment).
For Oracle: The individual tables to be replicated must be marked, either explicitly using the pdb_setreptable command, or automatically during pdb_init processing when configuration parameter pdb_automark_tables is set to true.
To replicate transactions that affect the data in a table in the primary database, that table must be marked for replication, and replication must be enabled for the marked table.
By default, Mirror Replication Agent creates a replication
definition in Replication Server for each table that is explicitly
marked for replication. Also, Mirror Replication Agent creates a
replication definition for each table created during replication
(by reading the DDL command). If this is not the default behavior
desired, you can turn off automatic replication definition creation using
the pdb_auto_create_repdefs configuration
parameter.
The ra_init command no longer
causes pdb_auto_create_repdefs settings to
take effect. To create replication definitions after initialization,
execute rs_create_repdef all after ra_init for
all tables currently marked for replication.
Marking a table can be separate from enabling replication for that table. If the value of the pdb_dflt_object_repl parameter is true, replication is enabled automatically at the time a table is marked. See “Enabling and disabling replication for marked tables”.
When a table is marked for replication with the log-based Mirror Replication Agent for Oracle, the Mirror Replication Agent does the following:
Connects to the RASD
Records the mark status for the table in the RASD Article for that table.
When a table is marked, any subsequent operations that affect the data in that table are replicated.
