September 2023 version of AutoUpgrade is available

Posted on September 29, 2023 by AutoUpgrade 13

It’s time again – and the new September 2023 version of AutoUpgrade is available for download to you.

Where to download it?

As usual, the MOS Note: 2485457.1 offers you access to the new release, and to the previous versions of the tool as well. This new version will show the following version information:

java -jar autoupgrade.jar -version

build.version 23.4.230921
build.date 2023/09/21 14:43:05 -0400
build.hash 165be072
build.hash_date 2023/09/21 13:05:52 -0400
build.supported_target_versions 12.2,18,19,21
build.type production
build.label (HEAD, tag: v23.4, origin/stable_devel, stable_devel)

This version will be also included in the Jan 2024 RU, 19.22.0, but not in the October 2023 one due to code freeze constraints. For you, this means you should update the AutoUpgrade tool in ?/rdbms/admin in your current and new homes please.

 

What is changing, what’s improved?

There are no new features this time but added checks and fixes.

New Features 

  • None

Enhancements 

  • None

Change in behavior 

  • BUG-35575340 – AutoUpgrade now defaults to classic upgrade instead of replay upgrade.  This effects only upgrades coming from 21. The catctl_options (-t) is no longer supported. Use configuration parameter
    • replay = (yes | no) instead.
  • BUG-35592200 – Pick up the latest data dictionary health checks package was renamed from DBMS_HCHECK TO DBMS_DICTIONARY_CHECK

Added Checks

  • BUG-35587118 – TARGET_CDB_COMPATIBILITY check not displaying warning plug in violations to users

Fixes

  • AUPG-2976 – NullPointerException in JSON file creation
  • AUPG-3465 – PARAM_VALUES_IN_MEM_ONLY check not behaving as expected in RAC databases
  • BUG-34536467 – RAC on windows was failing when DBUA invoked the AutoUpgrade jar file
  • BUG-35700241 – Analyze fails for the DISK_SPACE_FOR_RECOVERY_AREA check when a Oracle RAC database is not registered with srvcrtl
  • BUG-35810043 – FAST_DEPLOY did not detect when the Prefixups where not run

Further Links and Information

–Mike

Tags:

You may also like...

13 Responses

  1. P. Musolf says:
    October 12, 2023 at 09:44

    Mike,

    I visited last week your meeting at Oracle the Netherlands. You showed some cases using autoupgrade.
    We are planning to use autoupgrade with the pre-check option.
    But the only version of autoupgrade I can download supports only up to 21c

    build.version 23.4.230921
    build.date 2023/09/21 14:43:05 -0400
    build.hash 165be072
    build.hash_date 2023/09/21 13:05:52 -0400
    build.supported_target_versions 12.2,18,19,21 <=========
    build.type production
    build.label (HEAD, tag: v23.4, origin/stable_devel, stable_devel)

    Where can I find the versions which supports 23c … I have seen that in your demo ..

    Regards,
    Paulfrans Musolf

    Reply
    • Mike.Dietrich says:
      October 19, 2023 at 18:35

      Hi Paulfrans.

      this is correct for now. The beta of 23c has a the 23c version but as long as 23c is not available on-prem, the team decided to not release the 23c version yet.

      Cheers,
      Mike

      Reply
  2. John Fernsby says:
    October 12, 2023 at 16:39

    Hi Mike,
    I am trying to use Autoupgrade to perform out-of-place patching databases on windows, without success. I am especially struggling at handling the services and listener. Is there a documentation or something to point us in the right direction?
    Thanks, best regards,
    John

    Reply
    • Mike.Dietrich says:
      October 19, 2023 at 18:34

      Hi John,

      AU can’t handle the services part right now on Windows. This is coming with the next release of AU. Then you can pass on your OS password into the keystore AU provides, and then AU will execute the commands being necessary. So far, only a PS script would be a viable solution.

      Cheers,
      Mike

      Reply
  3. mauro says:
    October 26, 2023 at 08:48

    hello Mike,
    using the version:
    [oracle@vmorasvil02 upgrade] nssvil 19.20 $ $OH/jdk/bin/java -jar /home/oracle/upgrade/autoupgrade.jar -version
    build.version 23.4.230921
    build.date 2023/09/21 14:43:05 -0400
    build.hash 165be072
    build.hash_date 2023/09/21 13:05:52 -0400
    build.supported_target_versions 12.2,18,19,21
    build.type production
    build.label (HEAD, tag: v23.4, origin/stable_devel, stable_devel)

    on a oracle restart linux installation, I receive the following error:
    [oracle@vmorasvil02 upgrade] nssvil 19.20 $ cat /u01/app/oracle/cfgtoollogs/autoupgrade/nssvil/nssvil/100/autoupgrade_20231026_user.log
    2023-10-26 09:23:43.339 INFO
    build.hash:165be072
    build.version:23.4.230921
    build.date:2023/09/21 14:43:05 -0400
    build.max_target_version:21
    build.supported_target_versions:12.2,18,19,21
    build.type:production
    build.hash_date:2023/09/21 13:05:52 -0400
    build.label:(HEAD, tag: v23.4, origin/stable_devel, stable_devel)

    2023-10-26 09:23:54.137 INFO Analyzing nssvil, 120 checks will run using 32 threads
    2023-10-26 09:23:58.362 ERROR
    ============================ check info ============================
    [nssvil][DISK_SPACE_FOR_RECOVERY_AREA][ERROR]
    ============================ check info ============================
    =========================== trace start ==============================
    Exception: ArrayIndexOutOfBoundsException
    Err message: 3
    java.lang.ArrayIndexOutOfBoundsException: 3
    at oracle.upgrade.commons.helpers.Utilities.getASMUsableSpace(Utilities.java:785)
    at oracle.upgrade.commons.helpers.Utilities.getUsableSpace(Utilities.java:920)
    at oracle.upgrade.commons.dbinspector.checks.disk_space_for_recovery_area.checkCode(disk_space_for_recovery_area.java:188)
    at oracle.upgrade.commons.dbinspector.tools.Check.presentInDb(Check.java:298)
    at oracle.upgrade.commons.dbinspector.tools.CheckTrigger.call(CheckTrigger.java:96)
    at oracle.upgrade.commons.dbinspector.tools.CheckTrigger.call(CheckTrigger.java:49)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:750)

    ============================ trace end ===============================
    2023-10-26 09:23:58.389 ERROR “Database check failed with a runtime exception” (conName=”nssvil”, stage=”PRECHECKS”, checkName=”DISK_SPACE_FOR_RECOVERY_AREA”)
    2023-10-26 09:23:59.009 ERROR Dispatcher failed: AutoUpgException [Error running database checks or fixups]
    2023-10-26 09:23:59.013 ERROR Error running dispatcher for job 100
    Cause: Error running database checks or fixups
    2023-10-26 09:23:59.014 ERROR Dispatcher failed:
    Error: UPG-1316
    [Unexpected exception error]
    Cause: Error running database checks or fixups
    For further details, see the log file located at /u01/app/oracle/cfgtoollogs/autoupgrade/nssvil/nssvil/100/autoupgrade_20231026_user.log; stopping job 100 for database nssvil

    recovery area is on ASM.
    Can you help me pls ?
    Thanks
    Mauro

    Reply
    • Mike.Dietrich says:
      January 9, 2024 at 20:05

      Hi Mauro,

      somebody else found the same problem.
      It seems to be the local_listener parameter not set correctly.

      This is from Boris:

      My local_listener parameter was empty. I corrected pointing to the IP address of my host.
      SRVCTL was not working with this new database, so I configured:
      srvctl add database -d MYDB -o $ORACLE_HOME -p +DATA/mydb/parameterfile/spfile.300.1145180019

      After that, I made a shutdown and started with SRVCTL.

      Let me know if that helps.

      Cheers.
      Mike

      Reply
    • Mike.Dietrich says:
      January 9, 2024 at 20:56

      Mauro,

      can you please execute:
      $ORACLE_HOME/bin/kfod op=groups nohdr=TRUE
      and tell me the output?

      Thanks,
      Mike

      Reply
      • Parsa says:
        January 17, 2024 at 05:59

        Hi Mike,
        I’m getting the same error as Mauro, so I checked and the local_listener is already set for my environment. I then tried running what you mentioned and I’m getting the following output:

        $ $ORACLE_HOME/bin/kfod op=groups nohdr=TRUE
        /u01/app/oracle/product/12.2.0/db_home1/bin/kfod: line 22: /stage/software/database/patches/19000/%ORACLE_HOME%/bin/kfod.bin: No such file or directory

        Do you need me to create an SR with Oracle so I can provide you with the logs?

        Thanks,
        Parsa

        Reply
  4. Alexander Eßer says:
    December 19, 2023 at 17:13

    Hello Mike,

    will AU be able to work with custom Windows user details (user + password) for the Windows services (like Listener and DB)?

    Kind regards,
    Alex

    Reply

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Mike Dietrich
Oracle Vice President of Product Management and Development for Database Upgrade, Cloud Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 11.3K other subscribers