13 Replies Latest reply: Mar 27, 2012 3:00 AM by 807928 RSS

    Sun cluster OS upgrade

    846180
      Got an application requirement to stay on the current cluster version but to upgrade the DB which requires OS upgrade. The current OS release is Solaris 10 SPARC 64 (Solaris 10 3/05 s10_74L2a SPARC ) Generic_118822-30. The upgrade is going to be to (Solaris 10 10/09 s10s_u8wos_08a SPARC ) Generic_144488-08.

      The database is sitting at :

      Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production With the Partitioning, OLAP and Data Mining options.

      Getting upgraded to:

      Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
      PL/SQL Release 11.2.0.2.0 - Production
      CORE 11.2.0.2.0 Production
      TNS for Solaris: Version 11.2.0.2.0 - Production
      NLSRTL Version 11.2.0.2.0 - Production

      Installed cluster components are :

      Sun Cluster 3.1u4 for Solaris 10 sparc
      SUNWscr: 3.1.0,REV=2005.07.18.14.37, 120500-05
      SUNWscu: 3.1.0,REV=2005.07.18.14.37, 120500-05
      SUNWscsckr: 3.1.0,REV=2005.07.18.14.37
      SUNWscscku: 3.1.0,REV=2005.07.18.14.37
      SUNWscnmr: 3.1.0,REV=2005.07.18.14.37
      SUNWscnmu: 3.1.0,REV=2005.07.18.14.37
      SUNWscdev: 3.1.0,REV=2005.07.18.14.37, 120500-05
      SUNWscgds: 3.1.0,REV=2005.07.18.14.37, 120500-05
      SUNWscman: 3.1.0,REV=2005.07.18.14.37
      SUNWscsal: 3.1.0,REV=2005.07.18.14.37
      SUNWscsam: 3.1.0,REV=2005.07.18.14.37
      SUNWscvm: 3.1.0,REV=2005.07.18.14.37
      SUNWmdmr: 3.1.0,REV=2005.07.18.14.37
      SUNWmdmu: 3.1.0,REV=2005.07.18.14.37
      SUNWscmasar: 3.1.0,REV=2005.07.18.14.37, 120489-02
      SUNWscmasau: 3.1.0,REV=2005.07.18.14.37
      SUNWscva: 3.1.0,REV=2005.07.18.14.37
      SUNWscspm: 3.1.0,REV=2005.07.18.14.37
      SUNWscspmu: 3.1.0,REV=2005.07.18.14.37, 120489-02
      SUNWscspmr: 3.1.0,REV=2005.07.18.14.37
      SUNWscor: 3.1.0,REV=2005.07.18.10.43
      SUNWsctomcat: 3.1.1,REV=07.17.03,20:11:29, 116429-03 116729-03

      Current resource and the resource groups are :

      Group: PROD-rg PRODprod1 Online

      Resource: PROD-lhn-res PRODprod1 Online Online - LogicalHostname online.

      Resource: PROD-hastp-res PRODprod1 Online Online
      Resource: PROD-lsnrPRD-res PRODprod1 Online Online
      Resource: PROD-lsnrHPA-res PRODprod1 Online Online
      Resource: PROD-oraPRO8PROD-res PRODprod1 Online Online
      Resource: PROD-tuxedo-res PRODprod1 Online Online
      Resource: PROD-tomcat-res PRODprod1 Online Online

      We have tested the switchover among the 2 nodes (PRODprod1 and PRODprod2 ) which work fine at the moment.

      We are planning to do a LU to upgrade to OS to the given solaris release. What I need to know is how the resources would behave onece the upgrade is done in terms of the OS and the DB. We are planning to apply the two patches 120514-04 and 120500-26. The other major concern is the oracle agents ( DB server and listener). Should there be any changes for them to cater to ORACLE 11.2.02 in terms of resource configuration? Any info/thoughts are appreciated.
      Cheers.
        • 1. Re: Sun cluster OS upgrade
          807928
          HA-Oracle 11gR2 11.2.0.2 has not yet been certified on Solaris Cluster. The highest supported release is currently 11.2.0.1.

          Tim
          ---
          • 2. Re: Sun cluster OS upgrade
            HartmutStreppel
            Even if it had been certified, I would be surprised if it were supported with Sun Cluster 3.1. I can see 11g in the list, but no mention of 11gR2.

            Why do you want to upgrade DB and OS, but not the cluster. That does not make sense.
            • 3. Re: Sun cluster OS upgrade
              807928
              Actually, there is no reason, in practice, why we should not support 11.2.0.2 on SC3.1 through 3.3. That decision would be taken once any QA work was completed.

              It is often the case that users want to minimize the amount of change when performing an upgrade, although I would agree that going to the latest release would have significant benefits in terms of patches incorporated and new features added.

              Regards,

              Tim
              ---
              • 4. Re: Sun cluster OS upgrade
                user13843357
                Are there any specific hardware requrements to run SC 3.2 or 3.3 ?. Planning to upgrade SC 3.1 to either 3.2 or 3.3
                cheers
                • 5. Re: Sun cluster OS upgrade
                  user13843357
                  Hi Tim,

                  The plan now is to upgrade the cluster version 3.2 or 3.3 in order to have a compatible environment for 11.2.0.2. This is non RAC solution. What is the best aproach to follow ?.
                  1) upgrade oracle and then upgrade the cluster software
                  2) upgrade the cluster software and then upgrade to 11.20.2 ?
                  cheers
                  • 6. Re: Sun cluster OS upgrade
                    807928
                    No, if you are running SC 3.1 on certain h/w then we will support SC 3.3 on that same h/w, so long as it runs Solaris ! :-)

                    Tim
                    ---
                    • 7. Re: Sun cluster OS upgrade
                      807928
                      I would upgrade the cluster s/w first and then once you've run that for a week or so and you are happy that the upgrade is stable, I'd then do the Oracle upgrade. BTW - If I recall correctly, we announced support (on Solaris Cluster) for 11.2.0.2 yesterday, but it currently excludes 11.2.0.2 RAC in zone clusters.

                      Tim
                      ---
                      • 8. Re: Sun cluster OS upgrade
                        user13843357
                        Thanks Tim,

                        Does Oracle have a defined EOL date for SC 3.1 ?.
                        After the upgrade can i use the scrgadm -c -j to alter the current oracle resource to point to new 11gr2 ORA_HOME and the listner ? Is this the only parameter setting i should do in order to point it to the new 11gR2 instance ?
                        cheers
                        • 9. Re: Sun cluster OS upgrade
                          807928
                          Hi,

                          Took a while to track down the EOL info...

                          http://www.oracle.com/us/support/library/lifetime-support-hardware-301321.pdf

                          I've not tried this, so I can't say for definite, but that does sound about right. You should only need to change the ORACLE_HOME, LISTENER and Alert_log_file properties everything else being equal.

                          Regards,

                          Tim
                          ---
                          • 10. Re: Sun cluster OS upgrade
                            user13843357
                            Thanks Tim,

                            We upgraded the cluster to 3.2.

                            Solaris Cluster 3.2u3 for Solaris 10 sparc
                            SUNWscu: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 144221-02
                            SUNWsccomu: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 144221-02
                            SUNWsczr: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 140017-02
                            SUNWsccomzu: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42
                            SUNWsczu: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 144221-02
                            SUNWscsckr: 3.2.0,REV=2006.12.05.22.58, 125992-05 800149-01 125992-07
                            SUNWscscku: 3.2.0,REV=2006.12.05.22.58, 125992-05 800149-01 125992-07
                            SUNWscr: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 140017-02 144221-02
                            SUNWscrtlh: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscnmr: 3.2.0,REV=2009.09.25.13.28
                            SUNWscnmu: 3.2.0,REV=2009.09.25.13.28
                            SUNWscdev: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 144221-02
                            SUNWscgds: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscsmf: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscman: 3.2.0,REV=2006.09.26.13.45, 128556-04 800141-01
                            SUNWscsal: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscsam: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscvm: 3.2.0,REV=2006.12.05.22.58, 800149-01
                            SUNWmdmr: 3.2.0,REV=2006.12.05.22.58, 800149-01
                            SUNWmdmu: 3.2.0,REV=2006.12.05.22.58, 125514-05 800149-01 125514-07
                            SUNWscmasa: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscmasar: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscmasasen: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWscmasau: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42 144221-02
                            SUNWscmautil: 3.2.0,REV=2006.12.05.22.58, 125508-08 126106-38 800149-01 126106-42
                            SUNWscmautilr: 3.2.0,REV=2006.12.05.22.58, 800149-01
                            SUNWjfreechart: 3.2.0,REV=2006.12.05.22.58, 139921-02 800149-01
                            SUNWscspmr: 3.2.0,REV=2006.12.05.22.58, 800149-01
                            SUNWscspmu: 3.2.0,REV=2006.12.05.22.58, 125508-08 126106-38 800149-01 126106-42
                            SUNWscderby: 3.2.0,REV=2006.12.05.22.58, 126106-38 800149-01 126106-42
                            SUNWsctelemetry: 3.2.0,REV=2006.12.05.22.58, 125511-02 126106-38 800149-01 126106-42
                            SUNWscor: 3.2.0,REV=2006.12.06.18.32, 126047-12 800144-01 126047-17
                            SUNWsctomcat: 3.2.0,REV=2006.12.06.18.32, 126071-02 800144-01 126071-03

                            I would like to have your thoughts about the database server resource. ( http://pastie.org/private/ah6jfwil6qbfjrdo6bbfw )

                            One speciific concern i have is the "Parameter_file:", As per my understanding this is picked up automatically when i give the SID and the ORA_HOME. It's the pfile it's pointing to and is there a possibility for me to do a resource re-configuration to do get it to point to the spfile. I'm aware that the spfile could be the only parameter in the pfile which makes the resource call the spfile indirectly. Is this the best aproach in this case.

                            TIA
                            • 11. Re: Sun cluster OS upgrade
                              807928
                              In general, I don't use the parameter file property. I simply ensure that the ORACLE_HOME, ORACLE_SID, ALERT_LOG_FILE and CONNECT_STRING are set correctly. I doubt the parameter_file property is needed unless you have a non-standard installation of Oracle.

                              Tim
                              ---
                              • 12. Re: Sun cluster OS upgrade
                                926513
                                I have the Solaris patch Generic_144488-09 sun4v sparc SUNW,SPARC-Enterprise-T5220 on my server( Sun OS 5.10).
                                I have some scripts which has "mget" command in it and it stopped working after the patch i believe.

                                Can someone please help me confirm that the above patch would not allow the "mget" command to work on the server.
                                Fy! Using just the "get" command works on this server.
                                • 13. Re: Sun cluster OS upgrade
                                  807928
                                  Could you explain or demonstrate what you mean by '...would not allow the "mget" command to work on the server."

                                  Is this a cluster problem or a Solaris problem? If it is the latter, it might be better to post it to another forum.

                                  Tim
                                  ---