As Operations Manager moves more into management of heterogeneous environments, it’s become more apparent that this is an area of interest in OpsMgr 2012 for a lot of our clients. In a previous blog post I went through the steps required to integrate Tomcat into OpsMgr monitoring, and to integrate Unix/Linux systems in System Center Virtual Machine Manager 2012 (for monitoring by OpsMgr). The next big questions which comes up is what about monitoring Oracle with Operations Manager? The focus of this blog article is the steps required to get Oracle installed on Windows for monitoring by Operations Manager 2012. To be clear on this, I am not an Oracle subject matter expert (SME) nor do I know that the approaches that I use in this article are the best-practice approach for installation. I chose to install Oracle on a Windows platform to provide the quickest way to provide a functional Oracle environment for monitoring – not to effectively represent a production environment. In a later blog article I plan to blog about the monitoring functionality available through a third party vendor in this space.
The following are steps I took to lab install Oracle on Windows Server 2008 R2 and get it to a state that it could be monitored by OpsMgr:
1) Acquisition of the evaluation version of Oracle 11g from: http://www.oracle.com/technetwork/indexes/downloads/index.html
I installed Oracle 11g on a Windows Server 2008 R2 system with Service Pack 1 installed and current patches in place which was deployed by a template image using System Center Virtual Machine Manager 2012.
After both files were downloaded to my database server (cloud-db04), the next step is to extract the zip files to the server (move all extracted files to the SAME folder for installation, don’t extract them into two different folders or if you do merge them before you do the installation). After these files were extracted I had them stored in c:\install\oracle_install\database as shown below:
2) Installation of Oracle 10g and creation of the initial database: As I am not familiar with Oracle installation processes (and many OpsMgr admins may not be) all of the major screenshots are shown below which occurred during the installation. I started by running the step file shown above. I took the defaults on all screens where possible, and noted any passwords I provided for later use.
On the third step I chose the server class installation instead of the default setting of desktop class.
Be sure to note the administrative password you provide here. Getting into the database without this is either not possible or just extremely challenging.
The installation was pretty straight-forward. The tough part for me was how to access the database and validate it was functional after it was installed.
3) Validate the Oracle database is online and functional
To access the database, run the SQL Plus application application under the Oracle folder structure shown below:
The account to use to log in is “SYSTEM” with the password specified during installation.
The next step for me was to create a user which OpsMgr would use for monitoring (shown below):
And then to log into the SQL Plus with the user that was created to validate that it works.
The next step to validate Oracle is functional is to telnet to port 1521 from the server which will be monitoring it. A blank screen indicates a successful connection.
Finally, I opened Oracle Enterprise Manager via the database control program shown below using the same SYSTEM account.
And validate that the database was up and the listener was online as shown below.
Summary: Oracle installation on Windows 2008 R2 was pretty straightforward. My lessons learned are to extract both Oracle downloads to the same folder, the default account with access rights is called “SYSTEM” and the default port for Oracle is 1521.
Thank you to my colleague Roger Myers for his Oracle insights, and for my colleagues at the company who provide Oracle monitoring which brought this onto my radar screen. Now to get this database monitored by Operations Manager 2012…