Oracle7 Server Distributed Systems Volume II: Replicated Data

DBMS_REPCAT.REFRESH_SNAPSHOT_REPGROUP

Purpose

To refresh a snapshot site object group with the most recent data from its associated master site. For additional information, refer to

Syntax

The parameters for the REFRESH_SNAPSHOT_REPGROUP procedure are described in Table 12 - 155, and the exceptions are listed in Table 12 - 156. The syntax for this procedure is shown below:

DBMS_REPCAT.REFRESH_SNAPSHOT_REPGROUP(
	gname			IN	VARCHAR2,
	drop_missing_contents	IN	BOOLEAN := FALSE,
	refresh_snapshots	IN	BOOLEAN := FALSE,
	refresh_other_objects	IN	BOOLEAN := FALSE
	execute_as_user		IN	BOOLEAN := FALSE)

Parameter Description
gname The name of the replicated object group.
drop_missing_contents If an object was dropped from the replicated object group, it is not automatically dropped from the schema at the snapshot site. It is simply no longer replicated; that is, changes to this object are no longer sent to its associated master site. Snapshots can continue to be refreshed from their associated master tables; however, any changes to an updatable snapshot will be lost. When an object is dropped from the object group, you can choose to have it dropped from the schema entirely by setting this argument to TRUE.
refresh_snapshots Set this parameter to TRUE to refresh the contents of the snapshots in the replicated object group.
refresh_other_objects Set this parameter to TRUE to refresh the contents of the non-snapshot objects in the replicated object group.
execute_as_user The default, FALSE, indicates that a deferred call is authenticated at the remote system using the authentication context of the user who originally queued the deferred call (as indicated in the ORIGIN_USER column of the DefTran view). Set this to TRUE if you want the execution of a deferred call to be authenticated at the remote system using the authentication context of the session user.

Table 12 - 155. Parameters for REFRESH_SNAPSHOT_REPGROUP

Exception Description
nonsnapshot The invocation site is not a snapshot site.
nonmaster The master is no longer a master site.
commfailure The master is not accessible.

Table 12 - 156. Exceptions for REFRESH_SNAPSHOT_REPGROUP

Parameter	Description
`gname`	The name of the replicated object group.
`drop_missing_contents`	If an object was dropped from the replicated object group, it is not automatically dropped from the schema at the snapshot site. It is simply no longer replicated; that is, changes to this object are no longer sent to its associated master site. Snapshots can continue to be refreshed from their associated master tables; however, any changes to an updatable snapshot will be lost. When an object is dropped from the object group, you can choose to have it dropped from the schema entirely by setting this argument to TRUE.
`refresh_snapshots`	Set this parameter to TRUE to refresh the contents of the snapshots in the replicated object group.
`refresh_other_objects`	Set this parameter to TRUE to refresh the contents of the non-snapshot objects in the replicated object group.
`execute_as_user`	The default, FALSE, indicates that a deferred call is authenticated at the remote system using the authentication context of the user who originally queued the deferred call (as indicated in the ORIGIN_USER column of the DefTran view). Set this to TRUE if you want the execution of a deferred call to be authenticated at the remote system using the authentication context of the session user.

Exception	Description
nonsnapshot	The invocation site is not a snapshot site.
nonmaster	The master is no longer a master site.
commfailure	The master is not accessible.