Grid Control Post Implementation Configuration Guide

Background & Overview

The following documentation provides instructions on how to configure Grid Control after the installations steps have been completed.

Assumptions & Pre-Requisites

This document expects and assumes the following:

  • The instructions are carried out by a qualified DBA.
  • Access to the internet is available.
  • The following software library exists and contains the correct binaries /u01/app/oracle/SOFTWARE

Useful Information

Step-By-Step Guide ~ Proxies, Metrics and Policies.

1. Configure Proxy & Connection Settings

  • In the Grid Control Console click on the Home tab.
  • Under the section titled Critical Patch Advisories for Oracle Homes click on the Not Configured link.
  • Click on Proxy & Connection Settings
  • Ensure the radio button for Manual proxy configuration is selected.
  • Set the Host to proxyserver.dmz.co.uk
  • Set the port to 8080
  • Set the Don't proxy for to hostname
  • Set the Realm local
  • Set the Username to a valid proxy server username.
  • Enter a valid password for password
  • Click *Apply*

2. Configure Critical Patch Advisories

  • In the Grid Control Console click on the Setup in the top right hand corner.
  • From the menu on the left hand side, click on Patching Setup
  • Select the section titled MetaLink & Patching Settings.
  • Enter the MetaLink Username to ku.oc.ynapmocym|emanresu#ku.oc.ynapmocym|emanresu
  • Enter a valid MetaLink password.
  • Click Apply

3. Disabled Unnecessary Database Metrics.

  • Click on the Targets tab in the Grid Control Console.
  • Click the Database breadcrumb.
  • Select SID database.
  • Select Metric and Policy Settings located at the bottom of the page.
  • Click on Polices
      • (a) Navigate the screen until you reach the Password Grace Time policy
      • (b) Click on the Pencil alongside the policy.
      • (c) Set the drop down box next to the Policy Evaluation field to Disabled
      • (d) Click Continue
    • Repeat steps a to d above for the following metrics.
      • Password Complexity Verification Function Usage
      • Background Dump Destination
      • Audit File Destination
      • User Dump Destination
      • Core Dump Destination
      • Log Archive Destination Permissions
      • Password Life Time
      • Naming Database Links
      • Use of SQL92 Security Features
      • Enable Database Auditing
      • Remote Password File
      • Click Ok

NB The above is an example on how to disable Database Metrics. Each site is different and will require a different configuration. Furthermore, disabling certain metrics may mean there is no visibility on the vulnerability of your system to security violations. Disable with care

4. Disabled Unrequired Host Metrics.

  • Click on the Targets tab in the Grid Control Console.
  • Click the Hosts breadcrumb.
  • Select hostname database.
  • Select Metric and Policy Settings located at the bottom of the page.
  • Click on Polices
    • (a) Navigate the screen until you reach the Open Ports policy
    • (b) Click on the Pencil alongside the policy.
    • (c) Set the drop down box next to the Policy Evaluation field to Disabled
    • (d) Click Continue
  • Click ok

NB The above is an example on how to disable Host Metrics. Each site is different and will require a different configuration. Furthermore, disabling certain metrics may mean there is no visibility on the vulnerability of your system to security violations. Disable with care

5. Add User Defined Filesystem metrics

  • Click on the Targets tab in the Grid Control Console.
  • Click the Hosts breadcrumb.
  • Select hostname database.
  • Select Metric and Policy Settings located at the bottom of the page.
    • (a) Click the pencil alongside the Filesystem Space Available metric.
    • (b) Click Add
    • (c) In the Mount Point box enter /u01/app/oracle
    • (d) In the Warning Threshold box enter 10
    • (e) In the Critical Threshold box enter 5
    • (f) Click Continue
  • Repeat steps a to f for mount point /u06/oradata/SID/arch/d1, setting the thresholds to 50 and 10.
  • Repeat steps a to f for mount point /tmp, setting the thresholds to 10 and 5.
  • Click the pencil alongside the Filesystem Space Available metric
  • Delete the contents in the Warning Threshold and Critical Threshold boxes for the metric All Others
  • Click Continue
  • Click ok

NB The above is for example purposes only. Each site is different and will require a different configuration.

6. Set-up the Management Access Packs for the OMS and OMS Agent.

  • Navigate to the Grid Control Home page.
  • Click on Setup in the top right-hand corner of the page.
  • Select Management Pack Access
  • For the Grid Control database ensure the following selections
    • Database Change Management Pack - NOT Ticked
    • Database Diagnostics Pack - Ticked
    • Database Tuning Pack - Ticked
    • Data Masking Pack - NOT Ticked
    • Database Configuration Management Pack - Ticked
    • Provisioning Pack - NOT Ticked
    • Pack Access Agreed - Ticked
  • Click Apply

NB The above is for example purposes only. Each site is different and will require a different configuration. This is particularly relevant when dealing with the management pack access as each management pack requires a separate licences over and above the database licence.

7. Create Default Database Monitoring Template.

  • Click on Setup in the top right-hand corner of the page.
  • Select Monitoring Templates from the Menu on the left of the page.
  • Click Create
  • Enter SID in the Target box.
  • Click Continue
  • Enter Default Database Monitoring Template in the Name box.
  • Enter Default Database Monitoring Template in the Description box.
  • Click Ok
  • From the Monitoring Templates home page, select the radio button for the Default Database Monitoring Template
  • Click Apply
  • Click Add
  • Click Select All and then click Next 11.
  • Repeat the last step until ALL of the targets have been selected.
  • Once ALL targets have been selected, click Select at the top right of the page.
  • Click Ok

NB The above is for example purposes only. Each sitte will have a different set of requirments. However, it does make systems easier to manage if you have a default set of monitoring templates.

8. Create Default Host Monitoring Template.

  • Click on Setup in the top right-hand corner of the page.
  • Select Monitoring Templates from the Menu on the left of the page.
  • Click Create
  • Enter hostname in the Target box.
  • Click Continue
  • Enter Default Host Monitoring Template in the Name box.
  • Enter Default Host Monitoring Template in the Description box.
  • Click Ok
  • From the Monitoring Templates home page, select the radio button for the Default Host Monitoring Template
  • Click Apply
  • Click Add
  • Click Select All and then click Next 11.
  • Repeat the last step until ALL of the targets have been selected.
  • Once ALL targets have been selected, click Select at the top right of the page.
  • Click Ok

NB The above is for example purposes only. Each sitte will have a different set of requirments. However, it does make systems easier to manage if you have a default set of monitoring templates.

Step-By-Step Guide ~ Set-up the Agent Download Directory.

NB This section relies on the files detailed/created in the references section below. It is advised that you read the references section first to ensure you have access to the relevant files.

1. Download the Oracle Grid Control Agent 10.2.0.4 binaries from Oracle OTN into /u01/app/oracle/SOFTWARE/GRID/AGENT/SolarisSPARC

Grid Control Agent 10.2.0.4 for Solaris Operating System (SPARC) (64-bit)
Solaris_Grid_Control_agent_download_10_2_0_4_0.zip : 535,897,621 bytes; cksum - 4150947712

2. Backup the existing AgentDownload directory 10.2.0.4.0.

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download
  • mv 10.2.0.4.0 10.2.0.4.0.ORIG
  • mkdir 10.2.0.4.0
  • chmod 750 10.2.0.4.0

3. Copy the Agent binaries to the AgentDownload directory.

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Solaris_Grid_Control_agent_download_10_2_0_4_0.zip .
  • unzip Solaris_Grid_Control_agent_download_10_2_0_4_0.zip
  • rm Solaris_Grid_Control_agent_download_10_2_0_4_0.zip

4. Copy the customised response file into the AgentDownload directory

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom/agent_download.rsp agent_download.rsp

5. Copy the customised agentDownload.solaris into the correct location

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom/agentDownload.solaris agentDownload.solaris
  • chmod 755 agentDownload.solaris

6. Copy the agent_fix_script to the correct location

  • mkdir -p /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris/custom
  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris/custom
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom/agent_fix_script.ksh agent_fix_script.ksh
  • chmod 755 agent_fix_script.ksh

7. Copy the properties files the correct location

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris/custom
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom/*.properties .

8. Copy the VCSoraInst.loc file to the correct location

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris/custom
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom/VCSoraInst.loc .

9. Download the Oracle Grid Control Agent Recommended Patch Bundle 1 into /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Recommended.

Grid Control Agent 10.2.0.4 for Solaris Operating System (SPARC) (64-bit)
Solaris_x64_GridControl_agent_download_10_2_0_2_0.zip : 1,252,284 bytes; cksum - 3136653290

NB Rename the file to *Solaris_Patch_Bundle_1_For_10_2_0_4_0.zip*. This is required becuase Oracle wrongly named the patch bundle after the Solaris x86 Agent.

10. Copy the 10.2.0.4 patch bundle to the correct directory.

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download
  • mkdir -p Patches/SolarisSPARC/Recommended
  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/Patches/SolarisSPARC/Recommended
  • cp /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Recommended/Solaris_Patch_Bundle_1_For_10_2_0_4_0.zip Solaris_Patch_Bundle_1_For_10_2_0_4_0.zip

NB Notice the change of name on the file.

Known Issues

Issues Setting up Proxy Servers

Description

After setting up the proxy server, you get errors on the OMS Agent home page and the database home page.

The following error message may be displayed on the Agent home page within the Grid Console.


headless java exception


Cause

When setting up a proxy server, if you do not get the Do Not Proxy For settings correct the agent will no longer be able to connect to the OMS. Further, because the agent cannot connect to the OMS it will not be possible to remove the proxy settings.

Fix Step-By-Step

1. Shut down the agent and the OMS

2. Log on to the database as SYSMAN

  • . oraenv
  • ORACLE_SID = [oracle] ?
  • sqlplus sysman
  • SQL> create table mgmt_url_proxy_backup;
  • SQL> truncate table mgmt_url_proxy;
  • SQL> quit

3. Start the oms and the agent

4. Set-up the proxy server correctly.

NB If you get this error for any other agent, then you can update the do not proxy for settings using the Grid Control front end without having to use SQL*Plus

References

Customisations to the agent_download files.

As part of the agent_download configuration a number of files need to be amended or created. The following files should be loaded up to /u01/app/oracle/SOFTWARE/AGENT/SolarisSPARC64/Custom

agent_fix_script.ksh
staticports.ini
VCSoraInst.loc

In addtion the following details how to make the changes to the Oracle supplied agent download files.

Making Changes to the agent_download.rsp file.

1. Create an agent_download.rsp file.

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0
  • cp agent_download.rsp.bak agent_download.rsp

2. Using vi configure the response file.

  • Set the following parameters in the response file to the specified values:-
    • UNIX_GROUP_NAME="dba"
    • FROM_LOCATION="../stage/products.xml"
    • s_OMSHost="hostname"
    • s_OMSPort="4889"
    • s_encrSecurePwd=""

Making Changes to the agentDownload.solaris script.

1. Backup the original *agentDownload.solaris* script.

  • cd /u01/app/oracle/GRID/oms10g/sysman/agent_download/10.2.0.4.0/solaris
  • cp agentDownload.solaris agentDownload.solaris.ORIG

2. Using vi update the agentDownload.solaris script.

  • After line *142*, add the following code.
      • Line 143: ftp_get_file () {
      • Line 144: cp $1 .
      • Line 145: return $?
      • Line 146: }
  • Change line 147 from InstallerDownloadCmd=$WGET to InstallerDownloadCmd=ftp_get_file
  • Hash out line 591: #AgentDownloadURL="http://${OMShost}:${httpPort}/agent_download/${EmVersion}"
  • After line 591 add the following line.
    • Line 592: AgentDownloadURL="/net/${OMShost}/u01/app/oracle/GRID/oms10g/sysman/agent_download/${EmVersion}"
  • After line 691 add the following.
    • Line 692: echo ""
    • Line 693: echo "Copy fix script from Agent Download URL"
    • Line 694: echo ""
    • Line 695:
    • Line 696: cp $AgentDownloadURL/solaris/custom/agent_fix_script.ksh $InstallerLocalStage/../agent_fix_script.ksh
    • Line 697: chmod 755 $InstallerLocalStage/../agent_fix_script.ksh
  • After line 842 add the following.
    • Line 843: #
    • Line 843: #Running Custom Fix Script
    • Line 843: #
    • Line 843:
    • Line 843: $InstallerLocalStage/../agent_fix_script.ksh $ORACLE_HOME $InstallerLocalStag $AgentDownloadURL
    • Line 843: fix_status=$?
    • Line 843: if [ $fix_status -eq 0 ]
    • Line 843: then
    • Line 843: echo "Fix Script Successful" | tee -a $LogFile
    • Line 843: fi
    • Line 843:
  • Using vi change the " at the end of line 291 with the following string ORACLE_HOSTNAME=$AGENT_HOSTNAME"

NB Make sure you don't forget the *"* after AGENT_HOSTNAME as indicated above.

Making Changes to the .properties Files.

1. Make a backup of the existing .properties files.

  • cd AGENT_HOME/sysman/config/esa
  • cp database.properties database.properties.ORIG=
  • cp instance.properties instance.properties.ORIG=

NB The host.properties file can be ignored as this is okay.

2. Fix the .properties files

  • Using vi remove and blank lines.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License