RESYNC

When an analytic workspace is attached in multiwriter mode, the RESYNC command drops private changes for the specified variables, relations, valuesets, and dimensions and promotes them so that the user now sees the data from the latest visible generations. You can only resychronize read-only objects. Oracle OLAP ignores any requests to resychronized acquired objects.

Syntax

RESYNC [objects] [analytic_workspaces]

Arguments

When no parameters are specified, all read-only objects in the current analytic workspace are resychronized.

objects: A list of one or more variables, relations, valuesets, or dimension names, separated by commas, that you want to resynchronize.
analytic_workspaces: A list of names, separated by commas, of one or more analytic workspaces presently attached in multiwriter mode. Oracle OLAP resynchronizes all read-only variables, relations, valuesets, and dimensions in a listed analytic workspace at the same time.

Notes

Keeping Logical Relationship of Objects

When using RESYNC keep in mind the logical relationship of different objects to avoid losing the logical consistency of the data by promoting some objects, but not others to a new generation.

Resynchronizing Objects that Share a Composite Dimension

All objects that share a composite dimension must be resynchronized together.

Examples

Example 21-2 Resynchronizing Objects

In this example, user A is periodically updating actuals, while user R needs to periodically check the latest view of the data. They could execute the following OLAP DML statements.

User A could execute the following OLAP DML statements.

AW ATTACH myworkspace MULTI
ACQUIRE actuals
...make modifications
UPDATE MULTI actuals
COMMIT
...make modification
UPDATE MULTI actuals
COMMIT

At the same time, user R could execute the following OLAP DML statements.

AW ATTACH myworkspace MULTI
...
RESYNC actuals
...
RESYNC actuals
...
RESYNC actuals
...