Troubleshooting Partitions

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

Table 37. Troubleshooting Problems with Partitions

Symptom

Possible Cause

Solution

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 only the available databases.

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.

A new or recently changed partition is validated and saved but does not function.

The partition may have a circular dependency. If database A is the source for database B, database B cannot be source for database A for the same slice.

Edit the partition definition to remove the circular dependency.

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.

Edit the partition having problems to specify the new application name or location.

Partitioned databases no longer can connect to each other.

Your host names may not match. Did you use the hosts file to provide aliases to your local machine?

See Setting up the Data Source and the Data Target.

Ensure that the host names are synchronized between the servers.

Essbase overwrites user edits.

Users are changing data at a replicated partition that you overwrite each time you update the partition.

Set the partition to disallow user updates, or explain to users why their data disappears.

Administration Services does not reflect outline changes; that is, it lists the outlines as being in sync although one outline has changed.

  • Was the target outline changed, but not the source outline? Essbase propagates changes only to the source outline.

  • Does the outline change affect a defined partition? Essbase does not propagate changes to the outline that do not affect any partitions.

Examine the partition definition.

Data is confusing.

Your partition may not be set up correctly.

Check your partition to ensure that you are partitioning the data that you need.

Moved members or dimensions in the source outline are not reflected properly in a synchronized target outline.

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

Structure your outline so that members and dimensions are not moved across partitions. If doing so is not possible, change the target outline to reflect the source outline moved members or dimensions.