The fields under the Tables folder
tab contain table-specific information, for each table which will be
replicated within the database. Tables should be grouped together based
upon how data is written into the tables during a transaction. For instance
if a Customer and an Address table are always updated during a transaction,
then both tables should be grouped together within the same replication
group.
field: Replication Group Names
This field provides the master listing of all of the replication groups
which will be created during the setup of replication.
field: Group
The replication group where the table is located.
Note: Tables which are written together within a single database
transaction should reside within the same replication group. This grouping
is important for replication maintenance situations because individual
replication groups may be quiesced independently (with Oracle 8 versions
and above).
field: Schema
The schema which owns the table. The table must be owned by the same
schema at each of the master sites.
field: Table Name
The full name of the table.
field: Shortened Table Name
A version of the table name which has been shortened to 20 or fewer
characters. This version of the table name is used for creating the
names of the conflict resolution methods. The text "_cr_date"
is appended to the shortened table name, representing the fact that
"LATEST TIMESTAMP" is the 1st conflict resolution method,
followed by the "SITE PRIORITY" and "OVERWRITE"
methods.
Note: This shortened table name must be unique within a particular
schema or the database will be unable to create the conflict resolution
methods due to name conflicts.
field: Date Modified Column
The name of the column in the table which will store the latest table
modification date/time information. A dedicated date column is required
within each replicated table in order for conflict resolution methods
to operate correctly.
Note: If a Date column does not already exist in any of the tables,
this column and its associated trigger may be added with the SQL code
within the repcolumns.sql and reptriggers.sql files.
field: Site ID Column
The name of the column in the table which will store the name of the
replication master site which most recently modified the table. A dedicated
varchar2 column is required within each replicated table in order for
the Site Priority conflict resolution method to operate correctly.
Note: If a Varchar2 column does not already exist in any of the
tables, this column and its associated trigger may be added with the
SQL code within the repcolumns.sql and reptriggers.sql files.
