Upgrade to Oracle Database 12.2 – New MOS Notes

Some very helpful MOS Notes got published regarding the upgrade to Oracle Database 12.2.0.1:

Furthermore check regularly for Known Issues and Alerts – currently the note has no content but exists already:

Cheers
–Mike

21 thoughts on “Upgrade to Oracle Database 12.2 – New MOS Notes

  1. Mike,
    I am a bit confused about MOS note 2173141.1. There is no mention of parallel upgrade using catctl.pl. This note mentions running dbupgrade with no mention of parallelism.

    Is there any MOS note on how to upgrade from 11.2.0.4 to 12.2 and convert from non-CDB to single tenant?

    Thanks,
    Arun

  2. Hi Mike,

    I guess the patch updates will follow the Jan/Apr/Jul/Oct schedule. It wouldn’t be cloud first? We can expect the first patch updates to be out in Apr 2017?

    Cheers.

  3. Hi Mike,

    I’m also interested in question from Arun in regards upgrade (or migrate) from 11.2.0.4/12.1 to 12.2 and convert from non-CDB to single tenant.

    Could you please advise if there are some MOS notes related to that?

    Thank you!

    Cheers,

    Vlatko

  4. Hello,

    Just some feedback for the community that follows this blog.

    I downloaded the 12.2 software yesterday and did a couple of test upgrades, everything worked as expected. Roy/Mike, great job making the upgrades simple and straight forward.

    We have close to 150 single instance databases that we plan to upgrade to 12.2 in the next 3-6 months. I tried the GUI DBUA and the process took close to 53 mins.

    I tried the DBUA -silent option and that went pretty well as well. The same database took 30 mins to upgrade. I used the following options for the -silent option.

    /u01/app/oracle/product/12.2.0.1/bin/dbua -silent \
    -sid <SID NAME> \
    -oracleHome /u01/app/oracle/product/12.1.0.2 \
    -recompile_invalid_objects true \
    -gatheringStatistics true \
    -upgradeTimezone true \
    -emConfiguration NONE \
    -upgrade_parallelism 4

    Thanks.

  5. Mike,

    Is DBUA -silent the best option to get to a one command database upgrade. I’m trying to give something to my team that is simple and quick. I read something with an upgrade command line utility called "dbupgrade", is that new in 12.2?

    Thanks.
    Naveen

  6. Naveen,

    for "simple" DBUA (either silent or interactive) is currently the best approach for now (there will be something in a future patch set which may be even better).

    "dbupgrade" is just a wrapper for:
    $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catctl.pl -n 4 $ORACLE_HOME/rdbms/admin/catupgrd.sql

    Cheers
    Mike

  7. Mike,
    Thank you so much for putting together all this excellent information. It is really coming in handy as we do our upgrade planning.

    Can you please cover some fallback scenarios? If I want to upgrade a database from 11.2.0.4 to 12.2 and convert to single tenant, I will have to do it in two steps.

    First upgrade the 11.2.0.4 database to 12.2 non-CDB. In second step, I will unplug the CDB and plug it into a single tenant CDB as a PDB.

    This would imply that I will have to raise the COMPATIBLE parameter in step 1. The moment I do that, there is no fallback except to restore from cold backup.

    How to deal with this situation?

    Best regards,
    Arun

  8. Mike,
    I am testing upgrade of 12.1 RAC GI to 12.2 and it fails at creating GIMR. It seems that after upgrade to 12.2, ASM is unable to read the spfile with the error:

    ERROR: Unable to get logical block size for spfile ‘+DG_CRS/clu12c/ASMPARAMETERFILE/registry.253.938012473’.
    MEMORY_TARGET defaulting to 1128267776.

    Since ASM cannot read spfile, it does not know the disk discovery path and the diskgroups are not mounted. Querying the v$asm_diskgroup returns no rows. This causes failure of creating GIMR. The 12.1 GI home was patched to Oct 2016 patch. The cluvfy pre crsinst did not show any error. The 12.1 GI was working perfectly and I had tested stop/start of ASM multiple times. There is nothing on MOS about this error. The disks are iSCSI with 512 byte block size, so there is nothing unusual. Any help will be appreciated.

    Thanks,
    Arun

  9. Hi Mike,

    I’m getting ready to upgrade Oracle SE2 database from v12.1.0.2 to 12.2.0. I thought I read in upgrade notes that I needed to apply any SPU’s to 12.1.0.2 first, then upgrade to 12.2.0. I was under the impression that the major releases included all previous patches, which was kind of why we decided to wait and do the 12.2 upgrade. If I am supposed to apply SPU’s first, is the last one (ie Jan 2017) sufficient. Again I’m assuming they’re cumulative?

    thank you,
    Jennifer

  10. Jennifer,

    there are no SPUs for Oracle Database 12c (12.1 and 12.2) anymore.
    You can choose between PSUs and BPs whereas I strongly recommend you the BPs as they contain more fixes and get some significant additions soon.

    For 12.2.0.1 there are no patch bundles (PSUs or BPs) available yet. The first one will be released in mid April.

    And you are right, SPUs (11.2), PSUs (11.2, 12.1, 12.2) and BPs (11.2. Exa-only, 12.1, 12.2) are all cummulative having the previous SPUs or PSUs or BPs included as well.

    Cheers
    Mike

  11. Arun,

    may I please ask you to open an SR and send me the SR number?
    I won’t be able to solve this but I’m very interested what causes this.

    Thanks
    Mike

    • Mike,
      I found out what was causing the ASM error. When I do a fdisk on the disk I used for ASM, it shows two sector sizes, logical and physical. The logical sector size was 512 bytes, the physical sector size was 128k. In my iSCSI target (I use FreeNAS), there is a setting which disables reporting of physical sector size. I checked that box and the physical sector size changed to 512 bytes and the error was resolved.
      This seems to be a bug somewhere in Oracle as up to version 12.1, fdisk always reported physical sector size as 128k without causing any problem to ASM. In 12.2, it seems that instead of checking for logical sector size, some library is checking for physical sector size and throwing an error. Either that or they are verifying if physical and logical sector sizes match or something like that. But definitely, there is a behavior change. It took hours and hours of troubleshooting.

      ERROR: Unable to get logical block size for spfile ‘+DG_CRS/clu12c/ASMPARAMETERFILE/registry.253.938012473’.
      MEMORY_TARGET defaulting to 1128267776.

      Thanks,
      Arun

      • Arun,

        first of all, sorry to hear that. Second, I will get in touch with the right people. If I get a useful insight answer I’ll let you know.

        Cheers and thanks again for explaining – and glad you could solve it!
        Mike

  12. Arun,

    would you please mind to grab our big 12.2 slide deck from the Slides Download Center and scroll forward to around slide 400 to the "Fallback Scenarios" section?

    This will show you options for issues "During" and "After" the upgrade.

    Let me know if anything is unclear.

    Cheers
    Mike

  13. Mike,

    How to upgrade from 12.1.0.2 to 12.2.0.1 with multitenent concept of one cdb with fours pdb database using dbua .please share the any doc of this .

    Thanks
    Baskar

  14. We would like to do upgrade from 11.2.0.4 to 12.2 and 12.1 to 12.2. We are having single instance [HAS/ASM] ,RAC with Golden Gate and RAC with Data Guard. I would like to know where I can find documents that lists step by step for RAC with Data Guard environment and for RAC with Golden Gate.

    Thanks,

    • I would blindly direct you:
      – for Data Guard to the Data Guard documentation
      – for RAC to MOS and/or the RAC documentation.

      The complexity of your environments may make it necessary that you talk to somebody at Oracle assisting you to define all the potential paths. The database upgrade itself is the least complicated part. And Data Guard isn’t either as long as you have a physical standby. But as soon as you move between hardware etc things get a bit more tricky. Please understand that I can’t deliver this via the blog for an entire environment.

      Cheers
      Mike

Leave a Reply

Your email address will not be published. Required fields are marked *