Create Replicated Partition

The MaxL create replicated partition statement helps you create or validate a replicated partition between two Essbase databases.

A replicated partition copies a portion of the source (or originating) cube to be stored in a target cube. Users can access the target cube as if it were the source. The administrator must periodically refresh the target data from the source data.

Keywords

Use the MaxL create replicated partition statement to create a partition in the following ways:

create replicated partition

Create a replicated partition. A replicated partition is a copy of a portion of the data source that is stored in the data target.

create or replace replicated partition...

Create a partition definition, or replace an existing partition definition.

create replicated partition ... area ...

The area specification is where you define the partition areas to share with the other cube. Optionally, nickname the area using an area-alias.

create replicated partition ... to DBS-NAME

Use the to clause to create a partition definition between the current source cube and the second cube (the target).

create replicated partition ... from DBS-NAME

Use the from clause to create a partition definition between the current target cube and the second cube (the source).

create replicated partition ... at HOST-NAME

Use the at clause, with a host name, to specify the discovery URL (ending in /agent) of the remote cube.

create replicated partition ... as USER-NAME identified by PASSWORD

Use the as clause to provide the name and password of a default partition user who can connect to both cubes. Essbase uses the login information to:

  • Transfer data between the source and the target for replicated and transparent partitions. Security filters can be applied to prevent end users from seeing privileged data.

  • Synchronize outlines for all partition types.

create replicated partition ... using USER-NAME identified by PASSWORD for creation

Use the using clause to create the partition using a different user than the one being set as the default partition user. This can be useful when you want to specify a read-only user account as the default partition user.

create replicated partition ... mapped...

Use the mapped clause to define the member-name mapping for shared sections of both cubes, if member names for sections that map are different in the two cubes.

create replicated partition ... outline...

Use the outline clause to specify the direction in which outline synchronization should proceed, if necessary. The default direction is the same as the data-refresh direction.

create replicated partition ... update...

Use the update clause to allow or disallow the updating of data in a replicated-type partition target. If you do not specify update allow, by default, the replicated partition cannot be updated.

create replicated partition ... comment

Use the comment clause to create a comment to describe the source half of the partition definition.

create replicated partition ... remote comment

Use the remote comment clause to create a comment to describe the target half of the partition definition.

create replicated partition ... validate only

Use the validate only clause to validate the existing partition definition described by this statement, without actually creating it.

Notes

  • Multiple area specifications are allowed, provided they are separated by space. Multiple mappings are allowed, provided they are separated by space. All area aliases used in a mapping should be associated with the target, and the direction of the mapped clause should go from source to target.

  • The first DBS-NAME is the local cube, and the second DBS-NAME is the remote cube.

  • Creating a partition to the remote site means the current cube is the source. Creating a partition from the remote site means the current cube is the target.

  • Aggregate storage cubes can be the target, but not the source, of a replicated partition.

Example

create or replace replicated partition source.source
area 'DimensionA' sourceAreaA
area 'DimensionB' sourceAreaB
to target.target at "https://myserver.example.com:9001/essbase/agent"
as admin identified by 'password'
area 'ParentMemberA' targetAreaA
area 'ParentMemberB' targetAreaB
mapped targetAreaA (ChildA) to (Child_a)
mapped targetAreaB (ChildB) to (Child_b)
; 

Creates a partition from cube Source to cube Target where the partitioned areas between them are DimensionA and DimensionB on the source, corresponding to ParentMemberA and ParentMemberB (respectively) on the target. Differences in member names between the two partitioned areas are resolved during the partition creation, using the mapped clauses. Area aliases are used after each area specification, so that members can be mapped specifically for each area.

create or replace replicated partition sampeast.east
area '@IDESCENDANTS("Eastern Region"), @IDESCENDANTS(Qtr1)'
to samppart.company at "https://myserver.example.com:9001/essbase/agent"
as partitionuser identified by 'password'
area '@IDESCENDANTS(East) @IDESCENDANTS(Qtr1)'
update disallow;

Creates a replicated partition from an area in the source cube, sampeast.east, to an area in the target cube, samppart.company.

create or replace replicated partition sampeast.east
area '@IDESCENDANTS("Eastern Region"), @IDESCENDANTS(Qtr1)' 
to samppart.company at "https://myserver.example.com:9001/essbase/agent"
as admin identified by 'password'
area '@IDESCENDANTS(East) @IDESCENDANTS(Qtr1)' myalias
mapped myalias (Year) to (Yr) 
update allow validate only;

Validates the syntax of a replicated partition you might want to create. To create the partition after checking validity, simply remove the validate only phrase. For an explanation of myalias as used above, see the definition for AREA-ALIAS.