Grid Control 11g: How to Install 11.1.0.1.0 on IBM AIX 6.1 with an 11.1.0.7.0 Repository Database

Goal

This note is intended as a successful use case demonstration for comparison purposes by those trying to

install Enterprise Manager Grid Control 11.1.0.1.0 on IBM AIX 6.1 using an existing remote 11.1.0.7.0

repository database. This demonstration may also represent the actions required and the display

available for other similar certified platforms and database versions.

The sequence of events during installation and the detailed prerequisites are summarized in the

following document, which should be considered the universal reference for Grid Control 11.1.0.1.0

installation:

Oracle Enterprise Manager

Grid Control Basic Installation Guide

11g Release 1 (11.1.0.1.0)

E15838-01

Section 2.1 - 2.2 for overview information

including Table 2-1 Installation Process for Installing Enterprise Manager System

Section 2.3 for full Grid Control 11.1.0.1.0 prerequisites.

Additionally, numerous options to the specific procedure detailed in this document are provided in this

section of the Grid Control Basic Installation Guide, which may allow adaptation of this procedure under

other conditions:

Section 2.4 Installation Procedure

See also this document for detailed background information on the Grid Control architecture:

Oracle Enterprise Manager

Grid Control Advanced Installation and Configuration Guide

11g Release 1 (11.1.0.1.0)

E16847-01

The procedure described here may include alternative or different information (from the published

documentation) where it has been found helpful for the completion of the successful installation on the

specific platform and with the other specific conditions being used.

This same procedure with step-by-step screen shot graphics can be found here.

Solution

A) Prerequisites:

Prerequisites are extensively described in other documents. Listed below is a summary of where to go to

cover all of the prerequisites requirements.

1) See the following references for the detailed prerequisites associated with full installation of Grid

Control 11g using an existing database:

Oracle Enterprise Manager

Grid Control Basic Installation Guide

11g Release 1 (11.1.0.1.0)

E15838-01

Section 2.3 for full Grid Control 11.1.0.1.0 prerequisites.

including Table 2-2 Prerequisites for Installing Enterprise Manager System

including Table 2-3 Setting Fixed Initialization Parameters

including Table 2-4 Setting Variable Initialization Parameters

2) Additional existing database requirements:

a) The following database issues are addressed in Note.1064441.1 Grid Control 11g: Database

Considerations for the Grid Control 11.1.0.1.0 Repository:

- Determine if the repository database listener can support the 11.1.0.1.0 Grid Control installation. This

will help avoid failure in the OMS CA.

- Prepare the DBSNMP user for configuration of any local databases discovered by the local agent after

Grid Control installation is complete.

- Properly size the UNDO tablespace datafile to avoid failing for this inadequacy during Grid Control

installation.

- A 10.2.0.4.0 database will require execution of the dbmspool.sql package for use as a repository

database or failure will be encountered in the Repository Configuration step.

See Note.1068644.1 Example 11.1.0.7.0 Database Installation for Repository Use on OEL 4.7 x86 for a

demonstration of how a database can be installed and configured to avoid Database Control repository

object creation.

3) Additional Hardware Requirements:

See the following reference for details on how to determine the hardware support needed based on

enterprise size:

Oracle® Enterprise Manager Administration

11g Release 1 (11.1.0.1)

Part Number E16790-02

Chapter 9 Sizing Your Enterprise Manager Deployment

4) Environment requirements:

For the full 11.1.0.1.0 Grid Control installation, the user environment should contain no references to

existing Oracle software locations, including TNS_ADMIN, ORACLE_HOME, ORACLE_SID, PATH, etc. All

environment settings will be created by the installer from the information provided in the installation

process.

5) Other Software requirements

An existing WebLogic Server 10.3.2 installation must be available to the Grid Control installer on the

OMS host. This is the only version supported. Its location will be known as the Middleware home. See

the following reference for an example installation of WLS 10.3.2 appropriate for supporting Grid

Control 11.1.0.1.0:

Note.1063112.1 Grid Control 11g: Example for Installing WebLogic Server 10.3.2 on OEL 5.3 x86_64

Note that 64bit platforms will require installation of a supporting jdk, which is not required o 32bit

platforms, like Linux x86 and Windows 32bit.

6) IBM AIX 6.1 Prerequisites

While most prerequisites are generic, certain OS characteristics are required of the IBM AIX 6.1

platform. These OS packages must be available for proper installation and operation of Grid Control

11.1.0.1.0 (as listed by lslpp -l):

bos.adt.base.0.0 bos.adt.lib.0.0 bos.adt.libm.0.0 bos.perf.libperfstat0.0 bos.perf.perfstat0.0 bos.perf.proctools0.0 rsct.basic.rte0.0

rsct.compat.clients.rte0.0 xlC.aix61.rte.9.0.0.0 xlC.rte.9.0.0.0

7) Existing WLS

An existing WebLogic Server installation must be available for deployment of Grid Control and

installation of the associated Oracle Homes.

This home should have the characteristics of a default WLS installation.

8) Database free of sysman, mgmt_view, sysman_mds

Issue this query to verify that the required repository users do not already exist:

select username from dba_users;

While potentially numerous users may be listed, the sysman, mgmt_view and sysman_mds users should

not be listed or else removal efforts will need to be undertaken.

9) Run Smartupdate on the WLS installation

Execute the following to verify a proper patching level for WLS 10.3.2:

.../Middleware/utils/bsu/bsu.sh

After login and a scan of the WLS installation, the Oracle Smart Update window will be presented. Under

the Manage Patches view, the WDJ7 patch should be listed in the Default location.

The version of WLS can also be verified as 10.3.2 in the "Target Installation" expansion tree. Other

versions will not work with the Grid Control installer.

10) Creating the Product Install Stage

The install source can be copied from supplied DVD's or downloaded from Oracle Technology network.

In either case, the install source should be copied to a volume associated with the intended Grid Control

host for the purposes of installation. Installation cannot be performed from the provided DVD's directly.

All install source files should be located in the same directory and extracted in that location starting with

*_1of3.zip and proceeding to *_3of3.zip in sequence. The resulting set of extracted files constitutes the

install stage.

B) Installer Configuration

1) Execute the runInstaller utility from the install stage top level to initiate Grid Control 11.1.0.1.0

installation.

./runInstaller

2) My Oracle Support Details

The first screen is My Oracle Support Details, which allows registration for future security updates,

among other things.

To elect this option, enter the data requested.

If this option is not desired, uncheck the selection box, and verify in the pop-up windows.

Note that installer progress is tracked in the panel to the far left.

Select Next to proceed.

3) Check for Updates

The Check for Updates screen asks the user if updates to the installer should be obtained.

This action is recommended and selected by checking the "Download and install updates from My

Oracle Support" radio button, entering the MOS credentials and selecting the Next option.

Updating makes changes to the installer itself to add valid new prerequisites or to change the installer

action.

A pop-up window will indicate that there are updates to apply and request permission to proceed.

An option to check the connection to My Oracle Support is also offered.

If updates are available, the user will be informed and asked if they should be downloaded.

Select Download Updates to continue with the updating action.

The installer screen will index from this point, whether updates have been elected or not.

4) Select Installation Type

The installation type should be selected from the Select Installation Type screen.

Note that in this version, options for Additional Management Agent and Grid Control with a New

Database are not offered.

Agent installation through a GUI-based OUI is not offered in version 11.1.0.1.0.

The 11.1.0.1.0 Grid Control installer is not equipped for installation of a database as an option.

Select Next after the Installation type is selected.

5) Oracle Inventory

The inventory location and the Operating System Group can be designated on the Oracle Inventory

screen, if Grid Control is the first Oracle product being installed. If an inventory location and default

/etc/oraInst.loc file are already placed, then this screen will not be displayed.

Select Next after the inventory location and OS Group designation have been provided.

6) Check Prerequisites

On the Check Prerequisites page, any noted shortcomings should be resolved before continuing.

It is not uncommon for the OS package requirements to fail, for example.

Highlight the line "Checking for required packages installed on the system" line and select the "more

details" link to get a report on the deficiencies.

The resulting report shows specifically what OS packages are at issue.

All deficiencies should be corrected before proceeding.

Use the Check Again option on the main Check Prerequisites screen when any noted deficiencies have

been corrected to allow the installer to acknowledge.

Note the ulimit requirement of 6144

Treat any other prerequisites failures similarly.

Select Next when all prerequisites have been met.

7) Specify Install Locations

Verify the location of the existing WebLogic Server installation (Middleware location) and the location of

the related Grid Control gc_inst Domain directory.

The default gc_inst location is usually acceptable.

Select Next once verification is complete.

8) Create WebLogic Server Domain

Add passwords for the Domain Server and the Node Manager on the Create WebLogic Server Domain

screen. The default WebLogic User name can be accepted for the Grid Control Installation.

Select Next to proceed.

9) Connect to Oracle Database

The repository database must already exist and the Connect to Oracle Database screen requests the

connection details to this database as the SYS user.

All data except the sys password can be obtained from a "lsnrctl status" output from the database

listener.

This connection will be used to check the database prerequisites after selecting Next to advance the

installer.

10) Configure Oracle Management Repository

The passwords for the SYSMAN and MDS users are determined on the Configure Oracle Management

Repository screen.

Also, the filepath to the desired location for the management tablespaces' datafiles is requested. Often,

these are located in the database's oradata directory.

Select Next once all of the required data has been entered and/or verified.

11) Secure Oracle Management Server

On the Secure Oracle Management Service screen, enter the following:

- Agent registration password (remember for future use)

- Access type for agent to OMS (http/https or https only)

- Access type to console URL (http/https or https only)

Select Next when all determinations are complete.

12) Customize Ports

A summary of the TCP ports automatically selected for the various Grid Control functions is displayed on

the Customize Ports screen.

Changes may be made here, and these altered port values will be verified for availability before the

installer proceeds.

Select Next once the port numbers have been settled.

13) Review

The Review screen allows a final review of install source file, disk use details, Oracle Home locations for

OMS and agent, the product language and the port selections.

Select Install if this configuration is acceptable to begin installation of Grid Control 11.1.0.1.0.

C) Installer Actions

1) Installation Progress Details

The progress of three separate installations will be tracked on the Installation Progress Details screen:

OMS: Installing Oracle Management Service 11g Release 1 (11.1), uses the existing WLS installation to

deploy the Grid Control web application.

Agent: Installing Oracle Management Agent 11g Release 1 (11.1), installs the agent that will monitor the

Grid Control components and hosting node.

HTTP Server: Installing Web tier, establishes the Oracle HTTP Server (based on Apache) that will serve as

the web listener for the Grid Control web application.

The selected locations of these Oracle Homes are listed at the bottom of this screen.

The installer will cycle through each installation, completing file copying, linking and setup as required.

2) Root Actions

At the end of the Installation Phase, the user will be requested to run the allroot.sh script as the root

user. This is a required action and cannot be avoided for proper operation of Grid Control.

Once the script has completed successfully, select OK from the Execute Configuration Scripts popup

window to proceed.

D) Configuration Assistants

1) On acknowledgment of the root script success, the installer will automatically sequence through the

Configuration Assistants:

- OMS Oneoff Patch Application

- Repository Configuration: creates the sysman and mgmt_view users and objects (Grid Control views

and data)

- MDS Schema Configuration: creates the sysman_mds user and objects (WLS customization)

- OCM EM Repository Instrumentation: support for OCM

- OMS Configuration: deploys the Grid Control web application

- Add-on OMS Side Configuration

- Agent Oneoff Patch Application: applies last minute bug patches

- Agent Configuration Assistant: configures, secures and starts the agent

- Agent Add-on Plug-in

2) Repository Configuration

Repository Configuration takes some time with no feedback to the user.

Track the progress by watching the file size growth of these files in sequence:

rcu.log

em_repos_config.log

emrep_config.log

these files are in this directory location:

.../oms11g/sysman/log/schemamanager/m_<date>_<time>_<>/ m_<date>_<time>_<>.CREATE/

The rcu.log will grow first and update again periodically through the CA actions.

The em_repos_config.log will slowly grow very large (approx. 180-240 MB) in one long step.

3) OMS Configuration

The OMS configuration will also require some time, while the Grid Control web application is deployed.

These actions can be tracked in the logs under the .../oms11g/cfgtoollogs/omsca and cfgfw directories,

notably these files:

.../oms11g/cfgtoollogs/omsca/logs<datestamp>/omsca_<datestamp>.log

.../oms11g/cfgtoollogs/cfgfw/CfmLogger_<datestamp>.log

.../oms11g/cfgtoollogs/cfgfw/oracle.sysman.top.oms_<datestamp>.log

On the AIX platforms, failure can be expected in the Add-on OMS Side Configuration action due to an

error in the addonca.pl script.

In order to work around this failure to configure, a change must be made to the

…/oms11g/bin/addonca.pl:

From: $osname = “unix” ;

To: $osname = “AIX”

Once the addonca.pl script is updated with the “AIX” value, execute the configuration manually as follows:

…/oms11g/bin/addonca -oui -name vt -install gc

Once manual addonca.pl configuration has succeeded, select the “Retry” option to allow the installer to

finish the configuration actions.

4) Finish

Completion of the configuration Assistants is signaled by the Finish screen.

Important information is provided here for login to the Grid Control and Admin Server web sites.

Also note the information concerning future additional OMS installation. It is a good idea to record this

information for use later, because it will be needed in the case of additional OMS installation.

Select Close to exit the installer.

Closing the installer session returns the user to the command line session.

Use a carriage return to get back to a command prompt.

E) Functional Checks

1) Agent Status

A status of the agent can provide information about the OMS in addition to information about the agent

itself. upload status, versions, last successful heartbeat and upload all demonstrate effective

communication and data transfer between agent and OMS:

.../agent11g/bin/emctl status agent

2) First Access to Grid Control

Use the URL provided in the Finish window to access the Grid Control web application, which should be

active as the configuration assistants complete.

Use the sysman account for login.

Likewise, the agent will be active and reporting on the Grid Control component targets.

3) Grid Control Initial Target Set

The initial Grid Control All Targets page under the Targets tab shows the various components of the Grid

Control stack.