In this cloud-era it’s almost weird to explore stuff on-premises, but I did…. In this case a slightly Higher Availibility configuration of Oracle Enterprise Manager (OEM) that doesn’t cost anything, is not disruptive to the existing configuration and gives a tiny bit more confidence during patching of OEM : Always On Monitoring (AOM). Maybe a bit underrated functionality – within Oracle .
When Oracle Management Server (OMS) is down for patching, AOM is capable of mailing you when a critical target is down. It’s a limited functionality, but can be quite useful in some cases. Some details has changed since the start in 2016, when DBIservices wrote about it. At the end of the blogpost my findings. (more…)
With Oracle Enterprise Manager (OEM) you are able to monitor an Oracle environment as well as a non-Oracle environment, like Microsoft’s SQL Server.
You are also able to exchange notifications between Oracle Enterprise Manager and e.g. Microsoft’s SCOM. How to monitor this heterogeneous environment. What licenses do you for monitoring? And.. do you need Oracle licenses when sending notifications by mail? Hold on to this thought.
After an upgrade of Oracle Enterprise Manager from 220.127.116.11 to 13.2, I wanted to deploy a new version of the plugin oracle.sysman.db. Downloaded the new version and got to the plugin-management page to apply the patch. But all I got was a blank page. Cost me quite a while to figure out what the – almost humiliating – workaround / solution eventually was.
Situation at customer’s site: OMS 13.2 on Oracle Linux, targets are Windows machines, and a bit ancient: Windows 2008 R2. How to deploy agents on those targets? Several methods are possible in theory. In this blog I’ll describe my efforts to determine what is really possible and what is efficient. (more…)
After the upgrade of the 12c central agent to 13c, I noticed the new central agent’s home located under the wrong – old agent – directory: /u01/app/oracle/agent12c/agent_18.104.22.168.0. Must have done something wrong. How to correct this? Want to move the directory to /u01/app/oracle/agent13c/. A very short blog to describe the two steps.
Despite the potential of Oracle Management Cloud, I’m a fan of Oracle Enterprise Manager, with its small imperfections. So when noticing a 12c Oracle Enterprise Manager on Linux, and targets on Windows, I took the challenge of modernizing the customer’s environment a bit. And the starting point , 22.214.171.124 for OMS and 126.96.36.199 database as repository wasn’t that bad at all. This post is purely about upgrading the OMS. Upgrading agents is a different story with Windows as target.