Learn how to install the Oracle Enterprise Manager Grid Control component on Windows 2003 Server.
In the previous articles, the installation of Oracle Enterprise Manager, the preparation of the database and the installation of the middleware (Oracle WebLogic Server) have been discussed. This article is about installing Grid Control. My Oracle Support (MOSC) Note 1067438.1, Master Note for Grid Control 22.214.171.124 Installation and Upgrade can be used as a starting point, and from there other MOSC Notes for your platform of interest can be referenced for more details. Since my example is based on Windows 2003 Server, the platform specific note is 1091325.1.
An additional prerequisite for setting up the database includes an optional step, which is to apply a patch to fix a few bugs. The database version here is 126.96.36.199, so bugs 9002336 and 9067282 can be fixed. Bug 9002336 (document ID 9002336.8 at the time of this writing) is related to subquery factoring (i.e. using the SQL WITH clause). The solution is to set an undocumented parameter. This parameter can be changed dynamically (no need to bounce the instance).
alter system set “_optimizer_distinct_agg_transform”=true scope=both;
The second bug (Document ID 9067282.8 at the time of this writing) can be resolved by applying one of two patches: the 188.8.131.52.2 patch set update or the 184.108.40.206 patch 2 on Windows platforms (Hotfix 9736835). Since not everyone reading this has access to My Oracle Support, I am opting out of installing the fix for this bug. Indications of hitting this bug are error ORA-00600 (ORA-600 [kksfbc-wrong-kkscsflgs]). Just for a quick overview, you will need OPatch version 11.2 and when updating on Windows, make sure the SID service is stopped as well as the listener service. If all goes well, you will see this at the end:
Verifying the update... Inventory check OK: Patch ID 9736835 is registered in Oracle Home inventory with proper meta-data. Files check OK: Files from Patch ID 9736835 are present in Oracle Home. Execution of 'cmd /C "C:TEMPp9736835_112010_WINNT9736835customscriptspost.bat" (line return added here for formatting) -apply 9736835 ': Return Code = 0 The local system has been patched and can be restarted. OPatch succeeded.
Once the three zipped files for Grid Control have been downloaded, unzip them into the same folder. Files 1_of_3 to 3_of_3 were unpacked in my GridControl_220.127.116.11.0_Win32 folder.
Files unzipped from OTN download
At this point we are ready to run setup.exe. From this point follow section 2.4 of the Grid Control Basic Installation Guide. Since you have already installed Oracle Database 11g, you will be familiar with the new look of Oracle Universal Installer.
For the installation type, you will see the note under creating a new system that the installation is going into a WebLogic server (as a new domain) and will use a database for the repository. To install in a domain, it would also help to have WLS running, which is not explicitly stated anywhere.
In Check prerequisites, you may see warnings regarding hostname and physical memory. Don’t rely on using localhost. My system has 4 GB allocated to Windows in its VM environment. The actual reported value is 4095MB instead of the expected 4096MB. A 1MB difference here is hardly alarming and the 4GB requirement in the installer is double what the installation guide shows.
The installer will display an error dialog window if the parameters were not set correctly. For example:
After correcting the settings (some work with scope=both, a few are scope=spfile, so an instance bounce is required), the next step will prompt you for a password for SYSMAN. You will also see where the three data files are created for the three new tablespaces.
You will definitely want to capture the port numbers shown in the Customize Ports section.
After checking the summary/review page (note the 6GB disk space requirement), the next step is to monitor the installation progress for quite a while.
A series of large green checkmarks at the top middle of the window is a good sign that all is well.
After completing the Management Service, Management Agent, and Web Tier steps, the next part of the installation is similar to what you’ve seen in many other installations or wizards.
Once all configuration tasks are complete, note the URL displayed at the end – this is what you will use to log in to Grid Control.
Failed to install Oracle Enterprise Manager
Oracle Technology Network’s Enterprise Manager forum is full of posts about installation failures. Many messages are related to the OMS configuration step. The best thing that can be said about the overall installation experience is that patience and careful reading of the installation guide is essential. The instructions are pretty clear on using WebLogic Server 10.1.3.2, but for some reason people are trying to use 10.1.3.3. It’s a self-inflicted wound. Believe me, there are many possibilities for errors or problems even when you follow the instructions carefully.
A general overview of the cleanup process is to remove SYSMAN and SYSMAN_MDS schemas, remove tablespaces and MGMT* data files, remove a public synonym (MGMT_AVAILABILITY, and there are hundreds of others, but this one raises a problem during a reinstallation), and to remove or clean several directories (“homes”) under the home middleware (oms11g, agent11g, oracle_common and Oracle_WT). When an operation fails, the installer window dialog text prompts you to check the logs under any directory, and in many cases the logs are useless because they show no errors .
To remove the four “homes” under Middleware, start the installer from the command line and pass the “-deinstall” option. When YES is started in this way, the “Remove” button becomes enabled in the Installed Products window. If you get an error about a directory that already exists in the inventory (and the installer won’t let you continue), find the offending home in the Inventory.xml file and remove the entry (and adjust the position of the index finger if necessary).
A few comments
At this point, it should be painfully obvious that the installation steps or differences between Database Control and Grid Control are quite significant. Configuring and creating Database Control is extremely simple compared to the many steps you need to take to get Grid Control up and running.
Although the degree of difficulty increases a bit, watch what you are exposed to (and learn) in this process:
- Installing Oracle 11g (if not already) and exposure to the new look of Oracle Universal Installer
- Installing WebLogic Server and Using Oracle Smart Update
- Installing Network Control
As mentioned in a previous article, getting a handle on WebLogic Server is going to have a good return on investment. Many Oracle tools and applications now use WebLogic Server. The list includes Grid Control, OBIEE and Application Express (APEX). Virtually everything about “Fusion” will be based on WebLogic Server. Installing Grid Control is a convenient way to get familiar with two of Oracle’s main management tools for databases and everything in between.
» See all articles by columnist Steve Callan