A growing number of reliable sources (like Intel, Apple Support, Azure Blog, Amazon, Red Hat, Xen, among many others) provide details regarding major security vulnerabilities that affect modern microprocessors, and two specific exploits, called Meltdown & Spectre.

Meltdown dissolves the barriers between user applications and the operating system; This allows a program to access the memory of other programs and the operating system.

Spectre breaks the isolation between different applications on a system, allowing even well-designed programs that operate without error to leak their secrets.

Such exploits would likely include passwords or sensitive data held in memory.

tested with file V44215-01
5/24/2015
The README for Patch 17529887: (Release 11.1.2.3.500 Patch Set Update (PSU): 17529887)  indicates you can apply to 11.1.2.3.0 and that there are no prerequisites beyond the usual Visual C++ 2005 Redistributable Package.

This is not exactly the case, as various Windows OS prerequisites impact whether the patch is applied successfully.

As others have noted, the ADF patches often do not truly apply. I have applied the superpatch on nearly a dozen systems without having any issues so was surprised to finally see the ADF patch deployment failure today.

A new interesting quirk came up as well, when installing the patch with local accounts on a multi-node system. The Microsoft (R) Windows Script Host will fail to process vbscripts like:

D:\software\17529887\custom\scripts\create_version_history.vbs(32, 1) Microsoft VBScript runtime error: Path not found

The intrepid Windows administrators had not set up Windows with cohesive Region and Language settings.

steps

Rollback the patch

D:\Oracle\Middleware\EPMSystem11R1\OPatch\opatch rollback -id 17529887 -oh D:\Oracle\Middleware\EPMSystem11R1 -jre D:\Oracle\Middleware\jrockit_160_37

Check that Region and Language settings match the System Locale. This was corrected by changing the Region and Language setting from “English (United Kingdom)” to “English (United States)“.

Reapply the patch.

Verify after restart that the expected versions are picked up and showing in Workspace > About.

description

None

external links

None at this time

tested PSU 11.1.2.2.104,~.105, ~.106
After installation of the Essbase Client via exe file p17608120_111220_MSWIN-x86-64.zip a number of source files will be over-written and corrupted. For example, epmsys_registry.bat, validate.bat, and ziplogs.bat will no longer work. The applications will still start from Windows Services.msc but will no longer communicate with each other nor with the Admin Server.

steps

The general format I use in this publication is to provide steps to replicate the issue.

You should not replicate this issue.

If you insist on replicating the issue, install the client in a vanilla server, then back-track any mismatch between target files and the files installed by the Essbase Client using a nice diff utility. Here is one for Mac OS X.

description

11.1.2.2.105 Essbase Client exe corrupts EPM Systems: Do not install!

None at this time

external links

None at this time