9 Replies Latest reply: Jul 30, 2013 1:00 PM by JohnGoodwin RSS

    Applying patches to EPM 11.1.2.2.000

    kent_

      Hi All,

       

      This is my first time patching and I would like some guidance...:

      - I upgraded EPM 11.1.2.1 to EPM 11.1.2.2.000 consisting of Foundation services, Workspace, APS, EAS, Essbase server and Essbase studio components.

       

      Below two patches can be applied on releases: "11.1.2.2.100,11.1.2.2.101,11.1.2.2.102" as per the readme
      16171596 - "PATCH SET UPDATE: ORACLE ESSBASE STUDIO SERVER 11.1.2.2.103 (Patch)" for "Oracle Solaris on SPARC (64-bit)"
      16171601 - "PATCH SET UPDATE: ORACLE ESSBASE STUDIO CONSOLE MSI 11.1.2.2.103 (Patch)" for "Oracle Solaris on SPARC (64-bit)"

      and below patch can be applied on Release "11.1.2.2.100,11.1.2.2.101,11.1.2.2.102,11.1.2.2.103"
      16674524 - "MERGE PATCH FOR MULTIPLE DEFECTS FOR STUDIO SERVER 11.1.2.2.103 PSE (Patch)" for "Oracle Solaris on SPARC (64-bit)"

      1. So once I apply patches 14400511,14400514 to Essbase Studio 11.1.2.2.000 and upgrade it to 11.1.2.2.100, can I directly apply patches 16171596,16171601 to upgrade to 11.1.2.2.103?

      2. If yes, does that mean that 11.1.2.2.103 contains the fixes provided by 11.1.2.2.102 ?

       

      Thanks.

        • 1. Re: Applying patches to EPM 11.1.2.2.000
          JohnGoodwin

          The base release for Essbase products is 11.1.2.2.100 so you will already be at that level.

          You should be able apply 16171601 or 16674524, .103 should contain previous patches.

           

          Cheers

           

          John

          http://john-goodwin.blogspot.com/

          • 2. Re: Applying patches to EPM 11.1.2.2.000
            kent_

            Thank you John.

             

            ----

             

            Hi John / All,

             

             

            I am planning to patch all components up to the latest patch... I am not sure what strategy would be better. Could someone kindly advice on this...

             

            1. Apply patches Component-wise:

             

            - I could apply all patches for one component and then proceed to the next component..Check if the services are running fine or if the defects are fixed and then proceed.

            - Eg. Patch Essbase server to 11.1.2.2.103 from 11.1.2.2.100. Then patch Essbase Studio from 11.1.2.2.000 to 11.1.2.2.103.

             

            OR

             

            2. Patch all components to a particular version :

            - Patch all components to the same version. This makes sense to me as patches are rolled out together.. so as having one component with the latest patches might have issues working with a less-recently patched component..

            - Eg. Patch Essbase and Essbase studio components to 11.1.2.2.101. Then patch these components to 11.1.2.2.102...

             

            ---

             

             

            Also, in the case of the below patches:

             

            16171583-PATCH SET UPDATE: HYPERION ESSBASE CLIENT 11.1.2.2.103 (Patch)

            16171585-PATCH SET UPDATE: HYPERION ESSBASE RTC 11.1.2.2.103 (Patch)

            16171586-PATCH SET UPDATE: HYPERION ESSBASE SERVER 11.1.2.2.103 (Patch)

            .. for "Oracle Solaris on SPARC (64-bit)" can be applied on releases: "11.1.2.2.100,11.1.2.2.101,11.1.2.2.102"

             

            3. Can I run opatch for above patches and then proceed with the restart and other mentioned activities..? or is it that every patch needs to be applied individually?

            • 3. Re: Applying patches to EPM 11.1.2.2.000
              $anty

              Your approach 1 should also be fine, because as per Oracle readmes, you can apply latest patch (.103) to the base version(.100) as well. So directly going from .100 -> .103 is fine.

              As John says, this should cover patches in between.   No need to apply every patch (.101 / .102) i.e. individually.

               

              After applying all patches, you can cross check them (patch number & defect fixed) using Opatch lsinventory command.

               

              Thanks,
              Santy.

              • 4. Re: Applying patches to EPM 11.1.2.2.000
                kent_

                Thanks Santy. Once I finish applying .103, I will run opatch to check if intermediate patch the .102 was applied..

                • 5. Re: Applying patches to EPM 11.1.2.2.000
                  $anty

                  Ok...I don't think you will see patch numbers for intermediate patches (.102/.101).

                  It should cover the "bug fixed" that are with intermediate patches.

                   

                  Thanks,

                  Santy

                  • 6. Re: Applying patches to EPM 11.1.2.2.000
                    kent_

                    okay. The thing is, I do not see the defects in .102 or any other intermediate patches, so there is no way to verify whether they got fixed. So from what I have understood how patches should work - if I apply the latest patch that can be applied on some base patch, then the intermediate "bug fixes" would always be part of the latest patch.

                    • 7. Re: Applying patches to EPM 11.1.2.2.000
                      JohnGoodwin

                      If you have a look at the read for .103 it says

                      "Note: This patch is cumulative and includes defects fixed in earlier patches"

                       

                      Cheers

                       

                      John

                      http://john-goodwin.blogspot.com/

                      • 8. Re: Applying patches to EPM 11.1.2.2.000
                        kent_

                        Hi John, yes I did notice that for the Essbase Server patches.

                        But for the Essbase Studio patches (mentioned in the top-most post) there was no such mention - thus my doubt...

                         

                        Thanks again for your guidance!

                        • 9. Re: Applying patches to EPM 11.1.2.2.000
                          JohnGoodwin

                          As the patch does not say it requires previous patches and says it can be applied to 11.1.2.2.100 then I would take it as cumulative.

                           

                          Cheers

                           

                          John

                          http://john-goodwin.blogspot.com/