AutoUpgrade New Features: Update Enterprise Manager Configuration

Patching, Upgrade 1 Minute

With the latest version, 24.8, AutoUpgrade can interact with Oracle Enterprise Manager:

  • Blackout the database
  • Modify target configuration

Details

  • AutoUpgrade interacts with Enterprise Manager through the command line interface, EM CLI.
  • In the DRAIN phase, AutoUpgrade creates a blackout of the target. It will also remove the blackout again after the job.
  • The blackout is named blackout_<SID>.
  • AutoUpgrade updates the target configuration in Enterprise Manager to reflect the new Oracle home if the job succeeds.
  • If you restore the job (returning to the pre-upgrade state with Flashback Database), AutoUpgrade restores the original target configuration.

How To

  • Install and configure EM CLI on the database host.

  • Persist the credentials on the database host using the autologin feature.

  • Get the latest version of AutoUpgrade:

    wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar

  • Specify the path to EM CLI in the AutoUpgrade config file:

    upg1.emcli_path=/u01/app/oracle/oem

  • Specify the target name from Enterprise Manager:

    upg1.em_target_name=ORCL_myhost.domain.int

Happy Upgrading

You can use the functionality when you patch and upgrade your Oracle Database.

If you use Oracle Enterprise Manager, AutoUpgrade can handle even more tasks in your runbook.

What are the next tasks that AutoUpgrade should do for you? Leave a comment, and we’ll consider it.

Published

16 thoughts on “AutoUpgrade New Features: Update Enterprise Manager Configuration”

    1. Hi,

      Yes, you need to install EM CLI on each server where you run AutoUpgrade. In practice, that is on each database host (although for a RAC system, you could settle with just installing on one node).

      Unfortunately, Enterprise Manager REST API does not support creating blackout and updating the target configuration, so EM CLI is the only option. In the future, if more capabilities arise in Enterprise Manager REST API, we’ll be happy to revisit this enhancement.

      Regards,
      Daniel

      Like

      Reply

  4. Hi,

    I got this error message. Is there a specific format for em_target_name?

    The em_target_name parameter for prefix patch1 includes a value that is not supported or is not in the required format

    I’m performing autoupgrade patching from 19.16 to 19.26.

    I downloaded and installed emcli and configured it with autologin

    — Configuration-File:

    patch1.emcli_path=/u01/app/oracle/oem
    patch1.em_target_name=vmoem.mydom.com

    Regards

    Adel

    Like

    Reply

  5. Hi Daniel,

    i get it in analyze mode!

    [oracle@kubcdb cdb_autoupgrade_config]$ /u01/app/oracle/product/19.26/jdk/bin/java -jar /mnt/hgfs/shared/autoupgrade_patching/autoupgrade_jar/autoupgrade.jar -config /mnt/hgfs/shared/autoupgrade_patching/cdb_autoupgrade_config/JENNYCDB_oop_patchconf.cfg -patch -mode analyze
    AutoUpgrade Patching 25.1.250212 launched with default internal options
    Processing config file …
    The following errors were found in the configuration file:
    The em_target_name parameter for prefix patch1 includes a value that is not supported or is not in the required format The creation of the ORACLE_HOME and the installation were successful.

    Do I have to put these parameters in a separate configuration file and execute it after patching?

    Thanks

    Adel

    Like

    Reply

      1. Hi Daniel!

        Any updates regarding this error?

        I’m getting the exact same error with the same versions of autoupgrade.jar and emcli as Adel.

        Regards

        /Rickard

        Like

        Reply

          1. I will try to create a SR during the day.

            Will send you the SR number when it’s done.

            Regards

            /Rickard

            Like

            Reply

  6. Hi Daniel,

    FYI!

    i use Autoupgrade Tool Version 25.1
    Oracle Enterprise Manager 24ai Release 1

    EMCLI:

    [oracle@kubcdb oem]$ ./emcli setup
    Oracle Enterprise Manager 24ai Release 1.
    Copyright (c) 1996, 2024 Oracle Corporation and/or its affiliates. All rights reserved.

    Instance Home : /home/oracle/.emcli
    Verb Jars Home : /u01/app/oracle/oem/./bindings/24.1.0.0.0/.emcli
    EM URL : https://vmoem.mydom.com:7803/em
    EM user : sysman
    Trust all certificates : true
    Auto login : true

    Thanks

    Adel

    Like

    Reply

    1. I’m getting the same error when doing a analyze with autoupgrade.jar.

      Using the same version of autoupgrade.jar end emcli for Enterprise Manager 24.1.

      Testing with RU 19.27

      /Rickard

      Like

      Reply

  7. Hello!

    I cannot figure out how to get this working. I had both values set:

    scand2.emcli_dir=/ora/app/oracle/product/emcli
    scand2.em_target_name=scand2

    I have created SR: 3-41022261881 , but it is going nowere, can you help, or check logs on it?

    Like

    Reply

    1. Hi,
      There is a documentation bug. In “em_target_name” you must specify the full target name from Enterprise Manager, like “scand2_host1.corp.internal”. AutoUpgrade inserts this directly into the call to EM CLI. AutoUpgrade needs the full target name because there’s no way for it to deduce it – it could be virtually anything.
      Next, the latest version of AutoUpgrade might also tell you that the value you specify in “em_target_name” contains invalid characters (or the like). This is fixed in the coming version of AutoUpgrade. But I can provide you with a fixed version of AutoUpgrade. If you hit that error and are interested send me an e-mail on daniel.overby.hansen (a) oracle.com.
      Thanks,
      Daniel

      Like

      Reply

Leave a reply to adel8560 Cancel reply

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