Creating Replicated Partition With MaxL Disables Target Partition Data Updates (Doc ID 1065955.1)

Last updated on JULY 29, 2016

Applies to:

Hyperion Essbase - Version 11.1.1.3.00 and later
Information in this document applies to any platform.
*** Checked for Currency 22-Oct-2012 ***
*** Bug fixed in Essbase v11.1.2.1 Documentation ***


Symptoms

In Essbase 11.1.1.3, if you create a Replicated Partition using MaxL, the 'Target Partition Can be Updated' option does not get ticked and therefore prevents users from being able to update data in the target database.

If you create the partition manually through EAS data can be updated.
 

To reproduce the issue:

Use SampEast Application in Essbase.

1. Create a Copy of the Sampeast application called 'SaEaTarg'.
2. Open MaxL through the EAS console or though the essmsh.exe.
3. Use the following MaxL statement to create the partition:

create or replace replicated partition 'Sampeast'.'East'
area '"100-10", "New York", "Actual", "Sales", "Jan"' Sourcearea1
to 'SaEaTarg'.'East'
at 'machinename'
as 'username' identified by 'password'
area '"100-10", "New York", "Actual", "Sales", "Jan"' targetarea;



4. Connect to the target database in Smartview and try to update the data in the following intersection:

Jan->Sales->Actual->New York->100-10

You will see that you cannot alter the data.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms