Oracle Database

ORACLE-WIKI.NET

Background & Overview

This guide details how to deploy a Grid Control Agent to another server via the Grid Control frontend.

It is worth noting, that as part of the installation of Grid Control 11g an agent is deployed on the OMS server. This agent will be used to self monitor the OMS. As such, a set of agent binaries for the platform your OMS is deployed on will automatically be available for deployment to other identical platforms.

In this install guide, the Grid Control infrastructure is deployed on Oracle Linux x86 (64 bit). Consequently, the following documentation provides instructions for installing an Oracle Grid Control Agent version 11.1.0.1 on Oracle Linux x86 (64 bit).

If you wish to deploy a Grid Control Agent to a different platform, you will first need to download the Grid Control Agent Software. This can be achieved by following the Downloading Agent Software instructions in the Grid Control Post Implementation Configuration Guide

Finally, there are various other ways to install the Grid Control Agent, but by far the easiest is via the Grid Control frontend. This is made even easier if access sudo root is made available. However, this guide assumes sudo root access is not available.

Assumptions & Pre-Requisites

This document expects and assumes the following:

• The instructions are carried out by a qualified DBA.
• Access to Grid Control Console is available.
• The DBA performing the install does NOT have access to sudo root.

Useful Information

• Known Issues

Step-By-Step Guide

1. Log onto the Grid Control 11g Console.

1. Follow the instructions as demonstrated in the Example Agent Install section below.

^NOTE
If you have access to sudo root then tick the Run root.sh box after entering the OS Credentials. See screenshot below.

1. Get a UNIX Administrator to run the root.sh script on each host where the agent was deployed.

• cd /u01/app/oracle/agent11g
• ./root.sh
• This step will not have to be performed if the Run root.sh box was ticked.

Example Agent Install

• Click on the Deployments tab.

• Select Install Agent

• Select Fresh Install

• Ensure Default, from Management Server location is selected in the Source Software section
• Select Version 11.1.0.1 from the drop down menu in the Version section.
• Select Platform Linux x86-64 from the drop down menu in the Hosts section. (Or the platform you wish to deploy to).
• Enter a list of comma separated hosts in the box titled Provide Host List in the Hosts section.
  • NOTE: If installing against a virtual hostname, for example, as part of a VCS cluster, the virtual hostname should be specified in the Provide Host List. Furthermore, the Allow local hostname to override provided hostname should be ticked.
• At this point scroll the page down and continue to fill out the New Agent Installation Details page.

• Set Username to oracle in the OS Credentials section.
• Enter a valid password in the Password box.
• Re-enter the password in the Confirm Password box.
• Ensure the Run root.sh box is NOT ticked.
• Set the Installation Base Directory to /u01/app/oracle
• Ensure a valid Port value is specified in the Port section.
• If installing against a virtual hostname, for example, as part of a VCS cluster, then set Additional Parameters to -R myvirtualhost, where virtualhost the virtual hostname known to the clustering software. Otherwise, leave blank.
• Enter the Management Server Registration Password in the Management Server Security section.
• Re-enter the password in the Confirm Password box.
• At this point scroll the page down and continue to fill out the New Agent Installation Details page.

• Review the details and click Continue
• Note - This page may take a while to move on as it waits for a timeout on the proxy server. Be patient!!

• Tick the I wish to receive security updates via My Oracle Support if required.
• Enter a valid Proxy Server in the Connection Details section if required.
• Enter a valid Proxy Port in the Connection Details section if required.
• Enter a valid Proxy Username in the Connection Details section if required.
• Enter a valid Proxy Password in the Connection Details section if required.
• Click Submit

• This page will move on automatically

• Review the Agent Installation Sessions Details ensuring there are no failures.
• Click the Click Here link.

• Review the Prerequisite Details ensuring there are no failures.
• Click Back to Session Details

• Click Done

Known Issues

Wrong Location Specified for SCP and SSH

On some OMS platforms the provisioning files, located in /u01/app/middleware/oms11g/sysman/prov/resources have the wrong path defined for SCP and SSH.

example

The following provisioning file is for Solaris SPARC

myhost> cat ssPaths_solx64.properties

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

SH_PATH=/usr/bin/bash
SH_ARGS=-c
KSH_PATH=/usr/bin/ksh
RMDIR_ARGS=
#the date should be in the format of year:month:date:hour:minute:second
DATE_ARGS=-u +%y:%m:%d:%H:%M:%S
PING_PATH=/usr/sbin/ping
PING_ARGS=
SSH_PATH=/usr/local/bin/ssh
SCP_PATH=/usr/local/bin/scp
TAR_EXCLUDE_ARGS=X
TAR_INCLUDE_ARGS=-I
DF_COL_NAME=avail
NODENAME_ARGS=-n

SSH and SCP are typically stored in /bin and not /usr/local/bin on Solaris.

Fix

Symbolically link scp and ssh to /bin

cd /usr/local/bin
ln -s /bin/ssh ssh
ln -s /bin/scp scp

Install Fails if a System Banner is Used.

If the Unix server is configured to use a system banner, the install will fail when using ssh to copy the files onto the remote server.

Fix

There are two fixes for this problem

FIX 1

• Prior to the install, log onto the OMS server
• cd $HOME/.ssh
• Add the following line to the config file
  • LogLevel quiet
• chmod 444 config

NOTE
If there is a global config file for SSH on the OMS server, then this files should be updated instead of the oracle config file.
It is vitally important that you chmod the config file to 444 otherwise Grid Control will overwrite the file during the install process and the install will fail again with the same message.

FIX 2

• Prior to the install, log onto the OMS server
• cd $OMS_HOME/sysman/prov/resources
• Add the system banner text to the ignoreMessages.txt file

WARNING - Although, this solution will work, it can easily be undone if the system banner text is changed
NOTE - At the time of producing this guide, it seems that this fix does not seem to work for all platforms.