When a large form or ad-hoc retrieval is run then there is a possibility that an out of memory error may occur in the JVM, the common errors to be generated in the logs are:
When I first patched an environment with .500 everything looked good, well that was until I tested out a planning form in Smart View.
There are a few exceptions as the .500 Essbase related products were released last week and are separate downloads, I believe this also applies to DRM.
In the pre 11.1.2 world of EAS it was simple to find out what users, server, profiles were being used in EAS as the information was all stored in XML files within the EAS storage directory.
Patch 17307819: PSU 220.127.116.11.050
In 18.104.22.168 a new command line utility appeared which allows the cloning of environments and it basically uses LCM (Lifecycle Management) as the engine to achieve this.