Monday, October 27, 2014

How to avoid implicit share in config file.

When does Implicit sharing happen in Essbase? And what are the ways we can define them in Essbase config file?

Cause & Solution

1) A parent has only one child. In this situation, the parent and the child contain the same data.
Essbase ignores the consolidation property on the child and stores the data only once — thus the parent has an implied shared relationship with the child.

2) A parent has only one child that consolidates to the parent. If the parent has four children, but three are marked as no consolidation, the parent and child that consolidates contain the same data. Essbase ignores the consolidation property on the child and stores the data only once — thus the parent has an implied shared relationship with the child.

3) The following commands can be inserted in the CFG file to disable Implied Sharing:
IMPLIED_SHARE FALSE/TRUE (This shall Turn OFF/ON implied sharing for All Application on that Essbase Server)
IMPLIED_SHARE [app_name] FALSE/TRUE (This shall Turn OFF/ON implied sharing for Specified Application on that Essbase Server)
Tagging the Outline Members “Never Share” Turns OFF implied Sharing for those Members and not tagging Turns ON implied sharing.

Order of Prevalence
Member level Implied Sharing Setting – Prevails over Application, Server Setting
Application level Implied Sharing Setting – Prevails over Server Setting
Server level Implied Sharing Setting – Least


4) 
ImpliedShare.txt exists in E:\Oracle\Middleware\user_projects\epmsystem1\ EssbaseServer\essbaseserver1\bin


Hope this Helps.

Greetings
SST!

No comments:

Post a Comment

Oracle Planning and Budgeting Cloud (PBCS) - August 2018 Updates

The following announcements and considerations are outlined in the upcoming  Oracle Planning and Budgeting Cloud (PBCS)  update: Oracl...