Installing and Configuring Oracle OEM 10g Grid Control on Solaris

Page 1 of 75 Copyrights © 2009 by Sethunath. U

http://oraclechronicle.blogspot.com

Oracle Enterprise Manager Grid Control

Installation and Configuration -----------------------------------------------------------------------------------------------------------------------------------------------------------

Purpose : <Text comes here >

Date : 18-JUN-2009

Status : Draft

Author : Sethunath.U

File : Oracle_OEM10g_Grid_Control_Solaris.doc

Pages : 75

Classification: Technology Guidelines

18-JUN-2009

Page 2 of 75 http://oraclechronicle.com Copyrights © 2009 by Sethunath. U


Installation and Configuration

History

Version Date Author Remark

0.1 25-JUN-2009 Sethunath.U First Draft

References

1. Oracle® Enterprise Manager Grid Control Quick Installation Guide for Solaris (SPARC) 10g Release 2 (10.2) - b31198

2. oracle.ittoolbox.com-Workaround for ''Management Services and Repository' Target is Temporarily in Status Pending State'

3. Metalink Notes 418199.1, 419886.1, 734981.1, 303359.1

4. http://www.oracle.com/corporate/pricing/technology-price-list.pdf

5. http://www.oracle.com/technology/documentation/oem.html

6. http://www.oracle.com/technology/obe/fusion_middleware/wls103/InstallConfig/install_wls/Install_WLS.htm

18-JUN-2009




Table of Contents

1 Introduction ................................................................................................................ 9

2 Purpose ...................................................................................................................... 9

3 Disclaimer .................................................................................................................. 9

4 The environment ........................................................................................................ 9

5 System Requirements ............................................................................................. 10

5.1 Hardware requirements ................................................................................................. 10

5.2 Software requirements ................................................................................................... 10

5.2.1 Operating System Requirements ...................................................................................................... 10

5.2.2 Packages Requirements ................................................................................................................... 11

5.2.3 Checking for 32-bit and 64-bit Application Support .......................................................................... 11

5.2.4 Kernel parameter requirements ........................................................................................................ 12

6 Download and extract product installation binaries ............................................. 13

7 Installing Oracle Enterprise Manager Grid Control 10.2.0.1 ................................ 13

7.1 Start oracle Universal Installer ...................................................................................... 14

7.2 Specify installation location............................................................................................... 14

7.3 Specify inventory directory and location............................................................................ 15

7.4 Product specific pre-requisite checks ............................................................................... 16

7.5 Specify configuration ........................................................................................................ 17

7.6 Specify optional configuration ........................................................................................... 18

7.7 Specify security option ...................................................................................................... 18

7.8 Summary of installation options selected .......................................................................... 19

7.9 The installation ................................................................................................................. 20

18-JUN-2009




7.10 Execute configuration scripts ............................................................................................ 20

7.11 Configuration Assistants ................................................................................................... 24

7.12 End of installation ............................................................................................................. 25

8 Installing grid control agent.................................................................................... 25

8.1 Start OUI .......................................................................................................................... 26

8.2 Specify agent installation location ..................................................................................... 26

8.3 Product specific checks for agent installation ................................................................... 27

8.4 Specify oracle management Service Location .................................................................. 27

8.5 Specify agent registration password ................................................................................. 28

8.6 Oracle Configuration Manager Registration ...................................................................... 28

8.6.1 Connection settings for OCM ............................................................................................................ 29

8.7 Installation progress ......................................................................................................... 29

8.7.1 Execute configuration scripts ............................................................................................................ 30

8.8 End of Agent Installation ................................................................................................... 30

8.9 Adding a target in grid control ........................................................................................... 31

8.9.1 Login to EM Grid Control................................................................................................................... 31

8.9.2 Search target host ............................................................................................................................. 31

9 Upgrading OEM Grid Control to 10205 .................................................................. 32

9.1 Pre-installation Tasks ....................................................................................................... 32

9.2 Upgrade Tasks ................................................................................................................. 37

9.2.1 Unzip the files .................................................................................................................................... 37

9.2.2 Upgrading the Oracle Management Service ..................................................................................... 38

9.2.3 Upgrading the Oracle Management Agent ....................................................................................... 45

10 OEM Grid Control Features - Overview .............................................................. 49

10.1 The Grid Control Framework ............................................................................................ 49

10.1.1 Management Console ....................................................................................................................... 49

18-JUN-2009




10.1.2 Management Service ........................................................................................................................ 50

10.1.3 Management agent ........................................................................................................................... 50

10.2 Features of Grid Control ................................................................................................... 50

10.2.1 Scalability .......................................................................................................................................... 50

10.2.2 Consolidated management ............................................................................................................... 51

10.2.3 Logical grouping of targets ................................................................................................................ 51

10.2.4 Automation of tasks ........................................................................................................................... 51

10.2.5 System monitoring and diagnosis ..................................................................................................... 51

10.3 Configuring Grid Control ................................................................................................... 51

10.3.1 The grid Control Home Page ............................................................................................................ 52

10.3.2 Management pack configuration ....................................................................................................... 52

10.3.3 Notification Methods .......................................................................................................................... 53

10.3.4 E-mail addresses and schedules ...................................................................................................... 54

10.3.5 Configuring preferred credentials for monitored targets ................................................................... 58

10.3.6 Configuring Notification Rules ........................................................................................................... 59

10.3.7 Adding a Middleware Target (WebLogic Server Domain) ................................................................ 62

11 Licensing ............................................................................................................... 67

11.1 Database Management Packs .......................................................................................... 67

11.1.1 Database Diagnostics Pack .............................................................................................................. 67

11.2 System Monitoring Plugins ............................................................................................... 68

11.3 Diagnostics pack for Oracle Middleware ........................................................................... 69

11.4 The Prices ........................................................................................................................ 70

12 Exception / Justification and Corrective Action Instructions ........................... 70

12.1 Exception Number - 1 ....................................................................................................... 70

12.1.2 Exception Number - 2 ....................................................................................................................... 72

I. Appendix 1: Sample Licensing Worksheet .......................................................................... 75

II. Appendix 2 Oracle 10g Grid Control management packs Licensing information................... 75

18-JUN-2009




Table of Figures

Figure 1: Start Oracle Universal Installer ....................................................................................................... 14

Figure 2: Specify Installation Location ........................................................................................................... 14

Figure 3: Specify Inventory directory and Location ........................................................................................ 15

Figure 4: product specific pre-requisite checks.............................................................................................. 16

Figure 5: Specify configuration....................................................................................................................... 17

Figure 6: Specify optional configuration ......................................................................................................... 18

Figure 7: Specify security option .................................................................................................................... 18

Figure 8: Summary of installation options selected ....................................................................................... 19

Figure 9: Installation screen ........................................................................................................................... 20

Figure 10: Execute configuration scripts ........................................................................................................ 20

Figure 11: DB Configuration Assistant ........................................................................................................... 24

Figure 12: Grid control Configuration Assistants .......................................................................................... 24

Figure 13: End of installation.......................................................................................................................... 25

Figure 14: Starting Agent installation ............................................................................................................. 26

Figure 15: Specify agent installation location ................................................................................................. 26

Figure 16: product specific checks for Agent installation ............................................................................... 27

Figure 17: Specify Oracle Management Service Location ............................................................................. 27

Figure 18: Specify agent registration password ............................................................................................. 28

Figure 19: Specify OCM registration .............................................................................................................. 28

Figure 20: Specify connection settings .......................................................................................................... 29

Figure 21: Agent installation progress ........................................................................................................... 29

Figure 21: Execute root.sh for agent installation ........................................................................................... 30

Figure 23: End of agent installation ............................................................................................................... 30

Figure 24: Grid control login ........................................................................................................................... 31

Figure 25: Search and find target .................................................................................................................. 31

Figure 26: Added target and it’s details ......................................................................................................... 32

Figure 27: Added targets and it’s details ........................................................................................................ 32

Figure 28: Specify Home Details (OMS Upgrade) ......................................................................................... 39

Figure 29: Provide Metalink Credentials (OMS Upgrade) ............................................................................. 40

Figure 30: Product Specific Checks (OMS Upgrade) .................................................................................... 40

Figure 31: Provide Repository Administrator Password(OMS Upgrade) ....................................................... 41

Figure 32: Provide Application Instance Password(OMS Upgrade) .............................................................. 41

18-JUN-2009




Figure 33: Installation Options Summary (OMS Upgrade) ............................................................................ 42

Figure 34: Installation Progress (OMS Upgrade) ........................................................................................... 42

Figure 35: Execute Configuration Scripts (OMS Upgrade) ............................................................................ 43

Figure 36: Configuration Assistants (OMS Upgrade) .................................................................................... 43

Figure 37: End of Upgrade (OMS Upgrade) .................................................................................................. 44

Figure 38: Specify Oracle Management Agent Home (OM Agent Upgrade) ................................................. 45

Figure 39: Provide Metalink Credentials (OM Agent Upgrade) ..................................................................... 46

Figure 40: Product Specific Prerequisite Checks (OM Agent Upgrade) ........................................................ 46

Figure 41: Summary of Upgrade (OM Agent Upgrade) ................................................................................. 47

Figure 42: Upgrade Progress (OM Agent Upgrade) ...................................................................................... 47

Figure 43: Configuration Assistants (OM Agent Upgrade) ............................................................................ 48

Figure 44: Execute root.sh (OM Agent Upgrade) .......................................................................................... 48

Figure 45: End of Upgrade (OM Agent Upgrade) .......................................................................................... 49

Figure 46: Grid Control Management Console .............................................................................................. 50

Figure 47: The Grid Control Home Page ....................................................................................................... 52

Figure 48: Management Pack Access ........................................................................................................... 53

Figure 49: Notification Methods ..................................................................................................................... 54

Figure 50: Email addresses ........................................................................................................................... 55

Figure 51: Notification Schedule .................................................................................................................... 56

Figure 52: Edit Notification Schedule definition ............................................................................................. 56

Figure 53: Edit Notification Schedule definition: Email Addresses ................................................................ 57

Figure 54: Edit Notification Schedule definition: Select Email Addresses ..................................................... 57

Figure 55: Preferred credentials .................................................................................................................... 58

Figure 56: Database Preferred credentials .................................................................................................... 58

Figure 57: Notification Rules .......................................................................................................................... 59

Figure 58: Notification Rule Details ................................................................................................................ 60

Figure 59: Selecting and Editing a Notification Rule ...................................................................................... 60

Figure 60 Creating a Notification Rule ........................................................................................................... 61

Figure 61 Changing Notification Rule Applicationt o specific targets ............................................................ 61

Figure 62 Set Actions ..................................................................................................................................... 62

Figure 63 Start Adding Middleware Target .................................................................................................... 63

Figure 64 Provide Weblogic Management Server Credentials ..................................................................... 64

Figure 65 Provide Host Logon Credentials .................................................................................................... 64

Figure 66 Select Managed Server ................................................................................................................. 65

18-JUN-2009




Figure 67 Review and Finish Weblogic Server Domain Discovery................................................................ 66

Figure 68 The middleware targets console .................................................................................................... 66

Figure 69 Database Management Pack ........................................................................................................ 67

Figure 70 System Monitoring Plugins ............................................................................................................ 68

Figure 71 Weblogic Managed Server Packs .................................................................................................. 69

List of Tables

Table 1: Certification Matrix – OMS and Agent Vs Weblogic ........................................................................ 62

Table 2: Management Pack Price List ........................................................................................................... 70

18-JUN-2009




1 Introduction

The Oracle Grid offers a proven solution that allows businesses to heighten application

performance and deliver unparalleled IT infrastructure reliability. Businesses of all sizes attain

measurable IT cost savings by extending the availability of computing resources, cultivating more

productive and effective administrators, and achieving higher quality of service—all direct benefits

of the Oracle Grid. A critical ingredient to achieving the full benefits of the Oracle Grid is

employing the right solution for managing the grid systems and, most importantly, the applications

that run on those systems.

Oracle Enterprise Manager 10g is Oracle's single, integrated solution for managing all aspects of

the Oracle Grid and the applications running on it. Grid Control couples a potent, top-down

monitoring approach to delivering the highest quality of service for applications with a cost-

effective automated configuration management, provisioning, and administration solution. This

powerful combination provides unequaled management for any size Oracle data center.

2 Purpose

This document describes how to quickly install and configure Oracle Enterprise Manager Grid

Control on Solaris (SPARC) systems.

3 Disclaimer

You may use this document on your on responsibility and the author of this document is not

responsible for any damage that are caused by the actions described in this document. Though

the steps described in this document has strictly followed oracle documentation, it reflects the

author’s point of view and NOT Oracle Corporation’s . This document is not certified by Oracle.

Use this document at the user’s discretion and risk.

Oracle ™, Solaris ™, Sun ™ are registered trademarks of Oracle Corporation and Sun Micro

Systems respectively. All other trademarks are registered trademarks of the corresponding

organizations.

Author is not responsible for any legal issues associated with the actions described in this

document. This is strictly a technology guide and freely accessible service document open for all

interested parties.

If you copy the contents of this document elsewhere make sure to keep the trademarks,

copyrights, references and credits described in this document.

4 The environment

The environment used in this document is

Server : Sun Fire V245 (Sparc)

OS : Solaris 10

18-JUN-2009




5 System Requirements

The system or systems must meet the minimum hardware and software requirements given in the

following sections. Even though Oracle Universal Installer runs prerequisite checks on your

system to verify that it meets the listed requirements, to make sure that prerequisite checks do not

fail, you should verify the requirements before running Oracle Universal Installer.

5.1 Hardware requirements

The system or systems must meet the minimum hardware requirements for hard disk space,

available memory, processor speed, and operating memory.

Hard Disk Space Requirements The hard disk requirements are:

• 4.5 GB for the "Enterprise Manager Grid Control Using a New database" installation type

• 2.5 GB for the "Enterprise Manager Grid Control Using an Existing Database" installation

type

Available Memory Requirements

The available operating memory requirements for installation are:

• To install "Enterprise Manager Grid Control Using a New Database," a minimum of 1 GB

of available operating memory for the host [The option used in this installation]

• To install "Enterprise Manager Grid Control Using an Existing Database," a minimum of 1

GB of available operating memory for the node

The hardware requirements to run Enterprise Manager are:

• Minimum of 2 GB of free physical memory for the host running the Management Service

• Minimum of 2 GB of free physical memory for the Management Repository node

5.2 Software requirements

The system or systems must meet the minimum software requirements for operating system,

packages, and kernel parameters.

5.2.1 Operating System Requirements

Operating System Requirements The operating system must be one of the following, with the

listed (or later) kernel version if you are installing the new database:

Solaris 8 Update 7 or later

Solaris 9 Update 6 or later

Solaris 10 [The option used in this installation]

18-JUN-2009




5.2.2 Packages Requirements

The system must be running the following (or later) package versions:

SUNWarc

SUNWbtool

SUNWhea

SUNWlibm

SUNWlibms

SUNWsprot

SUNWsprox

SUNWtoo

SUNWi1of

SUNWxwfnt

bash-3.00# pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt

system SUNWarc Lint Libraries (usr)

system SUNWbtool CCS tools bundled with SunOS

system SUNWhea SunOS Header Files

system SUNWi1of ISO-8859-1 (Latin-1) Optional Fonts

system SUNWlibm Math & Microtasking Library Headers & Lint Files (Usr)

system SUNWlibms Math & Microtasking Libraries (Usr)

system SUNWsprot Solaris Bundled tools

system SUNWtoo Programming Tools

system SUNWxwfnt X Window System platform required fonts

ERROR: information for "SUNWsprox" was not found

Note : In Solaris 10 you may ignore this

5.2.3 Checking for 32-bit and 64-bit Application Support

bash-3.00# /usr/bin/isainfo -v

64-bit sparcv9 applications

vis2 vis

32-bit sparc applications

vis2 vis v8plus div32 mul32

18-JUN-2009




5.2.4 Kernel parameter requirements

Kernel Parameters for Solaris 10

Set the values in /etc/system

set semsys:seminfo_semmni=100

set semsys:seminfo_semmsl=256

set shmsys:shminfo_shmmax=4294967295

set shmsys:shminfo_shmmni=100

1. Make a project named "user.oracle" in /etc/project with the user oracle as it's only member. (If it does not exist)

bash-3.00# projadd -U oracle -K \

> "project.max-shm-memory=(priv,4096MB,deny)" user.oracle

2. Verify it

# cat /etc/project

system:0::::

user.root:1::::

noproject:2::::

default:3::::

group.staff:10::::

user.oracle:100::oracle::project.max-shm-memory

=(priv,4294967296,deny)

bash-3.00# cat /etc/project

system:0::::

user.root:1::::

noproject:2::::

default:3::::

group.staff:10::::

user.oracle:100::oracle::project.max-shm-memory=(priv,4294967296,deny)

bash-3.00# projmod -s -K "project.max-sem-ids=(priv,256,deny)" \

> user.oracle

Check the Paramters as User oracle

$ prctl -i project user.oracle

bash-3.00# id -p

18-JUN-2009




uid=0(root) gid=0(root) projid=1(user.root)

bash-3.00# prctl -n project.max-shm-memory -i project user.root

project: 1: user.root

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

project.max-shm-memory

privileged 1.46GB - deny -

system 16.0EB max deny -

bash-3.00# prctl -n project.max-sem-ids -i project user.root

project: 1: user.root

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

project.max-sem-ids

privileged 128 - deny -

system 16.8M max deny

3.

4.

6 Download and extract product installation binaries

Download the complete files from oracle.com

Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1)

for Solaris Operating System (SPARC)

Sol_Grid_Control_full_102010_disk1.zip (470,575,730 bytes) (cksum - 3364605454)




Directions

1. All files are in the .zip format. There is an unzip utility for this platform here if you need one.

2. Download all the zip files and unzip them into a same directory.

Unzip all the three files in a single directory otherwise after initiating the installation you will receive an error

message "OUI-10133: Invalid Staging Area. There Area No Top Level Components". (Metalink Note ID

395030.1).

7 Installing Oracle Enterprise Manager Grid Control 10.2.0.1

Once the hardware and software requirements have been met to configure the system, start

Oracle Universal Installer (OUI) and install Grid Control as follows

18-JUN-2009




7.1 Start oracle Universal Installer

bash-3.00$ cd /data1/oracle/dvd

bash-3.00$ ./ runInstaller

Figure 1: Start Oracle Universal Installer

Select one of the installation types provided. The complete installation type is chosen by default.

7.2 Specify installation location

Figure 2: Specify Installation Location

18-JUN-2009




Specify the "parent" directory location for the installation. All Oracle homes created during installation will

be placed as subdirectories under the parent directory.

7.3 Specify inventory directory and location

Figure 3: Specify Inventory directory and Location

Appears only during the first installation of Oracle products on a system. Specify the full path of the Oracle

Inventory directory. Make sure to select the appropriate operating group.

18-JUN-2009




7.4 Product specific pre-requisite checks

Figure 4: product specific pre-requisite checks

Verify that all prerequisite checks succeed. OUI checks the system to verify that it is configured correctly

to support your Oracle software. If you have met all hardware and software requirements in this guide, all

of the checks should pass. If a check fails, review the cause of failure, rectify the problem, and retry the

check. You can also choose to manually verify failed checks if you are satisfied that your system meets the

requirements.

18-JUN-2009




7.5 Specify configuration

Figure 5: Specify configuration

Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.

Specify the name of the database you want to create, as well as the location to store the

Management Repository files. Choose a file location outside of the Oracle home. Select the

OSDBA and OSOPER groups that you are a member of. These memberships are required to

grant the SYSDBA and SYSOPER privileges required to create the new database.

18-JUN-2009




7.6 Specify optional configuration

Figure 6: Specify optional configuration

All parameters can be configured through Grid Control after installation. If you want, set the parameters

for email notification, OracleMetaLink credentials, and proxy configuration settings.

7.7 Specify security option

Figure 7: Specify security option

18-JUN-2009




Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.

Specify password used to secure the Management Service, as well as passwords to secure the

Management Repository Database. The first password will be asked during agent installation .

Reference Link : 8.5 Specify agent registration password

7.8 Summary of installation options selected

Figure 8: Summary of installation options selected

Review the information displayed here, then click Install.

18-JUN-2009




7.9 The installation

Figure 9: Installation screen

This screen displays status information while the product is being installed.

7.10 Execute configuration scripts

Figure 10: Execute configuration scripts

18-JUN-2009




When prompted, read the instructions and run the scripts listed here. You must run the scripts as root

from a terminal window.

Login as root and run the above two scripts. The output will be as follows.

# /data2/oracle/oraInventory/orainstRoot.sh

cp: cannot create /var/opt/oracle/oraInst.loc: No such file or directory

Changing permissions of /data2/oracle/oraInventory to 770.

Changing groupname of /data2/oracle/oraInventory to oinstall.

The execution of the script is complete

# /data2/oracle/OracleHomes/db10g/allroot.sh

-e

Starting to execute allroot.sh .........

Starting to execute /data2/oracle/OracleHomes/db10g/root.sh ......

Running Oracle10 root.sh script...

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /data2/oracle/OracleHomes/db10g

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:

Creating /var/opt/oracle/oratab file...

Adding entry to /var/opt/oracle/oratab file...

Entries will be added to the /var/opt/oracle/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

Oracle Cluster Registry for cluster has been initialized

18-JUN-2009




Adding to inittab

Startup will be queued to init within 30 seconds.

Checking the status of Oracle init process...

Expecting the CRS daemons to be up within 600 seconds.

CSS is active on these nodes.

dcser04

CSS is active on all nodes.

Oracle CSS service is installed and running under init(1M)

Finished execution of /data2/oracle/OracleHomes/db10g/root.sh ......

Starting to execute /data2/oracle/OracleHomes/oms10g/root.sh ......




ORACLE_HOME= /data2/oracle/OracleHomes/oms10g





Adding entry to /var/opt/oracle/oratab file...





chmod: WARNING: /data2/oracle/OracleHomes/oms10g/bin/emtgtctl2: Corresponding set-ID also disabled on file since

set-ID requires execute permission

Finished execution of /data2/oracle/OracleHomes/oms10g/root.sh ......

18-JUN-2009




Starting to execute /data2/oracle/OracleHomes/agent10g/root.sh ......




ORACLE_HOME= /data2/oracle/OracleHomes/agent10g









Finished product-specific root actions.

Finished execution of /data2/oracle/OracleHomes/agent10g/root.sh ......

#

18-JUN-2009




7.11 Configuration Assistants

Figure 11: DB Configuration Assistant

Figure 12: Grid control Configuration Assistants

Displays status information for configuration assistants

18-JUN-2009




7.12 End of installation

Figure 13: End of installation

Contains important information about your installation, including the URLs configured for your

applications. Make a note of these URLs. The port numbers used in these URLs are recorded in the

following file: $ORACLE_HOME/install/portlist.ini

Note : At the end of the instllation one configuration assistant was failed with error

'oracle.sysman.emcp.agent.AgentPlugIn has failed'. A work around has been implemented to solve this

issue, which is detailed under section Exception Number - 1

8 Installing grid control agent

To attach a database server or application server to the OEM grid control, an agent should be

installed in each host targets.This agent installation assumes you are using a doing an

installation on a Linux machine which already has a an Oracle 10.2.0.3 database .As such there

are no prerequisites as they should match those of the original product installation.

Unzip the agent installation and patch set:

[oracle@N6947 grid_agent]$ unzip Linux_Grid_Control_agent_download_10_2_0_3_0.zip

Make an appropriate directory for the agent software to be loaded into, like:

[oracle@N6947 grid_agent]$ mkdir /data/oracle/emagent

18-JUN-2009




Set the display

[oracle@N6947 grid_agent] DISPLAY=192.168.6.149:0.0

[oracle@N6947 grid_agent] export DISPLAY

8.1 Start OUI

Start the Oracle Universal Installer (OUI) by issuing the following command in the “./linux/agent"

directory:

[oracle@N6947 agent]$ ./runInstaller

Figure 14: Starting Agent installation

8.2 Specify agent installation location

Figure 15: Specify agent installation location

18-JUN-2009




8.3 Product specific checks for agent installation

Figure 16: product specific checks for Agent installation

8.4 Specify oracle management Service Location

Figure 17: Specify Oracle Management Service Location

Enter the name of grid control server followed by port number. Make sure your grid control server up and

running and the server is reachable from the monitored host target (her the Linux box where the agent is

being installed)

18-JUN-2009




8.5 Specify agent registration password

Figure 18: Specify agent registration password

This is the password you entered during Grid Control server setup. Reference Link 7.7 Specify security

option

8.6 Oracle Configuration Manager Registration

Figure 19: Specify OCM registration

Enter the Oracle CSI number and metalink account name if you want to enable oracle configuration

manager.

18-JUN-2009




8.6.1 Connection settings for OCM

Figure 20: Specify connection settings

8.7 Installation progress

Figure 21: Agent installation progress

18-JUN-2009




8.7.1 Execute configuration scripts

Figure 22: Execute root.sh for agent installation

8.8 End of Agent Installation

Figure 23: End of agent installation

18-JUN-2009




8.9 Adding a target in grid control

After installing agent in the specified targets, we need to discover and add those targets in grid

control. For that, login to grid control server as super user (sysman)

8.9.1 Login to EM Grid Control

Figure 24: Grid control login

8.9.2 Search target host

Click in (Targets) tab and enter the host name where the agent had been installed,

up and running.

Figure 25: Search and find target

18-JUN-2009




Figure 26: Added target and it’s details

Figure 27: Added targets and it’s details

This will display the specified target and it’s details as above.

9 Upgrading OEM Grid Control to 10205

9.1 Pre-installation Tasks

The following are the general pre-installation tasks.

1. Oracle recommends that you back up the Oracle home that will be upgraded using this

patch set. In the case of a Management Repository, Oracle recommends that you back up

the repository database before applying the patch set because the patch set makes

changes to the repository that cannot be rolled back. Also, back up the Oracle Inventory

directory.

18-JUN-2009




a. Backup $AGENT_HOME,$OMS_HOME,$DB_HOME

b. Backup Database (Cold backup)

c. Backup Inventory directory

2. Make sure that you meet the product pre-requisites (operating system patches, packages

etc.) for the 10.2.0.5 patch set. For information about platform-specific package and kernel

requirements, refer to the Enterprise Manager Grid Control Installation and Basic

Configuration Guide.

3. Before upgrading your Oracle Management Service, ensure that the shared pool size is

set in your Grid Control repository database as per your infrastructure. Minimum size for

shared pool is 512 MB. For information about the fixed initialization parameter values,

refer to the pre-installation requirements described in the Enterprise Manager Grid Control

Installation and Basic Configuration Guide.

4. Be sure that the partitioning option is enabled in the database that contains the Grid

Control repository (Sysman schema) . Connect to the Database as sysdba and run the

following query to determine whether the Partitioning Option is installed:

SQL> select value from v$option where parameter ='Partitioning';

The preceding query should result in VALUE=TRUE.

5. Both the DBSNMP and SYSMAN users require the EXECUTE privilege on the

DBMS_RANDOM package in the Repository Database. You must grant the privilege to

both users as follows:

a. Log into the Repository Database as SYSDBA.

b. Run the following SQL commands:

SQL> grant execute on dbms_random to dbsnmp;

SQL> grant execute on dbms_random to sysman;

c. Verify that the query below does not return any invalid objects:

SQL> select object_name, object_type, owner from dba_objects where status='INVALID';

6. If the repository database is configured with the UTF8 character set, the value of

NLS_LENGTH_SEMANTICS needs to be set to BYTE. To check this in the database, run

the following command :

18-JUN-2009




SQL> SELECT value FROM nls_database_parameters WHERE

parameter='NLS_LENGTH_SEMANTICS';

If the value is not set to BYTE, change it by running the following command:

SQL> ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=BYTE SCOPE=both;

7. Login in the Database as Sysman and remove the following job:

SQL> SELECT job FROM user_jobs WHERE what=

'MGMT_CNTR_TT.clean_up_old_ticket_recs';

If the above query returns the job id then run the following command to remove it:

SQL> exec dbms_job.remove(<that job id>);

SQL> COMMIT;

8. If the database containing the Grid Control repository is linked with a Data Guard

database, the database must be forced in logging mode before the upgrade starts to force

all index maintenance commands to be propagated to the standby database. The upgrade

by default will perform the index maintenance commands in a 'NOLOGGING' mode. This

means that any Data Guard database linked to the repository database will not have these

index operations replicated to it.

To make sure these commands get replicated to the Data Guard instance, force the

database into logging mode:

SQL> CONNECT / AS SYSDBA;

SQL> ALTER DATABASE FORCE LOGGING;

Once the OMS upgrade is successful then revert the Data Guard force logging changes:

SQL> CONNECT / AS SYSDBA;

SQL> ALTER DATABASE NO FORCE LOGGING

9. If your Enterprise Manager is shut down for a long period of time, you must follow the

below steps before conducting the upgrade:

a. Log into the Repository Database as SYSMAN

b. Run the following SQL:

SQL> exec emd_maintenance.analyze_emd_schema('SYSMAN');

c. Start the Oracle management service

18-JUN-2009




10. Make sure that there are no invalid sysman objects present in your Grid Control repository.

Important: Oracle recommends that you back up your database before you perform the

upgrade operation. Perform the following steps before upgrading:

a. Login into the Database as SYS user.

b. Check if there are any invalid SYSMAN objects.

SQL> select object_name, object_type from all_objects where owner='SYSMAN' and

status <> 'VALID';

The above query should return 0 rows. If there are rows, then run the below SQL

statement:

SQL> @admin_recompile_invalid.sql SYSMAN

The admin_recompile_invalid.sql script is available under

$OMS_HOME/sysman/admin/emdrep/sql/core/latest/admin/

Where $OMS_HOME is the Oracle home directory of the Oracle Management Service

(OMS).

c. Go to step b again to be sure all SYSMAN objects are valid. If you still have invalid

SYSMAN objects that are not in the Recycle bin, contact Oracle support.

d. Check to be sure there is no invalid SYS object:

SQL> select object_name, object_type from all_objects where status<>'VALID' and

object_name like 'DBMS%';

The above query should return 0 rows. If there are rows, then try to "recompile" them. For

example:

if the object_type = "PACKAGE" and object_name = "foo"

alter package foo compile;

if the object_type = "PACKAGE BODY" and object_name ="foo"

alter package foo compile body;

e. If any of the packages fail to become valid even after recompilation, then Contact Oracle

Support to assist you. Once this verification is done, continue through with the rest of the

pre-installation tasks.

11. If the 10.1.0.5.0 database containing the Grid Control repository does not have the CPU

Jan 2008 patch 6826532 applied, then make sure that you apply this patch. If you have

applied the latest CPU Jan 2009 patch 7592360 on your database containing the Grid

Control repository, then you do not need to apply the old CPU Jan 2008 patch 6826532.

18-JUN-2009




12. If you have applied the latest CPU Jan 2009 patch 7608318 to your Oracle Management

Service (OMS) before upgrading, then make sure that permission of the following files

under the Oracle home directory of OMS <ORACLE_HOME>/rdbms/admin is set to 664.

(dbmsaqds.plb,dbmsaw.plb,prvtlmd.plb,prvtpexp.plb,prvtlsby.plb,prvtlms.plb,prvtaqip.plb,p

rvtstas.plb,prvtsqlt.plb,prvttxfm.plb,prvtaqdi.plb,prvtaqds.plb,prvtcdpu.plb,prvtcdpi.plb,prvt

meti.plb,prvtxdbz.plb,exfeapvs.plb,prvtdupg.plb,prvtupgi.plb,prvtkupc.plb,prvtbpw.plb,prvta

qiu.plb,prvtaqim.plb,prvtbsqu.plb,prvtbut4.plb,prvtmetu.plb,prvtmeta.plb,prvtcdcp.plb,prvtc

dcu.plb)

If the permission is not set to 664 for the above files, you will get a permission denied error

during the upgrade.

For example: Error in writing to file

'/u01/app/oracle/product/10.2.0/oms10g/rdbms/admin/dbmsaw.plb' Permission denied

13. Before proceeding with the upgrade, make sure that the dbms jobs are stopped. To do

this, follow these steps:

a. Login into the Database as SYSMAN.

b. Run the following SQL command:

SQL> execute emd_maintenance.remove_em_dbms_jobs;

SQL>commit;

c. Stop the Grid Control Repository Database.

d. d. Start the Grid Control Repository Database.

14. Make sure DBMS JOBS and DBMS Scheduler (for version 10.1+ RDBMS) in the

Enterprise Manager Grid Control Repository are turned off during the Enterprise Manager

schema upgrade process. To perform this task, follow these steps:

a. Log into the repository as SYSMAN.

b. For each instance, perform the tasks below:

1. Write down the values of job_queue_processes for each of the instances after you run the

following command:

SQL> select a.instance_name as sid, b.value as jobqueue from gv$instance a, gv$parameter b

where a.inst_id = b.inst_id and b.name='job_queue_processes';

2. Turn off DBMS JOBS by running the following command:

SQL> alter system set job_queue_processes=0 sid='*';

Be sure there were no active jobs running by waiting until the following query returns 0:

18-JUN-2009




SQL> select count(*) from dba_jobs_running;

3. Turn off the DBMS Scheduler by running (for version 10.1+ RDBMS) by the following

command:

SQL> exec dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','TRUE');

Be sure there were no active schedules running by waiting until the

following query returns 0 (for version 10.1+ RDBMS):

SQL> select count(*) from dba_scheduler_running_jobs where SLAVE_PROCESS_ID IS NOT

NULL;

9.2 Upgrade Tasks

Upgrading any existing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.x) or

higher to Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)

Make sure that you follow the Pre-installation steps described in the above section 9.1 Pre-

installation Tasks before upgrading any existing Oracle Enterprise Manager 10g Grid Control

Release 2 (10.2.0.x) or higher to Oracle Enterprise Manager 10g Grid Control Release 5

(10.2.0.5)

Note: Make sure that you first upgrade the Oracle Management Service (OMS), and then the

Management Agent before upgrading the database that contains the Management repository

(sysman schema).

9.2.1 Unzip the files

Unzip gc_10205_1of2.zip and gc_10205_2of2.zip.

Enter the following command to unzip and extract the installation files from the downloaded

software.

$ unzip gc_10205_1of2.zip

$ unzip gc_10205_2of2.zip

This will extract 3731593_10205_SOLARIS64.zip,3731596.zip,3822442.zip and

p3731593_10205_SOLARIS64.zip to the directory.

$ unzip p3731593_10205_SOLARIS64.zip.

This extracts the files to the "3731593" directory.

18-JUN-2009




9.2.2 Upgrading the Oracle Management Service

The pre-installation tasks can be broadly categorized based on the following types of upgrade that

you can perform:

• Upgrading First Oracle Management Service and repository

• Upgrading Additional Oracle Management Services

• Upgrading Management Agent

The steps to be taken before upgrading the first OMS are:

• While applying the OMS patch set, leave the repository database and listener instance

running.

• Make sure that you follow all the pre-installation tasks as mentioned in the Section 9.1

Pre-installation Tasks before going ahead with upgrade process.

• Shut down all OMS instances attached to the Grid Control repository, from the respective

Oracle homes in their respective hosts. Also stop the Application Server components that

run in each Oracle home directory of the Oracle Management Service (OMS).

To stop all the Grid Control components on a host, follow these steps:

1. Stop the Oracle Management Service (OMS) by running the following command from the

Oracle home directory of the OMS, where $ORACLE_HOME is the Oracle home directory

of the Oracle Management Service:

bash-3.00# $OMS_HOME/bin/emctl stop oms

2. Stop the Application Server Control Console, which is used to manage the Oracle

Application Server instance used to deploy the Management Service:

bash-3.00# $OMS_HOME/bin/emctl stop iasconsole

3. Stop all the application server components, such as Oracle HTTP Server and OracleAS

Web Cache by running the following command from the Oracle home directory of the

OMS.

bash-3.00# $OMS_HOME/opmn/bin/opmnctl stopall

4. Wait four to five minutes to ensure that all the OPMN processes are stopped and TCP

ports are released.

18-JUN-2009




5. Set the Oracle_Home to your Oracle home directory of the Oracle Management Services

before applying the patch set. Set the display as well.

bash-3.00# ORACLE_HOME=/data2/oracle/OracleHomes/oms10g

bash-3.00# export $ORACLE_HOME

bash-3.00# DISPLAY=192.168.6.149:0.0

bash-3.00# export DISPLAY

6. Navigate to the 3731593 directory where the p3731593_10205_SOLARIS64.zip had been

extracted.

bash-3.00# cd 3731593/Disk1

7. Execute the OUI

bash-3.00# ./runInstaller

9.2.2.1 Specify Home Details

Figure 28: Specify Home Details (OMS Upgrade)

18-JUN-2009




9.2.2.2 Procide Metalink Credentials

Figure 29: Provide Metalink Credentials (OMS Upgrade)

9.2.2.3 Product Specific Checks

Figure 30: Product Specific Checks (OMS Upgrade)

18-JUN-2009




9.2.2.4 Provide Repository Administrator Password

Figure 31: Provide Repository Administrator Password(OMS Upgrade)

9.2.2.5 Provide Application Server Instance Password

Figure 32: Provide Application Instance Password(OMS Upgrade)

18-JUN-2009




9.2.2.6 Installation Options Summary

Figure 33: Installation Options Summary (OMS Upgrade)

9.2.2.7 Installation Progress

Figure 34: Installation Progress (OMS Upgrade)

18-JUN-2009




9.2.2.8 Execute configuration scripts

Figure 35: Execute Configuration Scripts (OMS Upgrade)

Run root.sh while logged in as root and upon completion of running the script, click OK button

above.

9.2.2.9 Configuration Assistants

Figure 36: Configuration Assistants (OMS Upgrade)

18-JUN-2009




9.2.2.10 End of Upgrade

Figure 37: End of Upgrade (OMS Upgrade)

9.2.2.11 Post upgrade actions

After the upgrade is completed, turn on DBMS JOBS and DBMS Scheduler (for version 10.1+

RDBMS) for each instance by performing the following steps:

a. Log into the repository as SYSMAN

b. Turn on DBMS JOBS by setting the job_queue_processes to the values written down

earlier for each instance

c. Turn on DBMS Scheduler (10.1+ RDBMS) using the following command:

SQL> exec dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','FALSE');

Note :

The script preinstall.pl, which can be found at the top directory of the extracted patch set, must be

run as perl preinstall.pl <OMSHome> before a Grid Control 10.2.0.5 OMS upgrade if the one-off

#7214697 was applied in the OMSHome before the upgrade. However if the one-off was not

applied,running the script will not cause an issue.

18-JUN-2009




9.2.3 Upgrading the Oracle Management Agent

9.2.3.1 Pre upgrade actions

Stop the agent using the following command. Setup the Oracle home and execute OUI.

bash-3.00# $$AGENT_HOME/bin/emctl stop agent

+ Set the ORACLE_HOME variable to the Oracle home directory of Management Agent.

bash-3.00# $ORACLE_HOME=/data2/oracle/OracleHomes/agent10g

bash-3.00# $export $ORACLE_HOME

+ Execute the runInstaller

bash-3.00# $$./runInstaller

Note: This will only upgrade your Management Agent residing on the OMS host. For detailed

instructions refer to section 4 "Installation Procedure" of the Release notes under the "doc"

directory.The upgrade process then upgrades the Oracle Management Service (OMS), Oracle

Management Repository and the Management Agent on the same host as the OMS to the latest

Enterprise Manager 10g Release 5 (10.2.0.5). This will not upgrade the Database in which

Management repository resides.

9.2.3.2 Specify Oracle Management Agent Home

Figure 38: Specify Oracle Management Agent Home (OM Agent Upgrade)

18-JUN-2009




9.2.3.3 Provide Metalink Credentials

Figure 39: Provide Metalink Credentials (OM Agent Upgrade)

9.2.3.4 Product Specific Prerequisite Checks

Figure 40: Product Specific Prerequisite Checks (OM Agent Upgrade)

18-JUN-2009




9.2.3.5 Summary of Installation

Figure 41: Summary of Upgrade (OM Agent Upgrade)

9.2.3.6 Installation Progress

Figure 42: Upgrade Progress (OM Agent Upgrade)

18-JUN-2009




9.2.3.7 Configuration Assistants

Figure 43: Configuration Assistants (OM Agent Upgrade)

9.2.3.8 Execute Configuration Scripts

Figure 44: Execute root.sh (OM Agent Upgrade)

Execute the above root.sh script while logged in as root and click OK button above.

18-JUN-2009




9.2.3.9 End of Upgrade

Figure 45: End of Upgrade (OM Agent Upgrade)

10 OEM Grid Control Features - Overview

Oracle Enterprise Manager (EM) management software offers the management framework called

Grid Control, which provides a centralized, integrated approach for managing different versions of

Oracle products in the enterprise. Grid Control uses HTTP and HTTP over Secure Sockets Layer

(HTTPS) protocols to provide administrators with a browser-based management interface. The

EM suite is bundled with a Grid Control management console; a management service, which

includes management repository components; and a management agent. The self-monitoring

features of EM help ensure that critical components of Grid Control are always available and

functional.

10.1 The Grid Control Framework

The Grid Control framework has a three-tiered architecture comprising the management console,

management service, and management agent, as follows:

10.1.1 Management Console

This is the central console from which administrators can manage the Grid Control framework.

The console is Web-based and can be connected from any supported Web browser. The browser

communicates with the management service over standard protocols such as HTTP and HTTPS

to enable communication within EM.

18-JUN-2009




Figure 46: Grid Control Management Console

10.1.2 Management Service

The management service is the middle tier in the EM suite. The management service and

management repository generally reside on a system that is separate from the database server

and application server. The management service communicates with the management agents,

which are deployed on target nodes, and collects host and database-related statistics.

10.1.3 Management agent

Managed servers are the final components in the EM suite. A management agent runs on each

monitored target. The management agent is a lightweight process that is responsible for

monitoring different services and host parameters on the host on which it is deployed.

10.2 Features of Grid Control

Grid Control provides a robust, reliable, and scalable management framework across the

enterprise. The key Grid Control features are as follows:

10.2.1 Scalability

Grid Control has been designed for scalability. In heterogeneous environments, which include

databases and application servers of different versions on different platforms, the Grid Control

18-JUN-2009




framework scales seamlessly even when the environment has a large number of servers (see

Figure 2). To add a new system to the management target list, the administrator simply installs

the management agent on the system. As the IT infrastructure grows, administrators can add

more management servers for server load balancing.

10.2.2 Consolidated management

Consolidated management: Every managed server appears as a target on the Grid Control

management console. On the console, each server has a home page that provides a consolidated

view of server parameters such as resource utilization (CPU, memory, and disk); performance

characteristics; and configuration options. Each database (cluster and noncluster) also appears

as a target on the Grid Control home page and can be monitored and administered through the

console after the administrator logs in to the database.

10.2.3 Logical grouping of targets

Logical grouping of targets: The targets on the console, including the database servers and

application servers, can be grouped logically for ease of management. For example,

administrators can create a group for all the hosts running Oracle Real Application Clusters (RAC)

10g in the enterprise. Similarly, another group can be defined for all the hosts running

Oracle10g™ on Linux® platforms.

10.2.4 Automation of tasks

Automation of various tasks is one of the most salient features of Grid Control. Each automated

task is scheduled in the form of a job to EM. Automated tasks may include modeling applications,

backing up databases, deploying custom SQL scripts, or deploying patch updates (see Figure 3).

To enable the Grid Control management console to automatically download and apply patches,

administrators must first configure Grid Control with a MetaLink1 login, password, and other

credentials. MetaLink is an Oracle Web site that allows registered users to download Oracle

database patches and patch sets. EM can also be configured with Simple Mail Transport Protocol

(SMTP) to send the logs and alerts to the system administrator via the management console.

10.2.5 System monitoring and diagnosis

System monitoring and diagnosis: EM can be used for continuous monitoring of targets such as

hosts, databases, and application servers, and can be configured to send automated alerts and

warnings when the target resource utilization reaches threshold values established by the system

administrator.

10.3 Configuring Grid Control

After installation, we need to configure grid control to use it effectively and customize it according

to our environment. The following figures and descriptions will comprehensively explain the

sample configurations which can be implemented in a typical environment.

18-JUN-2009




10.3.1 The grid Control Home Page

Figure 47: The Grid Control Home Page

This home page provide so many information at a glance. The first section “All targets Status”

shows the status of hosts managed by grid control and the total availability percentage. The “All

Targets Alerts” section describes the Critical and Warning alert in various targets and the link

towards the details of alerts.The “All targets Jobs” shows the status of jobs scheduled as

failed/succeeded/suspended etc. Grid control closely watches the security policy violations

through section “Security Policy Violations” The links from each sub sections such as ‘Critical’/

‘Warning’ will show you the details of each of the violation for which you can take remedial

actions. The “critical patch advisories” section shows the live patch update information available

from Oracle Metalink. “Deployment summary” section displays the type of installations, number of

targets against each type, no of installations of each type and patch information for each type.

10.3.2 Management pack configuration

Enterprise Manager provides central management for entire Oracle environment. Some premium

functionality contained within this release of Enterprise Manager requires a separate Oracle

license. Use target based access to enable or disable access for each target or use pack based

batch update to enable or disable selected packs for all targets associated with the specified

target type. For detailed licensing information refer section : ____________________

18-JUN-2009




Figure 48: Management Pack Access

Click Setup�Management Pack Access

Tick or Un-tick each pack option against each monitored target. This is critical as this require

license of these packs for each monitored target. Click apply to make the changes permanent.

10.3.3 Notification Methods

Notification Methods allow you to globally define different mechanisms for sending notifications.

These include e-mail, SNMP traps and running custom scripts. Once defined, Notification

Methods are used by Notification Rules to send notifications to administrators for alerts, policy

violations or job status changes. Each administrator has Notification Rules defined as a

preference.

18-JUN-2009




Figure 49: Notification Methods

Click Setup�Notification Methods

Enter the “Outgoing Mail (SMTP) Server Name.

Enter the Sender name “Identify Sender as”

Enter the Sender’s Email Address.

When a specific alert in a monitored target has to be sent to a target email address(es), that will

be managed by the above configuration. Click “Test Mail Servers” to verify the SMTP server. A

test mail will reach at the inbox of “Sender’s E-mail Address”

10.3.4 E-mail addresses and schedules

10.3.4.1 E-mail addresses

The generated alerts have to be sent to some email addresses of the monitoring

personnel/teams. This is the master list of email addresses to receive alerts where as the

configurable mail scheduling will be done through “Schedule” option in Grid Control. To configure

this, click on “Preferences”. Enter the email addresses/ email groups to which the generated alerts

will be sent. Click on “Test” to test whether you are receiving the mail from the grid control server.

18-JUN-2009




Figure 50: Email addresses

10.3.4.2 Schedules

Configuring schedules are of extreme importance to receive notifications. You need to set up your

notification schedule in order to receive e-mail notifications for alerts. For each day in the

schedule, specify the e-mail addresses that should be used to send you e-mail notifications. If

multiple teams are working on different work schedules or shifts, the email addresses of those

teams should be entered here. There may be different administrators for different set of targets.

You may change the administrator by selecting the specific administrator( ) and click

“Change”. Then, the schedules for that administrator will be displayed here. Each administrator

has exactly one notification schedule. When an alert needs to be e-mailed to an administrator,

Enterprise Manager consults that administrator's notification schedule to determine the e-mail

address to be used.

18-JUN-2009




Figure 51: Notification Schedule

To edit a schedule definition for an administrator, click in the above

screen and you will be forwarded to the below screen.

Figure 52: Edit Notification Schedule definition

In a notification schedule, an administrator can specify different e-mail addresses based on day of

the week and time of the day. When sending e-mail notifications, Enterprise Manager will use the

e-mail addresses appropriate for that day and time. Time periods that are left empty signify

periods where no e-mail notifications should be sent. A notification schedule repeats every

18-JUN-2009




interval specified in the notification schedule definition. Clicking “Continue” will take you to the

following page.

Figure 53: Edit Notification Schedule definition: Email Addresses

Enter e-mail addresses in each time slot to specify how you should be notified. To fill in many time slots at

once, use 'Batch Fill-in'. Click button to select email addresses you specified in Step 10.3.4.1 E-mail

addresses as below. Then after filling in the email addresses, click to complete the schedule info.

Figure 54: Edit Notification Schedule definition: Select Email Addresses

18-JUN-2009




10.3.5 Configuring preferred credentials for monitored targets

When you consolidate monitoring, it is desirable to standardize access to the environments. You

can use preferred credentials to simplify access to targets that you manage. If a target has

preferred credentials set, applications that log in to that target will automatically use the preferred

credentials.

Figure 55: Preferred credentials

Click in Preferences�preferred Credentials and click against ‘Database Instance’ target type

to navigate to a screen as follows

Figure 56: Database Preferred credentials

Supply all the credentials and click to save the changes.

18-JUN-2009




10.3.6 Configuring Notification Rules

Notification rules allow you to choose the targets and conditions for which you want to receive

notifications from Enterprise Manager. These notifications include e-mail, SNMP traps and

running custom scripts.

Click Preferences �Notification �Rules to have a view of available notification rules. There are

15 notification rules available by default.

Figure 57: Notification Rules

Click a Rule name to view the details as below

18-JUN-2009




Figure 58: Notification Rule Details

Click the radio button against a notification rule and click the buttons available in the window to create,

edit, create like or delete a notification rule.

Figure 59: Selecting and Editing a Notification Rule

18-JUN-2009




10.3.6.1 Creating a Notification Rule

After clicking the radio button aside “Database Availability and Critical States”, click “Create Like”

button. Enter a meaningful name for the notification rule. Here we entered

“CORP_DB_AVAILABILITY_NOTIFICATION_RULE”. You may note that the Target Type is

“Database Instance” by default.

Figure 60 Creating a Notification Rule

The option “Apply rule to all Database Instance targets” apply the rules to all the database

instances. If you change the option to “Apply rule to specified Database Instance targets or

groups containing Database Instance targets” the screen will be changed as follows.

Figure 61 Changing Notification Rule Applicationt o specific targets

Click “Add” and add the database targets to which the notification rules will be applied.

18-JUN-2009




10.3.6.2 Set Actions

If you want to get notifications on alerts, tick “Send Me E-Mail”. The repeat notification options can

be configured as per your requirements.

Figure 62 Set Actions

10.3.7 Adding a Middleware Target (WebLogic Server Domain)

10.3.7.1 Pre-requisite

There should be a compatible Oracle Management Agent running in the host where the Oracle

Weblogic Server Domain has been installed. The certification matrix for OMS and Agent versions

with specific Weblogic version follows.

OMS and Agent Versions WebLogic 10.x WebLogic 9.x WebLogic 8.1.x and 7.x

10.2.0.5 Yes Yes Yes

10.2.0.4 Yes (*) Yes Yes

10.2.0.3 No Yes Yes

10.2.0.2 No No Yes

10.2.0.1 No Yes Yes

Table 1: Certification Matrix – OMS and Agent Vs Weblogic

18-JUN-2009




10.3.7.2 Start Adding Middleware Target

Go to Targets � Middleware � Search � Oracle Weblogic Server Domain

Figure 63 Start Adding Middleware Target

Select “Oracle Weblogic Server Domain” from the drop down list

and click GO

10.3.7.3 Provide Weblogic Management Server Credentials

Browse and Select / Type the Weblogic Admin Server hostname. Select the correct version of

weblogic server. Enter the weblogic admin server credentials. If the OM Agent is installed in the

same host where Oracle Weblogic Management Server is running, “Agent Host” is not required.

Type the directory name of “weblogic.jar” is located in the host where Oracle Weblogic

Management Server is running. Click next

18-JUN-2009




Figure 64 Provide Weblogic Management Server Credentials

10.3.7.4 Provide Host Logon Credentials

Enter the host logon credentials for the host where Oracle Weblogic Management Server is

running. Click next

Figure 65 Provide Host Logon Credentials

18-JUN-2009




10.3.7.5 Select Managed Servers

The Weblogic Server will be discovers as follows. Select the managed server we want to monitor

through grid control. Click next

Figure 66 Select Managed Server

10.3.7.6 Review the Weblogic Server Domain and Finish

The details will be displayed as follows. Click finish to come back to the Middleware targets

console.

18-JUN-2009




Figure 67 Review and Finish Weblogic Server Domain Discovery

10.3.7.7 Successful addition of Weblogic Domain to the middleware targets

Now the target weblogic server domain added to the middleware targets and Oracle Enterprise

Manager Grid Control is actively monitoring it.

Figure 68 The middleware targets console

18-JUN-2009




11 Licensing

It is extremely important to understand the OEM grid Control Licensing policy. Oracle does not

charge anything for OEM Grid Control as a product. Instead the licensing is based on the

“Management Pack” usage per server per processor.

11.1 Database Management Packs

The following packs are available for database management. Click Preferences�

Figure 69 Database Management Pack

When you select each pack against a target database, a license should be acquired for that pack.

Eg : If you select “Database Diagnostic Pack “ for the database “CORPprd1”, and the database is

having 2 processors, total license fee payable for that pack for “CORPprd1” is 2 X 3500 = USD

7000.

11.1.1 Database Diagnostics Pack

Offers a complete, cost-effective, and easy to use solution for managing the performance of

Oracle Database environments by providing unique functionality such as automatic identification

of performance bottlenecks, guided problem resolution, and comprehensive system monitoring.

The Diagnostics Pack includes:

• Historical performance monitoring and trending (Database, RAC, Host and Cluster target)

• RAC/Cluster Interconnect monitoring

• ADDM (Automated Database Diagnostic Monitor)

• Automatic Workload Repository

• Event/Alert Notifications: Notification Methods, Rules and Schedules

• Event/Alert history/metric history (Database, RAC, Host and Cluster target)

18-JUN-2009




• User-defined metrics

• Blackouts/Planned Outages

• Monitoring templates

• Corrective actions (including response actions)

• Adaptive metric thresholds

• Metric Baselines

• Memory Access Mode

• Diagnostic, Performance and Event reports

• Database and repository tables/views/api's that store/expose the above data

11.2 System Monitoring Plugins

Figure 70 System Monitoring Plugins

The license for the above is same as described under previous section.

Provides performance and availability data collection, real-time and historical monitoring, event

management/monitoring, notifications, and performance reporting for host systems. This plug-in

includes:

• Real-time and historical performance monitoring and trending (Host target)

• Event management/monitoring (Host target)


• Event/Alert history/metric history (Host target)


• Metric Snapshots


18-JUN-2009






• Performance and Event reports

• Repository tables/views that store/expose the above data

11.3 Diagnostics pack for Oracle Middleware

Figure 71 Weblogic Managed Server Packs

Offers a complete, cost-effective, and easy to use solution for managing the performance of

Oracle Application Server environments by providing unique functionality such as automatic

identification of performance bottlenecks, guided problem resolution, and comprehensive system

monitoring. The Diagnostics Pack includes:

• Root cause diagnostics of Java application performance issues

• Historical performance monitoring and trending (Application Server and Host target)

• Monitoring of JMX/Web Services endpoints hosted on the Oracle Application Server


• Event/Alert history/metric history (Application Server and Host target)





• Metric Snapshots

• Real end user performance monitoring

• End to end tracing with middle tier and database drill downs (database SQL level

diagnostics requires Diagnostics Pack for Oracle Database)

18-JUN-2009




• Component request diagnostics

• Diagnostic, Performance and Event reports

• Repository tables/views that store/expose the above data

11.4 The Prices

Packs Unit License Price Support

System Monitoring Plug-in for Hosts Processor 1800 396

Diagnostics Pack for Oracle Middleware Processor 7000 1540

Database Diagnostics Pack Processor 3500 770

Table 2: Management Pack Price List

• Prices based on Oracle Technology Global Price List April 28, 2009

• http://www.oracle.com/corporate/pricing/pricelists.html

12 Exception / Justification and Corrective Action Instructions

12.1 Exception Number - 1

Section - 7.11

Description of Exception : Configuration Assistants – Failed with error

Grid control is failing at the agent installation with the following error:

The installActions<DateTime>.log files shows:

INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn ... ...

Performing targets discovery and agent configuration

Command =

oracle.sysman.emcp.agent.AgentPlugIn has failed

Exception :

java.lang.Exception: 6

INFO: Configuration assistant "Agent Configuration Assistant" failed

-----------------------------------------------------------------------------

*** Starting OUICA ***

Oracle Home set to

/usr/local/oracle/product/agent10g

Configuration directory is set to

/usr/local/oracle/product/agent10g/cfgtoollogs. All xml files under the

directory will be processed

INFO: The "/usr/local/oracle/product/agent10g/cfgtoollogs/configToolFailedCommands"

script contains all commands that failed, were skipped or were cancelled.

18-JUN-2009




This file may be used to run these configuration assistants outside of OUI.

Note that you may have to up date this script with passwords (if any)

before executing the same.

-----------------------------------------------------------------------------

SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly

recommended that you retry the configuration assistants at this time. Not successfully

running any "Recommended" assistants means your system will not be correctly configured.

1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.

2. Fix the errors causing these failures.

3. Select the failed assistants and click the 'Retry' button to retry them.

-------------------------------------------------------------------------

12.1.1.1 Troubleshooting

Checked the logfiles at $AGENT_HOME/ cfgtoollogs/cfgfw

/data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/ oracle.sysman.top.agent_<timestamp>log

data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

And found that the following error occurred.

INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn

Performing free port detection on host=myhost.oracle.com

Securing the agent


Command = oracle.sysman.emcp.agent.AgentPlugIn has failed

Exception : java.lang.Exception: 6


From the CfmLogger_*.log:

SQL*Plus: Release 10.1.0.4.2 - Production on Sat Mar 17 17:41:31 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected.

DEFAULT WEBSITE EM Website CREATION FAILED : ORA-01403: no data found ORA-01403:

no data found

18-JUN-2009




BEGIN

*

ERROR at line 1:

ORA-20999: CREATE DEFAULT WEBSITE FAILED : ORA-01403: no data found

ORA-06512: at line 224

12.1.1.2 Cause

From the configuration logs we can see that only website creation target has failed. Other than

that everything works fine. This can happen if the machine is to slow/busy for the Agent to upload

data to OMS during installation. The log clearly says that "no data found" as the Agent was not

able to upload data during the configuration phase

12.1.1.3 Solution

1. Backup the following files:

$AGENT_HOME/sysman/emd/targets.xml

$AGENT_HOME/sysman/config/emd.properties

2. Then run "$AGENT_HOME/bin/agentca -f" command.

(Under heavy load it may take some time to create the website target)

3. Click finish to end the installation. Even though the OUI announce that some configuration

assistants failed, it will work fine.

12.1.2 Exception Number - 2

Section - 7.11

Description of Exception : Configuration Assistants – Failed with error

Grid control is failing at the agent installation with the following error:

The installActions<DateTime>.log files shows:

INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn ... ...


Command =

oracle.sysman.emcp.agent.AgentPlugIn has failed

Exception :

java.lang.Exception: 6


-----------------------------------------------------------------------------

*** Starting OUICA ***

Oracle Home set to

/usr/local/oracle/product/agent10g

18-JUN-2009




Configuration directory is set to

/usr/local/oracle/product/agent10g/cfgtoollogs. All xml files under the

directory will be processed

INFO: The "/usr/local/oracle/product/agent10g/cfgtoollogs/configToolFailedCommands"

script contains all commands that failed, were skipped or were cancelled.

This file may be used to run these configuration assistants outside of OUI.

Note that you may have to up date this script with passwords (if any)

before executing the same.

-----------------------------------------------------------------------------

SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly

recommended that you retry the configuration assistants at this time. Not successfully

running any "Recommended" assistants means your system will not be correctly configured.

1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.

2. Fix the errors causing these failures.

3. Select the failed assistants and click the 'Retry' button to retry them.

-------------------------------------------------------------------------

12.1.2.1 Troubleshooting

Checked the logfiles at $AGENT_HOME/ cfgtoollogs/cfgfw

/data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/ oracle.sysman.top.agent_<timestamp>log

data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

And found that the following error occurred.

INFO: Command = oracle.sysman.emcp.agent.AgentPlugIn

Performing free port detection on host=myhost.oracle.com

Securing the agent


Command = oracle.sysman.emcp.agent.AgentPlugIn has failed

Exception : java.lang.Exception: 6


From the CfmLogger_*.log:

SQL*Plus: Release 10.1.0.4.2 - Production on Sat Mar 17 17:41:31 2007

18-JUN-2009




Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected.

DEFAULT WEBSITE EM Website CREATION FAILED : ORA-01403: no data found ORA-01403:

no data found

BEGIN

*

ERROR at line 1:

ORA-20999: CREATE DEFAULT WEBSITE FAILED : ORA-01403: no data found

ORA-06512: at line 224

12.1.2.2 Cause

From the configuration logs we can see that only website creation target has failed. Other than

that everything works fine. This can happen if the machine is to slow/busy for the Agent to upload

data to OMS during installation. The log clearly says that "no data found" as the Agent was not

able to upload data during the configuration phase

12.1.2.3 Solution

1. Backup the following files:

$AGENT_HOME/sysman/emd/targets.xml

$AGENT_HOME/sysman/config/emd.properties

2. Then run "$AGENT_HOME/bin/agentca -f" command.

(Under heavy load it may take some time to create the website target)

3. Come back to the OUI installation screen and click finish to end the installation. Even though

the OUI announce that some configuration assistants failed, it will work fine.

18-JUN-2009




Appendix

I. Appendix 1: Sample Licensing Worksheet

Packs Unit License Price

Suppor

t

No Of

Processo

rs

Total

License

Price(US

D)

System Monitoring Plug-in

for Hosts

Process

or 1800 396 4 7200

Diagnostics Pack for Oracle

Middleware

Process

or 7000 1540 0 0

Database Diagnostics Pack

Process

or 3500 770 4 14000

Total

21200

Discount (Change

Here)==>> 35%

7420

Net

13780

Total CPU(Core) Core

Core

Factor

Total

Cores

Hosts 2 2 2 0.5 4

Databases 2 2 2 0.5 4

Weblogic Servers 0 4 2 0.25 0

Note : For database purchases Diagnostic Pack is "Required".

So, for already deployed databases it is not required to buy new license

Ref : Prices based on Oracle Technology Global Price List as on April 28, 2009

II. Appendix 2 Oracle 10g Grid Control management packs Licensing information

Oracle Enterprise Manager 10g Release 5 Grid Control License Information.mht

Documents

Installing and Configuring Oracle OEM 10g Grid Control on Solaris