Followers

Saturday, January 30, 2016

JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer in deployment JRFWSAsyncJmsModule in hyperion 11.1.2.x


It is possible that Hyperion / Weblogic does not start anymore and weblogic or service sysout log pointing to force shutdown
This can have several causes 
• There is a deploy of web server made through the Configuration Tool (extra deployment)
• There is an extra tool installed in the weblogic server


ERROR::

<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
Caweblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml: The following failures occurred:
-- [JMSExceptions:045047]The SubDeploymentMBean JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer in deployment JRFWSAsyncJmsModule
can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue,
topic or quota) has a sub-deployment-name element with value JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer

at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:127)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)


Sollution:

Locate the config.xml file in the directory:
D:\Oracle\Middleware\user_projects\domains\EPMSystem\config

(at the Weblogic server (HSS server)) Edit this file and look for the following:

<sub-deployment>
<name>JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer</name>
<target>FMWebServices</target>
</sub-deployment>


Replace it with the following (only the word ‘FMWebServices’ to ‘JRFWSAsyncJmsServer’)

<sub-deployment>
<name>JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer</name>
<target>JRFWSAsyncJmsServer</target>
</sub-deployment>


Try again to start Hyperion.


Thanks,
Mady

Sunday, January 3, 2016

Deleting a dimension from Hyperion Planning application 11.x

                     Deleting a dimension from Hyperion Planning application 11.x

To delete dimension from Hyperion Planning application, we can follow the below steps:


John goodwin suggested in OTN like below, one of the simplest way to delete dimension::
You are really not meant to delete a dimension, if possible recreate the application without the dimension.
If you want to take the risk and delete the dimension using SQL then do a search on this forum and you will find some possible solutions.


My Team lead and friend Rahul Sharma suggested, using SQL we can delete dimension using below steps:
This procedure should only be performed by your SQL or Oracle DBA.

BE SURE YOU HAVE A BACKUP OF YOUR APPLICATION BEFORE ATTEMPTING THIS PROCEDURE.

You will need to delete all the children first, then the dimension.

If you have the dimension in forms, you may also need to(after step 5) go into the hsp_form obj_def_mbr table and delete all references of that object ID. Then delete the dim id in the hsp_form_layout table. Recycle services of Planning.

Procedure:
If you create a custom dimension in planning and wish to delete it,here is how you might remove it from SQL manually. We recommend that only someone familiar with relational databases attempt this.

The following assumptions are being made about the dimension:

* No forms have any references to the dimension.
* Any and all attribute dimensions have been removed from the dimension.
* Any and all members have been removed from the dimension.
* All security access has been removed from dimension.
* Any Alias associated with the dimension has been removed.

In this example we have created a dimension called DummyDimension.

1. Open the Enterprise Manager for SQLserver
2. Open the database that has your planning application
3. Open the table HSP_OBJECT
4. You need to find the row that has the dimension name you want to delete:
5. Take note of the OBJECT_ID in my example it is 50051, don't delete it yet.
6. Open the table HSP_MEMBER
7. Find and delete any rows that have a MEMBER_ID equal to the OBJECT_ID from step 5.
8. Close the Table HSP_MEMBER
9. Open the table HSP_MRU_MEMBERS.
10. Find and delete any rows that have a DIM_ID equal to the OBJECT_ID from step 5.
11. Close the table HSP_MRU_MEMBERS.
12. Open the table HSP_DIMENSION
13. Find and delete any rows that have a DIM_ID equal to the OBJECT_ID from step 5.
14. Close the table HSP_DIMENSION
15. Also delete it's reference from the HSP_UNIQUE_NAMES table.
16. Delete the row in the HSP_OBJECT table that you found in step 4.
17. Close the HSP_OBJECT table.
18. Open Essbase Application Manager for the application and remove the dimension from the necessary Essbase outlines. 
19. Restart the application server.

Thanks to John goodwin and Rahul Sharma...!!

For EPMA deployed application:
How Can We Delete Dimensions In Planning Once The application has been deployed From EPMA? [ID 1055007.1]


Thanks,
Mady