Create Replicated Partition

Create or validate a replicated partition definition between two databases. A replicated partition copies a portion of the source (or master) database to be stored in a target database. Users can access the target database as if it were the source. The administrator must periodically refresh the target data from the source data.

Syntax

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

Keyword	Description
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 ...partition	Create a partition definition, or replace an existing partition definition.
area...	Define the partition areas to share with the other database. Optionally nickname the area using an area-alias .
to <dbs-name>	Create a partition definition between the current database source and the second database (the target).
from <dbs-name>	Create a partition definition between the current database target and the second database (the source).
at <host-name>	Specify the remote computer name, if you are creating a partition definition between the current database and one residing on a remote Essbase Server host.
as <user-name> identified by <password>	Provide the name and password of a default partition user who can connect to both databases. Essbase uses the login information to: Transfer data between the source and the target for replicated and transparent partitions. Database security filters can be applied to prevent end users from seeing privileged data. Synchronize database outlines for all partition types.
using <user-name> identified by <password> for creation	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.
mapped...	Define the member-name mapping for shared sections of both databases, if member names for sections that map are different in the two databases.
outline...	Specify the direction in which outline synchronization should proceed, if necessary. The default direction is the same as the data-refresh direction.
update...	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.
comment	Create a comment to describe the source half of the partition definition.
remote comment	Create a comment to describe the target half of the partition definition.
validate only	Validate the existing partition definition described by this statement, without actually creating it.

Notes

Multiple area specifications are allowed, provided they are separated by whitespace. Multiple mappings are allowed, provided they are separated by whitespace. 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 database, and the second DBS-NAME is the remote database.
Creating a partition tothe remote site means the current database is the source. Creating a partition fromthe remote site means the current database is the target.
If you are creating a partition and specifying a host name that includes a port number, see Specifying Port Numbers in Partition Host Names for more information.
If you are using host name aliases, see Using Host Name Aliases When Partitioning.
Aggregate storage databases can be the target, but not the source, of a replicated partition.
To create a partition as an externally authenticated user, when using MaxL Script Editor, you must enter a login statement before the create partition statement. The login statement must include the full external user name with provider, as well as the host name.
For example,
```
login 'admin@Native Directory' 'password' on 'FQN';
create partition....;
```

Example

create or replace replicated partition source.source
area 'DimensionA' sourceAreaA
area 'DimensionB' sourceAreaB
to target.target at localhost
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 database Source to database 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 localhost
as partitionuser identified by 'password'
area '@IDESCENDANTS(East) @IDESCENDANTS(Qtr1)'
update disallow;

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

create or replace replicated partition sampeast.east
area '@IDESCENDANTS("Eastern Region"), @IDESCENDANTS(Qtr1)' 
to samppart.company at localhost
as admin identified by 'password'
area '@IDESCENDANTS(East) @IDESCENDANTS(Qtr1)' foo
mapped foo (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 foo as used above, see the definition for AREA-ALIAS .