Grid Control 11.1.0.1 Administration Guide

Background & Overview

The following documentation provides instructions for managing an 11g Grid Control environment

Assumptions & Pre-Requisites

This document expects and assumes the following:

  • The instructions are carried out by a qualified DBA/Grid Control Administrator

Useful Information

Starting Grid Control

Step-By-Step Guide

1. Start the Database and Listener

  • export ORACLE_SID=SID
  • export ORAENV_ASK=NO
  • . oraenv
  • lsnrctl start
  • sqlplus '/ as sysdba'
  • SQL> startup
  • SQL> quit

1. Start the Grid Control Components

  • cd /u01/app/middleware/oms11g/bin
  • ./emctl start oms

1. Start the Local Grid Control Agent

  • cd /u01/app/middleware/agent11g/bin
  • ./emctl start agent

Script for Starting Grid Control

#!/bin/ksh
export ORACLE_SID=JSDGRD02
export ORAENV_ASK=NO
. oraenv
lsnrctl start
sqlplus '/ as sysdba' «EOF
startup
EOF
cd /u01/app/middleware/oms11g/bin
./emctl start oms
cd /u01/app/middleware/agent11g/bin
./emctl start agent

Stopping Grid Control

Step-By-Step Guide

1. Stopping the Local Grid Control Agent

  • cd /u01/app/middleware/agent11g/bin
  • ./emctl stop agent

1. Stopping the Grid Control Components

  • cd /u01/app/middleware/oms11g/bin
  • ./emctl stop oms -all

1. Stopping the Database and Listener

  • export ORACLE_SID=JSDGRD02
  • export ORAENV_ASK=NO
  • . oraenv
  • lsnrctl stop
  • sqlplus '/ as sysdba'
  • SQL> shutdown immediate
  • SQL> quit

Script for Stopping Grid Control

#!/bin/ksh
cd /u01/app/middleware/agent11g/bin
./emctl stop agent
export ORACLE_SID=SID
cd /u01/app/middleware/oms11g/bin
./emctl stop oms -all
export ORAENV_ASK=NO
. oraenv
lsnrctl stop
sqlplus '/ as sysdba' «EOF
shutdown immediate
EOF

Known Issues

Incorrect Documentation for Starting and Stopping Grid Control

Description

In the Grid Control Administrators Guide part number E16790-01, there are a number of missleading or incorrect statements on how to start Grid Control 11g.

The manual talks about starting and stopping the WebCache using the following command

  • OMS_HOME/opmn/bin/opmnctl stopproc ias-component=WebCache

Yet, when talking about stopping and starting all components further on in the manual, webcache is not mentioned.

The manual also says in section 7.6.1 and 7.6.2 that you need to stop and start iasconsole when stopping or starting Grid Control.

Elsewhere in the administrators guide there are references to the startWebLogic.sh script suggesting it should be used to start WebLogic.

All of the statements above, taken from the manual, are incorrect. There is no need to stop or start these components manually or to run the script startWebLogic.sh. The components where applicable, are all started or stopped when stopping or starting the OMS using emctl.

In particular, for shutting down Grid Control the manual in section 7.6.2 says to use the following commands

  • OMS_HOME/bin/emctl stop oms
  • IAS_HOME/bin/emctl stop iasconsole
  • AGENT_HOME/bin/emctl stop agent
  • Using SQLPLUS stop DB
  • DB_HOME/bin/lsnrctl stop

As already stated above, iasconsole does not need to be started and therefore, does not need to be stopped. But more importantly, the line

OMS_HOME/bin/emctl stop oms

should read

OMS_HOME/bin/emctl stop oms -all

Take notice of the -all flag on the command line. It is important you add this flag to the ./emctl command when shutting down Grid Control. Failure to do so will result in some of the components remaining up and running. It is not required on startup.

All of this information has been confirmed by Oracle Support via an SR.

Fix

Follow the documentation above when stopping and starting Grid Control.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License