Monday, 19 August 2019

Oracle Hyperion Issue: Port number in WebLogicCluster parameter specified in httpd.conf is not an integer less than 65535

Recently we faced one issue, which is related to weblogic cluster details on httpd.conf (mod_wl_ohs)

While doing regular maintenance activities, we have restarted all services over weekend. We have environment of 5 servers, but one of the server services not working in workspace, even services are up and running in particular. We have reporting and analysis, FR in that server, we got startup document error, no Explore button in workspace.



If we click okay, startup document error popup page. Next Internal error popup.




When i click Show details, i found below error msg.

<HTML><HEAD><TITLE>Weblogic Bridge Message</TITLE></HEAD> <BODY><H2>Failure of server APACHE bridge:</H2><P><hr><PRE>Port number in WebLogicCluster parameter specified in httpd.conf is not an integer less than 65535, or servers are not specified correctly. Cannot continue.</PRE><P>
<hr> </BODY></HTML>

Before proceeding with any changes here, please take proper backup and proceed..!!


Check out below files in Foundation server (if OHS configured along with Foundation), Otherwise in OHS server.



Solution:

When i verified httpd.conf file and mod_wl_ohs file, in mod_wl_ohs file, whatever services we have in this reporting server, that is not correct. How it got updated in that file we don't know.

Replaced that hostname with correct hostname and restarted services.

Now issues resolved..!!

Thanks,
Mady

Tuesday, 2 July 2019

Hyperion Updates from Kscope19 - On-Premise 11.2 version

Updates on On-Premise 11.2






Thanks,
Mady

Financial Reporting Migration Tool : FR Reports migration from HFM to FCCS

Kscope19 updates on Hyperion On-Premise:

The Financial Reporting Migration Tool (FRMT) is a utility that accelerates the migration and conversion of financial reports built in Oracle Hyperion Financial Management (HFM) into financial reports that are compatible with Oracle Financial Consolidation and Close Cloud (Oracle EPM Cloud).


The Financial Reporting Migration Tool (FRMT) is a utility that accelerates the migration and conversion of financial reports built in Oracle Hyperion Financial Management (HFM) into financial reports that are compatible with Oracle Financial Consolidation and Close Cloud (Oracle EPM Cloud).  This utility reduces the time and effort needed for report conversion by automating many of the manual tasks associated with the process.


The main features of the Financial Reporting Migration Tool include:


Maps dimension and member names to the new Financial Consolidation and Close model


Preserves the report formatting and layouts

Converts reports in bulk

Provides ready to use reports for Financial Consolidation and Close

The download includes the utility, full documentation, and examples.

Developers and implementer can extend and enhance the utility by editing the provide Python script to match specific use cases.











Reference links:

https://cloudmarketplace.oracle.com/marketplace/en_US/listing/50393071

https://kscope19.odtug.com/e/in/eid=32&s=2851&print=1&req=info


Thanks,
Mady

Friday, 21 June 2019

Oracle Hyperion Performance Tuning: Changing Heap size in UNIX machine

For UNIX machines or as an alternate method for Windows machine,
change the heap size of a managed server in the product start script:

On the machine hosting the product whose managed server you want to modify, open the product's custom start script in a text editor:

Go to below mentioned PATH for deploymentScripts

EPM_ORACLE_INSTANCE/bin/deploymentScripts/setCustomParamsManagedServerName.sh

For example, to change the heap size for the Foundation Services managed server, open EPM_ORACLE_INSTANCE/bin/deploymentScripts/setCustomParamsFoundationServices.sh.

For example, to change the heap size for the Planning managed server, open EPM_ORACLE_INSTANCE/bin/deploymentScripts/setCustomParamsPlanning.sh.

For example, to change the heap size for the EssbaseAdminServices managed server, open EPM_ORACLE_INSTANCE/bin/deploymentScripts/setCustomParamsEssbaseAdminServices.sh.

Modify the entry that looks like this:

set USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx512m
and edit the value for –XmxValuem to a value appropriate for your environment.

If  you want to change Xmx value to 8GB then mention as
set USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx8192m



Save the file.

Rerun the script for the product after making changes.

Complete these steps for each managed server on each machine in the deployment.

Thanks,
Mady

Oracle hyperion Performance Tuning: Changing the Heap Size in Windows

To change the heap size of a managed server:

For Windows machines, use Windows Registry Editor to change the heap size of the Windows service:

On the machine hosting the product whose managed server you want to modify, open Windows Registry Editor: Select Start and then Run, enter regedit, and then click OK.

In Registry Editor, select HKEY_LOCAL_MACHINE, then SOFTWARE, then Hyperion Solutions, then ManagedServerName, and then WindowsServiceName_InstanceName.

For example, if you deployed a single managed server, select HKEY_LOCAL_MACHINE, then SOFTWARE, then Hyperion Solutions, then EPMServer0, and then HyS9EPMServer_InstanceName.

If you scaled out a single managed server, on the scaleout machine, select HKEY_LOCAL_MACHINE, then SOFTWARE, then Hyperion Solutions, then EPMServer1, and then HyS9EPMServer_InstanceName.

For example, if you deployed Oracle Hyperion Planning, select HKEY_LOCAL_MACHINE, then SOFTWARE, then Hyperion Solutions, then Planning0, and then HyS9Planning_InstanceName.

Right-click JVMOptionX (where X is 1, 2, ...) whose value starts with -Xmx, and then select Modify. In Value data, change the value to a value appropriate for your environment.
-XmxValuem

For example, to set the heap size to 8 GB, enter the following:
-Xmx8192m

Start EPM System by selecting Start, then All Programs, then Oracle EPM System, then Foundation Services, and then Start EPM System.

Complete these steps for each managed server on each machine in the deployment.

Thanks,
Mady

Thursday, 20 June 2019

Oracle Hyperion FDM to FDMEE Migration Utility

Oracle that explains step by step process involved in migrating Oracle Hyperion FDM to Oracle FDMEE. It also discusses the challenges faced during the migration. It is intended to have a ‘look and feel’ of using the FDM Migration utility.

In EPM Release 11.1.2.4, FDM is no longer available. All customers who wish to continue using the key FDM functionality can migrate to FDMEE.

It captures key functionality from FDM, and preserves the ERP Integrator framework that enables users to load metadata and data, and to drill-through and write-back.

Pre requisites
 Download Patch 21379349: FDM CLASSIC TO FDMEE MIGRATION UTILITY V 1.0
 Working 11.1.2.x FDM Application Database
 Database details of the FDM application Schema
 Working FDMEE 11.1.2.4 Environment
 Downloaded FDM-FDMEE Migration Utility
 Database details of FDMEE Schema
 ODI studio Installed & Configured

Steps Involved in Migration
 Run the Prerequisite SQL Scripts in FDMEE & FDM Database
 Configure FDM Data source on ODI
 Import the Scenarios to ODI Designer
 Execute the Scenario from ODI
 Challenges in Migration

For complete migration steps, check Oracle FDMtoFDMEE_Migration_Whitepaper:
Oracle Hyperion Financial Data Quality Management (FDM) to Oracle Hyperion Financial Data Quality Management, Enterprise Edition (FDMEE) - White Paper on FDM to FDMEE Migration Utility (Doc ID 2077244.1)
http://docs.oracle.com/cd/E57185_01/epm.1112/fdm_migration.pdf

Thanks,
Mady

Wednesday, 19 June 2019

Hyperion 11.2 version release details and support details

Oracle is today announcing a “Continuous Innovation” release model for Oracle Hyperion
Enterprise Performance Management System 11.2, delivering ongoing applications and
underlying technology stack updates without a major upgrade. At the same time, we are
announcing Oracle Premier Support for Oracle Hyperion EPM System 11.2 through at least
2030.

This means that after upgrading to release 11.2 when it becomes available, Oracle Hyperion
EPM System customers running on release 11.2 will be able to continue to access new
applications functionality and separately uptake later versions of underlying technology for
years to come, without the time and expense of a major release upgrade.


Reference:

Thanks,
Mady