Sunday, September 17, 2017

Upload the OPatch that is of version "13.8.0.0.0" and platform "226" to the Software Library

I was having an issue trying to deploy a patch to an agent due to the version of OPatch available in the software library.

The error I got was “Upload the OPatch that is of version "13.8.0.0.0" and platform "226" to the Software Library”


The solution was to run the “OPatch Update” job available from the job console in OEM.




Choose “OPatch Update” as job type:



Type a name for the job:



And click submit:




After this the agent patching was successful.

Thanks,
Alfredo

“Failed to find the OPatch patch directory” while applying patch 25105555 ( 13.2.0.0.161231) from OEM console

While applying patch 25105555 ( 13.2.0.0.161231) to an agent using the "provisioning and Patching" console from OEM 13.2 and choosing the "Upgrade OPatch" option, got this error:

---------- Error Message ----------
Error: 010
Failed to find the OPatch patch directory "/tmp/p6880880_600000000057471_2000_0/oracle/OPatch".
If you chose "No" for the "StagePatches" option, ensure that you manually place the patch at the required location and retry the operation.
----------- End Message -----------

Tue Aug 27 15:41:48 2017 - Patching aborted.


You have to follow the solution section from below MOS note:

EM 13c: Applying EM-AGENT Bundle Patch 25105555 ( 13.2.0.0.161231) from Enterprise
Manager 13.2 Cloud Control Fails with Message: Error: 010 Failed to find the OPatch patch directory (Doc ID 2229452.1)

It depends on whether you have an online or offline OMS configuration.


After doing this I was able to apply patch 25105555 to the agent.

Hope this helps.


Alfredo

Thursday, August 31, 2017

RMAN restore slow due to ASMB process from ASM to filesystem

I was restoring a database running on ASM to an instance running on filesystem.
The step for cataloging files was extremely slow and after taking a look at the alertlog file, I noticed tons of errors related to ASMB process.

Well, turns out this is an unpublished bug explained in more detail on the below MOS note.

12c RMAN Operations from ASM To Non-ASM Slow Performance (Doc ID 2081537.1)

After applying the suggested patch (19503821) the performance went back to normal and the restore progressed as expected.

Thanks,

Alfredo

Friday, July 14, 2017

2017 April PSU - OEM sending tablespace related alerts every collection schedule

I noticed that several alerts related to tablespace full were sent from OEM every collection schedule. At first sight I thought this may be related to OEM itself but after spending some significant time in MOS found a bug note stating that the 2017 April PSU patch was responsible.




The issue is that dba_tablespace_usage_metrics is not accounting for autoextend datafiles. So even if you add a new datafile, your used space will continue be reported as it was before.

You need to apply patch 26198757 on top of April PSU.

Hope this help you to avoid all this noise and happy patching.

Thanks,

Alfredo

Wednesday, April 12, 2017

Oracle Management Cloud – Setup Entities in Log Analytics

In order to gather Weblogic’s Admin Server and Managed Server log files, you need first to install and configure the OMC Cloud Agent.  


Then you need to verify that the Cloud Agent is up and running.  Refer to my previous post on how to manage the Cloud Agent.


The next step is to setup the Log Analytics entities. In order to do this you have to make use of a JSON template. Oracle provides examples of these templates in the OMC documentation:


In this example we are going to add a Weblogic Admin Server and Managed server as Cloud Agent entities.

Unzip the example zip file and modify the omc_weblogic_domain_credless.json file.

The data added to this file really depends on your environment. This is how it looks for my environment:

{
   "entities":[
      {
         "name":"base_domain",
         "type":"omc_weblogic_domain",
         "displayName":"Weblogic_on_<servername>",
         "timezoneRegion":"PST",
         "properties":{
            "port":{
               "displayName":"Port",
               "value":"7001"
            },
            "domain_home":{
               "displayName":"Domain Home",
               "value":"/u01/app/oracle/product/ofm12.1.2/user_projects/domains/base_domain"
            },
            "admin_server_host":{
               "displayName":"AdminServer",
               "value":"<servername>.<domainname>"
            },
            "webLogic_home":{
               "displayName":"WebLogic Home",
               "value":"/u01/app/oracle/product/ofm12.1.2/wlserver"
            }
         },
         "associations":[
            {
               "assocType":"omc_contains",
               "sourceEntityName":"base_domain",
               "sourceEntityType":"omc_weblogic_domain",
               "destEntityName":" <servername>__AdminServer",
               "destEntityType":"omc_weblogic_j2eeserver"
            }
         ]
      },
      {
         "name":"<servername>_AdminServer",
         "type":"omc_weblogic_j2eeserver",
         "displayName":"AdminServer_<servername>",
         "timezoneRegion":"PST",
         "properties":{
            "host_name":{
               "displayName":"Weblogic Host",
               "value":"<servername>.<domainname>"
            },
            "domain_home":{
               "displayName":"Domain Home",
               "value":"/u01/app/oracle/product/ofm12.1.2/user_projects/domains/base_domain"
            },
            "listen_port":{
               "displayName":"Listen Port",
               "value":"7001"
            },
            "listen_port_enabled":{
               "displayName":"Listen Port Enabled",
               "value":"true"
            },
            "ssl_listen_port":{
               "displayName":"SSL Listen Port",
               "value":"7002"
            },
            "server_names":{
               "displayName":"Server Names",
               "value":"AdminServer"
            }
         },
         "associations":[
            {
               "assocType":"omc_monitored_by",
               "sourceEntityName":"<servername>_AdminServer",
               "sourceEntityType":"omc_weblogic_j2eeserver",
               "destEntityName":"base_domain",
               "destEntityType":"omc_weblogic_domain"
            }
         ]
      },
      {
         "name":"<servername>_ManagedServer_1",
         "type":"omc_weblogic_j2eeserver",
         "displayName":"ManagedServer_1_<servername>",
         "timezoneRegion":"PST",
         "properties":{
            "host_name":{
               "displayName":"Weblogic Host",
               "value":"<servername>.<domainname>"
            },
            "domain_home":{
               "displayName":"Domain Home",
               "value":"/u01/app/oracle/product/ofm12.1.2/user_projects/domains/base_domain"
            },
            "listen_port":{
               "displayName":"Listen Port",
               "value":"7003"
            },
            "listen_port_enabled":{
               "displayName":"Listen Port Enabled",
               "value":"true"
            },
            "ssl_listen_port":{
               "displayName":"SSL Listen Port",
               "value":"7005"
            },
            "server_names":{
               "displayName":"Server Names",
               "value":"ManagedServer_1"
            }
         },
         "associations":[
            {
               "assocType":"omc_monitored_by",
               "sourceEntityName":"<servername>_ManagedServer_1",
               "sourceEntityType":"omc_weblogic_j2eeserver",
               "destEntityName":"base_domain",
               "destEntityType":"omc_weblogic_domain"
            }
         ]
      }
   ]
}

Save this file and load the entities to the Cloud Agent as follows:

$ ./omcli add_entity agent /home/oracle/omc_weblogic.json
Oracle Management Cloud Agent 
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
Operation Succeeded: Accepted 3 of 3 entities for processing.

As you can see, 3 entities were loaded to the agent; the base_domain, Admin Server and Managed Server.


Now verify the new entities in the Log Analytics configuration page.
-        Click on the “Navigation” icon.
-        Under “Cloud Services” click on “Log Analytics”



Click on “Configuration” located in the right side of the screen






In the “Entities” section. Click on the icon with the number (ie. 4)





You will see a list of the new entities just added.
Go back to “Log Explorer” by clicking on







In the search box type ‘Log Source’ = ‘FMW WLS Server Logs’






Click on “Run”





Check all the log information displayed for the WLS Server