Oracle7 Server Distributed Systems Volume II: Replicated Data

DBMS_REPCAT.ADD_MASTER_DATABASE

Purpose

To add another master site to your replicated environment. This procedure regenerates all the triggers and their associated packages at existing master sites. You must call this procedure from the master definition site. For additional information, refer to

Syntax

The parameters for the ADD_MASTER_DATABASE procedure are described in Table 12 - 64, and the exceptions are listed in Table 12 - 65. The syntax for this procedure is shown below:

DBMS_REPCAT.ADD_MASTER_DATABASE(
             gname                 IN  VARCHAR2,
             master                IN  VARCHAR2, 
             use_existing_objects  IN  BOOLEAN := TRUE, 
             copy_rows             IN  BOOLEAN := TRUE,
             comment               IN  VARCHAR2 := '',
             propagation_mode      IN  VARCHAR2 := 'ASYNCHRONOUS')

Parameter Description
gname The name of the object group being replicated. This object group must already exist at the master definition site.
master The fully qualified database name of the new master database.
use_existing_objects Indicate TRUE if you want to reuse any objects of the same type and shape that already exist in the schema at the new master site. See for more information on how these changes are applied.
copy_rows Indicate TRUE if you want the initial contents of a table at the new master site to match the contents of the table at the master definition site.
comment This comment is added to the MASTER_COMMENT field of the RepSite view.
propagation_mode Method of forwarding changes to and receiving changes from new master database. Accepted values are synchronous and asynchronous.

Table 12 - 64. Parameters for ADD_MASTER_DATABASE

Exception Description
nonmasterdef The invocation site is not the master definition site.
notquiesced The replicated object group has not been suspended.
missingrepgroup The object group does not exist at the given database site.
missingobject A member of the replicated object group does not exist at the master definition site with a database status of VALID. If a package, package body, procedure, or function is invalid, Oracle recompiles the object once, in an attempt to make it valid.
commfailure The new master is not accessible.
typefailure An incorrect propagation mode was specified.
notcompat Compatibility mode must be 7.3.0.0 or greater to use synchronous propagation.
repcompatnum The GNAME is not an existing database schema at the remote master site and the remote master site is a pre-release 7.3 site.
duplrepgrp The master site already exists.

Table 12 - 65. Exceptions for ADD_MASTER_DATABASE

Parameter	Description
`gname`	The name of the object group being replicated. This object group must already exist at the master definition site.
`master`	The fully qualified database name of the new master database.
`use_existing_objects`	Indicate TRUE if you want to reuse any objects of the same type and shape that already exist in the schema at the new master site. See for more information on how these changes are applied.
`copy_rows`	Indicate TRUE if you want the initial contents of a table at the new master site to match the contents of the table at the master definition site.
`comment`	This comment is added to the MASTER_COMMENT field of the RepSite view.
`propagation_mode`	Method of forwarding changes to and receiving changes from new master database. Accepted values are synchronous and asynchronous.

Exception	Description
nonmasterdef	The invocation site is not the master definition site.
notquiesced	The replicated object group has not been suspended.
missingrepgroup	The object group does not exist at the given database site.
missingobject	A member of the replicated object group does not exist at the master definition site with a database status of VALID. If a package, package body, procedure, or function is invalid, Oracle recompiles the object once, in an attempt to make it valid.
commfailure	The new master is not accessible.
typefailure	An incorrect propagation mode was specified.
notcompat	Compatibility mode must be 7.3.0.0 or greater to use synchronous propagation.
repcompatnum	The GNAME is not an existing database schema at the remote master site and the remote master site is a pre-release 7.3 site.
duplrepgrp	The master site already exists.