Oracle Distributed Systems

Name

DBMS_REPCAT.RELOCATE_MASTERDEF

Synopsis

If your master definition site becomes unusable or if you simply want another site to serve that role, you can configure a different master site as the master definition site with the RELOCATE_MASTERDEF procedure. Follow these guidelines:

• If your relocation is planned (i.e., all sites are up and reachable), set the notify_masters and include_old_masterdef parameters to TRUE.

• If the current master definition site is not available, set the notify_masters parameter to TRUE, and set include_old_masterdef to FALSE.

• If the master definition site as well as some master sites are unavailable, invoke the RELOCATE_MASTERDEF procedure from each functioning master site with both the notify_masters and the include_old_masterdef parameters set to FALSE.

Neither the current master definition site nor the new master definition site need be reachable to run this procedure successfully from any given master site.

The specifications differ for Oracle7 and Oracle8 as follows.

Oracle7 specification:

PROCEDURE 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,
    sname IN VARCHAR2 := '')

Oracle8 specification:

PROCEDURE 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);

Parameters

Parameter Name	Description