This discussion is archived
9 Replies Latest reply: Sep 21, 2012 8:22 AM by user12026424 RSS

potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade

EdStevens Guru
Currently Being Moderated
Oracle GI 11.2.0.1
Oracle rdbms 11.2.0.1
OL 5.6 x86-64
No cluster, no RAC - all standalone

Am making final preperations for upgrade of GI from 11.2.0.1. to 11.2.0.2. Have been making trial runs on a virtual server and uncovered a few issues that have been solved. Just a couple of issues with the rootupgrade.sh script. It seems most of the complexities in the docs have to do with a clustered environment.


On our live systems (one dev, one prod), the dev system was done by my predecessor as his last act before moving on, so my first 'live' upgrade will be in prod. I feel pretty confident that things will go as planned, but am still left without a backout procedure, just in case. All the documentation I've been able to find (and that is a story in itself) only addresses a downgrade from 11.2 back to 11.1 or earlier.

Any hints or pointers to docs that I've overlooked would be appreciated.
  • 1. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    Shivananda Rao Guru
    Currently Being Moderated
    Hi Ed,

    Very recently, I had the upgradation done from 11.2.0.1.0 to 11.2.0.2.0 (Standalone System) involving a Standby database and the upgradation went fine.

    So a few measures would be like:

    1. making sure that the OPatch version is 11.2.0.3.0
    2. Patch 9706490 goes fine on GI home and RDBMS home
    3. A spool of what I had might help you out, I guess not much.
    ASM upgrade:
    
    
    Shutdown the Oracle database but not ASM instance;
    
    Create directory for new GI HOME.
    Run 11.2.0.2 GI GUI and selecting the upgrade option
    
    
    [root@dev ~]# /u01/app/oracle/product/11.2.0.2/grid/rootupgrade.sh
    Running Oracle 11g root script...
    
    The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /u01/app/oracle/product/11.2.0.2/grid
    
    Enter the full pathname of the local bin directory: [/usr/local/bin]:
    The contents of "dbhome" have not changed. No need to overwrite.
    The contents of "oraenv" have not changed. No need to overwrite.
    The contents of "coraenv" have not changed. No need to overwrite.
    
    Entries will be added to the /etc/oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root script.
    Now product-specific root actions will be performed.
    Using configuration parameter file: /u01/app/oracle/product/11.2.0.2/grid/crs/install/crsconfig_params
    
    ASM Configuration upgraded successfully.
    
    Creating OCR keys for user 'oracle', privgrp 'oinstall'..
    Operation successful.
    LOCAL ONLY MODE
    Successfully accumulated necessary OCR keys.
    Creating OCR keys for user 'root', privgrp 'root'..
    Operation successful.
    CRS-4664: Node dev successfully pinned.
    Adding daemon to inittab
    ACFS-9300: ADVM/ACFS distribution files found.
    ACFS-9312: Existing ADVM/ACFS installation detected.
    ACFS-9314: Removing previous ADVM/ACFS installation.
    ACFS-9315: Previous ADVM/ACFS components successfully removed.
    ACFS-9307: Installing requested ADVM/ACFS software.
    ACFS-9308: Loading installed ADVM/ACFS drivers.
    ACFS-9321: Creating udev for ADVM/ACFS.
    ACFS-9323: Creating module dependencies - this may take some time.
    ACFS-9327: Verifying ADVM/ACFS devices.
    ACFS-9309: ADVM/ACFS installation correctness verified.
    
    dev     2012/07/08 21:01:29     /u01/app/oracle/product/11.2.0.2/grid/cdata/dev/backup_20120708_210129.olr
    
    dev     2012/07/04 13:42:11     /u01/app/oracle/product/11.2.0/grid/cdata/dev/backup_20120704_134211.olr
    Successfully configured Oracle Grid Infrastructure for a Standalone Server
    
    
    ###################################################################
    
    Upgrade 11.2.0.2 database by installing 11.2.0.2 software
    
    ##################################################################
    
    Install 11.2.0.2 RDBMS software and run utlu112i.sql (11.2.0.2 RDBMS home/rdbms/admin) on 11.2.0.1 database to be upgraded and perform the recommendations
    
    shut immediate
    
    copy spfile/pfile from 11.2.0.1 to 0.2 and startup upgrade
    
    run catupgrd.sql
    startup the database and run utlrp.sql to validate invalid objects.
  • 2. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    EdStevens Guru
    Currently Being Moderated
    Shivananda Rao wrote:
    Hi Ed,

    Very recently, I had the upgradation done from 11.2.0.1.0 to 11.2.0.2.0 (Standalone System) involving a Standby database and the upgradation went fine.

    So a few measures would be like:

    1. making sure that the OPatch version is 11.2.0.3.0
    2. Patch 9706490 goes fine on GI home and RDBMS home
    3. A spool of what I had might help you out, I guess not much.
    <snip>
    Patch 9706490 ?? Going back through my notes, I don't see anytihng about that one ... but then I had to piece it all together from release notes, installation Guide, admin guide, etc. All of the patches that were referenced seem to be dealing with a clustered environment. Checking our dev box (as mentioned, that one was upgraded by my predecessor) I could find no sign of any patches beyond base install in either the 11.2.0.1 or 11.2.0.2 homes. Used opatch lsinventory to check.

    Will not be upgrading the database itself at this time. Just want to get the prod box caught up with dev, and that's were it's at -- asm at 11.2.0.2 and rdbms at 11.2.0.1.
  • 3. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    Shivananda Rao Guru
    Currently Being Moderated
    Patch 9706490 ?? Going back through my notes, I don't see anytihng about that one .
    Sorry about the 9706490. It was applied as fix for a bug which I do not remember. But, yes, I do remember applying PSU 11.2.0.1.2 on GI and RDBMS home before upgrading the ASM. (Patch 9655006)

    These Metalink notes which I referred might help you out.
    Bug 9413827 - CRS rolling upgrade from 11.2.0.1 to 11.2.0.2 fails with OCR on ASM [ID 9413827.8]

    Bug 10036834 - Linux Platforms: Patches not found upgrading Grid Infrastructure from 11.2.0.1 to 11.2.0.2 [ID 10036834.8]

    Pre-requsite for 11.2.0.1 to 11.2.0.2 ASM Rolling Upgrade [ID 1274629.1]
  • 4. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    585179 Expert
    Currently Being Moderated
    EdStevens wrote:
    I feel pretty confident that things will go as planned, but am still left without a backout procedure, just in case. All the documentation I've been able to find (and that is a story in itself) only addresses a downgrade from 11.2 back to 11.1 or earlier.

    Any hints or pointers to docs that I've overlooked would be appreciated.
    Hi Ed,

    Have you checked
    - How To Downgrade From Database 11.2 To Previous Release (includes 11.2.0.3-11.2.0.1) [ID 883335.1]
    - How to Downgrade 11.2 Grid Infrastructure Standalone (Oracle Restart) After Successful or Failed Upgrade [ID 1364412.1]

    All you have to make sure is having a good backups :)


    Cheers
  • 5. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    EdStevens Guru
    Currently Being Moderated
    Shivananda Rao wrote:
    Patch 9706490 ?? Going back through my notes, I don't see anytihng about that one .
    Sorry about the 9706490. It was applied as fix for a bug which I do not remember. But, yes, I do remember applying PSU 11.2.0.1.2 on GI and RDBMS home before upgrading the ASM. (Patch 9655006)

    These Metalink notes which I referred might help you out.
    Bug 9413827 - CRS rolling upgrade from 11.2.0.1 to 11.2.0.2 fails with OCR on ASM [ID 9413827.8]
    Can't see how it applies -- stand-alone = no cluster, no OCR, no rolling upgrade
    >>
    Bug 10036834 - Linux Platforms: Patches not found upgrading Grid Infrastructure from 11.2.0.1 to 11.2.0.2 [ID 10036834.8]
    Incorrectly reports a patch not installed when it has been ... if this were an issue I'd think I'd have seen it by now.
    Pre-requsite for 11.2.0.1 to 11.2.0.2 ASM Rolling Upgrade [ID 1274629.1]
    Again, this appears to be only for clustered systems doing a rolling upgrade.
  • 6. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    Sebastian Solbach (DBA Community) Guru
    Currently Being Moderated
    Hi,

    if you patch, I personally would recommend you upgrade to 11.2.0.3 and also grab the latest PSU.

    Even if your application does not allow 11.2.0.3 I would at least use the version for the GI Home and the ASM instance.

    Regards
    Sebastian
  • 7. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    EdStevens Guru
    Currently Being Moderated
    Sebastian Solbach (DBA Community) wrote:
    Hi,

    if you patch, I personally would recommend you upgrade to 11.2.0.3 and also grab the latest PSU.

    Even if your application does not allow 11.2.0.3 I would at least use the version for the GI Home and the ASM instance.

    Regards
    Sebastian
    Yes, 11.2.0.3 with latest PSU is my ultimate goal, but first I just need to 'complete' the current upgrade by getting production to the same level as dev. As soon as I complete this upgrade, I'll start working on the 11.2.0.3
  • 8. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    EdStevens Guru
    Currently Being Moderated
    Fiedi Z wrote:
    EdStevens wrote:
    I feel pretty confident that things will go as planned, but am still left without a backout procedure, just in case. All the documentation I've been able to find (and that is a story in itself) only addresses a downgrade from 11.2 back to 11.1 or earlier.

    Any hints or pointers to docs that I've overlooked would be appreciated.
    Hi Ed,

    Have you checked
    - How To Downgrade From Database 11.2 To Previous Release (includes 11.2.0.3-11.2.0.1) [ID 883335.1]
    - How to Downgrade 11.2 Grid Infrastructure Standalone (Oracle Restart) After Successful or Failed Upgrade [ID 1364412.1]
    No I hadn't seen those, will check them this morning.
    All you have to make sure is having a good backups :)
    Yeah, but backups of what? In an out-of-place upgrade, you obviosly can't back up the NEW home as it doesn't exist yet, presumably there'd be nothing happening in the OLD home (and I have specifically looked for that and couldn't find anything), we have backups of the database which is in archivelog mode. oratab is simple enough. What else?


    >
    >
    Cheers
  • 9. Re: potential backout of failed GI 11.2.0.1 to 11.2.0.2 upgrade
    user12026424 Newbie
    Currently Being Moderated
    Backup the following

    OCR Disk
    Voting Disk
    Grid Home
    /var/etc/
    /etc/opt
    /Oracle_home


    Thanks
    Adarsh Kumar
    Columbia MO

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points