Hyperion Planning (MOSC)

MOSC Banner

Simple alias change causing full db restructure

edited Nov 23, 2016 4:00AM in Hyperion Planning (MOSC) 6 commentsAnswered

We recently made a simple alias change to a member name in a sparse dimension, performed a database refresh and now the refresh is doing a full restructure as if we moved or added a member to a dense dimension. This also happened when we made a change to several members in a sparse dimension and enabled them for use in another plan type.

Does anyone know what and why it would cause a full db restructure for simple changes to a dense dimension and how we can prevent it from happening again?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center