Building and Maintaining Partitions

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:

Opening the Partition Manager

To open the Partition Manager:

Select the database to partition; for example, East.
Choose Database > Partition Manager.
Figure 16-1: Partition Manager

Click Help for information about items in the Partition Manager.

The Partition Manager contains the following parts:

Menus help you create and save new partitions; edit, delete, and open existing partitions; choose types of partitions displayed; and view online help.
The Source Cube list box lists all the database partitions for which the currently selected database is the data target.
The Target Cube list box lists all the database partitions for which the currently selected database is the data source.
The arrow buttons, and , change the currently selected database to the database in the selected partition. The buttons let you scroll through and select different databases.
Other buttons let you edit, delete, or display information about a partition. To do so, select the partition in the Source Cube or Target Cube list box and click the appropriate button.
An option to enable you to lock partition definition files so that other users cannot edit them while you are editing them. To do so, check the Lock Partition Definition Files box.

Creating a New Partition

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.

The Connect page of the Partition Wizard shown in Figure 16-2 is where you:

Choose the type of partition type to use.
Choose the server, application, and database containing the data source and the data target of the new partition.
Specify which outline to synchronize outline changes to.
Figure 16-2: Connect Page of the Partition Wizard

Note:

Moving a dimension past a dimension that is not in the partition may not get propagated to the target during outline synchronization. Similarly, moving a member past a member that is not in the partition may not get propagated.

For more information on using Dynamic Time Series members in partitions, see Using Dynamic Time Series Members in Partitions.

Creating a Replicated Partition

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:

Specifying the Partition Type and Connection Information

To set up a replicated partition:

Create a new partition. See Creating a New Partition.
Choose Replicated from the Connection page of the Partition Wizard.
Click the Settings button to open the Replication Properties dialog box.
Figure 16-3: Replication Properties Dialog Box
Check "The target partition can be updated" to allow users to update the data at the data target or clear "The target partition can be updated" to prevent users from updating the data at the data target.
Before setting this, consider that:
- Hyperion Essbase overwrites changes that users make at the data target when you update the replicated partition.
- If users can't update a replicated area, they cannot calculate it, load data into it, or change information in it using the Hyperion Essbase Spreadsheet Add-in. Data in this area can only be changed at the data source.
- Setting a partition as not updatable overrides security filters that let users update the partition.
Click OK.

Choose the server, application, and database names for the data source and the data target. If you are not connected to the appropriate server, click Connect. For our example, choose Sampeast and East as the data source and Samppart and Company as the data target. The server should correspond to the server on which your Samppart and Sampeast applications reside.

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.

If desired, enter notes about the data source or the data target by clicking the Note button to open the Note dialog box. Enter your notes and click OK.
To propagate changes in the data source's outline to the data target's outline, check the Outline changes move in the same direction as data changes box. To propagate changes from the data target's outline to the data source's outline, clear the box. If you're not sure which outline to use as the source outline, see Introducing Outline Synchronization.

Setting the User Name and Password

You must specify a user name and password for Hyperion Essbase to use when communicating between the data source and the data target. Hyperion Essbase uses this user name and password to:

Transfer data between the data source and the data target for replicated and transparent partitions. Local security filters apply to prevent end users from seeing privileged data.
Synchronize database outlines for all partition types.

See Setting Up Security for Partitioned Databases.

To set the user name and password for the data source and the data target:

From the Connection page of the Partition Wizard, click Next or Admin to move to the Admin page.
Figure 16-4: Admin Page of the Partition Wizard
Enter the user name and password to use as the default login to the data source; for example, partitionuser and password. When you enter the password, the Partition Wizard masks it with asterisks (*) so that the password is hidden.
Enter the user name and password to use as the default login to the data target; for example, partitionuser and password. When you enter the password, the Partition Wizard masks it with asterisks (*) so that the password is hidden.

Note: This user name and password must be identical to the user name and password defined for the data source.

Defining the Areas in a Partition

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:

From the Admin page of the Partition Wizard, click Next or Areas to move to the Areas page.
Figure 16-5: Areas Page of Partition Wizard
Define the member or member combinations for an area by entering them in the Area Definition dialog box or choosing them from the Member Selection dialog box. If you're not sure which areas to partition, see Determining Which Data to Partition.
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.

Manually Defining an Area

To enter the members in an area:

In the Areas page of the Partition Manager, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source box (Figure 16-5) to open the Area Definition dialog box.

Enter the member name for the data source and click OK. For our example, enter:

"Eastern Region", Actual

Note: You can enter Hyperion 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. For more information on Hyperion Essbase functions, see the online Technical Reference in the DOCS directory.

Repeat steps 2 and 3 for the Target box. For our example, enter:
```
East, Actual
```

Entering an Area Using the Member Selection Dialog Box

To choose the members that make up an area from the Member Selection dialog box:

In the Areas page of the Partition Manager, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source box (Figure 16-5) to open the Member Selection dialog box.
Figure 16-6: Member Selection Dialog Box

For more information about the parts of the Member Selection dialog box, click Help.
Choose the dimension and member to partition. For our example, choose Eastern Region in the Market dimension and Actual in the Scenario dimension.
Click Add. Hyperion Essbase adds the member to the Rules list.
By default, the member's children and descendants are not added to the Rules list in Figure 16-6. 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.
Repeat steps 2 through 4 for the Target box. For our example, choose East in the Market dimension and Actual in the Scenario dimension.
When you are finished, click OK.

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.

Mapping Data Source Members to Data Target Members

Hyperion 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, Hyperion 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.

Mapping Members with Different Names

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.

Mapping Data Cubes with Extra Dimensions

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 as shown in Figure 16-7:

Figure 16-7: 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, as follows:

Figure 16-8: Mapping Data Cubes with Extra Dimensions

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 as shown in Figure 16-9:

Figure 16-9: 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 as follows:

Figure 16-10: 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.

To map member names:

From the Areas page of the Partition Wizard, click Next or Mappings to move to the Mappings page.
Figure 16-11: Mappings Page of the Partition Wizard
You can map data source members to data target members in any of the following ways:
- Enter the name in the Member Name dialog box. See Manually Defining Mappings.
- Select the member name in the Member Select dialog box. See Entering an Area Using the Member Selection Dialog Box.
- Import the member mappings from an external data file. See Importing Member Mappings.

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.

Manually Defining Mappings

To enter the member in the data source and the member that it maps to in the data target:

In the Mappings page of the Partition Wizard, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source Members box (Figure 16-11) to open the Member Name dialog box.
Enter the member name for the data source and click OK. For our example, enter:
```
"Eastern Region"
```
Double-click the New field in the Target Members box to open the Member Name dialog box.
Enter the member name to map it to in the data target and click OK. For our example, enter:
```
East
```

Using the Member Selection Dialog Box to Enter Mappings

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:

In the Mappings page of the Partition Wizard, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source Members box (Figure 16-11) to open the Member Selection dialog box.
Figure 16-12: Member Selection Dialog Box

For more information about the parts of the Member Selection dialog box, click Help.
Choose the dimension or member to map. For our example, choose the Eastern Region dimension.
Click OK.
Repeat steps 2 through 4 for the Target Members box. For our example, choose East in the Market dimension.
When you finish, click OK.

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.

Importing Member Mappings

To import the names from an external file:

In the Mappings page of the Partition Wizard, click Import to open the Import Member Mappings dialog box.
Figure 16-13: Import Member Mappings Dialog Box
Choose the mapping file to import. Mapping files must end in.TXT. A sample member file must contain all of the following (except extra columns):
Figure 16-14: Member Mapping Import File
- Extra column--the file can contain extra columns that do not contain member names.
- Data target members column--lists the member names in the data target. Member names containing spaces must be in quotes.
- Data source members column--lists the member names in the data source. Member names containing spaces must be in quotes.
- Non-member column--missing members. Use when you are mapping an extra member in the data source to Void in the data target or vice versa.
- Separators--separate the columns. Separators can be tabs or spaces.
Click OK.

Creating a Transparent Partition

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 Hyperion Essbase database or on another Hyperion Essbase 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:

Specifying the Partition Type and Connection Information

To set up a transparent partition:

Create a new partition. See Creating a New Partition.
Choose Transparent from the Connection page of the Partition Wizard.

Choose the server, application, and database names for the data source and the data target. If you are not connected to the appropriate server, click Connect. For our example, choose the Samppart Company database as the data source and the Sampeast East database as the data target. The server should correspond to the server on which your Samppart and Sampeast applications reside.

Note:

If desired, enter notes about the data source or the data target by clicking the Note button to open the Note dialog box. Enter your notes and click OK.
To propagate changes in the data source's outline to the data target's outline, check the "Outline changes move in the same direction as data changes" box. To propagate changes from the data target's outline to the data source's outline, clear the box. If you're not sure which outline to use as the source outline, see Introducing Outline Synchronization.

Setting the User Name and Password

The procedure for this is identical to creating the user name and password for a replicated partition. See Setting the User Name and Password.

Defining the Areas in a Transparent Partition

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:

From the Admin page of the Partition Wizard, click Next or Areas to move to the Areas page.
Figure 16-15: Areas Page of Partition Wizard
Define the member or member combinations for an area by entering them in the Area Definition dialog box or choosing them from the Member Selection dialog box. If you're not sure which areas to partition, see Determining Which Data to Partition.
There must be a one-to-one correspondence between cells in the areas for the data source and the data target on each line.

Manually Defining an Area

To enter the members in an area:

In the Areas page of the Partition Manager, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source box to open the Area Definition dialog box.

Enter the member name for the data source and click OK. For our example, enter:

Corp_Budget, East

Note: You can enter Hyperion 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. For more information on Hyperion Essbase functions, see the online Technical Reference in the DOCS directory.

Repeat steps 2 and 3 for the Target box. For our example, enter:
```
Corp_Budget, "Eastern Region"
```

Using the Member Selection Dialog Box to Enter an Area

To choose the members that make up an area from the Member Selection dialog box:

In the Areas page of the Partition Manager, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source box to open the Member Selection dialog box.
Figure 16-16: Member Selection Dialog Box

For more information about the parts of the Member Selection dialog box, click Help.
Choose the dimension and member to partition. For our example, choose Corp_Budget in the Scenario dimension and East in the Market dimension.
Click Add. Hyperion Essbase adds the member to the Rules list.
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.
Repeat steps 2 through 4 for the Target box. For our example, choose Corp_Budget in the Scenario dimension and Eastern Region in the Market dimension.
When you are finished, click OK.

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.

Mapping Data Source Members to Data Target Members

Hyperion 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, Hyperion 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. Hyperion Essbase maps the real member, not the shared one, from the data source.

To map member names for a transparent partition:

From the Areas page of the Partition Wizard, click Next or Mappings to move to the Mappings page.
Figure 16-17: Mappings Page of the Partition Wizard
You can map data source members to data target members in any of the following ways:
- Enter the name in the Member Name dialog box. See Manually Defining the Mapping.
- Select the member name in the Member Select dialog box. See Using the Member Selection Dialog Box to Enter Mappings.
- Import the member mappings from an external data file. See Importing Member Mappings.

Manually Defining the Mapping

To enter the member in the data source and the member that it maps to in the data target:

In the Mappings page of the Partition Wizard, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source Members box (Figure 16-17) to open the Member Name dialog box.
Enter the member name for the data source and click OK. For our example, enter:
```
East
```
Double-click the New field in the Target Members box to open the Member Name dialog box.
Enter the member name to map it to in the data target and click OK. For our example, enter:
```
"Eastern Region"
```

Using the Member Selection Dialog Box to Enter Mappings

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:

In the Mappings tab of the Partition Wizard, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source Members box (Figure 16-17) to open the Member Selection dialog box. For information about the parts of the Member Selection dialog box, click Help.
Select the dimension or member to map. For our example, choose East in the Market dimension.
Click OK.
Repeat steps 2 through 4 for the Target Members box. For our example, choose Eastern Region in the Market dimension.
When you finish, click OK.

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.

Mapping Attributes Associated with Members

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 16-18:

Figure 16-18: Defining Areas for Mapping Attributes

Then map attributes in the Mapping tab of the Partition Manager as follows:

Figure 16-19: 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:

Create the Caffeinated attribute dimension and its members in the outline of the data target and associate them with the Product dimension. You can then map the attributes from the data source to the data target.
Map the Caffeinated attribute dimension in the data source to Void in the data target.

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. Hyperion Essbase maps the real member, not the shared one, from the data source.

Creating a Linked Partition

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 Hyperion Essbase.

Creating a linked partition involves the following steps:

Specifying the Partition Type and Connection Information

To set up a linked partition:

Create a new partition. See Creating a New Partition.
Choose Linked from the Connection page of the Partition Wizard.
Click the Settings button to open the Link Properties dialog box.
Figure 16-20: Link Properties Dialog Box
Enter the default login information for the data source. The user's client application, such as the Spreadsheet Add-in, uses this information to connect to the data target if the user does not have login privileges to the source database using the same user name and password as the target database. For more information, see Setting Up Security for Linked Partitions.

Choose the server, application, and database names for the data source and the data target. If you are not connected to the appropriate server, click Connect. For our example, choose the TBC Demo database as the data source and the Sample Basic database as the data target. Remember, however, that the TBC Demo database is not shipped with Hyperion Essbase.

Note:

If desired, enter notes about the data source or the data target by clicking the Note button to open the Note dialog box. Enter your notes and click OK. These notes display in the linked objects box to help users select the database to drill across to.
To propagate changes in the data source's outline to the data target's outline, check the "Outline changes move in the same direction as data changes" box. To propagate changes from the data target's outline to the data source's outline, clear the box. If you're not sure which outline use as the source outline, see Introducing Outline Synchronization.

Setting the User Name and Password

The procedure for this is identical to creating the user name and password for a replicated partition. See Setting the User Name and Password.

Defining the Areas in a Partition

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:

From the Admin page of the Partition Wizard, click Next or Areas to move to the Areas page.
Figure 16-21: Areas Page of Partition Wizard
Define the member or member combinations for an area by entering them in the Area Definition dialog box or choosing them from the Member Selection dialog box. If you're not sure which areas to partition, see Determining Which Data to Partition.
There must be a one-to-one correspondence between cells in the areas for the data source and the data target on each line.

Manually Defining an Area

To enter the members in an area:

In the Areas tab of the Partition Manager, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source box to open the Area Definition dialog box.

Enter the member name for the data source and click OK. For our example, enter:

Product

Note: You can enter Hyperion 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. For more information on Hyperion Essbase functions, see the online Technical Reference in the DOCS directory.

Repeat steps 2 and 3 for the Target box. For our example, enter:
```
Product
```

Using the Member Selection Dialog Box to Enter an Area

To choose the members that make up an area from the Member Selection dialog box:

In the Areas tab of the Partition Manager, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source box to open the Member Selection dialog box. For more information about the parts of the Member Selection dialog box, click Help.
Choose the dimension and member to partition. For our example, choose the Product dimension.
Click Add. Hyperion Essbase adds the member to the Rules list.
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.
Repeat steps 2 through 4 for the Target box. For our example, choose the Product dimension.

When you are finished, click OK.

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.

Mapping Data Source Members to Data Target Members

For a detailed introduction to member mapping, see Mapping Data Source Members to Data Target Members.

To map member names for a linked partition:

From the Areas page of the Partition Wizard, click Next or Mappings to move to the Mappings page.
Figure 16-22: Mappings Page of the Partition Wizard
You can map data source members to data target members in any of the following ways:
- Enter the name in the Member Name dialog box. See Manually Defining Mappings.
- Select the member name in the Member Select dialog box. See Entering an Area Using the Member Selection Dialog Box.
- Import the member mappings from an external data file. See Importing Member Mappings.

Manually Defining Mappings

To enter the member in the data source and the member that it maps to in the data target:

In the Mappings page of the Partition Wizard, make sure that the Enable the Member Selection Tool box is cleared.
Double-click the New field in the Source Members box (Figure 16-22) to open the Member Name dialog box.
Enter the member name for the data source and click OK. For our example, enter:
```
Channel
```
Double-click the New field in the Target Members box to open the Member Name dialog box.
Enter the member name to map it to in the data target and click OK. For our example, enter:
```
Void
```
For the linked partition described in Scenario 3: Linking Two Databases, you must also map the Package dimension to Void.

Using the Member Selection Dialog Box to Enter Mappings

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:

In the Mappings page of the Partition Wizard, make sure that the Enable Member Selection Tool box is checked.
Double-click the New field in the Source Members box (Figure 16-22) to open the Member Selection dialog box. For more information about the parts of the Member Selection dialog box, click Help.
Select the dimension or member to map. For our example, choose the Channel dimension.
Click OK.
Repeat steps 2 through 4 for the Target Members box. For our example, choose Void. For the linked partition described in Scenario 3: Linking Two Databases, you must also map the Package dimension to Void.
When you finish, click OK.

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.

Validating the Partition

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.

To validate a partition:

From the Mappings page in the Partition Wizard, click Next or Validate to move to the Validate page.
Figure 16-23: Validate Page of the Partition Wizard
Click Validate. Hyperion Essbase validates the partition. This may take some time.
If you receive a warning, double-click the warning message to move to the tab in the Partition Wizard where you can correct the problem shown in the warning message.

Use the VALIDATEPARTITIONDEFFILE command in ESSCMD to perform this task. See the online Technical Reference in the DOCS directory for information about this command. See Performing Interactive and Batch Operations Using ESSCMD for information about ESSCMD.

When Hyperion Essbase validates a partition definition, it checks on the server for the data source and the data target to ensure that:

The area definition is valid (contains no syntax errors).
The specified data source members are valid and map to valid members in the data target.
All connection information is correct; that is, the server names, database names, application names, user names, and password information.
For linked partitions, the default user name and password that you provide are correct.
For replicated and transparent partitions, a replication target does not overlap with a replication target; a replication target does not overlap with a transparent target; a transparent target does not overlap with a transparent target; and a replication target does not overlap with a transparent target.
For replicated and transparent partitions, the cell count for the partition is the same on the data source and the data target.
For replicated and transparent partitions, the area dimensionality matches the data source and the data target.

Note:

You must validate a transparent partition that is based on attribute values to ensure that the results are complete. Hyperion Essbase does not display an error message when results are incomplete.

Saving the Partition Definition

You can save partition definitions even if they have not been validated.

To save a partition definition:

From the Validate page of the Partition Wizard, click Next or Summary to open the Summary page.
Figure 16-24: Summary Page of the Partition Wizard

Check the information in the Summary page to make sure that the partition is defined correctly. If it's not, click the appropriate page in the Partition Wizard to change the settings.
Click Close to open the Close dialog box.
Figure 16-25: Partition Wizard Close Dialog Box
Choose where to save the partition definition:
- Select Save to Servers to save the partition definition, which is stored in two.DDB files, to both the data source server and the data target server.
- Select Save to Client to save the partition definition, which is stored in a single.DDB file, to your client machine. To open the partition definition later, choose Partition > Open From Client in the Partition Manager.
- Select Discard Changes to throw away any changes that you made to a new or existing partition and close the Partition Manager.

Click OK to commit the definition to the specified location.

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.

Testing Partitions

To test a partition:

View the data target(s) using the Spreadsheet Add-in or other tool to make sure that the user sees the correct data.
When testing a linked partition, make sure that Hyperion Essbase links you to the expected database and that the default user name and password works correctly.

Creating Advanced Area-Specific Mappings (Optional)

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 don't need to perform advanced area-specific mapping. Skip to Validating the Partition.

If, however, you need to control how Hyperion 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:

Map data differently depending on where it's coming from.
Map more than one member in your data source to a single member in your data target.

Since Hyperion 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.

Example 1: Advanced Area-Specific Mapping

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.

Since the data source does not have Actual and Budget members, you must also map these members to Void in the data target.

Area-Specific Mapping Example

To create this example mapping:

Create the 1998 and 1999 and 1998, Actual and 1999, Budget areas:
1. In the Areas tab of the Partition Wizard, define the area as 1998 in the data source and as 1998, Actual in the data target.
2. In the Areas tab of the Partition Wizard, define the area as 1999 in the data source and as 1999, Budget in the data target.
  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.
Use advanced area-specific mapping to map the members that are missing in the data source (Actual and Budget) to Void 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.
1. Click the Advanced button in the Mappings tab of the Partition Wizard.
2. Use the arrow buttons to scroll the area selection to 1998 to Actual, 1998.
3. Map Void in the data source to Actual in the data target.
4. Click the left arrow button to define a new area-specific mapping. Scroll to 1999 to Budget, 1999.
5. Map Void in the data source to Budget in the data target.
6. Click Close.

Now Hyperion Essbase maps the 1998 values to 1998, Actual and the 1999 values to 1999, Budget.

Example 2: Advanced Area-Specific Mapping

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

You know that 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.

Area-Specific Mapping Example

To create this example mapping:

Create the areas: NY, Actual, Budget and NY_Actual, NY_Budget; and CA, Actual, Budget and CA_Actual, CA_Budget.
1. In the Areas tab of the Partition Wizard, define the area as NY, Actual, Budget in the data source and as NY_Actual, NY_Budget in the data target.
  If you don't know how to use the Areas tab of the Partition Wizard, see Defining the Areas in a Partition.
2. Repeat these steps for CA, Actual, Budget and CA_Actual, CA_Budget.
  You split these into two areas so that you can map the members differently in each area in the next step.
Use advanced area-specific mapping to map the members that are missing in the data source (NY and CA) to Void.
1. Click the Advanced button in the Mappings tab of the Partition Wizard.
2. Use the arrow buttons to scroll the area selection to NY, Actual, Budget to NY_Actual, NY_Budget.
3. Map NY in the data source to Void in the data target.
4. Map Actual in the data source to NY_Actual in the data target.
5. Map Budget in the data source to NY_Budget in the data target.
6. Use the arrow buttons to scroll the area selection to CA, Actual, Budget to CA_Actual.
7. Map CA in the data source to Void in the data target.
8. Map Actual in the data source to CA_Actual in the data target.
9. Map Budget in the data source to CA_Budget in the data target.

Now Hyperion 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, Hyperion Essbase maps Actual to NY_Actual for the entire Actual, NY area and Actual to CA_Actual for the entire Actual, CA area. Hyperion Essbase maps the Actual member to different members depending on the area.

Specifying Area-Specific Mapping

To specify area-specific mapping:

Click Advanced in the Mappings tab of the Partition Wizard to open the Area Specific Member Mapping dialog box.
Figure 16-26: Area Specific Member Mapping Dialog Box
Enter the data source member in the Source Members text box.
Enter the data target member in the Target Members text box.
Map missing dimensions, Void, to their existing counterparts.
If desired, use the arrow keys to move to other area mappings.
When you are finished, click Close.

Introducing Outline Synchronization

When you partition a database, Hyperion 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, Hyperion 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 Hyperion Essbase does try to make whatever changes it can to replicated and transparent partitions when the outlines are not synchronized, Hyperion Essbase may not be able to make the data in the data source available in the data target.

What's the solution? Resynchronize your outlines. Hyperion 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.

Source Outline and Target Outline

Before you can synchronize your outlines, you must determine which outline is the source outline and which is the target outline.

The source outline is the outline that outline changes are taken from.
The target outline is the outline that outline changes are applied to.

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.

If you make changes to the:

Shared area in the source outline, you can propagate these changes to the target outline when you synchronize the outlines.
Target outline, those changes cannot be propagated back to the source outline when you synchronize the outlines. To move these changes up to the source outline, use the Outline Editor. See Creating and Changing Database Outlines

Note:

Hyperion Essbase updates as many changes as possible to the target outline. If Hyperion 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.

How Hyperion Essbase Tracks Changes

The following table describes what happens when you change the source outline and then synchronize the target outline with the source outline:


When You...	Hyperion Essbase...
Make changes to the source outline	Records the changes in a change log file named `ESS`xxxxx`.CHG`, where xxxxx is the number of the partition. If you have more than one partition on a source outline, Hyperion Essbase creates a change log file for each partition. Creates or updates the outline change timestamp for that partition in the`.DDB` file. Each partition defined against the source outline has a separate timestamp in the`.DDB` file.
Pull changes from the outline source	Compares the last updated timestamp in the target outline's`.DDB` file to the last updated timestamp in the source outline's`.DDB` file. Hyperion Essbase updates the target timestamp when it finishes synchronizing the outlines using the last updated time on the source outline, even if the two outlines are on servers in different time zones. If the source outline has changed since the last synchronization, Hyperion Essbase retrieves those changes from the source outline's change log file and places them in the target outline's change log file. The change log files may have different names on the source outline and the target outline.
Select the changes to apply to the target outline	Applies the changes to the target outline. Updates the timestamp in the target outline's`.DDB` file, using the time from the source outline.

CAUTION: If you choose to not apply some changes, you cannot apply those changes later.

Synchronizing Outlines

To synchronize a target outline to a source outline:

Connect to the source outline server and the target outline server, and select the target outline in the Hyperion Essbase desktop.
Choose Database > Synchronize Outline to open the Synchronize Outline dialog box. Click the Help button for detailed information about each item in the Synchronize Outline dialog box.
Figure 16-27: Synchronize Outline Dialog Box

Choose the types of changes to retrieve from the source outline. These changes are not applied until you click Apply.

Choose Dimension from the list box. Select the types of changes to retrieve by checking their boxes.
Choose Member from the list box. Select the types of changes to retrieve by checking their boxes.

Choose Member Properties from the list box. Select the types of changes to retrieve by checking their boxes.

Note:

The Apply button is enabled only when outline synchronization is necessary. If the database outlines are identical, the Apply button is not enabled.

CAUTION: Deselecting 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 Hyperion 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.

To accept or reject all changes, proceed to step 5. To choose which changes to accept or reject, proceed to step 4.

To choose which changes to accept or reject, click Edit to open the Outline Synchronization Editor dialog box.

Figure 16-28: 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.

Clear changes that you don't want to propagate. Be careful about not propagating changes. For example, if the database administrator creates a parent and children on the source outline and you clear the parent, you must also clear all of the children or the apply process fails.

CAUTION: 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 file for details. Messages that pertain to outline synchronization are prefixed with OUTLINE SYNC.

For more information about a specific change, double-click the change to open a Detail dialog box containing a brief description of the change.
When you are finished, click Apply. Hyperion Essbase propagates the accepted change records.
Proceed to Step 7.

Click Apply to open the Apply Outline Changes dialog box.
Figure 16-29: Apply Outline Changes Dialog Box
Choose whether to accept or reject all changes and click OK. If you choose to accept changes, the outline synchronization may take some time to complete. If you choose to reject all changes, Hyperion Essbase updates the timestamp and does not ask you to accept those changes the next time you synchronize the outlines.
To purge out-of-date change log files on both the target outline and the source outline, click Purge.
Hyperion Essbase deletes all records from the change log file that have been applied or rejected. If all records have been applied or rejected, Hyperion Essbase deletes the change log file as well. Hyperion Essbase does not purge records that have not yet been applied to the target outline.

Click Close to close the Synchronize Outline dialog box.

Note:

Hyperion Essbase keeps all change log files until you purge them. You should purge change log files 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.

How Shared Members are Treated in Outline Synchronization

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 following example, 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 16-30: 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 16-30, 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 following example, 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 16-31: 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 online Technical Reference in the DOCS directory for information about this command. See Performing Interactive and Batch Operations Using ESSCMD for information about ESSCMD.


Task:	ESSCMD to Use:
Retrieve the outline change log from the source outline. You can choose specific changes from the source outline. You can choose to: Get all changes from the outline. If you say Yes, Hyperion Essbase retrieves all changes. Get all dimension changes. If you say Yes, Hyperion Essbase retrieves all changes and proceeds to the next step. If you say No, Hyperion Essbase asks you which dimension changes to retrieve. You can retrieve: new dimensions, deleted dimensions, updated dimensions, moved dimensions, and renamed dimensions. Get all member changes. If you say Yes, Hyperion Essbase retrieves all changes and proceeds to the next step. If you say No, Hyperion Essbase asks you which member changes to retrieve. You can retrieve: new members, deleted members, renamed members, or moved members. Get all member property changes. If you say Yes, Hyperion Essbase retrieves all changes and proceeds to the next step. If you say No, Hyperion Essbase asks you which member property changes to retrieve. You can retrieve changed member: statuses, aliases, unary calc symbols, account types, currency conversion information, user defined attributes, calc formulas, level numbers, and generation numbers.	GETPARTITIONOTLCHANGES
Apply the changes in the change log file to the target outline.	APPLYOTLCHANGEFILE
Reset the timestamp on both the source and the target outline change log files.	RESETOTLCHANGETIME
Purge entries that have been applied to the target outline from the change log files.	PURGEOTLCHANGEFILE

Editing Partitions

To edit a partition:

Connect to the data source server and the data target server and select the data target outline in the Hyperion Essbase desktop.
Choose Database > Partition Manager to open the Partition Manager. The Partition Manager displays all of the partitions defined for the current database. The Partition Manager below displays the replicated partition that you created between the Sampeast East and Samppart Company databases earlier in this chapter.
Figure 16-32: Partition Manager

Select the partition to edit and select the operation to perform on that partition:


To...	Click...
Edit the partition	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 the partition	Delete. Hyperion Essbase deletes the partition definition from the partition's.DDB file on the data source and data target servers.
View more information about the partition	Info to open the Partition Information dialog box. You can also use the PRINTPARTITIONDEFFILE command in ESSCMD. See the online Technical Reference in the DOCS directory for information about this command. See Performing Interactive and Batch Operations Using ESSCMD for information about ESSCMD.

Introducing the Updating of Replicated Partitions

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. Hyperion 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.

Hyperion Essbase also tracks which cells in a partition are changed. You can choose to update:

Just the cells that have changed since the last replication. It's fastest to update just the cells that have changed.

Note:

If you've deleted data blocks on the data source, Hyperion 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 CLEARDATA command in a calc script; using "Clear combinations" in your rules file during a data load; issuing CLEAR UPPER, CLEAR INPUT or RESETDB commands in the Hyperion Essbase Application Manager; restructuring the database keeping only level 0 or input data; or deleting sparse members.

All cells. This is much slower. You may need to update all cells if you are recovering from a disaster where the data in the data target has been destroyed or corrupted.

You can replicate:

All data targets connected to a data source. For example, if you replicate all data targets connected to the Sampeast East database, Hyperion Essbase updates the Budget, Actual, Variance, and Variance % members in the Samppart Company database.
Figure 16-33: Put to Targets
From all data sources connected to a data target. For example, if you replicate from all data sources connected to the Samppart Company database, Hyperion Essbase pulls the Budget, Actual, Variance, and Variance % members from the Sampeast East database and updates them in the Samppart Company database.
Figure 16-34: Get from Sources

Updating Replicated Partitions

To populate or update a replicated partition:

Connect to the data source server or the data target server and select the database in the Hyperion Essbase desktop.
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 16-35: 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.
In the Options group, choose to update all data cells or just those that have changed. It's fastest to update just the changed cells. If you're not sure, see Introducing the Updating of Replicated Partitions.

Click Replicate. The replication may take some time to complete.

Note:

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.

Updating Replicated Partitions Using MaxL or ESSCMD

	You can easily update replicated partitions using refresh replicated partition in MaxL. See the online Technical Reference in the `DOCS` directory for information.
	You can update replicated partitions using ESSCMD. See the online Technical Reference in the `DOCS` directory for more information about the ESSCMD commands in the following table.


Task:	ESSCMD to Use:
Retrieve only the cells that have changed from the data source and update them on the current data target.	GETUPDATEDREPLCELLS
Retrieve all replicated cells from the data source and update them on the current data target.	GETALLREPLCELLS
Send only the cells that have changed from the current data source to the data target.	PUTUPDATEDREPLCELLS
Send all replicated cells from the current data source to the data target.	PUTALLREPLCELLS

Troubleshooting Partitions

The following table lists common problems that you may encounter when using partitions.


Symptom	Possible Causes	Solutions
When replicating to multiple data targets, some are not replicated.	The connection between the data source and one of the data targets was lost during the replication operation.	Retry the replication operation. If one database is unavailable, replicate into just the databases that are available.
Not all information arrived at the data target.	The data source and the data target outlines are no longer mappable.	Synchronize outlines for the data source and the data target and try again.
You keep running out of ports.	Partitions connect to other databases using ports.	Purchase more ports.
When you try to access a partition, you cannot connect to it.	Someone has deleted, renamed, or moved the application containing the database to which you are trying to connect.	Open the Partition Manager, select the partition having problems, and click the Edit button. A dialog box opens asking you to repair the connection by specifying the new application name or location.
Partitioned databases can no longer connect to each other.	Your host names may not match. Did you use the hosts file to provide aliases to your local machine?	Make sure that the host names are synchronized between the servers and the Application Manager.
Hyperion Essbase overwrites user edits.	Users are changing data at a replicated partition that you overwrite each time that you update the partition.	Set the partition to not allow user updates or explain to users why their data disappears.
The Synchronize Outline dialog box does not reflect outline change; that is, it lists the outlines as being in sync even though one outline has changed.	Was the target outline changed, but not the source outline? Hyperion Essbase only propagates changes to the source outline. Does the outline change affect a defined partition? Hyperion Essbase does not propagate changes to the outline that do not affect any partitions.	Open the Partition Manager and click Edit to examine the partition definition.
Data is confusing.	Your partition may not be set up correctly.	Check your partition to make sure that you are partitioning the data that you need.