Oracle Database

ORACLE-WIKI.NET

IMPORTANT ANOUNCEMENT CLICK HERE BEFORE CONTINUING

Background & Overview

The following documentation provides instructions for installing Grid Control 11g residing on a Enterprise Oracle Linux (Version 5, 64Bit) operating system using an existing database for a repository and conforming to Oracle OFA standards.

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.
• All necessary client software, e.g. Telnet and X-Server is available.
• All references to SID should be replaced with correct database name as derived using a valid database naming standard.
• There is only ONE database installed on the server and that database is at version 11.2.0.1 with ALL recommended patches applied as detailed in the following install guide

Useful Information

• Read the Known Issues section below.
• To use WebLogic Server with 64-bit JVM's on Linux and Solaris or to use WLS on other supported platforms, use the WebLogic Server generic installer listed under Additional Platforms on the Oracle WLS download page.

Step-By-Step Guide

Installing Grid Control 11g

1. Ensure oracle account and dba group exists.

1. Ensure you meet the hardware requirements as detailed in the Grid Control Basic Installation Guide, Appendix B (E15838-01)

2. Ensure JDK 1.6 is installed. See MyOracle note 1063587.1 for details on how this is done.

3. Ensure you file descriptors are greater than 4096.

• ulimit -n

4. Check the entropy value is greater than 400.

• cat /proc/sys/kernel/random/entropy_avail

5. Download the Oracle Grid Control 11.1.0.1 binaries from Oracle into /u01/app/oracle/software/grid11g/oms.

Grid Control 11.1.0.1 for Oracle Linux Operating System (x86) (64-bit)
V20515-01_1of3.zip : 1,430,649,163 bytes; cksum - 2264691416
V20515-01_2of3.zip : 1,589,674,193 bytes; cksum - 2607620908
V20515-01_3of3.zip : 1,408,054,490 bytes; cksum - 927174125

6. Download the Oracle WebLogic 10.3.2.1 binaries from Oracle into /u01/app/oracle/software/grid11g/wls.

Oracle WebLogic 10.3.2.1 for Oracle Linux Operating System (x86) (64-bit)
V18594-01.zip : 945,517,822 bytes; cksum - 80417988

7. Unzip the WebLogic binaries

• cd /u01/app/oracle/software/grid11g/wls
• unzip V18594-01.zip

8. Start an X-Server

9. Start the WebLogic installer

• export DISPLAY=<ip address>:0.0
• /usr/bin/java -d64 -jar wls1032_generic.jar

10. Follow the instructions as demonstrated in the Example WebLogic Install section below.

11. Patch the WebLogic Server with patch ID WDJ7 using smart update.

• cd /u01/app/middleware/utils/bsu
• Start an X-Server
• ./bsu.sh
• NB Note this may take some time to start. Be patient!!

12. Follow the instructions as demonstrated in the Example WebLogic Patch section below.

13. Install Grid Control 11g

• cd /u01/app/oracle/software/grid11g/oms
• Start an X-Server
• ./runInstaller

14. Follow the instructions as demonstrated in the Example Grid Control 11g Install section below.

15. Check that the OMS and Agent are running correctly

• cd /u01/app/middleware/oms11g/bin
• ./emctl status oms
• cd /u01/app/middleware/agent11g/bin
• ./emctl status agent
• ./emctl upload

Example WebLogic Install

• Next

• Set Middleware Home Directory to /u01/app/middleware

• IMPORTANT - Read the following Known Issue for a potential bug in the installer at this point
• Un-tick the I wish to receive security updates via My Oracle Support box.
• Click Next

• Click Yes to remain uninformed.

• Click Next

• Select Typical
• Click Next

• Ensure Sun SDK 1.6.0_18 (/usr/java/jdk1.6.0_18)
• Click Next

• Ensure WebLogic Server: is set to /u01/app/middleware/wlserver_10.3
• Click Next

• Review the Installtion Summary
• Click Next

• Monitor the install process. This screen will move on automatically

• Ensure Run Quickstart is not ticked.
• Click Done

Example WebLogic Patch

• Click Work Offline

• Select File -> Preferences -> Proxy

• Select the Proxy tab.
• Ensure Use HTTP Proxy is ticked.
• Set Host to a valid proxy.
• Set Port to a valid port number.
• Set Username to a valid username.
• Set Password to a valid password.
• Click Save.

• Restart the utility by selecting File -> Exit and re-running ./bsu.sh

• Set Support ID: to a valid Metalink username.
• Set Password to a valid Metalink password.
• Click Login.

• Select the Get Patches tab.

• Ensure WDj7 is ticked.
• Click Download Selected.

• Ensure Yes, check for conflicts now is selected.
• Click Ok.

• Click Ok.

• This screen will move on automatically

• Select the Manage Patches tab.

• Click on the Green Arrow Apply button.

• Click Ok.

• Click Ok.

• Select File -> Exit

Example 11g Grid Control Install

• IMPORTANT - Read the following Known Issue for details of a potential bug in the installer at this point.
• Set Email to a Metalink username.
• Ensure I wish to receive security updates via My Oracle Support is ticked.
• Ensure My Oracle Support Password is set to a valid Metalink password.
• Click Next

• Ensure Connection Method radio is set to proxy
• Set Proxy Server to a valid proxy server.
• Set Proxy Port to a valid proxy port.
• Set Proxy Username to a valid proxy username
• Set Proxy Password to a valid proxy password
• Click Continue

• Click Proxy Settings

• Ensure Enable Proxy is ticked.
• Ensure the proxy details are correct.
• Click Next

• Click Ok.

• IMPORTANT - Read the following Known Issue for details of a potential bug in the installer at this point.
• Ensure Skip Software Updates is selected.
• Click Next

• Ensure Install a new Enterprise Manager system is selected.
• Click Next

• Ensure all checks have succeeded.
• Click Next

• Ensure Middleware home location is set to /u01/app/middleware
• Ensure OMS instance base location is set to /u01/app/gc_inst

• Ensure WebLogic User Name is set to weblogic
• Set the WebLogic Password to a valid password.
• Set the Confirm Password to a valid password.
• Set the Node Manager Password to a valid password.
• Set the Confirm Password to a valid password.
• Click Next

• Ensure Database Host Name is set to the host name of the Grid Control Repository.
• Ensure Port is set to 1521
• Ensure Service/SID is set to the Grid Control Repository SID.
• Ensure SYS Passowrd is set to the sys password of the Grid Control Repository.
• Click Next

• Set SYSMAN Password to a valid password.
• Set Confirm Password to a valid password.
• Ensure Management Tablespace is set to /u07/oradata/SID/data/d1/mgmt.dbf
• Ensure Configuration Data Tablespace is set to /u07/oradata/SID/data/d1/mgmt_ecm_depot1.dbf
• Ensure JVM Diagnostics Data Tablespace is set to /u07/oradata/SID/data/d1/mgmt_ad4j.dbf
• Click Next

• Set the Registration Password to a valid password.
• Set Confirm Password to a valid password.
• Ensure Allow only secure agents to communicate with the OMS is ticked.
• Ensure Allow only secure access to the console is ticked.
• Click Next

• Take a screen shot or note down the port numbers used by Grid Control.
• Click Next

• Review the installation details.
• Click Install

• Monitor the install process.
• This screen will move on automatically.

• Ask a UNIX administrator to run script /u01/app/middleware/oms11g/allroot.sh
• Once the allroot.sh script has run successfully, click Ok.

• Monitor the configuration assistants progress.
• This screen will move on automatically.

• Whilst the configuration assistants are in progress the UNIX terminal session will display information similar to the above screen.

• Take a screen shot or note down the URLs used by Grid Control.
• Click Close

Known Issues

Please read all the known issues before continuing with the install.

Invalid URL for WebLogic BSU Update Tool

Description

The address to the download site was changed from http to https, but some versions of the WebLogic installer did not have the revised path. If you encounter a connection problem to the download site but do not have firewall issues (See below) contact Oracle Support. Tell them you need help editing ws.properties to change the URL from

• com.bea.plateng.patch.PatchServicesFactory.consumer.wsdl= http://pmlb.bea.com/axis/services/PatchConsumerService?wsdl …

to

• com.bea.plateng.patch.PatchServicesFactory.consumer.wsdl= https://pmlb.bea.com/axis/services/PatchConsumerService?wsdl …

Fix

Alternatively, you could try the update yourself, although this will be unsupported without Oracle agreement.

1. Export Variables

• export thisJar=com.bea.cie.patch-client_3.2.0.0.jar
• export ModuleDir=$MIDDLEWARE_HOME/modules

2. Extract Code

• mkdir $ModuleDir/temp
• cd $ModuleDir/temp
• cp ../$thisJar .
• jar –xvf $thisJar

3. Update properties file

• vi ws.properties # add the ‘s’

4. Package Code

• jar –cvf com.bea.cie.patch-client_3.2.0.0.jar *
• cp –f $thisJar ../

NOTE: Thanks to Ray Smith for this update.

Register for Security Updates Screen

Description

On some platforms it is not possible to un-tick the box I want to receive security updates via My Oracle Support. Clicking on the tick button to un-tick the box, results in the tick disappearing for a second before automatically reappearing. In effect, the installer forces the selection of the I want to receive security updates via My Oracle Support box.

If the install is being carried out behind a firewall this has the unfortunate side effect of the installer hanging for a long period of time as it tries to make a direct connection to My Oracle Support. Eventually, the installer will time out and display the Choose Install Type screen allowing you to progress the install.

Fix

None currently. Be patient and wait for the installer to timeout.

ADDENDUM I have noticed on some platforms, that the installer will eventually time out and display the following screen.

At this point it is possible to select I wish to remain uniformed of security issues in my configuration or this machine has no internet access., click continue and move onto the Choose Install Type screen.

My Oracle Support Details Screen

Description

The first screen of the Grid Control Install, namely the My Oracle Support Details Screen does not allow you to enter proxy details before specifying your Metalink credentials. Therefore, having specified your Metalink credentials and clicked on the Next button, if you are behind a firewall there will be a long pause in the install whilst the installer tries to make a direct connection to My Oracle Support. Eventually, the installer will timeout and display the Connection Failed:0 screen whereby you will be able to enter proxy server details.

Fix

None currently. Be patient and wait for the installer to timeout.

Check for Updates Screen

Description

Once the Check for Updates screen has been displayed and after having setup valid proxy server details via the Proxy Server Settings button, it is not possible to click on the Test Connection button nor the Next button from the Check for Updates screen. Both buttons seem dead.

Fix

Currently, the only known work around for this problem is to select the Skip Software Updates radio and then click Next. This has the obvious disadvantage of not being able to check for updates.

Error Messages Reported in Grid Control Local Agent Log Files.

Description

After a clean install of Grid Control the local Grid Control agent writes a number of errors and warnings to the following logs.

• emagent.trc
• emagent_perl.trc
• emagentfetchlet.trc

Fix

The following table details the errors and warnings with the proposed action required for each.