Oracle strongly recommends that you back up the Management Repository, the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails. This will upgrade only the software binaries of the Enterprise Manager along with the applicable plug-ins.

Invoke the Enterprise Manager Installation Wizard on the host where your existing OMS is running.

./em24100_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

For information about additional advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

On the Installation Types screen, select Upgrade software only with plug-ins and Configure Later to upgrade an existing Enterprise Manager system. Then select the Management Server (OMS) you want to upgrade, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

For instructions about downloading the software updates in offline or online mode, see Oracle Enterprise Manager Advanced Installation and Configuration Guide. If the host from where you are running the installation wizard does not have a connection to the Internet, you can manually collect the configuration information and upload it to My Oracle Support after you complete the upgrade. For instructions, see Oracle Enterprise Manager Advanced Installation and Configuration Guide.

If you do not want to run the software updates, select Skip and click Next.

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the upgrade. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

On the Installation Details screen, do the following, and click Next.

• Enter a new middleware home where the installer can automatically install Oracle WebLogic Server 12c Release 2 (12.2.1.4.0) and Java Development Kit 1.8.0_431 for you.

  Example: /u01/software/em24/middleware

  Note:

  Ensure that the Middleware home you enter or validate here is used only for Enterprise Manager. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware home.

• Enter a new agent base directory, a location outside the middleware home.

  Example: /u01/software/em24/agentbasedir

• Validate the host name. By default, the host name is the name of the host where the existing, earlier release of Enterprise Manager was installed. This is a non-editable field.

On the Database Connection Details screen, do the following, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

1. Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

   Note:

   • The SYSMAN password must begin with a letter, contain at least 8 characters, one numeric value and may contain the following characters: $ # _ 

   • To change the password, run the following on one of the OMSs:

     <OMSORACLE_HOME>/bin/emctl config oms -change_repos_pwd -old_pwd <old_pwd> -new_pwd <new_pwd> 

   • After the upgrade, you may run the same command to change the sysman password to a password of your choice.

2. Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

3. If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

   Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

   The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

   If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

   To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Console, from the Setup menu, select Manage Enterprise Manager, then select Post Upgrade Tasks.

4. Check the Select to provide Database SSL Configuration Details (one-way SSL) checkbox if the database is one-way SSL configured. The truststore details are required for one-way SSL configuration.

   Provide the database truststore file and password.

5. Check the Select to provide Database SSL Configuration Details (two-way SSL) checkbox if the database is two-way SSL configured. The keystore details are required for two-way SSL configuration.

   Provide the database keystore file and password.

After you complete selecting your choices, click Next.

The Information pop-up window is displayed indicating that the Central Agent is getting upgraded.

Review the information provided and click OK.

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager 24ai Release 1.

On the Database Prerequisite Checks screen, check the status of the database prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. Then click Next.

The installation wizard runs the database prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed or Succeeded.

If the installer finds that some plug-ins deployed in the previous release of Enterprise Manager are obsolete and are not supported in Enterprise Manager 24ai Release 1, then you are prompted to Check for Obsolete plugins. You can return to the installer and proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

1. Undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on Undeploying Plug-Ins in Oracle Enterprise Manager Administrator's Guide.

2. Optionally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on Updating Enterprise Manager in Oracle Enterprise Manager Administrator's Guide.

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager 24ai Release 1.

After you complete reviewing and fixing the prerequisites results, click Next.

The Information pop-up window is displayed.

Review the important information provided about the upgrade process and then click OK.

This step is only applicable to Enterprise Manager systems that have multiple editions of the Management Repository database.

If your system is not applicable or the EM prerequisite kit was already performed, this step is skipped automatically and the installer proceeds to the next step: Upgrading or Migrating Plug-ins, or Deploying Dependent Plug-ins.

If you get the Actualization screen, then additional editions of the Management Repository database besides the base edition are present in your system. For example, this could happen if you applied the zero down time patches to the Oracle Management Service (OMS) 13. 5 before the upgrade to Enterprise Manager 24ai.

If the actualization process fails, review the install and repository creation utility (rcu) log files and check for failures and resolve them. The logs are located under the oraInventory.

Review and click Start.

Once completed, click Next.

On the Plug-In Upgrade screen, review the plug-ins and click Next.

The plug-ins will experience one of the following effects:

• Upgraded when newer versions exist.

• Migrated when newer versions do not exist.

• Deployed when the plug-ins being upgraded have new dependencies, or when there are any new default plug-ins introduced with a release.

Here, newer versions refer to the newer versions of plug-ins available in the Enterprise Manager software (DVD, or downloaded software) that you are using to install.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

On the Select Plug-ins screen, select the additional plug-ins you want to deploy in addition to the plug-ins that will automatically be upgraded while upgrading the OMS, and click Next.

On the Review screen, review the details you have provided for the upgrade.

On the Install Progress Details screen, view the overall progress (in percentage) of the installation.

The installer performs the software only install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

(For UNIX Only) On the Installation Progress Details screen, once the software binaries are installed and configured, the Execute Configuration scripts pop-up window is displayed and you are prompted to run the allroot.sh script.

Open another window, log in as a root and run the allroot.sh script from the Oracle home of the OMS you installed in Upgrading the Enterprise Manager 24ai Release 1 Software Only with Plug-ins.

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em24/middleware/oms_home/allroot.sh

If you have additional OMS instances, then run this script on those additional OMS hosts as well.

If you are installing on Microsoft Windows, then you will NOT be prompted to run this script.

On the Finish screen, you should see information pertaining to the upgrade of Enterprise Manager. Review the information and click Close to exit the installation wizard.

Invoke the installation wizard to configure the software only with plug-ins by running the following script from the Oracle home of the OMS you installed in Upgrading the Enterprise Manager 24ai Release 1 Software Only with Plug-ins.

$<ORACLE_HOME>/sysman/install/ConfigureGC.sh [-invPtrLoc <absolute_path_to_oraInst.loc>]

For Microsoft Windows, run ConfigureGC.bat script.

Optional Parameter:

For information about additional advanced options you can pass while invoking the ConfigureGC script, see Using Advanced Script Options While Configuring the Enterprise Manager Software Using the Software Only Upgrade Method in Graphical Mode.

On the Installation Types screen, do the following:

On the Database Connection Details screen, do the following, and click Next.

1. Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

   Note:

   • The SYSMAN password must begin with a letter, contain at least 8 characters, one numeric value and may contain the following characters: $ # _ 

   • To change the password, run the following on one of the OMSs:

     <OMSORACLE_HOME>/bin/emctl config oms -change_repos_pwd -old_pwd <old_pwd> -new_pwd <new_pwd> 

   • After the upgrade, you may run the same command to change the sysman password to a password of your choice.

2. Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

3. If you have to stop the Enterprise Manager system for post upgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for post upgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

   Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

   The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

   If you have to stop the Enterprise Manager system for post upgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the post upgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

   To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Console, from the Setup menu, select Manage Enterprise Manager, then select Post Upgrade Tasks.

4. Check the Select to provide Database SSL Configuration Details (one-way SSL) checkbox if the database is one-way SSL configured. The truststore details are required for one-way SSL configuration.

   Provide the database truststore file and password.

5. Check the Select to provide Database SSL Configuration Details (two-way SSL) checkbox if the database is two-way SSL configured. The keystore details are required for two-way SSL configuration.

   Provide the database keystore file and password.

After you complete selecting your choices, click Next.

The Information pop-up window is displayed indicating that the Central Agent is getting upgraded.

Review the information provided and click OK.

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager 24ai Release 1.

On the Database User Details screen, do the following and click Next.

Select if you want to perform the upgrade using SYS or non-SYS database user.

SYS is the default user in the Repository database.

A non-SYS user is a less privileged administrator user of the Repository database that still allows you to perform Enterprise Manager administration tasks.

If the Perform Upgrade using non-SYS user is selected, you need to provide the database user name and password for the non-SYS user. The non-SYS user name should have the SYSMAN_ prefix as part of user name. For example, you can enter SYSMAN_ADMIN under DB Username. If the user doesn't exist, the Enterprise Manager upgrade process creates the new user in the Repository database and this user performs the database prerequisites checks.

On the Database Prerequisite Checks screen, check the status of the database prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. Then click Next.

The installation wizard runs the database prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed or Succeeded.

If the installer finds that some plug-ins deployed in the previous release of Enterprise Manager are obsolete and are not supported in Enterprise Manager 24ai Release 1, then you are prompted to Check for Obsolete plugins. You can return to the installer and proceed with the upgrade only after removing those obsolete plug-ins.

To remove the obsolete plug-ins, follow these steps:

1. Undeploy the obsolete plug-ins from the Management Agents. Next, undeploy them from the OMS instances. For instructions, see the chapter on Undeploying Plug-Ins in Oracle Enterprise Manager Administrator's Guide.

2. Optionally, remove the binaries of these obsolete plug-ins from the Self Update Console. For instructions, see the chapter on Updating Enterprise Manager in Oracle Enterprise Manager Administrator's Guide.

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager 24ai Release 1.

After you complete reviewing and fixing the prerequisites results, click Next.

The Information pop-up window is displayed.

Review the important information provided about the upgrade process and then click OK.

On the Extend WebLogic Server Domain screen, do the following to create a new WebLogic domain and a new OMS instance base directory for the upgraded OMS, and click Next.

The installer performs only the software install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

• Validate the Admin Server Host name, the Admin Server Port value and the WebLogic User Name, and enter the WebLogic user account password under WebLogic Password. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the Admin Server used by the earlier release of the OMS you are upgrading.

  Note:

  If you are upgrading an additional OMS, then the host name and port of the Admin Server configured for the first OMS that you have already upgraded, and also, the user name for the existing WebLogic user account will be populated automatically. You need to validate them, and then enter the password for the WebLogic user account.

  The host name is the name of the host where the first OMS is running. To identify the port, check the value set to the parameter AS_HTTPS_PORT in the following file:

  <OMS_INSTANCE_HOME>/em/EMGC_OMS<n>/emgc.properties

• Enter the absolute path to the new OMS instance base directory (gc_inst), which will be created for storing the configuration information related to the upgraded OMS. This gc_inst directory must not be your old gc_inst directory of 13c Release 5, therefore you need to enter a new directory location. If you enter the old gc_inst directory, then the installer will display a warning that the directory is not empty.

  For example: /u01/app/oracle/em24/gc_instr2

  Make sure the path you enter leads up to the instance base directory, and is maintained outside the middleware home.

  Note:

  If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Moving Lock Files from an NFS-Mounted Drive to a Local File System Location.

On the Port Configuration Details screen, customize the ports to be used for the new components being added for this release, and click Next.

The ports for most components are automatically carried over from the previous release, and therefore, this screen lists only the ports for the new components being added for this release.

You can enter a free custom port that is either within or outside the port range recommended by Oracle.

To verify if a port is free, run the following command:

• On Unix:

  netstat -an | grep <port no>

• On Microsoft Windows:

  netstat -an|findstr <port_no>

However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.

On the Review screen, review the details you provided for the selected installation type.

• If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

• After you verify the details, if you are satisfied, click Configure to begin the installation process.

On the Configuration Details screen, view the overall progress (in percentage) of the configuration.

On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

If you have additional OMS instances, then start upgrading each of them sequentially by following steps outlined in this section (Configuring the Enterprise Manager 24ai Release 1 Software Only With Plug-ins).

After upgrading all the OMS instances, upgrade the Standalone Management Agents. For more information, refer to Upgrading Oracle Management Agents.

The following are some additional advanced options you can pass while invoking the installer in graphical mode:

• By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures. By default, this location is the scratch path location (/tmp). The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

  If you want to override this location with a custom location, then invoke the installer with the -J-Djava.io.tmpdir option, and enter a unique custom location.

  For example,

  ./em24100_linux64.bin -J-Djava.io.tmpdir=/u01/install/em/STAGE/

  Note:

  /u01/install/em/STAGE/ directory should exists while using this option, else it will re-direct the tmp location to /var/tmp.

• After the upgrade operation ends successfully, the OMS and central Management Agent start automatically.

  If you do not want OMS to start automatically, then invoke the installer with START_OMS options, and set them to true or false depending on what you want to control.

  For example, if you want the OMS to start automatically, then run the following command:

  ./em24100_<platform>.bin START_OMS=true

  To understand the limitations involved with this advanced option, see Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

• During upgrade, if you want to install some plug-ins that are not in the software kit (DVD, downloaded software), then follow these steps:

  1. Manually download the required plug-ins from Plug-in Update.

     In addition, plug-ins produced by partners or customers are available for download from Enterprise Manager Extensibility Exchange .

  2. Invoke the installer:

     On UNIX platforms:

     ./em24100_<platform>.bin

     On Microsoft Windows platforms:

     setup_em24100_win64.exe

When you use START_OMS and START_AGENT as advanced options to control the way the OMS and the Management Agent start up automatically, sometimes the Management Agent and the host on which it was installed do not appear as targets in the Enterprise Manager console.

Table 4-1 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:

For more information on upgrading additional Oracle Management Services, see step 4 from Performing Postinstallation Tasks After Adding an Additional Oracle Management Service in Oracle Enterprise Manager Basic Installation Guide.

Invoke the installer and generate the response file you need to use for performing an upgrade software only with plug-ins in silent mode:

./em24100_<platform>.bin -getResponseFileTemplates -outputLoc <absolute_path_to_a_directory_to_store_the_generated_response_file>

Edit the softwareOnlyWithPlugins_upgrade.rsp file and enter appropriate values for the parameters described in Table 4-3.

To upgrade the software binaries with plug-ins in silent mode, invoke the Enterprise Manager installation wizard the following way:

./em24100_<platform>.bin -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/softwareOnlyWithPlugins_upgrade.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

For information about additional advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode

(For UNIX Only) After you install the software binaries, log in as a root user in a new terminal and run the allroot.sh script from the Oracle home of the OMS you installed in Upgrading Enterprise Manager 24ai Release 1 Software Only with Plug-ins in Silent Mode.

$<ORACLE_HOME>/allroot.sh

For example,

/u01/software/em24/oms_home/allroot.sh

If you have additional OMS instances, then run this script on those additional OMS hosts as well.

If you have additional OMS instances, then download the software binaries from Oracle Software Downloads site and copy them into the additional OMS hosts by following steps outlined in Upgrading Enterprise Manager 24ai Release 1 Software Only with Plug-ins in Silent Mode.

Access the upgrade.rsp file that you generated in Generating the Response File to Upgrade Software Only with Plug-ins in Silent Mode while generating the softwareOnlyWithPlugins_upgrade.rsp file. Edit the upgrade.rsp file and enter appropriate values for the parameters described in Editing the upgrade.rsp Response File for Upgrading Oracle Management Service and Oracle Management Repository in Silent Mode.

Configure the software binaries by invoking the ConfigureGC.sh script from the Oracle home of the OMS you installed in Upgrading Software Only with Plug-ins in Silent Mode, and passing the response file you edited in the previous step.

$<ORACLE_HOME>/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/upgrade.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

For Microsoft Windows, run ConfigureGC.bat script.

For information about additional advanced options you can pass while invoking the ConfigureGC.sh script, refer to Using Advanced Script Options While Configuring the Enterprise Manager Software Using the Software Only Upgrade Method in Graphical Mode.

If you have additional OMS instances, then start upgrading each of them sequentially by following steps outlined in Editing the Response File to Configure the Software Only with Plug-ins in Silent Mode and Configuring the Software Only with Plug-ins in Silent Mode.

After upgrading all the OMS instances, upgrade the Standalone Management Agents. For more information, refer to Upgrading Oracle Management Agents.

The following are some additional advanced options you can pass while invoking the installer in silent mode:

• After the upgrade ends successfully, the OMS and central Management Agent start automatically.

  If you do not want the OMS to start automatically, then invoke the installer with the START_OMS option, and set it to true or false depending on what you want to control.

  For example, if you want the OMS to start automatically then run the following command:

  ./em24100_<platform>.bin START_OMS=true -silent -responseFile <absolute_path>/upgrade.rsp

  To understand the limitations involved with this advanced option, see Limitations with the Advanced Installer Options Supported for Installing an Enterprise Manager System in Graphical Mode.

Refer to Database Version Requirements from Prerequisites for Installing an Enterprise Manager System.

Ensure that the existing database is a certified database as mentioned in the Enterprise Manager certification matrix available on My Oracle Support. To access the Enterprise Manager certification matrix and identify whether your database is a certified database, follow these steps in Accessing the Enterprise Manager Certification Matrix.

Alternatively, the database can be a database instance created with a preconfigured Management Repository using the database templates offered by Oracle. For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Creating a Database Instance with Preconfigured Repository Using Database Templates. Ensure that this database is dedicated to Enterprise Manager.

The database configuration types that are supported are pluggable database (PDB), lone-pluggable database (Lone-PDB), and non-container database (Non-CDB).

Invoke the Enterprise Manager Installation Wizard on the host where your existing OMS is running.

./em24100_<platform>.bin [-invPtrLoc <absolute_path_to_oraInst.loc>]

On the Installation Types screen, select Upgrade software only with plug-ins and Configure Later to upgrade an existing Enterprise Manager system. Then select the Management Server (OMS) you want to upgrade, and click Next.

The installer performs the software only install with plug-ins and this step is part of the process. There is no actual upgrade in progress.

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. Then click Next.

The installation wizard runs the prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the upgrade. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

On the Database Connection Details screen, do the following, and click Next.

• Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS.

• Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. This will enable you to revert to the original contents if the upgrade fails). As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.

• If you have to stop the Enterprise Manager system for postupgrade maintenance, then select Disable DDMP Jobs to disable the DDMP jobs. If you do not plan to stop the Enterprise Manager system for postupgrade maintenance, and hence do not want to disable the DDMP jobs, then do not select the option.

  Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded, and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.

  The time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Therefore, if you have a large amount of data, then it takes longer to migrate.

  If you have to stop the Enterprise Manager system for postupgrade maintenance, then you can choose to disable the DDMP jobs now and run them later from the postupgrade console after the maintenance period ends and after the Enterprise Manager system becomes operational.

  To run the DDMP jobs later from the Post Upgrade Console, in the Enterprise Manager Console, from the Setup menu, select Manage Enterprise Manager, then select Post Upgrade Tasks.

On the Deployment Size section, select one of the following options: Small, Medium or Large, and click Next.

On the Database Prerequisite Checks screen, check the status of the database prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. Then click Next.

The installation wizard runs the database prerequisite checks automatically when you come to this screen. The status of the prerequisite check can be either Warning, Failed or Succeeded.

For information about the various prerequisite checks that are run on the database at this point and how to fix them if they fail, see Prerequisites for Upgrading to Enterprise Manager 24ai Release 1.

After you complete reviewing and fixing the prerequisites results, click Next.

The Information pop-up window is displayed.

Review the important information provided about the upgrade process and then click OK.

Correction Types can be one of the following:

1. Not Required: This is simply a warning message, it can be ignored.

2. Manual: Manually fix all issues identified as this type.

3. Auto: In this case, the installer has pre-defined corrective actions and is able to automatically fix these issues. These actions will automatically be run during the upgrade process. Click Auto Fix to perform the auto corrective in the Admin (Primary) OMS.