Replicated partition Refresh

Hi All,
We have replicated partition from Cube03 to Cube01.. We refresh the replicated partition data daily using a MAXL Script.
In Cube03 the data in INtersection01 is copied to Intersection02 at the end of budget cycle.......and the data in INtersectiono1 is deleted...and We refresh the replicated partition to get data to Cube01 for these new intersections....
Since we have been refreshing the data in INtersectiono1 to Cube01....Is it stored in Cube01...Do we need to delete this data in Cube01 for INtersectiono1 ...so that ONLY the new intersection data Intersection02 is reflected in Cube01
Appreciate your respone........

Hi,
The partition exists but it has been created within EAS where the server added is the cluster as opposed to the actual server name essbase is on - EssbaseCluster-1 - So this is what it has for the Essbase Server for the Data Source and Data Target. When we try and create a partition with using the actual server name it orphans (I have another thread about that one)
Here is the output from the MAXL that I executed when trying the server name:
MAXL> refresh outline on replicated partition finance.sscstf to finance.bud
2> at 'http://HYPESSBASE-DEV.***.co.uk'
3> apply all;
ERROR - 1040042 - Unable to get the cluster name from the url [http://HYPESSBASE-DEV.***.co.uk].
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
ERROR - 1040042 - Unable to get the cluster name from the url [http://HYPESSBASE-DEV.***.co.uk].
ERROR - 1241128 - Partition does not exist - 'can't be found in local partition definition file'.
Here is the output when trying the server IP address
MAXL> refresh outline on replicated partition finance.sscstf to finance.bud
2> at '**.**.**.**'
3> apply all;
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
WARNING - 1040048 - HTTP communication failed with error [Couldn't connect to server].
ERROR - 1241128 - Partition does not exist - 'can't be found in local partition definition file'.

Similar Messages

Replicated partition is taking a long time

I have been using a replicated partition to move some data from one Database to another and it has been working working fine.
All of a sudden the replicated partition is taking a long time ( does not complete) when I run a maxl script to refresh the replicated partition. I can't seem to figure out what caused the issue. I made sure the there are no virtual members defined in the sparse dimensions and the mapping are correct.
Any idea of why the process will take so long all of a sudden?

I have narrowed down to the problem on part of the hierarchy of the dimension. The parent member has about 2500 children under it and any time we include this part of the tree in the partition the partition takes a long time( the total number of members in the Cost center is 18K)

Pb to setup replicated partition with substitution variables

Dear all,
I have the following problem with the replicated partition by using the substitution variables :
I would like to create a replicated partition using 3 substitution variables: &CurrPeriod, &CurrWeek, &CurrYear. The goal of this is to be able to copy data from application SourceApp to TargetApp every week, by changing the subst variables.
The script I have created is :
login useradmin identified by password on EssbServer
alter application SourceApp load database SourceDb
alter application TargetApp load database TargetDb
create or replace replicated partition SourceApp.SourceDb
Area ' "Account1", &CurrPeriod, &CurrWeek, &CurrYear, "ND_DISTRI","ND_PAGE","ND_PROD","VT", "REEL", "EUR" ' SourceArea
to TargetApp.TargetDb at EssbServer as useradmin identified by password
Area ' "Account1",    "M_N",     "S_N",     "FY1" , "ND_DISTRI","ND_PAGE","ND_PROD","VT", "REEL", "EUR" ' TargetArea
+     mapped TargetArea ("&CurrYear") to ("FY1")+
+     mapped TargetArea ("&CurrWeek") to ("S_N")+
+     mapped TargetArea ("&CurrPeriod") to ("M_N")+
+     update allow;+
refresh replicated partition SourceApp .SourceDb to TargetApp .TargetDb at EssbServer all data ;
The issue is that this is not working. I don’t see any data when launching the Maxl script even if the script syntax is validated by essbase. The very strange thing is that when I replace the substitution variable by members, this script works fine, I see my data in the target cube. For example if I replace the subst variables by
Area ' "Account1", “Month1”, “Week1”, “Year1”, "ND_DISTRI","ND_PAGE","ND_PROD","VT", "REEL", "EUR" ' SourceArea
to TargetApp.TargetDb at EssbServer as useradmin identified by password
Area ' "Account1",    "M_N",     "S_N",     "FY1" , "ND_DISTRI","ND_PAGE","ND_PROD","VT", "REEL", "EUR" ' TargetArea
+     mapped TargetArea (“Year1”) to ("FY1")+
+     mapped TargetArea (“Week1”) to ("S_N")+
+     mapped TargetArea (“Month1”) to ("M_N")+
So my conclusion is that there is something wrong with the syntax of the substitution variable in my mapping.
Your help on this would be very appreciated .

Hi,
I have the answer from Oracle support :
Hello,
This is a known bug.
BUG 7418041
This has been documented as a known issue in Essbase Release 9.3.1.3 with the following description: "Partitioning. Using substitution variables in replicated partition mappings incorrectly prevents data from replicating. [7418041]"
Currently the development team are working on a fix, but we don't have a release date yet.
The suggested workarounds are to use member names (which you have confirmed work) or use a Transparent partition in place of a replicated partition.

Problem with replicated partitioning between two BSO db's. version 9.3.0.1

Hi there,
I have a problem with partitioning between two BSO db’s.
I created the partition, it validates and I made an export for the partion definiton(xml file).
Everything is fine if I set this partition up as transparent partition.
This means I can see the data from the src in the trg db as ecpected.
But when I change over to replicated (what in fact I want to do) nothing happens for the trg site - there are still no data. (Yes I have choosen Update all cells.)
I got no error in any way neither AAS nor in the app logs of src and trg.
(Mayby this it important: one src-dimension is mapped to void for the trg.)
Can anyone give me a hint or even confirm this behaviour ?
Thank you in advance
Andre
Below the log infos:
log of src db:
[Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013210)
User [hyperion] set active on database [db]
[Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1013091)
Received Command [PutReplicatedCells] from user [hyperion]
[Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013210)
User [hyperion] set active on database [db]
[Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1013091)
Received Command [XferReplicatedCells] from user [hyperion]
[Fri Dec 04 15:29:03 2009]Local/AAA///Info(1013214)
Clear Active on User [hyperion] Instance [1]
[Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1023005)
Update of replicated partition elapsed time : [0] seconds
[Fri Dec 04 15:29:03 2009]Local/AAA/db/hyperion/Info(1243010)
Partition refreshed
log of trg db:
[Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013210)
User [hyperion] set active on database [db]
[Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
Received Command [ReqXferReplicatedCells] from user [hyperion]
[Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013210)
User [hyperion] set active on database [db]
[Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
Received Command [ProtocolXchg] from user [hyperion]
[Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1023044)
Processing distributed request from [P4B5A856A, AAA, db]
[Fri Dec 04 15:29:03 2009]Local/AAA1/db/hyperion/Info(1013091)
Received Command [PutLastUpdatedTime] from user [hyperion]
[Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013214)
Clear Active on User [hyperion] Instance [1]
[Fri Dec 04 15:29:03 2009]Local/AAA1///Info(1013214)
Clear Active on User [hyperion] Instance [1]

It sounds like you are doing it all correctly. One thing you might try just to be sure you are not getting any data in the target database is the following:
1) clear the target database
2) Run the replication for all cells
3) Run an export of all data on the target database
See if you get anything in the export file, maybe you are getting some of the data or possibly it is a rollup issue. Just a thought.
Jeff

Replicated Partition Question

With a replicated partition is it possible to have the source area be the same and send it to 2 different targets in the same database.
here is what i am trying to accomplish
Source A
@DESCENDANTS("GM",0),@DESCENDANTS("SECURED",0),"OCT","NOV","DEC",@DESCENDANTS("CUSTOM1",0),@DESCENDANTS("CUSTOM2",0),@DESCENDANTS("CUSTOM3",0),@DESCENDANTS("ICP",0),"2014","Version4","OUTLOOK","Local",@DESCENDANTS("SVCNA",0)
Target A
@DESCENDANTS("GM",0),@DESCENDANTS("SECURED",0),"OCT","NOV","DEC",@DESCENDANTS("CUSTOM1",0),@DESCENDANTS("CUSTOM2",0),@DESCENDANTS("CUSTOM3",0),@DESCENDANTS("ICP",0),"2014","MONTH1","OUTLOOK","Local",@DESCENDANTS("SVCNA",0)
MAP A
"VERSION4" to "MONTH1"
Source B (same as A)
@DESCENDANTS("GM",0),@DESCENDANTS("SECURED",0),"OCT","NOV","DEC",@DESCENDANTS("CUSTOM1",0),@DESCENDANTS("CUSTOM2",0),@DESCENDANTS("CUSTOM3",0),@DESCENDANTS("ICP",0),"2014","Version4","OUTLOOK","Local",@DESCENDANTS("SVCNA",0)
Target B
@DESCENDANTS("GM",0),@DESCENDANTS("SECURED",0),"OCT","NOV","DEC",@DESCENDANTS("CUSTOM1",0),@DESCENDANTS("CUSTOM2",0),@DESCENDANTS("CUSTOM3",0),@DESCENDANTS("ICP",0),"2014","MONTH1","ROLLING3MTH","Local",@DESCENDANTS("SVCNA",0)
MAP B
"VERSION4" to "MONTH1"
"OUTLOOK" to "ROLLING3MTH"
Tried setting this up and it doesnt work
Thinking I need a maxl to create partition, replicate drop it create a second partition, replicate, and drop it.
Any thoughts
Thanks

They are.
Version Dimension is Version1-5 in one app and Month1, Month2, and Month3 in the other app.
Scenario Dimension is Outlook in one app and Outlook AND ROLLING3MTH in the other.
Another thing is I can get the replicated partition to refresh the data. But if I have the map for OUTLOOK to ROLLING3MTH it only pushes to ROLLING3MTH. If I leave out the map it only goes to OUTLOOK in Target.

Error while extracting data to replicated partition (EAL)

Hi,
I´m using Essbase Analytics. I want to create a copy of my HFM application in Essbase.
So I´ve created a new bridge. In the Essbase tab of the bridge I choose "Replicated partition", because I want the data in Essbase directly, not in the EAL server.
So EAL created the application, database and the outline.
In the extract tab I select my created region and click "Extract data". After some time it ends, but no data is stored in the essbase database!
The log file of the EAL server says: Extract region requested (time stamp is the beginning of the process)
Has anyone an idea??
Thanks, Stefan
P.S.: The creation of an transparent partition works fine and I can see data via Smartview.

We use EAL with the transparent partition option without any issues. We write some report scripts to export the data from the app and load into another essbase app periodically for reporting. We can also use smartview or the add-in to pull data directly from the EAL essbase apps.
What are you trying to do that requires you to use a replicated partition? We were told transparent was the preferred method and so we used that option.

Replicated Partition-Cell Count not matching, what to do with Mappings tab

Hi All
I am creating a Replicated partition between 2 cubes on 9.3.1. The source cube has 8 dimensions(Cube A) and the target cube has 7 dimensions(Cube B).
2 Dimensions in cube A dont exist in Cube B and 1 Dimension in Cube B doesnt exist in Cube A.
6 of the dimensions map directly.
How do i deal with the 2 Dimensions in cube A that dont match cube B? At the moment I have mapped them to (void) in the mappings tab, by just selecting the dimension name and putting void in the target.
Cube B has dimension called SBU. All data from Cube A needs to go against member SBU Input in Cube B. I am stuck as to how to do this?
Cheers
Simon
Edited by: SimonWatts on Oct 16, 2008 4:23 PM

I believe the only issue that is likely to be wrong is the need to select a single member in the dimensions that you are eliminating (through a mapping to void). The 2 dims that exist in cube A should be selected as a single member for each, and mapped to void. If you selected the entire dimension in the partition, and only mapped the root to void, you would have a mismatched cell count.
So, change the partition spec to use a single member in those dimensions (if needed), and make sure that the member you select is mapped to void, which is not necessarilly the dimension itself.
Then, you do a similar void mapping to the SBU Input member, "Void = "SBU Input"". That handles the new cell count aspect if the other dimensions line up.
In total, there are three mappings identified from this. Two map source members to void, and one to map a target member to void.

Replicated Partition - Dynamic Calc member

I am trying to do a replicated partition where the source has 5 dimensions (Time, Account, Country, Product and Scenario) and the target has 4 dimensions (Time, Account, Country and Scenario).
I am trying to map "Product" to "void" because it's not needed in the target. However, Essbase won't let me because "Product" is dynamic calc.
Does replicated partition not allow dynamic calc members? In this case I am mapping that to "void", why would that matter?

What error is it giving you? I have a similar situation in which I am using a replicated partition and mapping a dynamic calc dimension to (void). It seems to be working fine for me.

Replicated Partition: One to many?

I am hoping to set up a replicated partition, which will take exchange rate data from source to multiple targets.The issue is that I have multiple homes in any given target database for (eg) USD rate. ie I have tried using UDA's, but one USD tagged member in source, has multiple USD tagged members in target, hence partition doesnt verify.In short, can I map one to many, source to target in a replicated partition?Thanks in Advance

Are you mapping from one outline to many outlines by using the same member in the source outline to couple different target outlines? If your answer is yes, then yes you can do it. ---Message Posted by kmooney ??3/19/02 07:16---I am hoping to set up a replicated partition, which will take exchange rate data from source to multiple targets.The issue is that I have multiple homes in any given target database for (eg) USD rate. ie I have tried using UDA's, but one USD tagged member in source, has multiple USD tagged members in target, hence partition doesnt verify.In short, can I map one to many, source to target in a replicated partition?Thanks in Advance

Essbase 11.1.2.3 Replicated Partition - No data replicated to target

Hi
I just created replicated partition in Essbase 11.1.2.3. Validation of partition was successful and I have made sure all mapping are identical between Source & Target database.
There is no data replicated to target.
Can anyone tell me what's the problem here?
Thanks

I would recommend to start with a single cell and then see if that works. If it does then expand to full. Also explaining the structure of source and target and mapping will also help us identify the issue.
Regards
Celvin

EAL Bridge - Replicated Partition

Hi Gurus,
Can data can be replicated in Essbase using EAL Bridge, configured using Replicated Partition in real time. If so, how frequently will the data replication happen.
I know that this happens real time or very close to real time if we use Transparent partitions. But want to understand how replicated partition works.
Also, will there be any difference for the users who use Smart view to view data between Transparent and Replicated partitition or the user experience will be the same?
Thanks.

Yes , it can be replicated . EAL Interface does provide an option for using Replicated partition, You have an Option to set in " Data Update Interval" within EAL to how frequently you want to replicate the data between Source and Target.
There are Technical difference between Replicated and Transparent , but Physically users wont find any difference when using Replicated . Just that in Transparent Data is loaded only in Source , as you might know in Replicated Part of the data is Physically available in Destination also.

Performance tips on transparent and replicated partitions?

I am quite new to this partitioning scene. Does anybody has tips on how to improve the performance and create the most feasible tranparent and replicated partitions? Thanks.

Our design is triangle shaped structure. There is a main application getting fed from two sub applications and these two sub applications are connected also by a transparent partition. One of the sub applications is the same as the main application. Same number of dimensions with the same dimensions. The second sub application is a smaller subset of the main application with less dimensions. All the transparent partitions defined as "(@IDESCENDENTS("Managerial Statement of Operations") @IDESCENDENTS("Income Statement Ratios") @IDESCENDENTS("Operating Ratios") @IDESCENDENTS("Statistics")@IDESCENDENTS("System Administration")) @IDESCENDENTS("Time") @IDESCENDENTS("Income Statement Type") @IDESCENDENTS("Funding Type") @IDESCENDENTS("Network Indicator") @IDESCENDENTS("Product") @IDESCENDENTS("Market Segment") @IDESCENDENTS("State") @IDESCENDENTS("Scenario") @IDESCENDENTS("Trading Partner") @IDESCENDENTS("Organization")" at the source and "(@IDESCENDENTS("Managerial Statement of Operations") @IDESCENDENTS("Income Statement Ratios") @IDESCENDENTS("Operating Ratios") @IDESCENDENTS("Statistics")@DESCENDENTS("System Admin - PL")) @IDESCENDENTS("Time") @IDESCENDENTS("Income Statement Type") @IDESCENDENTS("Funding Type") @IDESCENDENTS("Network Indicator") @IDESCENDENTS("Product") @IDESCENDENTS("Market Segment") @IDESCENDENTS("State") @IDESCENDENTS("Scenario") @IDESCENDENTS("Trading Partner") @IDESCENDENTS("Organization")" at the target. The dimensions are "Account", "Time", "Scenario", "Market Segment", "Income Statement Type", "Funding Type", "Product", "State", "Organization", "Trading Partner", and "Network Indicator". Thanks.

Difference between transparent and replicated partitions

whats the difference between transparent and replicated partitions in EAL. currently we have created essbase cube via transparent partition in eal. performance of obiee reports on essbase cube is very bad. now somebody suggested to create essbase cube via replicated partition in EAL. what difference would it make. one guy said replicated partition would make it more slow. i am confused. please explain.

Transparent Partition does not occupy or create extra memory Space in the Destination Application , it just shows the Data from Source to the Destination cube . This partition is completely dependent on Existence of Source Data . While , in replicated Partition you can use a copy of source data in the Destination cube.
FYI : Hyperion Essbase 11.1.1.0 &#8211; Partitioning and its use cases &#8211; Transparent, Replicated and Linked part…

Replicated Partition - overwrite

Has anyone heard of this?I have cube2 that gets data from cube1 via a replicated partition.The user wants the flexibility to override a member after replication.Problem:After the first time that replication is run, the member cannot be altered in any way. The database will not accept the override and if the database is reset the value also is not accepted. Other values (not in the partition area) can be loaded. I tried this on a few items in the partition area.If a new App is created, the data can be loaded - until the first time I run the replication. After that - it's messed up.Ideas?H

There is a setting (appropriately in the settings area accessed by clicking the settings button) in partition manager that applies to the partition that is "The target partition can be updated".By default, the target cells of a replicated partition are read-only. This read-only status should take effect when the partition is saved, not after the first replication, as you indicate.Does this address your problem? Jeff McAhren Dallas, Texas

Replicated Partition Hangs

I have created a replicated partition and everything validatescorrectly. When I attempt to replicate across the partitionit seems to be working but its just hanging. There is an .indfile created immediately in the new db but no page files. After a few minutes I kill the request and a page filesuddenly appears and the data in the cube exists like I wouldexpect it to. Anyone have any idea whats going on?

I looked up the error message codes and found that 1130203 seems to be the key. <blockquote>quote: <hr>1130203 Possible Problems Analytic Services is unable to allocate memory. Possible Solutions Try any of the following suggestions to fix the problem. Once you fix the problem, check to see if the database is corrupt. Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occuring, add more memory to the server computer. If you are on a UNIX computer, check the user limit profile. Check the block size of the database. If necessary, reduce the block size. Check the data cache and data file cache setting. If necessary, decrease the data cache and data file cache sizes. Make sure that the Analytic Services computer has enough resources. Consult the Analytic Services Installation Guide for a list of system requirements. If a resource-intensive application, such as a relational database, is running on the same computer, the resource-intensive application may be using the resources that Analytic Services needs. See Also 1006006 1006010 1006015 1006023 <hr></blockquote> It looks like you may be requiring more memory than might be available. This is the same sort of error that you see when you find dynamic calcs needing more calc lock block space, a problem normally resolved by increasing the data cache. It may be that the sparse-dense arrangements of your source and target databases are organized in such a way that you need to have multiple blocks cached for each during the replication. Without seeing the outlines and partition definitions, this is a best guess. I don't know whther the order of dimensions in the partition definition makes any difference, but different organizations can cause memory allocation problems, especially if the server is running at full load. You might see if there is any difference when replicating during a slow use time. Check to see that all inactive applications are stopped. That may help memory allocation. If you have a separate test server, you may want to play a bit with settings. Otherwise, try monitoring memory use on the server when doing the partition.

Replicated partition Refresh

Similar Messages

Maybe you are looking for