Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1681979.1
Update Date:2014-07-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1681979.1 :   How Does Data get Deleted when Renaming Member In EPMA And Deploying To Essbase  


Related Items
  • Exalytics In-Memory Machine X3-4
  •  
  • Hyperion Essbase
  •  
  • Oracle Exalytics Software
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalytics>Oracle Exalytics>DB: Exalytics_EST
  •  




In this Document
Goal
Solution


Created from <SR 3-8788748841>

Applies to:

Hyperion Essbase - Version 11.1.2.2.103 to 11.1.2.2.103 [Release 11.1]
Oracle Exalytics Software - Version 1.0.0.2.0 to 1.0.0.4.0 [Release 1.0]
Exalytics In-Memory Machine X3-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to retain data when renaming members in EPMA and then deploying to any Essbase cube?
 

Solution

Studio is a batch load tool. The way Studio deals with rename is actually to clear the outline
(delete all members) then reload all members, including the renamed member (such as D004134_FCL1), to outline.

So when "clear outline" happens, the link between cells and metadata (members) are broken. 

The reloading of members can rebuild the link for those cells whose intersection members (not renamed) are reloaded to outline.

But the renamed members will cause those cells which still remember the "original" members to lose the link. Customers need to reload data whenever they rebuild outline.
 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback