| Filename |
Features |
| repdoc.txt |
Contains replication setup, removal and
troubleshooting instructions. The information within this file is
customized to match the actual names of the database instances and
names of the files created by Repgen. |
| repprecheck.sql |
Checks the values of the critical init.ora
entries required for replication to function properly, and prints
this information on the command line.
NOTE: This file needs to be run to verify the parameters at each
master site. |
| repinitora.txt |
Contains the critical init.ora entries
required for replication to function correctly.
NOTES: These parameters must be set at each master site. These parameters
may be tuned to lower values for smaller servers, the values listed
here are for large SMP servers. The job_queue_interval parameter
is obsolete and is not required in Oracle 9.0.1. |
| reptnsnamesora_prod3.txt |
Contains the tnsnames.ora entries required
for the replication related database links to work. The contents
of this file are used on the prod3 master site. |
| reptnsnamesora_prod5.txt |
Contains the tnsnames.ora entries required
for the replication related database links to work. The contents
of this file are used on the prod5 master site. |
| replistenerora_prod3.txt |
Contains the listener.ora entries for
an additional listener which allows the replication related database
links to work.
NOTES: The contents of this file are not required if there isn't
a 2nd listener dedicated for use by replication.
This file must only be used at the master site prod3. |
| replistenerora_prod5.txt |
Contains the listener.ora entries for
an additional listener which allows the replication related database
links to work.
NOTES: The contents of this file are not required if there isn't
a 2nd listener dedicated for use by replication.
This file must only be used at the master site prod5. |
| repcolumns.sql |
Creates the date_modified and site_id
columns for all replicated tables.
This file needs to be run at each master site (unless all of the
data was exported/imported into the other master sites from the
master definition site after making these changes). |
| reppkcolumns_prod3.sql |
Creates the primary key column for all
replicated tables and makes it the primary key for the table. The
commands in this file are designed to be used to fix up tables not
containing a primary key which were not originally designed to be
replicated. Different versions of this file are created for each
master site in case additional post-generation customization is
required by the DBA.
This file is used for the master site prod3. |
| reppkcolumns_prod5.sql |
Creates the primary key column for all
replicated tables and makes it the primary key for the table. The
commands in this file are designed to be used to fix up tables not
containing a primary key which were not originally designed to be
replicated. Different versions of this file are created for each
master site in case additional post-generation customization is
required by the DBA.
This file is used for the master site prod5. |
| repsynonyms.sql |
Creates public synonyms for all replicated
tables. The use of this file is optional, but is created as a convenience
for the DBA.These synonyms would be useful if fully qualified table
names weren't being used. |
| reptriggers.sql |
Creates replication related triggers
for all replicated tables to support date_modified and site_id columns
used for replication conflict resolution.
NOTE: This file needs to be run at each master site. |
| repsequences_prod3.sql |
Creates sequences for all replicated
tables for the master site prod3.
NOTE: This script should only be run on the master site prod3. Each
master site has sequence starting values which are different in
order to avoid primary key conflicts when replicating data between
sites. This file should be run after any export files have been
imported into the master site to insure that sequences from the
master definition site are not accidently used from the export/import
process. |
| repsequences_prod5.sql |
Creates sequences for all replicated
tables for the master site prod5.
NOTE: This script should only be run on the master site prod5. Each
master site has sequence starting values which are different in
order to avoid primary key conflicts when replicating data between
sites. This file should be run after any export files have been
imported into the master site to insure that sequences from the
master definition site are not accidently used from the export/import
process. |
| idtriggers.sql |
Creates primary key "ID" triggers
for all replicated tables.
NOTE: This file needs to be run at each master site. |
| repsetup_prod3.sql |
Performs the initial replication setup tasks of
creating the replication tablespace,
running catrep.sql - to add replication support to the database,
moving replication tables out of the SYSTEM tablespace,
creating the repadmin user,
assigning the correct roles to the repadmin user,
creating the private and public database links,
creating the purge and push jobs.
NOTES: This file must only be run at the master site prod3.
The output of this file is customized by Repgen depending upon
whether version 9.0.1 or lower is being used. Scripts generated
for Oracle versions lower than 9.0.1 make use of svrmgrl, and
versions 9.0.1 and above use sqlplus. This change is made in order
to avoid bugs with older versions of sqlplus which sometimes occur
when starting up and shutting down databases. This file is generally
only executed once, in order to prepare the database for replication.
|
| repsetup_prod5.sql |
Performs the initial replication setup
tasks of
creating the replication tablespace,
running catrep.sql - to add replication support to the database,
moving replication tables out of the SYSTEM tablespace,
creating the repadmin user,
assigning the correct roles to the repadmin user,
creating the private and public database links,
creating the purge and push jobs.
NOTES: This file must only be run at the master site prod5.
The output of this file is customized by Repgen depending upon whether
version 9.0.1 or lower is being used. Scripts generated for Oracle
versions lower than 9.0.1 make use of svrmgrl, and versions 9.0.1
and above use sqlplus. This change is made in order to avoid bugs
with older versions of sqlplus which sometimes occur when starting
up and shutting down databases. This file is generally only executed
once, in order to prepare the database for replication. |
| repaddgroup.sql |
Adds each replication group to all master
sites
NOTE: This file must only be run at the master definition site prod3. |
| repaddtable.sql |
Adds tables to each replication group
along with the conflict resolutionmethods and conflict resolution
column grouping to all master sites
NOTE: This file must only be run at the master definition site prod3. |
| repregen.sql |
Regenerates replication
support for all tables.
NOTE: When running repregen, do not run the entire file at once.
Select 5 tables at a time from a single group, run the commands,
then keep doing this until all of the tables for the group have
been completed. Then check Replication Manager for status, and manually
apply administrative requests until the queue is empty.
This file must only be run at the master definition site prod3. |
| represume.sql |
Resumes master activity for all replication
groups.
NOTE: This file must only be run at the master definition site prod3. |
| repcheck_mdef.sql |
Contains the PL/SQL commands
for creating the replication_check procedure. The replication_check
procedure can be scheduled thru an OEM job to check replication
status and it will then send an email if the table counts are off
by more than 2 records. This procedure is to be installed at the
master def site, and is owned by the repadmin account. |
| repcheck_no_mdef.sql |
Contains the PL/SQL commands for creating
the replication_check procedure. The replication_check procedure
can be scheduled thru an OEM job to check replication status and
it will then send an email if the table counts are off by more than
2 records. This procedure is to be installed at a non-master def
site, and is owned by the repadmin account. Database links must
be created to each of the sites which are to be monitored by this
procedure. |
| repsuspend.sql |
Suspends master activity for all replication
groups
NOTE: This file must only be run at the master definition site prod3. |
| repremovegroup.sql |
Removes each replication group and its
conflict resolution methods and conflict resolution column grouping
from all master sites.
NOTE: This file must only be run at the master definition site prod3. |
| repremovesetup_prod3.sql |
Removes the initial replication setup tasks by
dropping the replication tablespace
running catrepr.sql - to remove replication support to the database
dropping the repadmin user
dropping the private and public database links
removing the purge and push jobs.
This file must only be run at the master site prod3.
|
| repremovesetup_prod5.sql |
Removes the initial replication setup
tasks by
dropping the replication tablespace
running catrepr.sql - to remove replication support from the database
dropping the repadmin user
dropping the private and public database links
removing the purge and push jobs.
This file must only be run at the master site prod5. |
