Oracle Enterprise Manager Cloud Control 12c Release 3 Upgrade
The third release of Oracle Enterprise Manager Cloud Control is now available. It includes numerous enhancements such as updated user interface, improved EMCLI with scripting options, Administration Group enhancements, OMS Disaster improvements among others. For the complete list see the New Features page.
For users still running on pre-12c or 12.1.0.1, it is a highly recommended upgrade. If you are running EM 12.1.0.2 you may see some benefits of upgrading but I personally wouldn't rush off unless there were some compelling features/fixes that would be of benefit. That said, if you do decide on going full speed with the new release, here is a step-by-step document on how I upgraded a POC environment with a single OMS and repository on the same server from 12.1.0.2 with PSU3 to 12.1.0.3.
The official Oracle documentation lists the detailed steps for the upgrade here.
The pre-requisite steps needed for the upgrade are listed below:
0. Allocate additional space (14GB on Linux x86-64) for new OMS home (out-of-place upgrade)
1. Copy EMKey to repository
2. Unset http_proxy environment variable
3. Check repository database pre-requisites. Run emprereqkit.
4. Stop existing OMS
5. Backup repository, OMS, inventory and software library.
Note: The upgrade is an out-of-place upgrade for the OMS even in a One-System Upgrade. A new OMS home will be created while the schema objects will be upgraded in the repository database.
Download the installation media from OTN or Oracle e-delivery (Software Delivery Cloud) and extract and stage it in a location accessible to the server.
Execute runInstaller from the installation directory. You will be prompted for the usual email address if you need Oracle to provide you with information about updates. Also if you have a valid CSI number you can opt to provide it. Click next when done.
The next screen will execute pre-requisite checks. If any should fail then fix it before continuing.
In this case I chose the second option to upgrade using One-System Upgrade. Select the radio button next to the home to be upgraded. Click next.
Since this is an out-of-place upgrade you need to enter the path with sufficient space where the new OMS home will be installed.
Provide the password for the SYS and SYSMAN user used for the existing management repository database. Also check the box to confirm that you have backed up your management repository. For a production environment I would do another backup to be on the safe side
Repository pre-req checks may fail if not already addressed. You can opt to fix the problem yourself by clicking No or allow OUI to fix them by clicking Yes.
You may see warnings related to database parameters and configuration settings which aren't required for the installation but necessary for optimal operation of OEM. Click OK to fix the issues manually and re-execute the checks or click Cancel to continue.
All existing plug-ins will be upgraded automatically. Click next to continue.
If you have downloaded additional plug-ins you can check the boxes next to the corresponding plug-in. Click next to continue.
Provide the name of the Admin Server, port, weblogic username and password. Also enter the path for the new OEM instance.
Note that 12.1.0.3 place the instance outside of the Middleware home by default.
Review the summary of the upgrade and click Install to begin the upgrade.
The upgrade begins and lists the steps and overall progress.
All the steps should complete successfully for the upgrade to be successful. If any steps failed click on the "View Log" link next to the step to see the details on the failure and fix it if possible.
Run the allroot.sh script as the root user to complete the upgrade.
Review the summary of the installation and make a note of any changes.
Check the status of the OMS using emctl status oms -details.
Once the OMS has been upgraded you also need to upgrade the central agent installed on the OMS server and other agents in the environment. This will be covered in a separate post.
The environment used for this test consisted of a single virtual server for the OMS and repository with 8GB physical memory and 2 cores. There were 80 targets and repository was 8GB. Total time for the upgrade was 2 hrs.
For users still running on pre-12c or 12.1.0.1, it is a highly recommended upgrade. If you are running EM 12.1.0.2 you may see some benefits of upgrading but I personally wouldn't rush off unless there were some compelling features/fixes that would be of benefit. That said, if you do decide on going full speed with the new release, here is a step-by-step document on how I upgraded a POC environment with a single OMS and repository on the same server from 12.1.0.2 with PSU3 to 12.1.0.3.
The official Oracle documentation lists the detailed steps for the upgrade here.
The pre-requisite steps needed for the upgrade are listed below:
0. Allocate additional space (14GB on Linux x86-64) for new OMS home (out-of-place upgrade)
1. Copy EMKey to repository
2. Unset http_proxy environment variable
3. Check repository database pre-requisites. Run emprereqkit.
4. Stop existing OMS
5. Backup repository, OMS, inventory and software library.
Note: The upgrade is an out-of-place upgrade for the OMS even in a One-System Upgrade. A new OMS home will be created while the schema objects will be upgraded in the repository database.
Download the installation media from OTN or Oracle e-delivery (Software Delivery Cloud) and extract and stage it in a location accessible to the server.
Execute runInstaller from the installation directory. You will be prompted for the usual email address if you need Oracle to provide you with information about updates. Also if you have a valid CSI number you can opt to provide it. Click next when done.
The next screen will execute pre-requisite checks. If any should fail then fix it before continuing.
In this case I chose the second option to upgrade using One-System Upgrade. Select the radio button next to the home to be upgraded. Click next.
Since this is an out-of-place upgrade you need to enter the path with sufficient space where the new OMS home will be installed.
Provide the password for the SYS and SYSMAN user used for the existing management repository database. Also check the box to confirm that you have backed up your management repository. For a production environment I would do another backup to be on the safe side
You may see warnings related to database parameters and configuration settings which aren't required for the installation but necessary for optimal operation of OEM. Click OK to fix the issues manually and re-execute the checks or click Cancel to continue.
All existing plug-ins will be upgraded automatically. Click next to continue.
If you have downloaded additional plug-ins you can check the boxes next to the corresponding plug-in. Click next to continue.
Note that 12.1.0.3 place the instance outside of the Middleware home by default.
Review the summary of the upgrade and click Install to begin the upgrade.
The upgrade begins and lists the steps and overall progress.
Run the allroot.sh script as the root user to complete the upgrade.
Review the summary of the installation and make a note of any changes.
Check the status of the OMS using emctl status oms -details.
The environment used for this test consisted of a single virtual server for the OMS and repository with 8GB physical memory and 2 cores. There were 80 targets and repository was 8GB. Total time for the upgrade was 2 hrs.
Comments
Post a Comment