https://www.iarchsolutions.com/news/applying-the-1129-maintenance-release
A good blog to check out by iArch
This blog is dedicated to Oracle Hyperion EPM Technical Architecture and Support tips.
https://www.iarchsolutions.com/news/applying-the-1129-maintenance-release
A good blog to check out by iArch
Released April 28, 2022
EPM 11.2.9.0 New features:
As companies implement Oracle EPM Cloud components (FCC, Planning, ARC, etc.), EPM Automate is almost always a part of the process.
Typically with data loads and backups, which all of the components need, but also restructures, database refreshes, and more. Along with the growth in these scripts is the need to communicate to users and admins the status of everything.
Each script can send an email or a text with the status of each run. But with hourly data loads, backups, restructures, regression tests, etc. the number of emails can easily become overwhelming.
An email or text should be sent if there are problems, but if things are going well, is a deluge of emails really the right solution?
As an alternative, a simple webpage can do the trick. Since EPM Automate typically runs on a server, the server can also serve up a webpage with the status of each job.
The basic steps are to have each script write the status to a web page.
Then use an overall web page that incorporates all of the individual status pages.
Users can access the one overall page to see where everything is in real time.
To generate a deployment report:
EPM_ORACLE_INSTANCE/bin
.epmsys_registry.bat|.sh report deployment
.By default, the report is saved as EPM_ORACLE_INSTANCE /diagnostics/reports/deployment_report_YYYYMMDD_HHMMSS.html
.
You can add an optional file name argument to the command to save the HTML report with a different file name or location. For example, this command saves the report as c:/epm_setup/epm_deployment.html
:
epmsys_registry.bat|.sh report deployment c:/epm_setup/epm_deployment
Use a single script to start or stop all Oracle Enterprise Performance Management System services. EPM System Installer installs a single start script in EPM_ORACLE_INSTANCE /bin
, called start.bat
| start.sh
.
Running the single start script on a machine in your EPM System deployment starts all EPM System services installed on that machine. The single start script works by calling the individual start scripts for every product.
The user running the start script should be a member of the Administrators group.
To start EPM System services:
After the single start script completes, you can run Oracle Hyperion Enterprise Performance Management System Diagnostics to determine which services on a machine are running. See Validating the Installation and Verifying Deployment.
Note:
To stop EPM System services: A single stop script is also installed in EPM_ORACLE_INSTANCE /bin
, called stop.bat
| stop.sh
. Running the stop script on a machine in your EPM System deployment stops all EPM System products on that machine. To stop services, from the Start menu, select Oracle EPM System, and then Stop EPM System.
Using Essbase 21c with EPM System
Beginning with Release 11.2.8, you can use Oracle Hyperion Planning and Oracle Hyperion Profitability and Cost Management applications from an Oracle Enterprise Performance Management System deployment to report on Oracle Essbase cubes in a Oracle Essbase 21c deployment integrated with EPM Shared Services.
Installation considerations in a Linux distributed environment:
Note:
The Hyperion Product Management recently advised the release of Patch Set Updates (PSU) for Oracle Hyperion Essbase 11.1.2.4.x.
These PSU downloads are available from the My Oracle Support > Patches & Updates section.
33485383 - Hyperion Essbase Server
Refer to the Readme files prior to proceeding with these PSU implementations for important information that includes the supported paths per component, along with a full list of the defects fixed, additional support information, prerequisites, details for applying patch and troubleshooting FAQ's. It is important to ensure that the requirements and support paths to this patch are met as outlined within the Readme file.
The Readme file is available from the Patches & Updates download screen for each of the Hyperion Essbase components.
Caution: Oracle recommends using the same version of all Essbase portfolio products (Essbase, Essbase Administration Services, Hyperion Provider Services, and Essbase Studio) and components (server, client, runtime client, API, and JAPI). When only some Essbase portfolio products are included in a patch release, the last released versions of the products that are not included in the patch are supported.
Essbase Administration Services 11.1.2.4.047, Provider Services 11.1.2.4.047, and Essbase Studio 11.1.2.4.045 are supported for use with Essbase 11.1.2.4.047. Furthermore, Essbase Runtime Client needs to be updated on systems that Essbase Administration Services is installed starting with this patch.
Recommendation: After you apply a patch within the same release codeline, Oracle recommends as a best practice that you export the data from your databases, clear the data from the databases, and then reload the data.
======================================================================================