By:| Architect <span id="XinhaEditingPostion"></span> Now that Enterprise Manager 12cR4 has been out for a little while, more people are getting around to upgrading their agents. Since the monthly Patch bundles were released we already have a few Agent side patches that we want to apply to our newly upgraded agents. I’ve written about before, but this feature still seems to fly under the radar. It’s days like these that I miss running a massive Enterprise Manager with thousands of databases, because this is one of the things that would have made me dance in my cubicle. Let’s say, you have 100 12.1.0.3.0 agents (50 with Database plug-in, 50 with Middleware plug-in). In my previous blog on, I explained the different types of patches available for EM, so I’m not going to go into detail here. What I'm going to illustrate is how we can upgrade those 100 agents, and patch them with the following patches in one step (current as of today): • 12.1.0.4.1 Agent: 18873338 • 12.1.0.6.1 Database Agent-Side Plug-in:19002534 • 12.1.0.6.1 Middleware Agent Side Plug-in: 18953219 • 12.1.0.4.0 JDBC: 1851761 Apply Pre-Requisite Patches to OMS Servers Before staging and applying any Agent patches, be sure to read the readme's completely for each patch. The Database and Middleware patches often rely on their OMS-side patch, so be sure to apply the OMS pre-requisite patches first. In this example, applying the OMS Plug-in System patch 18945232 is required. Not applying the OMS-side patches first can causes patch applications to fail or other various inconsistencies. Stage Patches on OMS Servers First we need to download and stage the 5 patches on our OMS Servers. In case of multi-OMS, they must be staged on each server. EM12c Release 4: Upgrading Agents with Ease. Download all 5 patches and transfer to your OMS servers. 'EM-AGENT BUNDLE PATCH 12.1.0.4.1'. OEM, oem 12c » OEM: AMP and Change Management. Patch 14825718 - oracle forms bundle patch 10.1.2.3.2 for. Download and apply the above. Bundle Patch or PSU on Windows. Metalink Patch note: Patch 21454170: WINDOWS DB BUNDLE PATCH 12.1.0.2.8. All part of learning! OEM; OEM 12c; OPatch; ORAchk. Oracle Enterprise Manager Cloud Control Upgrade. Framework and portal in Oracle Enterprise Manager. 5-Jan 15: 12.1.0.7.0. Bundle Patch 1) Download. ![]() The patches get staged in the $ORACLE_HOME/install/oneoffs directory. During the upgrade or install of a new agent, the patches are picked up from here. Download all 5 patches and transfer to your OMS servers. ![]() Create the $ORACLE_HOME/install/oneoffs/12.1.0.4.0/Generic directories on each of your OMS servers $ cd $ORACLE_HOME/install/oneoffs $ mkdir –p 12.1.0.4.0/Generic 3. Stage the zip files in the $ORACLE_HOME/install/oneoffs/12.1.0.4.0/Generic $ cd 12.1.0.4.0/Generic $ cp /tmp/12.1.0.4.0_patches/*.zip. $ ls -l /oracle/em/12.1.0.4/oms/install/oneoffs/12.1.0.4.0/Generic -rw-r--r-- 1 cllamas dba 516862 Jul 21 08:21 p18570_Generic.zip -rw-r--r-- 1 cllamas dba 101566 Jul 21 08:21 p18740_Generic.zip -rw-r--r-- 1 cllamas dba 14110135 Jul 21 08:21 p18840_Generic.zip -rw-r--r-- 1 cllamas dba 61619 Jul 21 08:21 p18960_Generic.zip -rw-r--r-- 1 cllamas dba 13242 Jul 21 08:21 p19060_Generic.zip 4. Repeat on each OMS server. Upgrade an Agent Now that we've staged our 5 patches, let’s upgrade an Agent. Starting with 12.1.0.2, agent upgrades are performed via the Upgrade Console. Click Setup / Manage Cloud Control / Upgrade Agents 2. Click Add to select the Agent(s) you want to upgrade and click OK. In the Choose Credentials section, you’ll notice it’s only asking for Privileged credentials. This is because the Agent uses its existing connection to upgrade, and you only need to provide credentials for the root.sh steps if required. Ess es1938s driver download xp. If you have a Privileged credential with root capabilities that is not set as your Preferred Credential, you can select Override Privileged Credentials and select or create the credential. If you don’t have the root credentials, you will be prompted to run root.sh manually as needed. In the Additional Inputs section, you can add pre-upgrade or post-upgrade scripts or specify alternate paramters or staging location if necessary. Click Submitto submit the upgrade procedure. If you did not provide a root credential, you will receive a warning. Paperport 14 Patch 1 DownloadClick OK to proceed. Once you submit the procedure, you’ll see the list of targets in the top screen, and the steps of the selected target in the bottom half. Clicking on any of the links will take you to the specific job output for that step. As you can see, the Agent Upgrade procedure takes care of starting and stopping the blackouts required to avoid false alarms on the targets. Validate Patches Once the agent is upgraded, let’s go to the agent and verify what patches were applied. $ OPatch/opatch lsinventory -oh /scratch/agent/core/12.1.0.4.0 Oracle Interim Patch Installer version 11.1.0.10.4 Copyright (c) 2014, Oracle Corporation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2019
Categories |