On a SCOM management server I’ve noticed event ID 31553 logged a lot constantly and in detail the error looked like this: Continue reading “Fixing Event ID 31553 On SCOM Management Server”
OpsLogix is a Microsoft System Center Alliance partner which develops innovative products for (virtual) infrastructure management. In my experience I was previously working with Oracle Intelligent Management Pack by supporting the SCOM environment of one of OpsLogix reference customers. I’ve never had issues with that MP. As being only supporting part I was not involved in implementing this MP but recently I was given this opportunity so this blog post is about my experience with OpsLogix Oracle Intelligent Management Pack.
First I want to start that instead of testing the Oracle IMP in supported scenario I’ve decided to test in unsupported environment in order to prove how good this MP is. I’ve always been enthusiast so I just I couldn’t resist. Also I want to make a notice that if you are deploying in production always use supported scenario.
Before introducing my test environment let’s first see what the architecture of the Oracle IMP is:
As we can see you just has to have one Windows node with SCOM Agent on it and ODAC.Net components installed. That node acts as a proxy and connects to all you Oracle database weather they lie on Windows OS, Unix OS or Linux OS. This architecture makes the MP very flexible which is especially important in the changes about unix an linux agents changes coming in SCOM 2012 R2. Basically it makes the MP SCOM 2012 R2 ready.
Now let’s look of how my lab looks:
· SCOM 2012 R2 Preview server that is installed on Windows Server 2012 R2 Preview.
· Oracle ODAC.Net components installed on the SCOM 2012 R2 Preview Management Server. You can install them on separate node but I’ve used my SCOM management server for simplicity. The components require .NET Framework 2.0 and are supported on Windows 2003/2008/2008R2 with x86 or x64 architecture. In production install them only on supported systems. I am sure that in the future OpsLogix will offer support for WS 2012 also.
· Windows Server 2012 (DB1) with Oracle 12c installed on it. Oracle 12c is not supported by the Oracle IMP but I’ve wanted to see if it is possible to add such database.
· Windows Server 2012 (DB2) with Oracle 11g installed on it.
After the overview of the lab we can continue with the first steps of implementing Oracle IMP.
1. First make sure you’ve installed .NET Framework 2.0 on the node that you will use as proxy. I already had it installed on my SCOM 2012 R2 Preview management server.
2. Second install SCOM agent on that same server. As my server is management server I do not need to do that.
3. Next you can proceed with installing Oracle ODAC.Net components. OpsLogix provides all components in a zip file that you can extract and then you run a simple script that install everything you need.
4. After successful installation you will see oracle folder on C:\ with all components:
5. After this procedure you can proceed with importing the OpsLogix Oracle IMP trough the SCOM console
6. You can see that you even have unsealed MP ready for overrides.
7. Everything is imported successful on SCOM 2012 R2.
8. After importing the first thing you need to do is to import your License keys in order to be able to monitor any Oracle database instance.
9. Importing is very easy you have to go to Monitoring -> OpsLogix -> OpsLogix Licensing Dashboard -> Add License.
10. After adding your license you can see all information about the license.
11. Next is to add the node(s) that will act as proxy for monitoring your Oracle database. You go to OpsLogix -> Oracle -> Oracle IMP Configuration Dashboard. The MP automatically detects all your SCOM Windows agents and lists them so you can just select the node(s) that will act as proxy and add them.
12. After adding monitoring node(s) you select Add/Remove instances tab to add databases that you want to monitor.
13. A simple information is added to monitor database as monitoring node, server name, instance name, port and credentials. It is very easy to add databases for monitoring. In fact as I’ve hadn’t any experience with Oracle databases it was harder for to actually configure the databases themselves than to add them for monitoring.
14. Let’s first add DB2 with Oracle 11g installed on it and then DB1 with Oracle 12c.
15. After a couple of minutes you will see both instances being discovered completely. Even that 12c is not supported that instance is discovered with all of its properties:
16. Now let’s see what capabilities this MP has. The MP has Oracle diagram where you can see health map of your Oracle instances and drill down to the root cause of every issue:
17. In the Action menu you will find three tasks:
18. In order to use these tasks you have to copy two files on all of your management servers:
19. You will also find a backup state view. This is very useful for database administrators.
20. You will also find a separate folder for Storage that you will find the different components of the Oracle database architecture in separate views. This helps locating problems faster.
21. What I like most is the Instance performance view where you can see and compare all performance data that is gathered.
22. As we know there is no perfect MP you could always find an error or performance counter that is not monitored for your particular case. The OpsLogix Oracle IMP covers that scenario by providing 3 templates for rules and monitors (Oracle Alert Rule, Oracle Performance Collection Rule and Oracle Two-State Monitor Template) so you can extend the MP very easy.
23. The last I want cover reporting. A lot of good MPs just do not have reporting but this one has one report which is very good. The MP gives you one general report that provides you with availability and performance which are the most common requirements for reports:
As a summary I can say that OpsLogix Oracle IMP is very easy to implement, will offer you with everything you need to monitor your Oracle database and it is definitely SCOM 2012 R2 ready.
New management pack is available for Windows Azure service. Now you can monitor your Windows Azure SQL Databases from SCOM. These are the key features:
- User-friendly wizard to discover Windows Azure SQL Database servers.
- Provides availability status of Windows Azure SQL Database server.
- Collects and monitors health of Windows Azure SQL Database databases.
- Space monitoring:
- Used space
- Free space
- Total allocated quota
- Track the total number of databases per server
- Space monitoring:
- Collects and monitors performance information:
- Average memory per session
- Total memory per session
- Total CPU time per session
- Total I/O per session
- Number of database sessions
- Maximum Transaction execution time
- Maximum Transaction lock count
- Maximum Transaction log space used
- Network Egress/Ingress bandwidth
- Ability to define Custom thresholds for each monitor to configure the warning and critical alerts.
- Run-as profile to securely connect to Windows Azure SQL Database.
- Detailed knowledge to guide the IT operator with troubleshooting the problem
- Custom tasks to redirect the user to the Windows Azure SQL Database online portal
- Custom query support to enable application-specific availability and performance monitoring
Grab the management pack and the installation and configuration guide from here.
On his blog Anders Bengtsson explains what are the key points in estimating the Orchestrator database size. If you are planning to install Orchestrator in your environment read Anders’ article so you can estimate the database size
Orchestrator team blog is publishing article after article and this is a sign that the community is getting stronger. Find out the most useful Orchestrator Database Queries.