Additionally I downloaded the plugin for the Oracle Database Appliance, because I wanted to have this during installation.
So, I started the installation with the following parameters, where -J-Djava.io.tmpdir points to a directory with enouph space and the PLUGIN_LOCATION points to the directory, where the Oracle Database Appliance plugin OPAR-file resides.
After a while the installation started. I choosed the “Advanced Install”
I skipped Software Updates.
Because I checked the system with the EM Prerequisite Kit, I ignored the warning about ip_local_port_range.
I filled in the Middleware home, the home of the agent and the hostname.
Then I got the following warning:
In my lab, I do not have a full qualified name, so I ignored it.
Because I started the installer with the parameter PLUGIN_LOCATION, I could choose the Oracle Database Appliance plugin.
Without the parameter and the OPAR-file, the choice to install the plugin does not appear.
I just filled in the needed weblogic configuration details
Then I provided the needed database information. I do not use SSL in my lab, so I leaved all blank
Then I decided to use the user SYS. You can here provide another username to avoid using SYS for reporitory operations.
Although I before ran the EM Prerequisite Kit, I got again a warning about the shared_pool_size. It should be at least 1024 M, so I changed this in my database.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 512M
SQL> alter system set shared_pool_size=1024M;
System altered.
SQL> alter session set container=emrep_pdb;
Session altered.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 512M
SQL> alter system set shared_pool_size=1024M;
System altered.
After changing this parameter in the database, the pre-checks ran fine.
And again (it happened also with OEM 13.5), Oracle warns about the characterset. My database has form the start the needed character set AL32UTF8.
Why is the character set check not included in the pre-checks? This is unsettling and irritating, because I then checked the character set again in the database anyway.
SQL> select * from nls_database_parameters where parameter='NLS_CHARACTERSET';
PARAMETER VALUE
-------------------------------------------------- --------------------------------------------------
NLS_CHARACTERSET AL32UTF8
So, everything is fine – but confusing 😉
Then I provided the needed OEM configuration details
Path to the Oracle Software Library, remember, if you install two OEMs, this location must be shared on both hosts!
Then I used the default ports, in this screen you can edit your own ports
After the port screen, I saw the summary. Do not forget to check it!
Then the installation started. It took a while…
As all configuation assistants ran fine, I ran the root-script
After I confirmed the run of the root-script, the installation was successfully completed
That’s it!
I think, in the installation, there were neither a suprise nor something new. If all requirements are met, the installation runs fine and without any problem.
The questioner had the problem that the EM Prerequisite Kit was checking the kernel version of the operating system. This is a normal and necessary check. However the Kit found a version 4.x, but the Kit checked for version 5.x.
My recommendation was to open an SR, because either in the documentation of OEM24ai nor on MOS there was any information about the necessary kernel version.
In the morning the questioner (thanks to Charles M) had opened an SR at MOS and got the answer, that this is a bug.
So, if you get the same error, when you use the the EM Prerequisite Kit, you can ignore this error.
Maybe the same error occurs when you install OEM, because the same checks were made during installation. So, I think you can than ignore that there, too.
Since OEM24ai is now available, I tried to install in my lab. But before I started the whole installation procedure to avoid errors or aborts, I used the EM Prerequisite Kit. This tool checks the operation system and also the database, where you want to install the repository. EM Prerequisite Kit is very useful to check, if your system is ready to install OEM24ai.
But how can you use the EM Prerequisite Kit? That is easy! You only have to have enough space for temp files. In the installation guide there is the requirement of 14 GB temp space – that is a lot! But don’t panic! You do not need 14 GB as mount point /tmp. You can use a parameter to tell the installer, where to find enough space.
After you downloaded the installation files from https://edelivery.oracle.com, copied them on the destination server and, please, unzipped all files in the same directory, you can now start the EM Prerequisite Kit. In my lab, I installed Oracle Enterrpise Linux 9.4, so please adopt the command properly to your operating system.
Also in my lab I do not have 14 GB /tmp, so I used the parameter -J-Djava.io.tmpdir.
If you have used the database template for Enterprise Manager, you can skip the database check, but I recommend that you do it anyway. But if you are sure, your database is ready for the installation, you can start the EM Prerequisite Kit with the parameter -componentVariables repository:EXECUTE_CHECKS_NOSEED_DB_FOUND:false
And by the way, unfortunatly, EM Prerequisite Kit is not supported in silent mode.
So, let’s start
[oracle@oem24ai oem_sw]$ ./em24100_linux64.bin -J-Djava.io.tmpdir=/u03/tmp EMPREREQ_KIT=true Launcher log file is /u03/tmp/OraInstall2024-12-30_03-38-07PM/launcher2024-12-30_03-38-07PM.log. Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Done Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed Checking swap space: must be greater than 512 MB. Actual 15359 MB Passed Checking if this platform requires a 64-bit JVM. Actual 64 Passed (-d64 flag is not required) Preparing to launch the Oracle Universal Installer from /u03/tmp/OraInstall2024-12-30_03-38-07PM Running EMPREREQ_KIT.
If you omit the parameter -J-Djava.io.tmpdir and do not have 14 GB or more in /tmp, the installation program aborts or you can then specify a different directory.
After a while a GUI comes up, so I will show you the screens.
Because I do not have a running OEM13.5 on my system, I do not get the possibility to choose EM Prerequisite Kit for an upgrade.
After the first step the operation system is checked. On all my OEM installations I saw the following warning – and I always ignored it 😉
In the next step you have to provide the database information. Remember, if you created the database with the template, you may not need this, and you can involke EM Prerequisite Kit with the parameter -componentVariables repository:EXECUTE_CHECKS_NOSEED_DB_FOUND:false
For example: [oracle@oem24ai oem_sw]$ ./em24100_linux64.bin -J-Djava.io.tmpdir=/u03/tmp EMPREREQ_KIT=true -componentVariables repository:EXECUTE_CHECKS_NOSEED_DB_FOUND:false
Also remember that EM Prerequisite Kit does not correct the warnings and errors. You have to do this manually.
In the next steps the database is checked, therefor the user SYS is needed. Or you create an SYSMAN_ADMIN user to do the checks (see second option)
If there are warnings or errors during the database check, please do all the corecction in the CDB and in the PDB.
I had few warnings – but I forgot to take a screenshot. So, I show you now my doings in the database
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 EMREP_PDB READ WRITE NO
SQL> show parameter session_cached_cursors
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
session_cached_cursors integer 50
SQL> alter system set session_cached_cursors=350 scope=spfile;
System altered.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 0
SQL> alter system set shared_pool_size=512M scope=spfile;
System altered.
SQL> show parameter "_allow_insert_with_update_check"
SQL> alter system set "_allow_insert_with_update_check"=TRUE scope=spfile;
System altered.
SQL> alter session set container=emrep_pdb;
Session altered.
SQL> show parameter session_cached_cursors
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
session_cached_cursors integer 50
SQL> alter system set session_cached_cursors=350 scope=spfile;
System altered.
SQL> show parameter sga_
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sga_max_size big integer 10G
sga_min_size big integer 0
sga_target big integer 0
unified_audit_sga_queue_size integer 1048576
SQL> alter system set sga_target=10G scope=spfile;
System altered.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 0
SQL> alter system set shared_pool_size=512M scope=spfile;
System altered.
SQL> show parameter "_allow_insert_with_update_check"
SQL> alter system set "_allow_insert_with_update_check"=TRUE scope=spfile;
System altered.
After these changes, I restarted the database and then all checks were successfully
Although my database has the right character set, EM Prerequisite Kit shows the following information
If all requirements are met, you can now start the installation. Good luck!
Last week I found by chance the Oracle Enterprise 24ai release 24.1.0.0 for download at edelivery.oracle.com. Today OEM24 is also available for download at https://www.oracle.com/enterprise-manager/downloads/
If you want to patch OEM with the latest release updates, you can find them very easily. There are various MOS notes that help you to find the current RU for the OEM. The easiest way is to use the MOS note:Enterprise Manager 13.5 Main Release Update List (Includes Plug-ins) (Doc ID 2760230.2)
But the RU only patches OEM itself, not the agents and not the Weblogic server. For the agent there is also the possibility to find the patch on the mentioned note. It is important to patch the agents promptly with the same RU after patching the OEM .
But where can you quickly and easily find the current PSU for the weblogic server on which OEM is installed? There is also a MOS note for this:My Oracle Support Recommended Patches for Oracle WebLogic Server and Oracle Fusion Middleware Products (Doc ID 859115.1) It describes how to search for the corresponding PSU.
Personally, I find that confusing 😉 In the OEM itself you have the possibility to look for all patches that should still be installed, not only for Weblogic. And here I would like to show you how I do this. I find this way easier 😉
My OEM is in the so-called “offline patching” mode. I download the current catalog (em_catalog.zip) via Setup – Provisioning and Patching – Offline Patching.
As soon as the associated job (Refresh From My Oracle Support) has run, you can view the recommended patches.
Find the recommended patches
In OEM go to “Enterprise – Provisioning and Patching – Patches & Updates”. The page looks very similar to the patch search in MOS. Under the link All Recommendations you will find all patches.
Depending on which target types are available in the OEM, all recommended patches are listed on the following page, including the one for Weblogic.
Using the patch number, you can now download and install the corresponding patch from MOS.
