Happy New Year – 2018!
Over the years we have featured numerous posts on technical how-tos, tips & tricks and insights from our consultants out in the field. Going into 2018 we are looking forward to expanding on our topics and will include more business-process articles, client successes, event presentations and more! And in case you missed some of these, we thought you might like to see what the most popular technical posts have been to date:
Oracle bundles an installer for WebLogic with their Oracle EPM suite of products, that ‘phones home’ to Oracle for more information. Many of us deal with clients who have firewalls that may block all attempts to communicate from the installation server to Oracle.com or other outside Internet addresses. In these cases, the installer for Oracle EPM informs us of the communication error and asks us to provide proxy information for the installer to communicate with Oracle.com. Refusal to grant the proxy information results in another nag screen after which we can move on with our installation.
Maintain Custom Account Structure Requirements in Planning via Oracle DRM Sourcing: The Oracle Data Relationship Management (DRM) product has always offered impressive flexibility when it comes to meeting the metadata requirements of subscribing target systems. This flexibility extends across numerous products and systems and is not limited to just the EPM stack. This core strength goes back to the origins of the product and has been key to its evolution from its inception with Razza, on to Hyperion MDM, and now within Oracle DRM.
New Financial Reporting Web Studio and end of life for Web Analysis
Since the release of HFM 18.104.22.168, and its change in architecture, many of the utilities that HFM administrators had come to know and love were deprecated from the product. One of the most popular of these utilities was the standalone Copy Application utility. This utility allowed you to do a direct, DB level copy of an HFM application from one environment to another, regardless of the version (you could upgrade the application after the copy) and DB type (in the most recent versions of the utility). It copied all application table contents between the environments, without a need to reload or re-consolidate data. All you needed were two UDLs created on the server that contained the utility, one pointing to the source HFM DB server and one pointing to the destination HFM DB server.
Administrators of Hyperion Essbase who are attempting to patch their applications may encounter an error similar to:
Platform ID needed is : 215
Platform IDs supported by patch are: 233 912
ApplySession failed during prerequisite checks: Prerequisite check "CheckPatchAp
System intact, OPatch will not attempt to restore the system
OPatch failed with error code = 74
Oracle EPM “mega-patches” like 22.214.171.124.500 are large patch bundles that incorporate fixes for multiple products, and are meant to be applied across an entire environment at once. The patches are not meant to be applied to any one product or server individually. If there is a single product within the patch whose fix your organization needs badly, you must either ask Oracle Support for a PSE for just that product and issue, or apply the mega-patch across the environment and risk breaking multiple products.
Gain Insight on Infrastructure Administrator and the Essbase Application Creators
Essbase is a complex tool that requires a well-tuned environment to perform at peak efficiency. Unfortunately, it’s this tuning that is hardest to achieve. This entry won’t delve into specific tuning strategies, but instead will describe the level of cooperation needed between the infrastructure administrator and the Essbase application creators.