Configuring SQL Server Monitoring in OEM 13c provides cross-database monitoring from a single tool. We have found this to be invaluable in multi-platform environments.
The first part was to install the OEM 13c agent on Windows from a Linux server. This was covered in my previous blog Install the OEM 13c agent on Windows from a Linux server. https://www.perftuning.com/blog/install-an-oem-windows-agent-from-a-linux-oem-platform/
In part one of this blog, I shared the process for installing the OEM agent to a SQL Server on a Windows Server. You can find this blog here: https://www.perftuning.com/blog/configuring-sql-server-monitoring-in-oem-13c-pt-1/
The rest of the configuration is done from the OEM console. There are several steps that must be completed in order to set it up.
- Download and configure the SQL Server Plugin for
This is done through the Setup->Extensions->Self Update page.
If the OMS (Oracle Management Service) is connected to the internet and hasn’t checked updates in a while click Check Updates. Else, scroll down until you see Plug-in and click on it.
Once you are in the Plug-in Updates screen search for “SQL Server” in the search box.
If “Microsoft SQL Server Database” shows “Available”, click on it to highlight and then click Download. It might take a little bit of time, but it will eventually download.
Check back occasionally to see if it is there and showing “Available”. An Available plugin can be activated by highlighting it and clicking the Apply button.
Once the plug-in has been downloaded and applied, it can be added to the OMS server and agents
From the list of Plug-Ins, highlight the Microsoft SQL Server Database plugin and select Deploy On->Management Server. This operation might take a while and might cause some downtime of the OMS.
Once you have deployed it on the OMS (Oracle Management Server) you can select it again and install it on the Microsoft Windows Agent that you have previously deployed.
Once this is completed you are ready to add SQL Server monitoring to OEM 13c.
From the Setup->Add Target->Add Targets Manually drop down select Add Non-Host Targets Manually (OEM 13.4) or Add Non-Host Targets Declaratively (OEM 13.3).
Choose the Host and search for SQL Server and select Target Type SQL Server.
In the Add: Microsoft SQL Server screen fill in the following information:
Target Name This is what you want the target to show up
as in the Databases List. Choose
something descriptive containing the host name and database instance if not
For example: MSSQL_MSSQL02. The hostname in this case is MSSQL02.
Monitoring Database Credentials
Select these fields if you are using SQL Server authentication.
Database User Name
(Optionally) Database Role
Monitoring Database Host Credentials
Select these fields if you are using Windows authentication
Target System Username
Target System Password
JDBC URL Use jdbc.sqlserver://<HOST>
The rest can be left as default.
Note: You will either use SQL Server credentials or Windows credentials, not both.
Once you have completed this and saved it you are done.
It will take several minutes for the Microsoft SQL Server database to show up in OEM under Targets->Databases. Once it shows up, you can select it and view the SQL Server instance.
The SQL Server instance monitoring in OEM allows you to drill down into databases. If the description is in blue, it is a hyperlink that can be drilled down into.