Essbase also tracks which cells in a partition are changed:

• Faster—Only the cells that have changed since the last replication

• Slower—All cells

  The slower update is useful under certain conditions; for example, updating all cells to recover lost data at the target.

Follow these guidelines:

• Unless you update all cells, replication does not update target data when the source data has not changed since the last replication.

• By default, Essbase replicates #MISSING cells.

• If you do not want to replicate #MISSING cells, you can use the DISABLEREPLMISSINGDATA configuration setting.

• If you deleted data blocks on the source, Essbase updates all data cells at the target, even if you choose to update only changed cells. You can delete data blocks at the source using any of these methods:

  • Using the CLEARDATA command in a calculation script

  • Using "Clear combinations" in your rule file during a data load

  • Restructuring the database, keeping only level 0 or input data

  • Deleting sparse members

You can replicate:

• All targets connected to a source.

  For example, if you replicate all data targets connected to the Sampeast.East database, Essbase updates the Budget, Actual, Variance, and Variance % members in the Samppart.Company database:

• From all sources connected to a target.

  For example, if you replicate from all sources connected to the Samppart.Company database, Essbase pulls the Budget, Actual, Variance, and Variance % members from the Sampeast.East database and updates them in the Samppart.Company database.

To update a replicated partition, you can use the refresh replicated partition MaxL statement.