Oracle7 Server Distributed Systems Volume II: Replicated Data

DBMS_REPCAT.RELOCATE_MASTERDEF

Purpose

To change your master definition site to another master site in your replicated environment. For additional information, refer to

Syntax

The parameters for the RELOCATE_MASTERDEF procedure are described in Table 12 - 159, and the exceptions are listed in Table 12 - 160. The syntax for this procedure is shown below:

DBMS_REPCAT.RELOCATE_MASTERDEF(
		gname				IN	VARCHAR2, 
		old_masterdef			IN	VARCHAR2, 
		new_masterdef			IN	VARCHAR2, 
		notify_masters		IN	BOOLEAN := TRUE,
		include_old_masterdef	IN	BOOLEAN := TRUE)

Parameter Description
gname The name of the object group whose master definition you want to relocate.
old_masterdef The fully qualified database name of the current master definition site.
new_masterdef The fully qualified database name of the existing master site that you want to make the new master definition site.
notify_masters If NOTIFY_MASTERS is TRUE, the procedure synchronously multicasts the change to all masters (including OLD_MASTERDEF only if INCLUDE_OLD_MASTERDEF is TRUE). If any master does not make the change, rollback the changes at all masters.
include_old_ masterdef If NOTIFY_MASTERS is TRUE and INCLUDE_OLD_MASTERDEF is also TRUE, the old master definition site is also notified of the change.

Table 12 - 159. Parameters for RELOCATE_MASTERDEF

Exception Description
nonmaster NEW_MASTERDEF is not a master site or the invocation site is not a master site.
nonmasterdef OLD_MASTERDEF is not the master definition site.
commfailure At least one master site is not accessible and NOTIFY_MASTERS is TRUE.

Table 12 - 160. Exceptions for RELOCATE_MASTERDEF

Usage Notes

It is not necessary for either the old or new master definition site to be available when you call RELOCATE_MASTERDEF. In a planned reconfiguration, you should invoke RELOCATE_MASTERDEF with NOTIFY_MASTERS TRUE and INCLUDE_OLD_MASTERDEF TRUE. If just the master definition site fails, you should invoke RELOCATE_MASTERDEF with NOTIFY_MASTERS TRUE and INCLUDE_OLD_MASTERDEF FALSE. If several master sites and the master definition site fail, the administrator should invoke RELOCATE_MASTERDEF at each operational master with NOTIFY_MASTERS FALSE.

Parameter	Description
`gname`	The name of the object group whose master definition you want to relocate.
`old_masterdef`	The fully qualified database name of the current master definition site.
`new_masterdef`	The fully qualified database name of the existing master site that you want to make the new master definition site.
`notify_masters`	If NOTIFY_MASTERS is TRUE, the procedure synchronously multicasts the change to all masters (including OLD_MASTERDEF only if INCLUDE_OLD_MASTERDEF is TRUE). If any master does not make the change, rollback the changes at all masters.
`include_old_ masterdef`	If NOTIFY_MASTERS is TRUE and INCLUDE_OLD_MASTERDEF is also TRUE, the old master definition site is also notified of the change.

Exception	Description
nonmaster	NEW_MASTERDEF is not a master site or the invocation site is not a master site.
nonmasterdef	OLD_MASTERDEF is not the master definition site.
commfailure	At least one master site is not accessible and NOTIFY_MASTERS is TRUE.