When you build a new partition, each database in the partition uses a partition definition file to record all information about the partition, such as its data source and data target and the areas to share. This chapter describes how to create a replicated, transparent, or linked partition.
Caution: You must design partitions carefully. We strongly recommend that you read Designing Partitioned Applications before creating partitions.
This chapter contains the following sections on creating partitions:
Maintaining a partition after you create it can involve synchronizing the data source and the data target outlines, modifying the partition, or updating replicated partitions.
This chapter contains the following sections on maintaining partitions:
To open the Partition Manager:
Click Help for information about items in the Partition Manager.
The Partition Manager contains the following parts:
To create a new partition, choose Partition > New in the Partition Manager. Click the Help button for detailed information about each item in the Partition Wizard.
The Partition Wizard is part of the Partition Manager and contains several pages that you fill out to create a new partition. You must have Designer privileges or higher to create a partition.
Use the Connect page of the Partition Wizard to perform these tasks:
For more information on using Dynamic Time Series members in partitions, see Using Dynamic Time Series Members in Partitions.
Note: If you try to create a partition using a calculation function that returns a set of members, and the value returned by the calculation function evaluates to an empty set, the partition definition does not validate. An error is written to the application log stating that the region definition evaluated to an empty set.
A replicated partition is a copy of a portion of the data source that is stored in the data target. For more information, see Replicated Partitions.
The examples used in this section are based on the example described in Scenario 1: Partitioning an Existing Database. This example replicates the Eastern Region's Actual member in the Sampeast database (the data source) to the Samppart Company database (the data target).
Creating a replicated partition involves the following steps:
To set up a replicated partition:
Figure 144: Replication Properties Dialog Box
Before setting this, consider that:
Note: Do not use network aliases when creating partitions unless you are certain that they are propagated to all computers on your system. If you're not certain, use the full server name. This is especially important for linked partitions, because this is the host name that clients connected to the data target use to find the data source.
You must specify a user name and password for Essbase to use when communicating between the data source and the data target. Essbase uses this user name and password to:
See Setting Up Security for Partitioned Databases.
To set the user name and password for the data source and the data target:
Figure 145: Admin Page of the Partition Wizard
Note: This user name and password must be identical to the user name and password defined for the data source.
The Areas page of the Partition Wizard lets you define or edit the areas of the data source to share with the data target. An area is a subcube within a database. For example, an area could be all Measures at the lowest level for Actual data in the Eastern Region. A partition is composed of one or more areas.
When you define a replicated area, make sure that both the data source and data target contain the same number of cells. This verifies that the two partitions have the same shape. For example, if the area covers 18 cells in the data source, there should be an area covering 18 cells in the data target into which to put those values.
Note: The cell count does not include those of attribute dimensions.
To define an area in a partition:
Figure 146: Areas Page of Partition Wizard
There must be a one-to-one correspondence between cells in the areas for the data source and the data target on each line.
Caution: Do not select Use Aliases when creating area definitions and mapping. Although Partition Manager will validate the aliases, the partitions will not work.
To enter the members in an area:
"Eastern Region", ActualNote: You can enter Essbase functions in the Area Definition dialog box. For example, you could share all descendants of East by entering @DESCENDANTS(East) or define areas based on user-defined attributes (UDAs). For more information on Essbase functions, see the Technical Reference in the docs directory.
East, Actual
To choose the members that make up an area from the Member Selection dialog box:
Figure 147: Member Selection Dialog Box
For more information about the parts of the Member Selection dialog box, click Help.
By default, the member's children and descendants are not added to the Rules list in Figure 147. To add the member's children or descendants to the Rules list, select the member in the Rules list and press the right mouse button to open a menu. Choose All Descendants.
Note: You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
Essbase must be able to map all shared data source members to data target members, to create a partition. If both, the data source and the data target, contain the same number of members and use the same member names, Essbase automatically maps the members. Skip to Validating the Partition.
Note: Use dimension member names instead of their aliases to create a valid partition.
It is recommended that the data source member names and the data target member names are the same. This reduces the maintenance requirements for the partition, especially when the partition is based on member attributes. See Introducing Outline Synchronization for more information.
If the data source outline and data target outline contain different members or the members have different names in each outline, you must map the data source members to the data target members. In the following example, the first two member names are identical but the third member name is different:
Source | Target |
---|---|
Product Cola | Product Cola |
Year 1998 | Year 1998 |
Market East | Market East_Region |
Because you know that East in the data source corresponds to Eastern_Region in the data target, map East to Eastern_Region. Then, all references to Eastern_Region in the data target point to East in the data source. For example, if the data value for Cola, 1998, East is 15 in the data source, the data value for Cola, 1998, Eastern_Region is 15 in the data target.
There can be instances when the number of dimensions in the data source and in the data target vary. The following example illustrates a case where there are more dimensions in the outline of the data source than in the outline of the data target:
Source | Target |
---|---|
Product Cola | Product Cola |
Market East | Market East |
Year 1999 1998 1997 |
If you want to map member 1997 of the Year dimension from the data source to the data target, you can map it to Void in the data target. But first, you must define the areas of the data source to share with the data target in the Areas tab of the Partition Wizard:
Figure 148: Defining Areas for Data Cubes with Extra Dimensions
You can then map the data source member to Void in the data target in the Mappings tab of the Partition Wizard:
Figure 149: Mapping Data Cubes with Extra Dimensions
Enter the member name you are mapping to Void using either of these methods:
The corresponding Source Members column automatically displays "Void." Entering "Void" yourself may cause errors.
If you do not include at least one member from the extra dimension in the Areas definition, you will receive an error message when you attempt to validate the partition.
Note: When you map a member from an extra dimension, the partition results reflect data only for the mapped member. In the above example, the Year dimension contains three members: 1999, 1998, and 1997. If you map member 1997 from the data source to the data target, then the partition results reflect Product and Market data only for 1997. Product and Market data for 1998 and 1999 will not be extracted.
The following example illustrates a case where the data target includes more dimensions than the data source:
Source | Target |
---|---|
Product Cola | Product Cola |
Market East | |
Year 1997 | Year 1997 |
In such cases, you must first define the shared areas of the data source and the data target:
Figure 150: Defining Areas for Data Cubes with Extra Dimensions
You can then map member East from the Market dimension of the data target to Void in the data source:
Figure 151: Mapping Extra Dimensions in Partitioning
If member East from the Market dimension in the data target is not included in the target areas definition, you will receive an error message when you attempt to validate the partition.
Figure 152: Mappings Page of the Partition Wizard
Note: You cannot map attributes dimension members in replicated partitions. For more information, refer to Rules for Transparent Partitions. You can, however, map attributes in transparent and linked partitions. For information on using attributes in partitions, see Using Attributes in Partitions. For information on mapping attributes, see Mapping Attributes Associated with Members.
To enter the member in the data source and the member that it maps to in the data target:
"Eastern Region"
East
To choose the member in the data source and the member that it maps to in the data target from the Member Selection dialog box:
Figure 153: Member Selection Dialog Box
For more information about the parts of the Member Selection dialog box, click Help.
Note: For the linked partition described in Scenario 3: Linking Two Databases, you must also map the Package dimension to Void.
You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
To import the names from an external file:
Figure 154: Import Member Mappings Dialog Box
Figure 155: Member Mapping Import File
A transparent partition allow users to access data from the data source as though it were stored in the data target. The data is, however, stored at the data source, which can be in another application or in another Essbase database or on another OLAP Server. For more information, see Transparent Partitions.
The examples used in this section are based on the example described in Scenario 1: Partitioning an Existing Database. This example creates a transparent partition containing the Corp_Budget member between the Samppart Company database (the data source) and the Sampeast database (the data target).
Creating a transparent partition involves the following steps:
To set up a transparent partition:
Note: Do not use network aliases when creating partitions unless you are certain that they are propagated to all computers on your system. If you're not certain, use the full server name. This is especially important for linked partitions, because this is the host name that clients connected to the data target use to find the data source.
The procedure for this is identical to creating the user name and password for a replicated partition. See Setting the User Name and Password.
The Areas page of the Partition Wizard lets you define or edit the areas of the data source to share with the data target. For more information about areas in a partition, see Defining the Areas in a Partition.
To define an area in a transparent partition:
Figure 156: Areas Page of Partition Wizard
There must be a one-to-one correspondence between cells in the areas for the data source and the data target on each line.
To enter the members in an area:
Corp_Budget, EastNote: You can enter Essbase functions in the Area Definition dialog box. For example, you could share all descendants of East by entering @DESCENDANTS(East) or define areas based on UDAs. For more information on Essbase functions, see the Technical Reference in the docs directory.
Corp_Budget, "Eastern Region"
To choose the members that make up an area from the Member Selection dialog box:
Figure 157: Member Selection Dialog Box
For more information about the parts of the Member Selection dialog box, click Help.
By default, the member's children and descendants are not added to the Rules list. To add the member's children or descendants to the Rules list, select the member in the Rules list and press the right mouse button to open a menu. Choose All Descendants.
Note: You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
Essbase must be able to map all shared data source members to data target members to create a partition. If both the data source and the data target contain the same number of members and use the same member names, Essbase automatically maps the members. Skip to Validating the Partition.
For a detailed introduction to member mapping, see Mapping Data Source Members to Data Target Members.
For information on using attributes in partitions, see Using Attributes in Partitions. For information on mapping attributes associated with members of a base dimension, see Mapping Attributes Associated with Members.
Note: When you create a replicated or transparent partition using a shared member, use the real member names in the mapping. Essbase maps the real member, not the shared one, from the data source.
To map member names for a transparent partition:
Figure 158: Mappings Page of the Partition Wizard
To enter the member in the data source and the member that it maps to in the data target:
East
"Eastern Region"
To choose the member in the data source and the member that it maps to in the data target from the Member Selection dialog box:
For information about the parts of the Member Selection dialog box, click Help.
Note: You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
You must accurately map attribute dimensions and members from the data source to the data target to ensure that partitioning is valid.
In the following example, the outline for the data source contains a Product dimension with a member 100 (Cola). Children 100-10 and 100-20 are associated with member TRUE of the Caffeinated attribute dimension, and child 100-30 is associated with member FALSE of the Caffeinated attribute dimension.
The data target outline has a Product dimension with a member 200 (Cola). Children 200-10 and 200-20 are associated with member Yes of the With_Caffeine attribute dimension, and child 200-30 is associated with No of the With_Caffeine attribute dimension.
First define the areas to be shared from the data source to the data target in the Areas tab of the Partition Manager as shown in Figure 159:
Figure 159: Defining Areas for Mapping Attributes
Then map attributes in the Mapping tab of the Partition Manager:
Figure 160: Mapping Attributes
If you map attribute Caffeinated_True to attribute With_Caffeine_No, you receive an error message during validation. You must associate caffeinated cola from the data source to caffeinated cola in the data target.
Note: You can only map attributes for transparent and linked partitions. An attempt to map attributes in replicated partitions results in an error message.
There can be instances where an attribute dimension or an attribute member exists in the outline of the data source but not in the outline of the data target, or vice versa. For example:
Source | Target |
---|---|
Caffeinated True False |
In such cases, you have the following choices:
For more information on mapping, see Mapping Data Cubes with Extra Dimensions. For more information on attributes, see Working with Attributes. For more information on using attributes in partitions, see Using Attributes in Partitions.
Note: You must validate the partition to ensure that the results are accurate. When you create a replicated or transparent partition using a shared member, use the real member names in the mapping. Essbase maps the real member, not the shared one, from the data source.
A linked partition sends users from a cell in one database to a cell in another database. This gives users a different perspective on the data. For more information, see Linked Partitions.
The examples used in this section are based on the example described in Scenario 3: Linking Two Databases. This example links the Product dimension in the Sample Basic database to the TBC Demo database. This scenario is not shipped with Essbase.
Creating a linked partition involves the following steps:
Figure 161: Link Properties Dialog Box
Note: Do not use network aliases when creating partitions unless you are certain that they are propagated to all computers on your system. If you're not certain, use the full server name. This is especially important for linked partitions, because this is the host name that the data target uses to find the data source.
The procedure for this is identical to creating the user name and password for a replicated partition. See Setting the User Name and Password.
The Areas page of the Partition Wizard lets you define or edit the areas of the data source to share with the data target. For more information about areas, see Defining the Areas in a Partition.
To define an area in a linked partition:
Figure 162: Areas Page of Partition Wizard
There must be a one-to-one correspondence between cells in the areas for the data source and the data target on each line.
To enter the members in an area:
Product
Note: You can enter Essbase functions in the Area Definition dialog box. For example, you could share all descendants of East by entering @DESCENDANTS(East) or define areas based on UDAs. For more information on Essbase functions, see the Technical Reference in the docs directory.
To choose the members that make up an area from the Member Selection dialog box:
By default, the member's children and descendants are not added to the Rules list. To add the member's children or descendants to the Rules list, select the member in the Rules list and press the right mouse button to open a menu. Choose All Descendants.
Note: You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
Essbase must be able to map all shared data source members to data target members to create a partition. If both the data source and the data target contain the same number of members and use the same member names, Essbase automatically maps the members. Skip to Validating the Partition.
For a detailed introduction to member mapping, see Mapping Data Source Members to Data Target Members.
For information on using attributes in partitions, see Using Attributes in Partitions. For information on mapping attributes associated with members of a base dimension, see Mapping Attributes Associated with Members.
To map member names for a linked partition:
Figure 163: Mappings Page of the Partition Wizard
To enter the member in the data source and the member that it maps to in the data target:
Channel
VoidFor the linked partition described in Scenario 3: Linking Two Databases, you must also map the Package dimension to Void.
To choose the member in the data source and the member that it maps to in the data target from the Member Selection dialog box:
Note: You can only use the Member Selection dialog box to enter new members, not to edit existing members. To edit existing members, use the Member Name dialog box. See Manually Defining an Area.
When you create a partition, validate it to ensure that it's correct before you use it.
Note: In order to validate a partition, you must have Designer privileges or higher.
To save the partition without validating it, see Saving the Partition Definition.
Figure 164: Validate Page of the Partition Wizard
Tip: You can also use the VALIDATEPARTITIONDEFFILE command in ESSCMD to perform this task. See the Technical Reference in the docs directory for information about this command. See Automating the Production Environment for information about ESSCMD.
When Essbase validates a partition definition, it checks on the server for the data source and the data target to ensure that:
Note: You must validate a transparent partition that is based on attribute values to ensure that the results are complete. Essbase does not display an error message when results are incomplete.
You can save partition definitions even if they have not been validated.
To save a partition definition:
Figure 165: Summary Page of the Partition Wizard
Check the information in the Summary page to make sure that the partition is defined correctly. If it is not, click the appropriate page in the Partition Wizard to change the settings.
Figure 166: Partition Wizard Close Dialog Box
Note: If you are creating a replicated partition, you must populate it after you create it. To populate a replicated partition, see Introducing the Updating of Replicated Partitions.
If you can map all of the members in your data source to their counterparts in the data target using standard member mapping, then you do not need to perform advanced area-specific mapping. Skip to Validating the Partition.
If, however, you need to control how Essbase maps members at a more granular level, you may need to use area-specific mapping. Area-specific mapping maps members in one area to members in another area only in the context of a particular area map.
Use area-to-area mapping when you want to:
Since Essbase cannot determine how to map multiple members in the data source to a single member in the data target, you must logically determine how to divide your data until you can apply one mapping rule to that subset of the data. Then use that rule in the context of area-specific mapping to map the members.
The data source and data target contain the following dimensions and members:
Source | Target |
---|---|
Product Cola | Product Cola |
Market East | Market East |
Year 1998 1999 | Year 1998 1999 |
Scenario Actual Budget |
The data source does not have a Scenario dimension. Instead, it assumes that past data is actual data and future data is forecast, or budget, data.
You know that 1998 in the data source should correspond to 1998, Actual in the data target and 1999 in the data source should correspond to 1999, Budget in the data target. So, for example, if the data value for Cola, East, 1998 in the data source is 15, then the data value for Cola, East, 1998, Actual in the data target should be 15.
Because mapping works on members, not member combinations, you cannot simply map 1998 to 1998, Actual. You must define the area (1998 and 1998, Actual) and then create area-specific mapping rules for that area.
The data source does not have Actual and Budget members, so you must also map these members to Void in the data target.
To create this example mapping:
If you do not know how to use the Areas tab of the Partition Wizard, see Defining the Areas in a Partition.
Now Essbase maps the 1998 values to 1998, Actual and the 1999 values to 1999, Budget.
You can also use advanced area-specific mapping if the data source and data target are structured very differently but contain the same kind of information.
This strategy works, for example, if your data source and data target contain the following dimensions and members:
Source | Target |
---|---|
Market NY CA | Customer_Planning NY_Actual NY_Budget CA_Actual CA_Budget |
Scenario Actual Budget |
NY and Actual in the data source should correspond to NY_Actual in the data target and NY and Budget in the data source should correspond to NY_Budget in the data target. So, for example, if the data value for NY, Budget in the data source is 28, then the data value for NY_Budget in the data target should be 28.
Because mapping works on members, not member combinations, you cannot simply map NY, Actual to NY_Actual. You must define the area (NY and Actual, and NY_Actual) and then create area-specific mapping rules for that area.
Since the data target does not have NY and CA members, you must also map these members to Void in the data target so that the dimensionality is complete when going from the data source to the data target. For more information on making the dimensionality complete, see Mapping Data Source Members to Data Target Members.
To create this example mapping:
If you don't know how to use the Areas tab of the Partition Wizard, see Defining the Areas in a Partition.
You split these into two areas so that you can map the members differently in each area in the next step.
Now Essbase maps NY, Actual to NY_Actual; NY, Budget to NY_Budget; CA, Actual to CA_Actual; and CA, Budget to CA_Budget. That is, Essbase maps Actual to NY_Actual for the entire Actual, NY area and Actual to CA_Actual for the entire Actual, CA area. Essbase maps the Actual member to different members depending on the area.
To specify area-specific mapping:
Figure 167: Area Specific Member Mapping Dialog Box
When you partition a database, Essbase must be able to map each dimension and member in the data source outline to the appropriate dimension and member in the data target outline. After you map the two outlines to each other, Essbase can make the data in the data source available from the data target as long as the outlines are synchronized.
If you make changes to one of the outlines, the two outlines are no longer synchronized. Although Essbase does try to make whatever changes it can to replicated and transparent partitions when the outlines are not synchronized, Essbase may not be able to make the data in the data source available in the data target.
However, Essbase tracks changes that you make to your outlines and provides tools to make it easy to keep your outlines synchronized. This section describes the steps you need to take to synchronize your outlines.
Before you can synchronize your outlines, you must determine which outline is the source outline and which is the target outline.
By default, the source outline is from the same database as the data source; that is, outline and data changes flow in the same direction. For example, if the East database is the data source and the Company database is the data target, then the default source outline is East.
You can also use the data target outline as the source outline. You might want to do this if the structure of the outline (its dimensions, members, and properties) is maintained centrally at a corporate level, while the data values in the outline are maintained at the regional level (for example, East). This allows the database administrator to make changes in the Company outline and apply those changes to each regional outline when she synchronizes the outline.
To set the source outline, see Specifying the Partition Type and Connection Information.
Shared area changes can be propogated, target outline changes cannot:
Essbase updates as many changes as possible to the target outline. If Essbase cannot apply all changes, a warning message prompts you to see the Application Server log for details. Messages that pertain to outline synchronization are prefixed with OUTLINE SYNC.
The following table describes what happens when you change the source outline and then synchronize the target outline with the source outline:
If you choose to not apply some changes, you cannot apply those changes later.
To synchronize a target outline to a source outline:
Figure 168: Synchronize Outline Dialog Box
Important: Clearing any of the Filter Settings for Outline Changes options, especially the Add and Move options, may result in losing additional changes. For example, if the database administrator creates a parent and children on the source outline and you clear the parent, the children may not get added to the target outline. If Essbase cannot apply all changes, a warning message prompts you to see the Application Server log file for details. Messages that pertain to outline synchronization are prefixed with OUTLINE SYNC.
Figure 169: Synchronization Editor Dialog Box
This dialog box lists each change made to the source outline since you last synchronized the outlines. For information about each item in the dialog box, click Help.
Important: Rejecting specific changes in the Outline Synchronization Editor may result in losing additional changes. For example, if the database administrator creates a parent and children on the source outline and you clear the parent, the children may not get added to the target outline. If the children are not added to the target outline, a warning message prompts you to see the Application Server log for details. Messages that pertain to outline synchronization are prefixed with OUTLINE SYNC.
Figure 170: Apply Outline Changes Dialog Box
If you choose to accept changes, the outline synchronization may take some time to complete. If you choose to reject all changes, Essbase updates the timestamp and does not ask you to accept those changes the next time you synchronize the outlines.
Essbase deletes all records from the change log that have been applied or rejected. If all records have been applied or rejected, Essbase deletes the change log as well. Essbase does not purge records that have not yet been applied to the target outline.
Essbase keeps all change logs until you purge them. You should purge change logs periodically, before they become too large.
Every time you change the source outline or target outline, you should re-validate your partition definitions. See Validating the Partition.
Note: If you have moved a dimension or member past another dimension or member that is not in the partition, the move may not be accurately reflected in the target outline. See the last entry in the table in Troubleshooting Partitions.
An actual member and its shared members in the source outline are propagated to the target outline if at least one actual or shared member is defined in the partition area. In the example illustrated in Figure 171, the partition definition is @IDESC("Diet"). The parent 100 and its children (100-10, 100-20, 100-30) are not defined in the partition area. The parent Diet and its children (100-10, 100-20, 100-30) are defined in the partition area. The children of Diet are shared members of the actual members.
Figure 171: Shared Members and Outline Synchronization
If you make a change to an actual member in the undefined partition area, such as adding an alias to the 100-10 actual member, that change is propagated to the target outline because it is associated with a shared member in the defined partition area.
The reverse is also true. If a shared member is not in the partition area and its actual member is, a change to the shared member in the undefined area is propagated to the target outline.
Any change made to a member that does not have at least one actual member (or shared member) in the defined partition area is not propagated to the target outline. For example, in Figure 171, a change to the parent 100 is not propagated to the target outline because it is in the undefined partition area and does not have an associated shared member in the defined partition area.
If a shared member is included in the partition area, then it is recommended to include its parent. In the above example, the parent Diet is included in the outline because its children are shared members and in the defined partition area.
Implied shared members are treated the same as shared members in Outline Synchronization. Actual members and their implied shared members in the source outline are propagated to the target outline if at least one actual or implied shared member is defined in the partition definition.
Using the partition definition as @CHILD("A") for the example illustrated in Figure 172, A1 and A2 are in the defined partition area, and A11, A21, A22 are in the undefined partition area. Although A11 (implied shared member) is in the undefined partition area, a change to A11 is propagated to the target outline because its parent, A1, is in the defined partition area. The change to the children A21 and A22 is not propagated to the target outline because these members are not defined in the partition area and are not associated with a member that is in the defined partition area.
Figure 172: Implied Shared Members and Outline Synchronization
The reverse is true again. If A1 is not defined in the partition area and its implied shared member is, then any change to A1 is propagated to the target outline.
You can synchronize outlines using ESSCMD. See the Technical Reference in the docs directory for information about this command. See Automating the Production Environment for information about ESSCMD.
Action To Take |
Button to Click |
---|---|
Edit or double-click the partition to open the Partition Wizard. Use the same tabs to edit the partition as you did to create it. For more information, see Building and Maintaining Partitions. |
|
Delete. Essbase deletes the partition definition from the partition's .DDB file on the data source and data target servers. |
|
Info to open the Partition Information dialog box. You can also use the PRINTPARTITIONDEFFILE command in ESSCMD. See the Technical Reference in the docs directory for information about this command. See Automating the Production Environment for information about ESSCMD. |
The database administrator should regularly update data in a replicated partition. How frequently you update replicated partitions depends on users' requirements for up-to-the-minute data. Essbase keeps track of when the data source was last changed and when the data target was last updated so that you can determine when to update replicated partitions. This information is saved at the data source. Either database administrator-that of the data source site or that of the data target site-can be responsible for replicating data.
Essbase also tracks which cells in a partition are changed. You can choose to update:
Note: If you've deleted data blocks on the data source, Essbase updates all data cells at the data target even if you choose to update only changed cells. You can delete data blocks at the data source by using the CLEARBLOCK command in a calculation script; using "Clear combinations" in your rules file during a data load; issuing CLEAR UPPER, CLEAR INPUT or RESETDB commands in the Application Manager; restructuring the database keeping only level 0 or input data; or deleting sparse members.
To populate or update a replicated partition:
If you opened the data source, choose Database > Replicate Data > To Targets. If you opened the data target, choose Database > Replicate Data > From Sources.
This opens the Data Replication dialog box.
Figure 176: Data Replication Dialog Box
The Data Replication dialog box lists all replicated partitions that are connected to this database and when they were last replicated. If the data source has changed since you last updated the data target, you should replicate the new information. You can choose which partitions to replicate.
Click the Help button for detailed information about each item in the Data Replication dialog box.
You must have Designer privileges or higher on the database from which you are initiating the replication. For example, if you are replicating from sources, you must have Designer privileges or higher on the target database. Likewise, if you are replicating to targets, you must have Designer privileges or higher on the source database.
You can easily update replicated partitions using refresh replicated partition in MaxL. See the Technical Reference in the docs directory for information.
You can update replicated partitions using ESSCMD. See the Technical Reference in the docs directory for more information about the ESSCMD commands in the following table.
The following table lists common problems that you may encounter when using partitions.
![]() © 2002 Hyperion Solutions Corporation. All rights reserved. http://www.hyperion.com |