Essbase 11.1.2.3.504

There is a flurry of activity going on with the Essbase product development team at Oracle.  Glenn Schwartzberg had the scoop on Essbase 11.1.2.3.504 that released just a few hours ago.

As I look at the current readme, I am struck by two things:

  1. This entry: “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.3.503, Provider Services 11.1.2.3.502, and Essbase Studio 11.1.2.3.502 are supported for use with Essbase 11.1.2.3.504.”
  2. And then this under Known Issues in this Patch: “The opatch ids for this patch were not updated so after unzipping the opatch file the root directory will not match the opatch id from 11.1.2.3.504 but will be the opatch ids from 11.1.2.3.503.  Any warnings from opatch can be ignored.”  I am wondering if you have applied the .503 Essbase patch, you may need to rollback that patch in order to apply the .504 patch since the IDs are the same.  I can report back on that later since I have .503 installed at a client site and now need to update it.

There are a set of patch numbers that you can search for, or just search under the Hyperion Essbase product.  There is no Essbase client MSI on Oracle Support for Windows (yet).  As per #1 above, the client for 11.1.2.3.502 should be fine as it was against Essbase 11.1.2.3.503.

Component Patch ID
Essbase Client MSI (Windows) 19613877
Essbase Client (OPatch) 19613886
Runtime Client 19613868
Essbase Server 19613865

The list of defects fixed isn’t terribly long; however, it appears that this patch addresses some instances where the Essbase server and/or applications may stop responding or terminate.  Based on that alone, it’s probably a good idea to patch any .500, .501, .502, or .503 instances to .504.

Advertisements

4 comments

  1. Hi Robert,

    I was using this document to track the patches, but Oracle seems to have released these new ones and not update it yet: Available Patch Sets and Patch Set Updates for Oracle Hyperion Essbase (Doc ID 1396084.1)

    Do you have any comments about the reasons Oracle has added this comment to the documentation with this release: “Essbase Native Security Mode Is No Longer Supported” ?

    They updated the main 11.1.2.3 documentation with the same comment. Does it really apply to every 11.1.2.3 not just the patch 504
    http://docs.oracle.com/cd/E40248_01/epm.1112/essbase_11123000_readme.pdf

    Any suggestions for service accounts for backups that are using a native account etc.?

    I see you have done over 130 installations of 11.1.2.x? That’s just amazing if each one is a custom install. Congratulations. If these patches continue I think I will have completed 130 re-installations of just 11.1.2.3. Glad that for me it is all scripted (SQL install, config, Essbase install and config) and runs in under an hour.

    Thank you.

    Best Regards,
    Jason

    1. Jason,

      Oracle has a blog called Proactive Support that gets updated when new patches are released. https://blogs.oracle.com/proactivesupportEPM/ It seems like this patch was rushed out, with the OPatch IDs being the same and all, so maybe they didn’t have time to update that document as well.

      There may be some confusion on what “Essbase Native Security Mode” is. During the configuration of Essbase server, you can set it up in “Stand-Alone mode” and this is Essbase Native security. Stand-Alone mode means that your users and group security for Essbase is defined and updated in EAS, not Shared Services. Beginning in System 9, Hyperion made Shared Services for a common security application across all of their products. If you do not use Shared Services for your Essbase security and manage those users in EAS, you are not supported on 11.1.2.3.

      I can guess about why they are no longer supporting Native Security mode, but I don’t have any insight to the actual reason. My thoughts are that they really want to make sure they are supporting a standard architecture. The Stand-alone Essbase Security model with a pared down Foundation Services repository probably isn’t something that Oracle wants to continue to support. It’s long been the best practice to convert into Shared Services security mode, so they are just making the only choice now. I would say, yes, their comment about Native Security not being supported is applicable to all 11.1.2.3 Essbase releases, not just 11.1.2.3.504.

      As far as service accounts, it’s ok to continue using Native Shared Services service accounts for backups – the Native Shared Services security is not going away, just the Native Essbase Security.

      My installation number includes multiple environments at the same client. Some clients have two, three, or four environments, and many clients have had me come back and do multiple engagements to install and then upgrade a couple years later. I started keeping a tally of the installs, but lost track after forty or so, that was a couple of years ago. It sounds like you have a really great process with it all scripted.

      Cheers,
      Robert

  2. Hi Robert,

    That is helpful indeed and, having forgotten about the real native mode security where the info is stored in the essbase.sec file, I was confusing the two types of security modes and thinking they were speaking of moving all the users we have in Native Security in Shared Services to an LDAP directory in the Shared Services. Silly mistake. That’s why I write scripts instead of documentation. With docs, the screens change and names change, but with scripts you have an API that is usually well defined for a certain version.

    To backup security information (users, groups, roles, filters, etc.), do you find it better to export everything with LCM ( I could write a Groovy/Java app using Shared Services API I suppose) or by doing a backup process like I have below after shutting down EPM?

    I would like to determine how to properly do a backup and restore procedure while including the Shared Services database information. I believe that by shutting down EPM, and then running the following script that I am getting everything I need (eas and hss plus master, model, and msdb).

    I have a feeling that you have probably seen better scripts than mine or maybe some of your readers will find it helpful. I won’t post the Essbase one here because it is much too complicated since it handles checking processes have stopped, logs, xcp files, and run maxl statements to archive to file etc. and I’m already happy with how it’s working and know that it can restore. It’s the shared services SQL portion that I need to verify for now.

    Take care,

    Jason

    This is in PowerShell 4 for an SQL 2008 system. Maybe somebody will find it useful.

    # Thanks to https://social.technet.microsoft.com/Forums/windowsserver/en-US/44466262-cae1-42c2-8b81-2aaf11e33542/how-to-backup-more-than-one-database-using-powershell?forum=winserverpowershell

    function sqlArchive($instance, $bkdir)
    {
    New-Item $bkdir -type directory -ErrorAction SilentlyContinue # SQL Backup Folder

    [System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SqlServer.SMO”) | out-null
    [System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SqlServer.SmoExtended”) | out-null
    $s = new-object (“Microsoft.SqlServer.Management.Smo.Server”) “$instance”

    $dbs = $s.Databases
    foreach ($db in $dbs)
    {
    if($db.Name -ne “tempdb”) #We don’t want to backup the tempdb database
    {
    $dbname = $db.Name
    $dt = get-date -format yyyyMMddHHmm #We use this to create a file name based on the timestamp
    #Create a Backup object instance with the Microsoft.SqlServer.Management.Smo.Backup namespace
    $dbBackup = new-object (“Microsoft.SqlServer.Management.Smo.Backup”)
    $dbBackup.Action = “Database” #Specify the Action property to generate a FULL backup
    $dbBackup.Database = $dbname
    #Add the backup file to the Devices collection and specify File as the backup type
    $dbBackup.Devices.AddDevice($bkdir + “\” + $dbname + “_db_” + $dt + “.bak”, “File”)
    $dbBackup.SqlBackup($s) #Call the SqlBackup method to generate the backup
    }
    }
    }

    sqlArchive -instance “127.0.0.1” -bkdir “E:\@BackupsSQL” # run the backup

    1. Thank you for the script, Jason. I believe doing backups of your relational database is very important along with file system backups on your servers. Oracle’s stated position is that LCM should not be relied upon for backup and recovery purposes, it should be used primarily as a migration tool. Given that information, you are right on with your backup routine.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s