SET COPYMISSINGBLOCK

Sets whether the DATACOPY calculation command creates #MISSING blocks during the copy of data from a dense dimension.

This setting does not apply to aggregate storage databases.

SET COPYMISSINGBLOCK allows DATACOPY to avoid creating #MISSING blocks during the copy of data from a dense dimension.

Using DATACOPY on a dense dimension can create blocks populated with #MISSING. This is done deliberately in some instances, because most batch calculations operate only on existing data blocks. Therefore, DATACOPY can be used to ensure that all necessary data blocks are created prior to batch calculation.

But if the creation of #MISSING blocks is not required, you may want to avoid the increase in database size, and the possibly slower performance that results when, for example, a default calculation visits every #MISSING block.

Syntax

SET COPYMISSINGBLOCK ON | OFF

Parameter	Description
ON	This is the default value. Allows missing blocks to be created during a data copy.
OFF	Suppresses the creation of missing blocks during a data copy.

Notes

Existing #MISSING blocks are not removed.
A message is added to the Essbase Server log to indicate the number of data blocks being copied from the source data blocks. The number of #MISSING blocks skipped, if any, is also reported in the log.

Example

SET COPYMISSINGBLOCK OFF;

The following log message indicates that SET COPYMISSINGBLOCK is OFF:

[Fri May 31 10:35:03 2002]Local/Test6/Test6/essexer/Info(1012574)
Datacopy command copied [1] source data blocks to [0] target data blocks

[Fri May 31 10:35:03 2002]Local/Test6/Test6/essexer/Info(1012576)
Datacopy command skipped creating [1] target data blocks with CopyMissingBlock OFF