Oracle8i Supplied Packages Reference Release 8.1.5 A68001-01 |
|
DBMS_REPCAT_RGT
controls the maintenance and definition of refresh group templates.
Subprogram | Description |
---|---|
ALTER_REFRESH_TEMPLATE procedure |
Lets the DBA alter existing deployment templates. |
ALTER_TEMPLATE_OBJECT procedure |
Alters objects that have been added to a specified deployment template. |
ALTER_TEMPLATE_PARM procedure |
Lets the DBA alter the parameters for a specific deployment template. |
ALTER_USER_AUTHORIZATION procedure |
Alters the contents of the |
ALTER_USER_PARM_VALUE procedure |
Changes existing parameter values that have been defined for a specific user. |
COMPARE_TEMPLATES function |
Lets a DBA compare the contents of two deployment templates. |
COPY_TEMPLATE function |
Lets the DBA copy a deployment template. |
CREATE_OBJECT_FROM_ EXISTING function |
Creates a template object definition from existing database objects and adds it to a target deployment template. |
CREATE_REFRESH_TEMPLATE function |
Creates the deployment template, which allows you to define the template name, private/public status, and target refresh group. |
CREATE_TEMPLATE_OBJECT function |
Adds object definitions to a target deployment template container. |
CREATE_TEMPLATE_PARM function |
Creates parameters for a specific deployment template to allow custom data sets to be created at the remote snapshot site. |
CREATE_USER_AUTHORIZATION function |
Authorizes specific users to instantiate private deployment templates. |
CREATE_USER_PARM_VALUE function |
Pre-defines deployment template parameter values for specific users. |
DELETE_RUNTIME_PARMS procedure |
Deletes a runtime parameter value that you defined using the |
DROP_ALL_OBJECTS procedure |
Lets the DBA drop all objects or specific object types from a deployment template. |
DROP_ALL_TEMPLATE_PARMS procedure |
Lets the DBA drop template parameters for a specified deployment template. |
DROP_ALL_TEMPLATE_SITES procedure |
Removes all entries from the |
DROP_ALL_TEMPLATES procedure |
Removes all deployment templates at the site where the procedure is called. |
DROP_ALL_USER_ AUTHORIZATIONS procedure |
Lets the DBA drop all user authorizations for a specified deployment template. |
DROP_ALL_USER_PARM_VALUES procedure |
Drops user parameter values for a specific deployment template. |
DROP_REFRESH_TEMPLATE procedure |
Drops a deployment template. |
DROP_SITE_INSTANTIATION procedure |
Removes the target site from the |
DROP_TEMPLATE_OBJECT procedure |
Removes a template object from a specific deployment template. |
DROP_TEMPLATE_PARM procedure |
Removes an existing template parameter from the |
DROP_USER_AUTHORIZATION procedure |
Removes a user authorization entry from the |
DROP_USER_PARM_VALUE procedure |
Removes a pre-defined user parameter value for a specific deployment template. |
GET_RUNTIME_PARM_ID function |
Retrieves an ID to be used when defining a runtime parameter value. |
INSERT_RUNTIME_PARMS procedure |
Defines runtime parameter values prior to instantiating a template. |
INSTANTIATE_OFFLINE function |
Generates a script at the master site that is used to create the snapshot environment at the remote snapshot site while offline. |
INSTANTIATE_ONLINE function |
Generates a script at the master site that is used to create the snapshot environment at the remote snapshot site while online. |
LOCK_TEMPLATE_EXCLUSIVE procedure |
Prevents users from reading or instantiating the template when a deployment template is being updated or modified. |
LOCK_TEMPLATE_SHARED procedure |
Makes a specified deployment template read-only. |
This procedure lets the DBA alter existing deployment templates. Alterations may include defining a new deployment template name, a new refresh group, or a new owner and changing the public/private status.
DBMS_REPCAT_RGT.ALTER_REFRESH_TEMPLATE ( refresh_template_name IN VARCHAR2, new_owner IN VARCHAR2 := '-', new_refresh_group_name IN VARCHAR2 := '-', new_refresh_template_name IN VARCHAR2 := '-', new_template_comment IN VARCHAR2 := '-', new_public_template IN VARCHAR2 := '-', new_last_modified IN DATE := to_date('1', 'J'), new_modified_by IN NUMBER := -1e-130);
This procedure alters objects that have been added to a specified deployment template. The most common changes may include altering the object DDL and/or assigning the object to a different deployment template.
Changes made to the template is reflected only at new sites instantiating the deployment template. Remote sites that have already instantiated the template need to re-instantiate the deployment template to apply the changes.
DBMS_REPCAT_RGT.ALTER_TEMPLATE_OBJECT ( refresh_template_name IN VARCHAR2, object_name IN VARCHAR2, object_type IN VARCHAR2, new_refresh_template_name IN VARCHAR2 := '-', new_object_name IN VARCHAR2 := '-', new_object_type IN VARCHAR2 := '-', new_ddl_text IN CLOB := '-', new_master_rollback_seg IN VARCHAR2 := '-', new_flavor_id IN NUMBER := -1e-130);
Exception | Description |
---|---|
miss_refresh_ template |
Deployment template name specified is invalid or does not exist. |
miss_flavor_id |
Flavor ID specified is invalid or does not exist. |
bad_object_type |
Object type is specified incorrectly. See Table 37-4 for a list of valid object types. |
miss_template_object |
Template object name specified is invalid or does not exist. |
dupl_template_object |
New template name specified in the |
Because the ALTER_TEMPLATE_OBJECT
procedure utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the ALTER_TEMPLATE_OBJECT
procedure. The following example illustrates how to use the DBMS_LOB
package with the ALTER_TEMPLATE_OBJECT
procedure:
DECLARE tempstring VARCHAR2(100); templob CLOB; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'CREATE SNAPSHOT snap_sales AS SELECT * FROM sales WHERE salesperson = :salesid and region_id = :region'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); DBMS_REPCAT_RGT.ALTER_TEMPLATE_OBJECT( refresh_template_name => 'rgt_personnel', object_name => 'SNAP_SALES', object_type => 'SNAPSHOT', new_ddl_text => templob); DBMS_LOB.FREETEMPORARY(templob); END; /
This procedure allows the DBA to alter the parameters for a specific deployment template. Alterations may include renaming the parameter or redefining the default value and prompt string.
DBMS_REPCAT_RGT.ALTER_TEMPLATE_PARM ( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2, new_refresh_template_name IN VARCHAR2 := '-', new_parameter_name IN VARCHAR2 := '-', new_default_parm_value IN CLOB := NULL, new_prompt_string IN VARCHAR2 := '-', new_user_override IN VARCHAR2 := '-');
Because the ALTER_TEMPLATE_PARM
procedure utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the ALTER_TEMPLATE_PARM
procedure. The following example illustrates how to use the DBMS_LOB
package with the ALTER_TEMPLATE_PARM
procedure:
DECLARE tempstring VARCHAR2(100); templob CLOB; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'REGION 20'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); DBMS_REPCAT_RGT.ALTER_TEMPLATE_PARM( refresh_template_name => 'rgt_personnel', parameter_name => 'region', new_default_parm_value => templob); DBMS_LOB.FREETEMPORARY(templob); END; /
This procedure alters the contents of the DBA_REPCAT_TEMPLATE_AUTH
view. Specifically, you can change user/deployment template authorization assignments. This procedure is helpful, for example, if an employee moves positions and requires the snapshot environment of another deployment template; the DBA simply assigns the employee the new deployment template and the user is authorized to instantiate the target template.
DBMS_REPCAT_RGT.ALTER_USER_AUTHORIZATION ( user_name IN VARCHAR2, refresh_template_name IN VARCHAR2, new_user_name IN VARCHAR2 := '-', new_refresh_template_name IN VARCHAR2 := '-');
This procedure changes existing parameter values that have been defined for a specific user. This procedure is especially helpful if your snapshot environment uses assignment tables; simply change a user parameter value to quickly and securely change the data set of a remote snapshot site.
See "Deployment Template Design" in the Oracle8i Replication manual for more information on using assignment tables.
DBMS_REPCAT_RGT.ALTER_USER_PARM_VALUE( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2, user_name IN VARCHAR2, new_refresh_template_name IN VARCHAR2 := '-', new_parameter_name IN VARCHAR2 := '-', new_user_name IN VARCHAR2 := '-', new_parm_value IN CLOB := NULL);
Because the ALTER_USER_PARM_VALUE
procedure utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the ALTER_USER_PARM_VALUE
procedure. The following example illustrates how to use the DBMS_LOB
package with the ALTER_USER_PARM_VALUE
procedure:
DECLARE tempstring VARCHAR2(100); templob CLOB; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'REGION 20'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); DBMS_REPCAT_RGT.ALTER_USER_PARM_VALUE( refresh_template_name => 'rgt_personnel', parameter_name => 'region', user_name => 'BOB', new_parm_value => templob); DBMS_LOB.FREETEMPORARY(templob); END; /
This function allows a DBA to compare the contents of two deployment templates. Any discrepancies between the two deployment templates is stored in the USER_REPCAT_TEMP_OUTPUT
table.
The COMPARE_TEMPLATES
function returns a number that you specify in the WHERE
clause when querying the USER_REPCAT_TEMP_OUTPUT
table. For example, if the COMPARE_TEMPLATES
procedure returns the number 10, then you would execute the following SELECT
statement to view all discrepancies between two specified templates (your SELECT
statement returns no rows if the templates are identical):
SELECT text FROM USER_REPCAT_TEMP_OUTPUT WHERE output_id = 10 ORDER BY LINE;
The contents of the USER_REPCAT_TEMP_OUTPUT
are lost after you disconnect or a ROLLBACK
has been performed.
DBMS_REPCAT_RGT.COMPARE_TEMPLATES ( source_template_name IN VARCHAR2, compare_template_name IN VARCHAR2) RETURN NUMBER;
Parameter | Description |
---|---|
source_template_name |
Name of the first deployment template to be compared. |
compare_template_ name |
Name of the second deployment template to be compared. |
Exception | Description |
---|---|
miss_refresh_ template |
The deployment template name to be compared is invalid or does not exist. |
This function allows the DBA to copy a deployment template. COPY_TEMPLATE
is helpful when a new deployment template will use many of the object contained in an existing deployment template. This function copies the deployment template, template objects, template parameters, and user parameter values. The DBA can optionally have the function copy the user authorizations for this template. The number returned by this function is used internally by Oracle to manage deployment templates.
This function also allows the DBA to copy a deployment template to another master site, which is helpful for deployment template distribution and to split network loads between multiple sites.
DBMS_REPCAT_RGT.COPY_TEMPLATE ( old_refresh_template_name IN VARCHAR2, new_refresh_template_name IN VARCHAR2, copy_user_authorizations IN VARCHAR2, dblink IN VARCHAR2 := NULL) RETURN NUMBER;
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
This function creates a template object definition from existing database objects and adds it to a target deployment template. The object DDL that created the original database object is executed when the target deployment template is instantiated at the remote snapshot site. This is ideal for adding existing triggers and procedures to your template. The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_OBJECT_FROM_EXISTING( refresh_template_name IN VARCHAR2, object_name IN VARCHAR2, sname IN VARCHAR2, oname IN VARCHAR2, otype IN VARCHAR2) RETURN NUMBER;
Exception | Description |
---|---|
miss_refresh_ template |
The specified refresh template name is invalid or missing. Query the |
bad_object_type |
The object type is specified incorrectly (see Table 37-24 for more information). |
dupl_template_object |
An object of the same name and type has already been added to the specified deployment template. |
objectmissing |
Existing object specified does not exist. |
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
This function creates the deployment template, which allows you to define the template name, private/public status, and target refresh group. Each time that you create a template object, user authorization, or template parameter, you reference the deployment template created with this function. This function adds a row to the DBA_REPCAT_REFRESH_TEMPLATES
view. The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_REFRESH_TEMPLATE ( owner IN VARCHAR2, refresh_group_name IN VARCHAR2, refresh_template_name IN VARCHAR2, template_comment IN VARCHAR2 := NULL, public_template IN VARCHAR2 := NULL, last_modified IN DATE := SYSDATE, modified_by IN VARCHAR2 := USER, creation_date IN DATE := SYSDATE, created_by IN VARCHAR2 := USER) RETURN NUMBER
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
This function adds object definitions to a target deployment template container. The specified object DDL is executed when the target deployment template is instantiated at the remote snapshot site. In addition to adding snapshots, this function can add tables, procedures, and other objects to your template. The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_TEMPLATE_OBJECT ( refresh_template_name IN VARCHAR2, object_name IN VARCHAR2, object_type IN VARCHAR2, ddl_text IN CLOB, master_rollback_seg IN VARCHAR2 := NULL, flavor_id IN NUMBER := -1e-130) RETURN NUMBER;
Parameter | Description |
---|---|
refresh_template_ name |
Name of the deployment template that you want to add this object to. |
object_name |
Name of the template object that you are creating. |
object_type |
The type of database object that you are adding to the template (i.e.,
|
ddl_text |
Contains the DDL that creates the object that you are adding to the template. Be sure to end your DDL with a semi-colon. (Remember, you can use a colon (:) to create a template parameter for your template object; see "Creating Snapshots with Deployment Templates" in the Oracle8i Replication book for more information. |
master_rollback_seg |
Specifies the name of the rollback segment to use when executing the defined object DDL at the remote snapshot site. |
flavor_id |
Defines the flavor ID for this template object. |
Exception | Description |
---|---|
miss_refresh_ template |
Specified refresh template name is invalid or missing. Query the |
bad_object_type |
Object type is specified incorrectly. See Table 37-24 for a list of valid object types. |
dupl_template_object |
An object of the same name and type has already been added to the specified deployment template. |
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
Because CREATE_TEMPLATE_OBJECT
utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the CREATE_TEMPLATE_OBJECT
function. The following example illustrates how to use the DBMS_LOB
package with the CREATE_TEMPLATE_OBJECT
function:
DECLARE tempstring VARCHAR2(100); templob CLOB; a NUMBER; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'CREATE SNAPSHOT snap_sales AS SELECT * FROM sales WHERE salesperson = :salesid'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); a := DBMS_REPCAT_RGT.CREATE_TEMPLATE_OBJECT( refresh_template_name => 'rgt_personnel', object_name => 'snap_sales', object_type => 'SNAPSHOT', ddl_text => templob, master_rollback_seg => 'RBS'); DBMS_LOB.FREETEMPORARY(templob); END; /
This function creates parameters for a specific deployment template to allow custom data sets to be created at the remote snapshot site. This function is only required when the DBA wants to define a set of template variables before adding any template objects (when objects are added to the template using the CREATE_TEMPLATE_OBJECT
function, any variables in the object DDL are automatically added to the DBA_REPCAT_TEMPLATE_PARMS
view).
The DBA typically uses the ALTER_TEMPLATE_PARM
function to modify the default parameter values and/or prompt strings (see ALTER_TEMPLATE_PARM procedure for more information). The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_TEMPLATE_PARM ( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2, default_parm_value IN CLOB := NULL, prompt_string IN VARCHAR2 := NULL, user_override IN VARCHAR2 := NULL) RETURN NUMBER;
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
Because the CREATE_TEMPLATE_PARM
function utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the CREATE_TEMPLATE_PARM
function. The following example illustrates how to use the DBMS_LOB
package with the CREATE_TEMPLATE_PARM
function:
DECLARE tempstring VARCHAR2(100); templob CLOB; a NUMBER; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'REGION 20'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); a := DBMS_REPCAT_RGT.CREATE_TEMPLATE_PARM( refresh_template_name => 'rgt_personnel', parameter_name => 'region', default_parm_value => templob, prompt_string => 'Enter your region ID:', user_override => 'Y'); DBMS_LOB.FREETEMPORARY(templob); END; /
This function authorizes specific users to instantiate private deployment templates. Users not authorized for a private deployment template are not able to instantiate the private template. This function adds a row to the DBA_REPCAT_AUTH_TEMPLATES
view.
Before you authorize a user, verify that the user exists at the master site where the user will instantiate the deployment template. The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_USER_AUTHORIZATION ( user_name IN VARCHAR2, refresh_template_name IN VARCHAR2) RETURN NUMBER;
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
This function is used to pre-define deployment template parameter values for specific users. For example, if you want to pre-defined the region parameter as WEST
for user 33456, then you would use the this function.
Any values specified with this function take precedence over default values specified for the template parameter. The number returned by this function is used internally by Oracle to manage deployment templates.
DBMS_REPCAT_RGT.CREATE_USER_PARM_VALUE ( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2, user_name IN VARCHAR2, parm_value IN CLOB := NULL) RETURN NUMBER;
Return Value | Description |
---|---|
<system generated number> |
System generated number is used internally by Oracle. |
Because the CREATE_USER_PARM_VALUE
function utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the this function. The following example illustrates how to use the DBMS_LOB
package with the CREATE_USER_PARM_VALUE
function:
DECLARE tempstring VARCHAR2(100); templob CLOB; a NUMBER; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'REGION 20'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); a := DBMS_REPCAT_RGT.CREATE_USER_PARM_VALUE( refresh_template_name => 'rgt_personnel', parameter_name => 'region', user_name => 'BOB', user_parm_value => templob); DBMS_LOB.FREETEMPORARY(templob); END; /
Use this procedure before instantiating a deployment template to delete a runtime parameter value that you defined using the INSERT_RUNTIME_PARMS
procedure.
DBMS_REPCAT_RGT.DELETE_RUNTIME_PARMS( runtime_parm_id IN NUMBER, parameter_name IN VARCHAR2);
Exception | Description |
---|---|
miss_template_parm |
The specified deployment template parameter name is invalid or missing. |
This procedure allows the DBA to drop all objects or specific object types from a deployment template.
DBMS_REPCAT_RGT.DROP_ALL_OBJECTS ( refresh_template_name IN VARCHAR2, object_type IN VARCHAR2 := NULL);
Exception | Description |
---|---|
miss_refresh_ template |
Specified deployment template name is invalid or does not exist. |
bad_object_type |
Object type is specified incorrectly. See Table 37-38 for a list of valid object types. |
This procedure allows the DBA to drop template parameters for a specified deployment template. The DBA can use this procedure to drop all parameters that are not referenced by a template objects or drop all objects that reference a parameter and the parameters themselves.
DBMS_REPCAT_RGT.DROP_ALL_TEMPLATE_PARMS ( refresh_template_name IN VARCHAR2, drop_objects IN VARCHAR2 := N);
Exception | Description |
---|---|
miss_refresh_ template |
Specified deployment template name is invalid or does not exist. |
This procedure removes all entries from the DBA_REPCAT_TEMPLATE_SITES
view, which keeps a record of sites that have instantiated a particular deployment template.
DBMS_REPCAT_RGT.DROP_ALL_TEMPLATE_SITES ( refresh_template_name IN VARCHAR2);
Parameter | Description |
---|---|
refresh_template_ name |
Name of the deployment template that contains the sites that you want to drop. |
Exception | Description |
---|---|
miss_refresh_ template |
Specified deployment template name is invalid or does not exist. |
This procedure removes all deployment templates at the site where the procedure is called.
DBMS_REPCAT_RGT.DROP_ALL_TEMPLATES;
None.
This procedure allows the DBA to drop all user authorizations for a specified deployment template. Executing this procedure removes rows from the DBA_REPCAT_AUTH_TEMPLATES
view.
This procedure might be implemented after converting a private template to a public template and the user authorizations are no longer required.
DBMS_REPCAT_RGT.DROP_ALL_USER_AUTHORIZATIONS ( refresh_template_name IN VARCHAR2);
Parameter | Description |
---|---|
refresh_template_ name |
Name of the deployment template that contains the objects that you want to drop. |
Exception | Description |
---|---|
miss_refresh_ template |
Specified deployment template name is invalid or does not exist. |
This procedure drops user parameter values for a specific deployment template. This procedure is very flexible in allowing the DBA to define a set of user parameter values to be deleted. For example, defining the following parameters have the effect:
refresh_template_name
: drops all user parameters for the specified deployment template.
refresh_template_name
, user_name
: drops all of the specified user parameters for the specified deployment template.
refresh_template_name
, parameter_name
: drops all user parameter values for the specified deployment template parameter.
refresh_template_name
, parameter_name
, user_name
: drops the specified user's value for the specified deployment template parameter (equivalent to DROP_USER_PARM
).
DBMS_REPCAT_RGT.DROP_ALL_USER_PARMS ( refresh_template_name IN VARCHAR2, user_name IN VARCHAR2, parameter_name IN VARCHAR2);
This procedure drops a deployment template. Dropping a deployment template has a cascading effect, removing all related template parameters, user authorizations, template objects, and user parameters (this procedure does not drop template sites).
DBMS_REPCAT_RGT.DROP_REFRESH_TEMPLATE ( refresh_template_name IN VARCHAR2);
Parameter | Description |
---|---|
refresh_template_ name |
Name of the deployment template to be dropped. |
Exception | Description |
---|---|
miss_refresh_ template |
The deployment template name specified is invalid or does not exist. Query the |
This procedure drops a template instantiation at a target site. This procedure removes all related meta data at the master site and disables the specified site from refreshing their snapshots.
DBMS_REPCAT_RGT.DROP_SITE_INSTANTIATION( refresh_template_name IN VARCHAR2, user_name IN VARCHAR2, site_name IN VARCHAR2, repapi_site_id IN NUMBER := -1e-130);
This procedure removes a template object from a specific deployment template. For example, a DBA would use this procedure to remove an outdated snapshot from a deployment template. Changes made to the template are reflected at new sites instantiating the deployment template. Remote sites that have already instantiated the template need to re-instantiate the deployment template to apply the changes.
DBMS_REPCAT_RGT.DROP_TEMPLATE_OBJECT ( refresh_template_name IN VARCHAR2, object_name IN VARCHAR2, object_type IN VARCHAR2);
This procedure removes an existing template parameter from the DBA_REPCAT_TEMPLATE_PARMS
view. This procedure is helpful when you have dropped a template object and a particular parameter is no longer needed.
DBMS_REPCAT_RGT.DROP_TEMPLATE_PARM ( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2);
Parameter | Description |
---|---|
refresh_template_ name |
The deployment template name that has the parameter that you want to drop |
parameter_name |
Name of the parameter that you want to drop. |
This procedure removes a user authorization entry from the DBA_REPCAT_TEMPLATE_AUTH
view. This procedure is used when removing a user's template authorization. If a user's authorization is removed, then the user is no longer able to instantiate the target deployment template.
DBMS_REPCAT_RGT.DROP_USER_AUTHORIZATION ( refresh_template_name IN VARCHAR2, user_name IN VARCHAR2);
Parameter | Description |
---|---|
refresh_template_ name |
Name of the deployment template that the user's authorization is being removed from. |
user_name |
Name of the user whose authorization is being removed. |
This procedure removes a pre-defined user parameter value for a specific deployment template. This procedure is often executed after a user's template authorization has been removed.
DBMS_REPCAT_RGT.DROP_USER_PARM_VALUE ( refresh_template_name IN VARCHAR2, parameter_name IN VARCHAR2, user_name IN VARCHAR2);
This function retrieves an ID to be used when defining a runtime parameter value. All runtime parameter values are assigned to this ID and are also used during the instantiation process.
DBMS_REPCAT_RGT.GET_RUNTIME_PARM_ID RETURN NUMBER;
None.
Return Value | Corresponding Datatype |
---|---|
<system generated number> |
Runtime parameter values are assigned to the system generated number and is also used during the instantiation process. |
This procedure defines runtime parameter values prior to instantiating a template. This procedure should be used to define parameter values when no user parameter values have been defined and you do not want to accept the default parameter values.
Before using the this procedure, be sure to execute the GET_RUNTIME_PARM_ID
function to retrieve a parameter ID to be used when inserting a runtime parameter. This ID is used for defining runtime parameter values and instantiating deployment template.
DBMS_REPCAT_RGT.INSERT_RUNTIME_PARMS ( runtime_parm_id IN NUMBER, parameter_name IN VARCHAR2, parameter_value IN CLOB);
Because the this procedure utilizes a CLOB
, you need to utilize the DBMS_LOB
package when using the INSERT_RUNTIME_PARMS
procedure. The following example illustrates how to use the DBMS_LOB
package with the INSERT_RUNTIME_PARMS
procedure:
DECLARE tempstring VARCHAR2(100); templob CLOB; BEGIN DBMS_LOB.CREATETEMPORARY(templob, TRUE, DBMS_LOB.SESSION); tempstring := 'REGION 20'; DBMS_LOB.WRITE(templob, length(tempstring), 1, tempstring); DBMS_REPCAT_RGT.INSERT_RUNTIME_PARMS( runtime_parm_id => 20, parameter_name => 'region', parameter_value => templob); DBMS_LOB.FREETEMPORARY(templob); END; /
This function generates a script at the master site that is used to create the snapshot environment at the remote snapshot site while offline. This generated script should be used at remote snapshot sites that are able to remain connected to the master site for an extended amount of time, as the instantiation process at the remote snapshot site may be lengthy (depending on the amount of data that is populated to the new snapshots). This procedure needs to be executed separately for each user instantiation.
The script generated by this function is stored in the USER_REPCAT_TEMP_OUTPUT
temporary view and is used by several Oracle tools, including Replication Manager, during the distribution of deployment templates. The number returned by this function is used to retrieve the appropriate information from the USER_REPCAT_TEMP_OUTPUT
view.
Note: This procedure is used in performing an offline instantiation of a deployment template. Additionally, this procedure is for replication administrators that are instantiating for another user. Users wanting to perform their own instantiation should use the public version of the "INSTANTIATE_OFFLINE function". This procedure should not be confused with the procedures in the DBMS_OFFLINE_OG package (used for performing an offline instantiation of a master table) or with the procedures in the DBMS_OFFLINE_SNAPSHOT package (used for performing an offline instantiation of a snapshot). See these respective packages for more information on their usage. |
DBMS_REPCAT_RGT.INSTANTIATE_OFFLINE( refresh_template_name IN VARCHAR2, site_name IN VARCHAR2, user_name IN VARCHAR2 := NULL, runtime_parm_id IN NUMBER := -1e-130, next_date IN DATE := SYSDATE, interval IN VARCHAR2 :'SYSDATE + 1') RETURN NUMBER;
This function generates a script at the master site that is used to create the snapshot environment at the remote snapshot site while online. This generated script should be used at remote snapshot sites that are able to remain connected to the master site for an extended amount of time, as the instantiation process at the remote snapshot site may be lengthy (depending on the amount of data that is populated to the new snapshots). This procedure needs to be executed separately for each user instantiation.
The script generated by this function is stored in the USER_REPCAT_TEMP_OUTPUT
temporary view and is used by several Oracle tools, including Replication Manager, during the distribution of deployment templates. The number returned by this function is used to retrieve the appropriate information from the USER_REPCAT_TEMP_OUTPUT
view.
Note: This procedure is for replication administrators that are instantiating for another user. Users wanting to perform their own instantiation should use the public version of the "INSTANTIATE_OFFLINE function". |
DBMS_REPCAT_RGT.INSTANTIATE_ONLINE( refresh_template_name IN VARCHAR2, site_name IN VARCHAR2 := NULL, user_name IN VARCHAR2 := NULL, runtime_parm_id IN NUMBER := -1e-130, next_date IN DATE := SYSDATE, interval IN VARCHAR2 :'SYSDATe + 1') RETURN NUMBER;
When a deployment template is being updated or modified, you should use the LOCK_TEMPLATE_EXCLUSIVE
procedure to prevent users from reading or instantiating the template.
The lock will be released when a ROLLBACK
or COMMIT
is performed.
DBMS_REPCAT_RGT.LOCK_TEMPLATE_EXCLUSIVE;
None.
This procedure is used to make a specified deployment template "read-only." This procedure should be called before instantiating a template, as this will ensure that nobody can change the deployment template while it is being instantiated.
The lock will be released when a ROLLBACK
or COMMIT
is performed.
DBMS_REPCAT_RGT.LOCK_TEMPLATE_SHARED;
None.