The Repgen Sites folder tab contains fields
for entering site-specific information regarding the replication setup.
field: Site Name
The name which will be used for the dblink used to connect to this replication
site. Since the init.ora global_names parameter is expected to be set
to TRUE, this dblink will be given the same name as the database itself.
Note: The first master replication site which is entered in the
list of Site Names will become the Master Definition site.
The format of the Site Name may be db_name or db_name.db_domain (as
recommended by Oracle). Therefore the format "PROD1" or "PROD1.WORLD"
may be used. The format "PROD1.WORLD.COM" is not a valid format
because only 1 period symbol is allowed.
field: Hostname
The hostname of the database server. On database server with multiple
network interfaces, this should be the hostname of the interface which
allows general purpose access to Oracle via the Oracle Listener configured
on that interface.
Notes: Both forward and reverse DNS must match in order for databases
to be managed via the OEM/OMS server. The Oracle Replication Manager
needs to use the OEM/OMS server environment in order to allow connections
to multiple databases simultaneously.
field: SID
The SID or database name configured within the init.ora.
field: Site Priority
The priority of the replication site which is used for Site Priority
conflict resolution method. If a table update conflict can't be resolved
by the timestamp information, resolution will be attempted based upon
the priority levels of the sites making simultaneous updates to the
table. The site with the highest priority will prevail in this type
of conflict. Site priorities are are numbered from 1 - 100. Determination
of which site should be given the highest priority is implementation
specific. The decision may include factors such as which site performs
the most frequent updates, corporate headquarters location, network
and overall server reliability. Some implementations may simply assign
the Master Definition site as the highest priority site, if all other
factors are equal.
field: Repadmin Account
The name of the account which sets up, manages, and owns replication
objects.Usually, the name of this account will be "REPADMIN",
but it may be given any valid Oracle account name.
field: Repadmin Password
The password for the repadmin account.
Note: The password should not be "repadmin" for security
reasons. The repadmin account has full access to replicated and other
database tables, thus it should be protected with a good password.
field: Sequence Start Value
Every replicated table must have a primary key column. The simplest
type of primary key to set up is an incrementing value inserted with
a trigger (supplied with the SQL code in the reptriggers.sql file).
Primary key values must not conflict with each other when records are
created at each of the master sites. One way to prevent primary key
conflicts is by assigning a block a primary key values to each site.
A consistent and organized assignment method is recommended in order
to assist the DBA when troubleshooting problems. A large enough block
of numbers should be picked to insure that sites won't overflow their
assigned block of numbers. Therefore it may be helpful to assign starting
primary key values in blocks of 1 billion at each site. In a 3 site
setup, the first site (Master Def site) may start at 1G, the 2nd site
may start of 2G and the 3rd site may have Sequence Start Values starting
at 3G. For troubleshooting purposes it is only necessary to look at
the 1st digit of the primary key value in order to know the source of
the data.
Note: The code required to set up the sequences is located within
the repsequences_SID.sql filename which is custom-generated for each
master site.
field: Tnsnames Entry
The Tnsnames.ora entry used to access this site for replication purposes.
This value will often be the same as the database SID. However in situations
where a network interface is dedicated for use by replication (a good
idea), the tnsnames.ora entry will be different from the general purpose
tnsnames.ora entry.
Note: If a dbdomain was used for the Site Name then the dbdomain
suffix should also be used within this field.
field: Replication Tablespace Path/Filename
The name of the path/filename fto be used when creating the replication
tablespace during the replication setup process.
Note: Oracle does not always put replication related objects in the
replication tablespace even when the replication tablespace is used
as the default tablespace during the running of the catrep replication
setup script. The DBA may choose to move these objects out of the SYSTEM
tablespace manually by using "ALTER TABLE MOVE..." and then
rebuilding any associated indexes.
field: Replication Tablespace Size
The size in Mbytes for each of the replication tablespace.
field: SYSTEM Password
The password for the Oracle SYSTEM account at each server. This password
is used during the execution of the repsetup_SiteName.sql files when
using Oracle 8.1.5 and higher databases. The setup script logs into
the SYSTEM account and moves replication tables out of the SYSTEM tablespace
and into the REPLICATION tablespace, and rebuilds indexes into the DBA-specified
index tablespace. Please see Oracle Note# 1037317.6 for more info.
field: Oracle Home
The path to the Oracle Home directory at each master site.
field: SYS Password
The password used for logging into the SYS account. The SYS account
is used during the initial phases of the replication setup process (for
instance when running catrep.sql).
field: Replication Network Interface
The hostname of the network interface dedicated for use by replication.
If there is only one network interface installed in the server, then
this field will contain the same values as the Hostname field.
Note: Most UNIX systems will not route TCP/IP traffic to a 2nd network
interface unless it is assigned an IP address in another network or
subnet. For instance if the primary network interface used an IP address
of 10.1.0.10 with a subnet of 255.255.255.0, then the 2nd network interface
could potentually use an IP address of 10.2.0.10 with a subnet of 255.255.255.0.
However if the 2nd network interface were assigned an IP address of
10.1.0.11, then it would not appear to function because all of the network
traffic would get sent thru the 1st network interface.
The network administrator should be consulted prior to assigning IP
addresses or subnetes in order to insure that the site's security policy
is followed and to insure that access lists in switches, routers and
firewalls are updated properly.
field: INDEX Tablespace
The name of the tablespace used for storing indexes at each master site.
Replication related indexes which were originally located within the
SYSTEM tablespace are rebuilt into this DBA specified tablespace during
the running of the repsetup_SiteName.sql script.
field: Oracle Version
The version of the Oracle database installed at each master site. The
version needs to be entered as a 3 digit integer. This info enables
the customization of commands within the scripts.
