EPMA REDEPLOY

Hi, I've a HFM application in EPMA, when I redeploy the app there are many sections that are not recognized and as a consecuence that impacts in the consolidation method dimension deleting all members. This only happens when I don't select "Clear all metadata and data" option.
Hope somebody could help me!!!
Regards!!

A deploy is really for first time deployment where the database tables are created, application registered in shared services, application created in Essbase, also you don't have the full deploy option which is for when redeploying.
Have a read of the following for more information - Deploying Planning Applications
Cheers
John

Similar Messages

EPMA Redeployment Error: Server.TaskOutOfMemoryException

Hi everyone,
we are working with with EPMA, Fusion Edition - 11.1.2.1.00.1204 and are facing the following problem:
When we redeploy one of our Essbase BSO applications we get the following error:
"Server.TaskOutOfMemoryException"
Who can help us?
Thanks in advance!

It might be worth having a look at the following doc on Oracle Support - Error: "server.TaskOutOfMemoryException" When Deploying an Enterprise Performance Management Architect (EPMA) Application [ID 1324301.1]
Cheers
John
http://john-goodwin.blogspot.com/

Error While Redeploying 11.1.2.2 EPMA essbase cube

Hi ,
I have a EPMA esssbase application (11.1.2.2) and having problems while redeployment.
The suppose the Hierarchy of a dimension is like this during 1st deployment :
Dimension+
MemberA
MemberA_1(Store)
MemberA_2(Store)
MemberB
MemberB_1(Store)
MemberB_2(Store)
MemberB_3(Store)
( Dimension has two child MemberA and MemberB
MemberA is Parent of MemberA_1 and MemberA_2
MemberB is Parent of MemberB_1 and MemberB_2 and MemberB_3
This gets deployed fine . Now suppose the MemberB_3 gets is regrouped from MemberB to MemberA . In EPMA I do a "Cut" and "Paste As a Child" on MemberA and it is fine.
Now while validating it does not give me an error. The deployment completes successfully . When I see the outline , I see the following hierarchy -
Dimension+
MemberA
MemberA_1(Store)
MemberA_2(Store)
MemberB_3(Shared)
MemberB
MemberB_1(Store)
MemberB_2(Store)
MemberB_3(Store)
( Dimension has two child MemberA and MemberB
MemberA is Parent of MemberA_1 and MemberA_2 and MemberB_3 as a shared member
MemberB is Parent of MemberB_1 and MemberB_2 and MemberB_3 )
How do I avoid such a happening??
Am I doing anything wrong ??? Any process needs to be followed??? Kindly let me know your thoughts on this.
Currently I have advised the following workaround.
1) Edit from EAS Console - The steps that need to be followed are as follows:
a) Take a data backup of the whole application
b) Regroup the Dimension members as per the new requirement.
c) Deploy the essbase applications.
d) Log into EAS console , and change the Property of the Dimension Members which are shared to Stored and the same dimension members where the property is Stored , change it to shared and save the outline.
e) After the restructuring is complete , again open the outline in the EASconsole and delete the Dimension members which are tagged as shared and then save the outline.
Is this the only way to handle this issue or there is something else. ???
I also tried the following :
a)I deleted a member from EPMA and deployed the application. The deployment was successful . But when I opened the outline , the member(that I deleted from EPMA) was still there.
b) I added a new member to the EPMA and deployed the application. The deployment was successful. When I opened the outline , the member(That I added in EPMA ) was added properly in the outline.
When am adding a new member it gets added properly , but after that when I try changing the properties of that member or a move the member to a new parent or delete the member , EPMA is unable to update the Essbase Application.
Kindly help .
Regards ,
SS

This gets deployed fine . Now suppose the MemberB_3 gets is regrouped from MemberB to MemberA .
Im not sure what you mean by this. Are you purposely trying to make a shared memeber? If so create a another memeber_c and add the shared in there.
Can you clarify?

EPMA 9.3.1 - Redeploying an application did not finish the job in EPMA

I was redeploying an application in the EPMA library. The refresh completed in Essbase, but the job did not complete in the EPMA console - we are not able to access the application - message is "Error - Service was unable to process request--> there is currently no application deployment pending for application "IncStmt". As a result the application export status for the last export cannot be updated. (org.apache.axis.axisfault). I cannot do anything to the application - this error comes up immediately when you click on the application. Any ideas on how I can clear it?

I did try changing the deploying time out but in the application library i still cannot redeploy my application.I even tried creating a new application and tried to deploy it but it too didnt deploy and shows the status as deployment pending.Is there any other way out.
It shows:
Detail : Initiating Product Action...
Inspecting Deployment History...
Generating Headers and Callback Information...
Generating Application Data...
Status : Running
Progress : 4%
but its not getting deployed for a really long time .Please Help
Edited by: user8667776 on Jul 28, 2009 10:15 PM

What are the front to backend steps for redeploying a live EPMA Planning ap

Hello All,
Can anyone outline considerations/steps for redeploying an EPMA Planning application in a live environment? Do users have to be logged off of the system? Does the Planning app have to be put into Administration mode? Does the Planning Essbase DB have to be put into standby mode or users logged out of it first? Do I have to restart Planning afterward? Thank you in advance for any information that you can provide.

Hello John,
Thank you very much for your quick response. We currently try to do this after hours but it seems invariably that there were some users still in or had some processes running that seemingly hang when we try to redeploy EPMA/Planning (the users are not able to log back in after the EPMA Planning re-deployment). Is there a sure fire way to ensure that users are out of the system before redeploying so that this doesn't happen? Please advise, thank you sir.
Edited by: 859885 on May 18, 2011 2:51 PM

Error 1002097 while redeploying the application

Please, SOS! :(
I need to redeploy my Planning 11.1.1.3 application in EPMA after having added some some new members to Version dimension in the Dimension Library. Validation of the application goes ok but the redeployment is aborted with the following error:
+Detail : An Exception occurred during Application deployment.: The Hyperion Essbase operation failed with an error code: % ERROR_CODE%.com.hyperion.planning.olap.EssbaseException: Unable to load database [%s] (1002097)+
I will highly appreciate any ideas! Thanks!

John, thank you so much for your guidance! I guess I am approaching the roots of this problem. So, I deploy the application with no problems if I leave "Create Outline" box unchecked. I cleared the application log and then launched the redeploy again with "Create Outline" box checked and for sure I got this error again, but then in EAS I have been able to see only the outline of the 1st of the 3 plan types to be created. Then I viewed the log for my application in EAS and it read the following:
+[Fri Jul 30 15:51:35 2010]Local/AppName///Error(1120006)+
+Unable to lock file [HyperionHome\products\Essbase\EssbaseServer\APP\AppName\Plan1\Plan1.esm]. Essbase will try again after a short delay.+
+[Fri Jul 30 15:51:36 2010]Local/AppName///Error(1120005)+
+Unable to lock file [HyperionHome\products\Essbase\EssbaseServer\APP\AppName\Plan1\Plan1.esm]. Please make sure other processes do not access Essbase files while Essbase server is running.+
+[Fri Jul 30 15:51:36 2010]Local/AppName///Warning(1007089)+
+Unable to open [HyperionHome\products\Essbase\EssbaseServer\APP\AppName\Plan1\Plan1.esm] for database [Plan1]+
+[Fri Jul 30 15:51:36 2010]Local/AppName///Error(1002097)+
+Unable to load database [Plan1]+
+[Fri Jul 30 15:51:36 2010]Local/AppName///Error(1002097)+
Unable to load database []
+[Fri Jul 30 15:51:36 2010]Local/AppName///Error(1002097)+
Unable to load database []
John, I would very highly appreciate your comment on the above! Thanks so much!

Urget Error while deploying the HFm application in EPMA

Dear All
Please suggest me on the below error while i am deploying the HFM application sencond time system throughs the below error. for this what i have to check ??
Error :The 'Test_YearCon' dimension has been modified since the first successful deployment of the application.
Error: The 'Test_Period' dimension has been modified since the first successful deployment of the application.
Thanks in Advace.
Regads.
Rao

you have made modifications in your Year and Period dimensions, even in just the aliases possibly, since the last time the Application was deployed.
it is not allowed to make any modifications to these dimensions after 1st deployment. HFM does not support it.
to get a successful deployment you will need to delete the application and redeploy.
also please make sure you are using the latest Service Pack version of your release of EPMA e.g. if 9.3.1 make sure you are using 9.3.1 Service Pack 3 and fully read the Readme documentation that comes with it.

EPMA woes 11.1.2.1

Hi all,
I require some suggestions for some problems I have encountered with EPMA. I upgraded a Planning system from 9.3.1. to 11.1.2.1. I am using interface tables to update some of the dimensions. I have an import profile which replaces each dimension and loads the dimensions into the shared library. Two planning applications have these dimensions. Shared dimensions should automatically update the application they are assigned to this is not happening. Data is unable to load into essbase following a deploy as members are missing. They are in the shared library but not the apps.
The second issue relates to alias. The error reads
"Swapping alias names is not supported because aliases must be unique in the application. To resolve the issue, temporary name must be used for one of the alias then the application redeployed. Then the temporary name can be changed and the application redeployed again."
Since the dimension is replaced I cannot see why EPMA believes a duplicate alias is being assigned. It is trying to assign the alias to the same member. A work around is to change the alias and deploy. Change it back, run and import and deploy. This is not good for automation. I have checked and there are no duplicates in the interface tables.
In version 9 the system used an ads file and none of the above never occured.
I would appreciate any suggestions as this is preventing an upgrade going live.
Thanks,
Nathan

I am also facing same problem,
Swapping alias names is not supported because aliases must be unique in the application. To resolve the issue, temporary name must be used for one of the alias then the application redeployed. Then the temporary name can be changed and the application redeployed again.
Any suggestion would be great.
-suresh.k

EPMA batch client with Essbase application - does not update aliases

Hello,
We are using EPMA 11.1.2.1 for managing outlines for Essbase applications.
Changing aliases in EPMA and launching manually redeploy from Workspace, with flag "Full Deploy" change correctly the aliases in Essbase..
Using the EPMA batch client to redeploy the Essbase application deletes all aliases in Essbase outline.
Someone knows how to solve this problem or what am I doing wrong in the EPMA script?
thanks...
this is the EPMA script:
SET bpmaserverurl=http://epma_server/hyperion-bpma-server;
SET workspaceurl=http://work_space_server/workspace;
login admin,password;
Execute reDeploy
Parameters(ApplicationName, InstanceName, waitforcompletion, deployOption)
Values('PNL', 'ESSBASE_STUDIO_SERVER:essbase_server_name', 'True', 'AppView');
Quit;
Edited by: AlexPavel on May 20, 2011 1:21 PM

Hi,
Thank you for posting in Windows Server Forum.
From your description it seems that you are facing issue only with windows 8\8.1. So firstly suggest you to check with application support team, whether they have whole support for application with newer version. Also check once with application support team
regarding this issue.
This issue occurs because the local taskbar does not receive the EVENT_OBJECT_NAMECHANGE event from the system due to a timing issue. The EVENT_OBJECT_NAMECHANGE is needed to update the taskbar title information.
More information (For reference).
The taskbar may not show the application name correctly when using a Terminal Server RemoteApp
Hope it helps!
Thanks.
Dharmesh Solanki

HFM deployment issue on EPMA - The application already exists

The first time I deploy the HFM application everything works fine until I try to redeploy after deleting the application. I have tried registering the application to SS and then try deleting it from there but that does not work. Here is my deployment abort details:
Submitted Time : Saturday, March 21, 2015 3:38:22 PM
Last Updated Time : Saturday, March 21, 2015 3:38:33 PM
User Name : hypadmin
Process Name :
Thread : 0
Server :
Detail : Initiating Product Action...
Generating Headers and Callback Information...
Generating Application Data...
Posting Product Request...
Waiting For Status Updates...
PRODUCT_UPDATE: Update from product
Financial Management is transforming metadata from EPMA...
Creating Application...
The application already exists.
Please help and thank you.
Gideon Seroney

Got around this issue by creating a classic application over the epma app, provision admin then delete it from consolidation admin.
Unfortunately it seems that the epma application should never have been registered like a classic app. Always perform 'deploy' and never 'register' since it get stuck in SQL data tables. Unless you are a DBA I would not suggest monkeying with the tables to begin with.
Thanks!

Deployment issue with EPMA & Planning in 11.1.2

Hi
I installed the following applications of Hyperion suite:
Essbase
EPMA
CalcManager
Planning
During configuring i configured each product separately since i wanted to configure separate DB for each of them.
The configuration went with no issues. But now when i log-in into workspace and go to Navigate, i only see administer.
There is no option for EPMA and Planning applications.
Did i miss any step?
I have used IIS as my webserver because Oracle HTTP gave me some error while deploying (unable to initiate OPMN). Is it some issue with IIS
I have installed my applications on Win XP SP3, IIS 5.1 and its a 32bit machine

Hi
Please redeploy only the Web Server under shared service. It has to be redeployed once EPMA and others are configured.
Thanks
Rupak
Mantra to Win | WinMantras.com | http://hyperion.winmantras.com

Can't open EPMA from workspace

Hi Folks,
I have successfully installed and configured EPM 11.1.1.3 on a single machine(Windows 2003 R2) and everything works fine but the problem is I can not open EPMA and Calculation Manager from the workspace.
I can connect and logon into http://localhost:19091/awb but in workspace menu, I see menu name as ${MITEM_DIMENSION_LIBRARY}, ${MITEM_APPLICATION_LIBRARY}, ... instead of Dimension Library, Application Library, ... and when I click the menu, I am getting the error message as "Invalid or could not find module configuration". I have redepolyed using configurator several times but still getting the same problem.
Could you please help me to solve this problem?
Thanks,
Chang.

After I configured HFM(Database, DCOM, Application Server, Web Server) with redeploying 3 Application Servers(Calc Manager, PMA, Workspace), It works fine.
Thanks.

EPMA Shared Members not reflecting in Planning application post deployment

Hi,
I have added a member in 'Entity' dimnesion. The same member is also added in an alternate hiererchy as shared member (Using Insert member option in dimension library). When I refresh the application view, I do see both the original member and shared member in application vieiw. But post deployment, only the base member is reflected in planning application and not the shared member.
I have redeployed the application multiple times now, but i am still not able to see the shared members reflected in Planning application.
Kindly let me know if you have any idea on the same or faced a similar issue?
Regards
Meenal

Hi,
Have you patched up EPMA with patches from Metalink3
9.3.1.1 Patch includes -
6897835 SHARED MEMBERS IN ENTITY DIMENSION CAN NOT BE DEPLOYED TO ASO/BSO APPS
It is advisable to keep a look out for patch fixes with EPMA
Hope this helps
John
http://john-goodwin.blogspot.com/

EPMA - Essbase BSO application - UDA problem

Hi
we have a shared hierarchy in EPMA which we are using to maintain the Dimensions in the applications.
Among the dimensions that I need in the Essbase BSO application - two of them have specific UDAs assigned to them. (two for each member in these dimensions - UDAs can be common between the dimensions)
Dimension_A
--Member_A1 (UDAx, UDAy)
--Member_A2 (UDAp,UDAq)
Dimension_B
--Member_B1 (UDAx, UDAy)
--Member_B2 (UDAp, UDAq)
UDA
--UDAx
--UDAy
--UDAp
--UDAq
But when I deploy the application I am only seeing one UDA getting updated into the Essbase Outline (am checking via EAS)
Dimension_A
--Member_A1 (UDAx)
--Member_A2 (UDAp)
Dimension_B
--Member_B1 (UDAx)
--Member_B2 (UDAp)
I don't know why it is not updating the outline correctly - can anybody suggest what the problem might be ?
I have tried redeploying multiple times / deleting the dimensions adding them again / even deployed a new application from scratch - no luck.
Regards
Ankur

I tried even in another environment - had the UDA dimension from the Shared Library - and another local dimension.
Just added multiple UDAs to the same member of the Local dimension and deployed the application - but in the Essbase application it only updated the first UDA that I had assigned to these members.
For e.g. I added 3 UDAs to
MemberX : Check1, Check2 & Check 3
MemberY : Check3, Check1 & Check 2
But it only updated the first UDA in each
MemberX : Check1
MemberY : Check3
Is there any setting that I am missing ? in EPMA or in Essbase.
Not sure about EPMA but I don't remember any setting that we need to configure in Essbase for multiple UDAs (it always accepts multiple UDAs)
Regards
Ankur

EPMA Validation Error: dimension removed or deleted since first deployment

Dear experts,
Our deployment is on EPMA and we were able to successfully deploy the Planning application before. Then we tried to update the dimension by loading UDA to each members, after which, we hit this error at validation:
Error : The xxxx dimension has been removed or deleted since the first successful deployment of the application.
We did have UDA dimension in it before the update and all dimensions in the applications are shared from the library.
Our application is on 11.1.1.3 and we have tried to removed all associations and redo it, but still hit this error. As there are many members being assigned with UDA, wonder if it's possible to solve the error without deleting the UDA dimension and recreate it?
Any input help, please kindly help!
Thanks!!
Edited by: 845931 on Apr 5, 2012 4:20 PM

You will find it in My Oracle Support.
The contents are as below:
Applies to:
Hyperion Planning - Version: 11.1.1.0.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Goal
You cannot delete a UDA dimension from EPMA once the application it belongs to has been deployed.
ERROR
The 'Colour' dimension has been removed or deleted since the first successful deployment of the application.
Is there some way to remove the UDA dimension (not just modify its members)? This was possible in the Classic Planning interface but is not when using EPMA.
Solution
This is a limitation of EPMA and Planning. There is no mechanism in version 11.1.1.3 and earlier to allow EPMA to remove dimensions from Planning, and because EPMA treats UDAs, Attribute Dimensions, and Smart Lists as dimensions they also cannot be removed from Planning once the application has been deployed for the first time. They can be modified, but not deleted.
In version 11.1.2 you can delete a UDA dimension in EPMA with no errors but the application will no longer validate (throwing the same error as in 11.1.1.3) and therefore cannot be deployed. However, this does offer an easy way to remove all UDAs assigned to members. If you delete and then re-create a UDA dimension in EPMA the application can be re-deployed again, even if you do not re-create any dimension associations. When you redeploy, all UDAs for this dimension are cleared from Planning and Essbase. This means that although the UDA dimension itself is required in EPMA, there is no trace of it in Planning and Essbase after redeploying.
HTH-
Jasmine.

EPMA REDEPLOY

Similar Messages

Maybe you are looking for