- Posted by Gavin Soorma
- On April 28, 2010
- 5 Comments
- 11g EM Grid Control, middleware, web logic
Last week on the 23rd of April, Oracle has announced availability of 11g EM Grid Control on the Linux x86 and the Linux x86-64 platforms.
I am attaching a document which has the screen shots of the installation process. There are some differences in the install process as well as prerequisites as compared to the 10g EM Grid Control which I will try to highlight.
Before installing Enterprise Manager Grid Control, we need to install Oracle WebLogic Server 10.3.2. This is available on OTN under the Oracle Fusion Middleware 11g Software Downloads category.
The installation will create a new Web Logic domain called GCDomain and we need to provide the location of the Oracle Middleware Home which was used to install the Web Logic server.
The Oracle Middleware Home will be the location for the Web Logic Server and it’s components, the OMS and the Management Agent as well.
In earlier releases of EM Grid Control, we had the option of using an existing database as the repository database or let the installer create a new database to house the repository. In 11g EM, we do not have that option and we have to provide the connection details of an existing Oracle database.
My Oracle Support note 412431.1 describes the certified Oracle Database which can be used as a database for creating the Grid Control Repository.
In our case we used an 11g Release 2 database, but the following init.ora parameters need to be kept in mind:
log_buffer needs to be minimum 10485760
session_cached_cursors should be 200 or higher
processes should be 500 or higher
open_cursors should be 300 or higher
Also UNDO tablespace needs to be at least 200 MB in size.
The database chosen should also not have any user called SYSMAN or SYSMAN_MDS and if the database had been configured prior with Database Control, then we need to deconfigure it first via the emca -deconfig dbcontrol command.