Installing Oracle Enterprise Manager 10g Grid Control Rel 5 on Oracle Database 11g and Linux |
| 发表者：admin分类：数据库2015-08-26 11:18:40 阅读[2076] |
Guide: Installing Oracle Enterprise Manager 10g Grid Control Rel 5 on Oracle Database 11g and Linux
by Mike Revitt
Install Oracle Enterprise Manager 10g Grid Control Rel 5 against an existing Oracle 11g database on Oracle Enterprise Linux version 5, step by step.
Published July 2009
Contents
- Introduction
- Prerequisites
- Reference Information
- Creating the Oracle Enterprise Template
- Create Database Virtual Machine from OEL 5.3 Template
- Create Management Service Virtual Machine
- Install Enterprise Manager Grid Control Repository Database (11.1.0.7.0)
- Install Enterprise Manager Grid Control Management Service
- Running Enterprise Manager Grid Control 10.2.0.5
- Install Enterprise Manager Grid Control Agent
1. Introduction
Oracle Enterprise Manager 10g Grid Control Release 2 became available in November 2005 and all subsequent versions are currently deployed as an upgrade to that release. Unfortunately, the pre-requisites for the initial release do not support the current releases of the operating system or database, and the support matrix for 10.2.0.1 requires a 10g Release 1 database.
To alleviate this issue, the current release of Oracle Enterprise Manager (Release 5 at the time of writing) supports a software-only install, allowing the product to be installed against current versions of the operating system and database.
2. Prerequisites
The following is required for this installation method:
2 x servers These servers can be physical or virtual, and although it is possible to install onto a single server, it is not recommended. In this guide I am
using two virtual servers deployed out of Oracle VM 2.1.2.
OEL 5.3 Oracle Enterprise Linux Release 5 update 3; x86 32bit version on DVD
11.1.0.6.0 Oracle Database 11g Release 1
11.1.0.7.0 Oracle Database 11g Release 1 – first patch-set (optional)
10.2.0.1.0 Oracle Enterprise Manager 10g Grid Control Rel 1 software
10.2.0.5.0 Oracle Enterprise Manager 10g Grid Control Rel 5 software and Oracle Enterprise Manager 10g Grid Control Agent Rel 5
Software; this release is fully supported against 11g databases and on the current operating systems.
3. Reference Information
The following information guides and reference documents have been used to compile this guide.
B32281-04 Oracle Database Quick Installation Guide 11g Release 1 (11.1) for Linux x86
E10953-07 Oracle Enterprise Manager Grid Control Installation Guide 10g Release 5 (10.2.0.5.0)
E14503-01 Oracle Enterprise Manager Grid Control Release Notes for Linux and Microsoft Windows 10g Release 5 (10.2.0.5.0)
Note 784963.1 “How to install Grid Control 10.2.0.5.0 on Enterprise Linux 5 Using the Existing Database (11g) Option”
Note 602750.1 “ConfigureGC.pl Reports - Invalid Username/Password”
4. Creating the Oracle Enterprise Template
When installing Oracle products it pays to prepare the environments ahead of time, as the installation will only succeed if all prerequisites have been met.
We start by installing Oracle Enterprise Linux 5 Update 3 (5.3) into a paravirtualized environment. If you already have a prepared OEL Release 5.3 template for use, proceed to the section “ Create Database Virtual Machine from the Linux Template .”
Prepare the DVD
Creating a paravirtualized environment is a little tricky as you cannot create a guest from a local hard disk or CD-ROM using the virtual install command-line tool. You can, however, create an installation tree on the host operating system, and mount it as an NFS share via the following commands:
[oracle@vm-manager Linux]$ su - root Password: [root@vm-manager ~]# mount -o ro,loop /u01/Linux/Enterprise-R5-U3-Server-i386-dvd.iso /u02 [root@vm-manager ~]# exportfs *:/u02 exportfs: No options for /u01/Linux/FC5 : suggest (sync) to avoid warning [root@vm-manager ~]#
Install Oracle Enterprise Linux Release 5 Update 3
Select Create Virtual Machine on the Virtual Machines tab within Oracle VM Manager and then select the following options:
- Create from installation media
- Select a server from the Server Pool
- Select the Paravirtualized virtualization method
- Enter the NFS path to the DVD mount point created earlier. (Use the IP Address rather than the name.)
- Name the machine and set the OS, memory, and disk parameter.
Once the new server has started launch the console and follow the on-screen prompts.
When setting the new partition size select manually create the following three partitions:
- 125MB /boot
- 3074MB swap (The swap file requires 1.5 times memory on servers with up to 2 GB RAM.)
- 4988MB /
Also:
- Give the server a fixed IP address.
- Add the Development Software package and then choose to Customize Later.
- Disable the firewall. (This is not required in our test environment.)
- Disable SELinux. (This is not required in our test environment.)
Do not create a user yet, we will do so after the install has completed.
Add the Missing Libraries
Once the installation has completed we need to install the following packages either from the DVD or from the CDs listed.
CD2
- unixODBC-2.2.11 (32 bit) or later
CD3
- libaio-devel-0.3.106
- sysstat-7.0.0
- libXp-1.0.0-8
- openmotif22-2.2.3-18
- compat-db-4.2.52-5
- unixODBC-devel-2.2.11 (32-bit) or later
To do this extract the files into the /tmp and then issue the following commands:
[root@Grid-DB ~]# rpm –i /tmp/libaio-devel-0.3.106-3.2.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/sysstat-7.0.2-3.el5.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/libXp-1.0.0-8.1.el5.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/openmotif22-2.2.3-18.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/compat-db-4.2.52-5.1.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/unixODBC-2.2.11-7.1.i386.rpm [root@Grid-DB ~]# rpm –i /tmp/unixODBC-devel-2.2.11-7.1.i386.rpm
Paravirtualized environments do not currently support CD or DVD drives so the easiest way to add the missing packages is to launch the DVD via ftp from Firefox.
The next step is to create a link to a library that has undergone a name change from Release 4 to Release 5 of Enterprise Linux:
[root@Grid-DB ~]# [root@Grid-DB ~]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2 [root@Grid-DB ~]#Configure Kernel Parameters
In a default install there are several parameters that require modification (shown below).
First, edit /etc/sysctl.conf and add the following at the the end of the file:
#Oracle Requirements #Mike Revitt 23rd March 2009 kernel.sem = 250 32000 100 128 net.ipv4.ip_local_port_range = 1024 65000 net.core.rmem_default = 4194304 net.core.rmem_max = 4194304 net.core.wmem_default = 262144 net.core.wmem_max = 262144 net.ipv4.tcp_wmem = 262144 262144 262144 net.ipv4.tcp_rmem = 4194304 4194304 4194304
Issue the following command to effect the changes immediately:
[root@Grid-DB ~]# sysctl -p net.ipv4.ip_forward = 0 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 kernel.sysrq = 0 kernel.core_uses_pid = 1 net.ipv4.tcp_syncookies = 1 kernel.msgmnb = 65536 kernel.msgmax = 65536 kernel.shmmax = 4294967295 kernel.shmall = 268435456 kernel.sem = 250 32000 100 128 net.ipv4.ip_local_port_range = 1024 65000 net.core.rmem_default = 4194304 net.core.rmem_max = 4194304 net.core.wmem_default = 262144 net.core.wmem_max = 262144 net.ipv4.tcp_wmem = 262144 262144 262144 net.ipv4.tcp_rmem = 4194304 4194304 4194304Save Template
This step completes the creation of a generic Oracle Enterprise Linux Release 5 Update 3 paravirtualized template.
Shutdown the virtual machine.
Select Save As Template from More Actions:
5. Create Database Virtual Machine from the Linux Template
If necessary, create a new virtual machine from the Oracle Enterprise Linux template.
Create U01 Mount Point
Add a U01 mount point to the new virtual machine by following these steps:
1. Edit the Virtual Machine.
2. Select the Storage tab.
3. Create an 8GB New Virtual Disk. (This will be enough to support the database and agents.)
4. Power On the virtual machine.
5. Connect to the Console and log on as root.
6. Open a terminal and issue the command fdisk –l; this will identify the new disk:
[root@Grid-DB ~]# fdisk -l Disk /dev/xvda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/xvda1 * 1 16 128488+ 83 Linux /dev/xvda2 17 408 3148740 82 Linux swap / Solaris /dev/xvda3 409 1044 5108670 83 Linux Disk /dev/xvdb: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/xvdb doesn't contain a valid partition table
7. Create a primary partition on the device identified above.
[root@Grid-DB ~]# fdisk /dev/xvdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-1044, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-1044, default 1044): Using default value 1044 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.
8. Add a filesystem to the new partition.
[root@Grid-DB ~]# mkfs -t ext3 /dev/xvdb1
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1048576 inodes, 2096474 blocks
104823 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2147483648
64 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@Grid-DB ~]#
Then add the necessary commands to the /etc/fstab file before issuing the mount command to mount the new device as shown below.
[root@Grid-DB ~]# vi /etc/fstab LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 LABEL=SWAP-xvda2 swap swap defaults 0 0 /dev/xvdb1 /u01 ext3 defaults 1 1 [root@Grid-DB ~]# mkdir /u01 [root@Grid-DB ~]# mount /u01 [root@Grid-DB ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda3 4.8G 2.5G 2.1G 55% / /dev/xvda1 122M 13M 104M 11% /boot tmpfs 1.1G 0 1.1G 0% /dev/shm /dev/xvdb1 7.9G 147M 7.4G 2% /u01
Create the Oracle User and Set-up the Environment
The next phase is to create the necessary users and groups and to set up the OS environment for those users.
Create groups and users in-line with OFA guidelines:
[root@Grid-DB ~]# groupadd -g 500 oinstall [root@Grid-DB ~]# groupadd -g 501 dba [root@Grid-DB ~]# groupadd -g 502 asmadmin [root@Grid-DB ~]# groupadd -g 503 oper [root@Grid-DB ~]# useradd -u 500 -g oinstall -G dba,asmadmin,oper -s /bin/bash oracle [root@Grid-DB ~]# passwd oracle Changing password for user oracle. New UNIX password: Retype new UNIX password: passwd: all authentication tokens updated successfully.
Set the Shell limits for the Oracle User; add the following lines at the end of the file:
root@Grid-DB ~]# vi /etc/security/limits.conf #@student - maxlogins 4 #Oracle Parameters #Mike Revitt 23rd March 2009 oracle soft nproc 2047 oracle hard nproc 16384 oracle soft nofile 1024 oracle hard nofile 65536 # End of file
Set the Pluggable Authentication Modules (PAM) limits by adding the following lines at the end of the file indicated.
root@Grid-DB ~]# vi /etc/pam.d/login # pam_selinux.so open should only be followed by sessions to be executed in the user context session required pam_selinux.so open session optional pam_keyinit.so force revoke #Oracle Parameters #Mike Revitt 23rd March 2009 session required pam_limits.so
Set the user limits in the global profile file. (Add the following lines at the end of the file.)
root@Grid-DB ~]# vi /etc/profile
for i in /etc/profile.d/*.sh ; do
if [ -r "$i" ]; then
. $i
fi
done
#Oracle Parameters
#Mike Revitt 23rd March 2009
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
unset i
unset pathmunge
Log on as Oracle and set the following parameters in the local bash profile file.
oracle@Grid-DB ~]# vi .bash_profile
# .bash_profile
umask 022
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
ORACLE_BASE=/u01/app/oracle
PATH=$PATH:$HOME/bin
export ORACLE_BASE PATH
Create the directories and set the permissions:
root@Grid-DB ~]# mkdir –p /u01/app root@Grid-DB ~]# chown oracle:oinstall /u01/app root@Grid-DB ~]# chmod 775 /u01/app
Edit the entries in the hosts file.
root@Grid-DB ~]# vi /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 172.16.47.98 Grid-DB.cougar.eu.com Grid-DB 172.16.47.99 Grid-EM.cougar.eu.com Grid-EM
6. Create Management Service Virtual Machine
One of the really useful features of Oracle VM is the ability to quickly clone environments. Now that we have created our virtual database server we can clone it for the Management Service server rather than having to build another one.
This is done by selecting the Clone option from the More Actions dropdown and following the prompts.
Set Management Service Server IP address and Host Name
The clone process creates the new server with the IP Address obtained via DHCP and does not alter the host name.
To modify these parameters follow these steps:
1. Start up the new virtual server.
2. Open the console and log on as root.
3. Edit the network file and make the following changes to the hostname:
root@Grid-DB ~]# vi /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTMANE=Grid-EM.cougar.eu.com GATEWAY=172.16.47.1
4. Edit the Network Interface Card file and make the following changes to the network parameters:
root@Grid-DB ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth0 # Xen Virtual Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes HWADDR=XX:XX:XX:XX:XX:XX #DO NOT CHANGE THIS VALUE IPADDR=172.16.47.99 NETMASK=255.255.255.0
5. Re-boot the server.
7. Install Enterprise Manager Grid Control Repository Database (11.1.0.7.0)
Before we can install any software we need to create a device that is large enough to store the installation files.
Within Oracle VM you can create a shared disk to contain the installation media that is mounted to servers on demand; this is what I will be using.
Alternatively you can use NFS mounts or create a new local disk as detailed in Create U01 Mount Point above. (Note: the servers need to be shut down to add the new storage.)
Install Oracle Database 11g Rel 1 (11.1.0.6)
Log onto the server as the new Oracle account and change directory to the location of the installation files, from there run the runInstaller command.
Launch the Oracle Universal Installer and select the Advanced Installation method. (Note that a default enterprise edition database installation is not sufficient for use as a Grid Control repository; see Ref Note 784963.1.)
Specify these Inventory details and credentials:
| Description | Value |
| Inventory Location | /u01/app/oraInventory |
| Operating System Group Name | oinstall |
Set Installation Type as Custom.
Install locations are shown below. (Use OFA Standards – these should be the defaults.)
| Description | Value |
| Oracle Base | /u01/app/oracle |
| Name: | OraDb11g_home1 |
| Path: | /u01/app/oracle/product/11.1.0/db_1 |
Product–specific prerequisite checks--these must all pass:
Required Product Compoents are shown below
| Checkbox | Component Name |
| √ | Oracle Database 11g |
| √ | Enterprise Edition Options |
| Oracle Advanced Security | |
| √ | Oracle Partitioning |
| Oracle Spatial | |
| Oracle Label Security | |
| Oracle OLAP | |
| Data Mining RDBMS Files | |
| Database Vault option | |
| Real Application Testing | |
| √ | Oracle Net Services |
| √ | Oracle Net Listener |
| Oracle Connection Manager | |
| √ | Oracle Call Interface |
| Oracle Programmer | |
| √ | Oracle XML Development Kit |
| Oracle ODBC Driver | |
| Oracle Configuration Manager |
Privileged Operating System Groups are as follows:
| Description | Value |
| Database Administrator (OSBDA) Group: | dba |
| Database Operator (OSOPER) Group: | oper |
| ASM Administrator (OSASM) Group: | asmadmin |
It is important not to create the database at this time as the default enterprise edition database installation is not sufficient for use as a Grid Control repository (as detailed in reference Note 784963.1); select Install Database Software Only.
Once the binaries have been installed, some scripts are created that need to be run as the user root:
[root@Grid-DB u02]#
[root@Grid-DB u02]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory to 770.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete
[root@Grid-DB u02]# /u01/app/oracle/product/11.1.0/db_1/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.1.0/db_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/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.
Finished product-specific root actions.
[root@Grid-DB u02]#
Install Oracle Database 11g Patchset 1 (11.1.0.7)
Log onto the server as the Oracle account and change directory to the location of the patch files, from there run the runInstaller command.
Select the Home Details. (Note: this will default to a new home if not selected.)
| Description | Value |
| Name: | OraDb11g_home1 |
| Path: | /u01/app/oracle/product/11.1.0/db_1 |
Product-Specific Prerequisite Checks - this check must succeed.
Configuration Scripts - Once the binaries have been installed, some scripts are created that need to be run as the user root:
[root@Grid-DB u02]#
[root@Grid-DB u02]# /u01/app/oracle/product/11.1.0/db_1/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.1.0/db_1
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]:
Entries will be added to the /etc/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.
Finished product-specific root actions.
[root@Grid-DB u02]#
Configure the Listener The next step is to create a listener for the database; this is best done by running the netca command from within the Oracle home environment.
Run the command /u01/app/oracle/product/11.1.0/db_1/bin/netca &.
Add a New Listener.
Enter Listener Name as LISTENER.
Select TCP as Protocol.
Use Standard Port (1521).
Create the Database
The final step is to create the database. To do this it is recommended to use dbca to create a custom database. (Note: Do not Configure Enterprise Manager.)
Run the command /u01/app/oracle/product/11.1.0/db_1/bin/dbca &
Database Information is as follows:
| Database SID | Global Name | REDO Size | Memory % |
| oemgc | oemgc.cougar.eu.com | 50 MB | 40 % |
Select Keep the enhanced 11g default security settings and Enable automatic maintenance tasks under Database Options.
File locations:
| Database SID | Name | Path |
| oemgc | Data Files | /u01/app/oracle |
| Index Files | /u01/app/oracle | |
| Redo Logs | /u01/app/oracle | |
| Archive Logs | /u01/app/oracle | |
| Control Files | /u01/app/oracle |
Character sets:
| Database Character Set | National Character Set | Language | Territory |
| WE8ISO8859P15 | AL16UTF16 | English | United Kingdom |
Configure the Database
Once the database has successfully been built, several database configuration steps are required.
First, edit the oratab file to allow the database to start automatically.
[oracle@Grid-DB Disk1]# vi /etc/oratab # This file is used by ORACLE utilities. It is created by root.sh # and updated by the Database Configuration Assistant when creating # a database. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:< N|Y >: # # The first and second fields are the system identifier and home # directory of the database respectively. The third filed indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # # oemgc:/u01/app/oracle/product/11.1.0/db_1:Y
Adjust the initialization parameter values.
[oracle@Grid-DB Disk1]# sqlplus / as sysdba SQL> ALTER SYSTEM SET session_cached_cursors=200 scope=spfile; SQL> ALTER SYSTEM SET aq_tm_processes=0 scope=spfile; SQL> ALTER SYSTEM SET undo_retention=10800 scope=spfile; SQL> ALTER SYSTEM SET "_b_tree_bitmap_plans"=false scope=spfile; SQL> @$ORACLE_HOME/rdbms/admin/dbmspool.sql Package created. Grant succeeded. SQL> exit
Apply the changes by stopping and starting the database.
8. Install Enterprise Manager Grid Control Management Service
The first step in installing the latest release of EM Grid Control is to install the software-only version of 10g Release 2 followed by a software-only install of 10g Release 5. Once these two releases are installed an automated configuration script is run.
Install Enterprise Manager 10g Grid Control Rel 2 (10.2.0 .1)
Install Enterprise Manager 10g Grid Control Rel 2 with a silent, software-only method as detailed below. All directories should be entered as the full path.
In all examples shown the installation files are located in /u02/gc10201.
Modify the base install response file for the “Grid Control with a new database” install type:
[oracle@Grid-EN ~]# vi response/em_using_existing_db.rsp
Alter the following parameters from the defaults as shown; full descriptions and meanings of these values are given in the response file.
UNIX_GROUP_NAME="oinstall" FROM_LOCATION="/u02/gc10201/oms/Disk1/stage/products.xml" BASEDIR="/u01/app/oracle/product/10.2.0" INSTALLATION_NAME="10gR5" s_reposHost="Grid-DB.cougar.eu.com" s_reposPort="1521" s_reposSID="oemgc" s_reposDBAPwd="Its-a-secret" s_mgmtTbsName=/u01/app/oracle/oemgc/mgmt.dbf s_ecmTbsName=/u01/app/oracle/oemgc/mgmt_ecm_depot1.dbf s_securePassword="Its-a-secret" s_securePasswordConfirm="Its-a-secret" b_lockedSelected=false s_reposPwd="Its-a-secret" s_reposPwdConfirm="Its-a-secret"
Create oraInst.loc. The silent install process does not allow the inventory directory to be specified and defaults the location the oracle home directory. Edit the oraInst.loc file as root and add the lines as shown.
[root@Grid-EN ~]# vi /etc/oraInst.loc inventory_loc=/u01/app/oraInventory inst_group=oinstall [root@Grid-EN ~]# mkdir –p /u01/app/oraInventory [root@Grid-EN ~]# chmod 644 /etc/oraInst.loc [root@Grid-EN ~]# chmod 770 /u01/app/oraInventory [root@Grid-EN ~]# cp /etc/oraInst.loc /u01/app/oraInventory/ [root@Grid-EN ~]# chmod 660 /u01/app/oraInventory/oraInst.loc [root@Grid-EN ~]# chown –R oracle:oinstall /u01/app/oraInventory
Install the base release using the following command. (Note: Ensure that ORACLE_BASE is set before running these commands.)
[oracle@Grid-EN ~]# /u02/gc10201/runInstaller -noconfig -ignoreSysPrereqs -silent -responseFile /u02/gc10201/response/em_using_existing_db.rsp use_prereq_checker=falseThis will produce the following output:
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat-3, redhat-4 or SuSE-9
Passed
Checking for Kernel version 2.4.21 Passed
Checking for glibc version glibc-2.3.2-95.3 Passed
Checking swap space: must be greater than 150 MB. Actual 3074 MB Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-03-24_05-03-54PM. Please wait
...[oracle@Grid-EM 10.2.0.1]$ Oracle Universal Installer, Version 10.2.0.1.0 Production
Copyright (C) 1999, 2005, Oracle. All rights reserved.
You can find a log of this install session at:
/u01/app/oraInventory/logs/installActions2009-03-24_05-03-54PM.log
........................................................................... 100% Done.
Loading Product Information
........................................................................... 100% Done.
Analyzing dependencies
........................................................................... 100% Done.
-----------------------------------------------------------------------------
Summary
Global Settings
Source: /u02/gc10201/oms/Disk1/stage/products.xml
Oracle Home: /u01/app/oracle/product/10.2.0/oms10g (oms10g)
Installation Type: Core
Product Languages
English
Space Requirements
/ Required 1.66GB (includes 383MB temporary) : Available 7.94GB
New Installations (224 products)
Oracle Enterprise Manager Grid Console 10.2.0.1.0
.
.
.
Setup in progress (Tue Mar 24 17:08:33 GMT 2009)
........ 100% Done.
Setup successful
End of install phases.(Tue Mar 24 17:08:34 GMT 2009)
WARNING:
The following configuration scripts need to be executed as the "root" user.
#!/bin/sh
#Root script to run
/u01/app/oracle/product/10.2.0/oms10g/allroot.sh
To execute the configuration scripts:
1. Open a terminal window
2. Log in as "root"
3. Run the scripts
4. Return to this window and click "OK" to continue
Starting to execute configuration assistants
The following configuration assistants have not been run. This can happen for following reasons -
either root.sh is to be run before config or Oracle Universal Installer was invoked with the -
noConfig option.
--------------------------------------
The "/u01/app/oracle/ product/10.2.0/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 update this script with passwords
(if any) before executing the same.
The "/u01/app/oracle/product/10.2.0/agent10g/cfgtoollogs/configToolAllCommands" script contains all
commands to be executed by the configuration assistants. This file may be used to run the
configuration assistants outside of OUI. Note that you may have to update this script with passwords
(if any) before executing the same.
--------------------------------------
The installation of Oracle Management Agent was successful.
Please check '/u01/app/oraInventory/logs/silentInstall2009-03-24_05-07-42-PM.log' for more details.
[oracle@Grid-EM 10.2.0.1]$
Once the binaries have been installed, some scripts are created that need to be run as the user root.
[root@Grid-EM ~]# /u01/app/oracle/product/10.2.0/oms10g/allroot.sh
Starting to execute allroot.sh .........
Starting to execute /u01/app/oracle/product/10.2.0/oms10g/root.sh ......
Running Oracle10 root.sh script...
\nThe following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/10.2.0/oms10g
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
\nCreating /etc/oratab file...
Adding entry to /etc/oratab file...
Entries will be added to the /etc/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.
Finished execution of /u01/app/oracle/product/10.2.0/oms10g/root.sh ......
Starting to execute /u01/app/oracle/product/10.2.0/agent10g/root.sh ......
Running Oracle10 root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/10.2.0/agent10g
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]:
Entries will be added to the /etc/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.
Finished product-specific root actions.
Finished execution of /u01/app/oracle/product/10.2.0/agent10g/root.sh ......
[root@Grid-EM ~]#
Install Enterprise Manager 10g Grid Control Rel 5 (10.2.0.5)
Install Enterprise Manager 10g Grid Control Rel 5 with a silent, software-only method as detailed below. All directories should be entered as the full path.
In all examples shown the installation files are located in /u02/gc10205/3731593/Disk1.
First, stop all of the running OPMN processes; these will have been left running by the previous install.
[oracle@Grid-EN ~]# /u01/app/oracle/product/10.2.0/oms10g/opmn/bin/opmnctl stopall [oracle@Grid-EN ~]# cp response/patchset.rsp response/agent_patchset.rsp
Make a copy of the response file that is located in /u02/gc10205/3731593/Disk1/response/patchset.rsp.
[oracle@Grid-EN ~]# cp response/patchset.rsp response/oms_patchset.rsp [oracle@Grid-EN ~]# cp response/patchset.rsp response/agent_patchset.rsp
Modify the OMS response file and Alter the following parameters from the defaults as shown; full descriptions and meanings of these values are given in the response file.
[oracle@Grid-EN ~]# vi response/oms_response.rsp
ORACLE_HOME="/u01/app/oracle/product/10.2.0/oms10g"
b_softwareonly=true
s_sysPassword="Its-a-secret"
sl_pwdInfo={ "Its-a-secret" }
oracle.iappserver.st_midtier:szl_InstanceInformation={ "Its-a-secret" }
Modify the Agent response file and Alter the following parameters from the defaults as shown; full descriptions and meanings of these values are given in the response file.
[oracle@Grid-EN ~]# vi response/agent_response.rsp
ORACLE_HOME="/u01/app/oracle/product/10.2.0/agent10g"
b_softwareonly=true
s_sysPassword="Its-a-secret"
sl_pwdInfo={ "Its-a-secret" }
Install the OMS upgrade using the following command: (Note: Ensure that ORACLE_BASE is set before running these commands.)
[oracle@Grid-EN ~]# /u02/gc10205/3731593/Disk1/runInstaller -noconfig -silent -responseFile /u02/gc10205/3731593/Disk1/response/oms_response.rsp
Once the binaries have been installed, some scripts are created that need to be run as the user root. This script will not give a success message.
[root@Grid-EN ~]# /u01/app/oracle/product/10.2.0/oms10g/root.sh [root@Grid-EN ~]#
Install the Agent upgrade using the following command:
[oracle@Grid-EN ~]# /u02/gc10205/3731593/Disk1/runInstaller -noconfig -silent -responseFile /u02/gc10205/3731593/Disk1/response/agent_response.rsp
Once the binaries have been installed, some scripts are created that need to be run as the user root.
[root@Grid-EM ~]# /u01/app/oracle/product/10.2.0/agent10g/root.sh Finished product-specific root actions. [root@Grid-EM ~]#
Configuring the Grid Control Installation with the ConfigureGC.pl Script
The final step of the install is to run the configuration scripts that were skipped during the install.
As the configuration assistants are run through the progress of the script, ORACLE_HOME/cfgtoollogs/cfgfw/ files will begin to populate with the results of these configuration actions for each Oracle Home in its respective directory (i.e. .../oms10g/ or .../agent10g/). As operational actions (i.e., process start) are taken in the configuration steps, operational logs will be populated in these locations:
.../oms10g/sysman/log/
.../agent10g/sysman/log/
.../oms10g/opmn/logs/
.../oms10g/j2ee/OC4J_EM/log/
.../oms10g/Apache/Apache/logs
The configuration may take around an hour with little command session update at times and will eventually issue a failure message, indicating to look in the .../oms10g/cfgtoollogs/cfgfw/CfmLogger<>.log file. The .../oms10g/cfgtoollogs/cfgfw/CfmLogger<>.log file and the emca_repos_drop<>.log will both show error code ORA-01017 logged.
These faults are tracked via Bug 7483221 and the known workarounds are documented as part of the detailed instructions below.
Preserve and set the PERL5IB environment variable.
[oracle@Grid-EN ~]# export PERL5LIB_BACKUP=$PERL5LIB [oracle@Grid-EN ~]# export PERL5LIB=/u01/app/oracle/product/10.2.0/oms10g/perl/lib/5.6.1
Configure Enterprise Manager Grid Control by running the ConfigureGC.pl script.
[oracle@Grid-EN ~]# /u01/app/oracle/product/10.2.0/oms10g/perl/bin/perl /u01/app/oracle/product/10.2.0/oms10g/sysman/install/ConfigureGC.pl /u01/app/oracle/product/10.2.0
First error:
Base Directory: /u01/app/oracle/product/10.2.0
Starting ito execute Configuration Assistants:
Running the configuration assistants using the following command:
/u01/app/oracle/product/10.2.0/oms10g/oui/bin/runConfig.sh
INV_PTR_LOC=/u01/app/oracle/product/10.2.0/oms10g/oraInst.loc
ORACLE_HOME=/u01/app/oracle/product/10.2.0/oms10g ACTION=configure MODE=perform
COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
RESPONSE_FILE=/u01/app/oracle/product/10.2.0/agent10g/responsefile
perform - mode is starting for action: configure
perform - mode finished for action: configure
You can see the log file: /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/oui/configActions2009-03-
24_07-14-44-PM.log
Configuration Assistants failed with errors. Please check the above log.
For more details also check
/u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/cfgfw/CfmLogger_<latest_time_stamp>.log
[oracle@Grid-EM Disk1]$
Check the log file, shown above, for the indicated error:<
[oracle@Grid-EN ~]# vi ./oms10g/cfgtoollogs/cfgfw/CfmLogger_<latest_time_stamp>.log INFO: oracle.sysman.top.oms:PerformSecureCommand:runCmd:/u01/app/oracle/product/10.2.0/oms10g/sysman/admin/ emdrep/bin/RepManager -connect(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=Grid- DB.cougar.eu.com)(PORT=1521)))(CONNECT_DATA=(SID=oemgc)))-action drop -repos_user SYSMAN -output_file /u01/app/oracle/product/10.2.0/oms10g/sysman/log/emca_repos_drop19_20_31.log have completed with exitCode=50 INFO: oracle.sysman.top.oms:PerformSecureCommand:runCmd:Command Output stdout: 'Enter SYS user's password : Getting temporary tablespace from database... Could not connect to SYS/(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=Grid- DB.cougar.eu.com)(PORT=1521)))(CONNECT_DATA=(SID=oemgc))): ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin)
This is a known bug (7483221); to work around the problem set the SYS password to default and re-run the configuration assistant.
On the Database Server run
[oracle@Grid-DB ~]# sqlplus / as sysdba SQL> ALTER USER sys IDENTIFIED BY default; User altered. SQL> EXIT;On the Management Server re-run the command file
[oracle@Grid-EN ~]# /u01/app/oracle/product/10.2.0/oms10g/perl/bin/perl /u01/app/oracle/product/10.2.0/oms10g/sysman/install/ConfigureGC.pl /u01/app/oracle/product/10.2.0
Monitoring the output
First tail the most recent CfmLogger file and look for the log file.
[root@Grid-EM ~]# cd /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/cfgfw/ [root@Grid-EM ~]# ls –al CfmLogger_*.log -rw------ 1 oracle oinstall 3764 Mar 26 11:25 CfmLogger_2009-03-26_11-25-19-AM.log -rw------ 1 oracle oinstall 4245 Mar 26 11:26 CfmLogger_2009-03-26_11-26-14-AM.log -rw------ 1 oracle oinstall 6231 Mar 26 11:53 CfmLogger_2009-03-26_11-53-21-AM.log -rw------ 1 oracle oinstall 41248 Mar 26 12:37 CfmLogger_2009-03-26_12-31-47-PM.log -rw------ 1 oracle oinstall 9208 Mar 26 12:45 CfmLogger_2009-03-26_12-45-39-PM.log [root@Grid-EM ~]# [root@Grid-EM ~]# tail –f CfmLogger_2009-03-26_12-45-39-PM.log INFO: oracle.sysman.top.oms:PerformSecureCommand:runCmd:/u01/app/oracle/product/10.2.0/oms10g/sysman/admin/ emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=Grid- DB.cougar.eu.com)(PORT=1521)))(CONNECT_DATA=(SID=oemgc))) -action create -repos_user SYSMAN -metalink_username _NOT_AVAILABLE_ -output_file /u01/app/oracle/product/10.2.0/oms10g/sysman/log/emca_repos_create12_45_49.log -ecm_datafile /u01/app/oracle/oemgc/mgmt_ecm_depot1.dbf -datafile /u01/app/oracle/oemgc/mgmt.dbf have completed with exitCode=0
Then Tail the output of this file to monitor the progress.
[root@Grid-EM ~]# cd /u01/app/oracle/product/10.2.0/oms10g/sysman/log/ [root@Grid-EM ~]# tail –f emca_repos_create12_45_49.log Package body created. No errors. No errors. Package body created. No errors. No errors. Package body created.
Once this completes successfully tail the CfmLogger file again.
[root@Grid-EM ~]# cd /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/cfgfw/ [root@Grid-EM ~]# tail –f CfmLogger_2009-03-26_12-45-39-PM.log INFO: oracle.sysman.top.agent:AddingToTargetsXml: Host target INFO: oracle.sysman.top.agent:Adding /u01/app/oracle/product/10.2.0/agent10g/sysman/install/hosttgt.out file to /u01/app/oracle/product/10.2.0/agent10g INFO: oracle.sysman.top.agent:addToTargetsXML:TargetInstaller added target file = /u01/app/oracle/product/10.2.0/agent10g/sysman/install/hosttgt.out to /u01/app/oracle/product/10.2.0/agent10g successfully. INFO: oracle.sysman.top.agent:AddingToTargetsXml: Data base targets INFO: oracle.sysman.top.agent:Adding /u01/app/oracle/product/10.2.0/agent10g/sysman/install/oracledb.out file to /u01/app/oracle/product/10.2.0/agent10g INFO: oracle.sysman.top.agent:addToTargetsXML:TargetInstaller added target file = /u01/app/oracle/product/10.2.0/agent10g/sysman/install/oracledb.out to /u01/app/oracle/product/10.2.0/agent10g successfully. INFO: oracle.sysman.top.agent:AddingToTargetsXml:
Second error:
Configuration Assistants has executed Successfully.
Executing emctl command /u01/app/oracle/product/10.2.0/oms10g/bin/emctl status oms
Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle Management Server is Up.
Stopping the oms inorder to run 10205 oms patch configuration
/u01/app/oracle/product/10.2.0/oms10g/opmn/bin/opmnctl stopall
opmnctl: stopping opmn and all managed processes...
Running OMS patch configuration using /u01/app/oracle/product/10.2.0/oms10g/oui/bin/runConfig.sh
INV_PTR_LOC=/u01/app/oracle/product/10.2.0/oms10g/oraInst.loc
ORACLE_HOME=/u01/app/oracle/product/10.2.0/oms10g ACTION=patchsetConfigure MODE=perform
COMPONENT_XML={oracle.sysman.top.oms.10_2_0_5_0.xml}
RESPONSE_FILE=/u01/app/oracle/product/10.2.0/oms10g/config.rsp
perform - mode is starting for action: patchsetConfigure
perform - mode finished for action: patchsetConfigure
You can see the log file: /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/oui/configActions2009-03-26_03-
36-32-PM.log
10205 OMS Configuration failed with errors. Please check the above log
[oracle@Grid-EM ~]$
Check the log file, indicated above, for the following error.
[oracle@Grid-EN ~]# vi ./oms10g/cfgtoollogs/cfgfw/CfmLogger_< LATEST_TIME_STAMP >.log The plug-in OMS Oneoff Patch Application has successfully been performed ------------------------------------------------------ ------------------------------------------------------ The plug-in Repository Upgrade is running Error occurred while connecting to Repository The plug-in Repository Upgrade has failed its perform method ------------------------------------------------------ The action patchsetConfiguration has failed its perform method ################################################### [root@Grid-EM ~]#
This is also known bug (7483221); to work around the problem set the SYS password back to its original value and re-run the configuration assistant.
On the Database Server run
[oracle@Grid-DB ~]# sqlplus / as sysdba SQL> ALTER USER sys IDENTIFIED BY "Its-as-secret"; User altered. SQL> EXIT;
On the Management Server re-run the command file
[oracle@Grid-EN ~]# /u01/app/oracle/product/10.2.0/oms10g/perl/bin/perl /u01/app/oracle/product/10.2.0/oms10g/sysman/install/ConfigureGC.pl /u01/app/oracle/product/10.2.0
Monitoring the output
Tail the most recent CfmLogger file. Note that this tail may be inactive for considerable periods of time.
[root@Grid-EM ~]# cd /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/cfgfw/
[root@Grid-EM ~]# ls –al CfmLogger_*.log
-rw------ 1 oracle oinstall 3764 Mar 26 11:25 CfmLogger_2009-03-26_11-25-19-AM.log
-rw------ 1 oracle oinstall 4245 Mar 26 11:26 CfmLogger_2009-03-26_11-26-14-AM.log
-rw------ 1 oracle oinstall 6231 Mar 26 11:53 CfmLogger_2009-03-26_11-53-21-AM.log
-rw------ 1 oracle oinstall 41248 Mar 26 12:37 CfmLogger_2009-03-26_12-31-47-PM.log
-rw------ 1 oracle oinstall 9208 Mar 26 12:45 CfmLogger_2009-03-26_12-45-39-PM.log
-rw------ 1 oracle oinstall 9208 Mar 26 12:45 CfmLogger_2009-03-26_12-57-27-PM.log
-rw------ 1 oracle oinstall 9208 Mar 26 12:45 CfmLogger_2009-03-26_12-57-39-PM.log
[root@Grid-EM ~]#
[root@Grid-EM ~]# tail –f CfmLogger_2009-03-26_12-57-39-PM.log
component beehive is already at 10.2.0.5.0
there is not need to do schema upgrade since all components are up to version
Running setSchemaStatus: BEGIN
EMD_MAINTENANCE.SET_VERSION('_UPGRADE_','0','0','SYSTEM',EMD_MAINTENANCE.G_STATUS_CONFIGURED_READY);
END;
Repository Upgrade Successful.
INFO: oracle.sysman.top.oms: Command Error:----------
INFO: oracle.sysman.top.oms:
This should complete successfully with a message similar to the following
Running OMS patch configuration using /u01/app/oracle/product/10.2.0/oms10g/oui/bin/runConfig.sh
INV_PTR_LOC=/u01/app/oracle/product/10.2.0/oms10g/oraInst.loc
ORACLE_HOME=/u01/app/oracle/product/10.2.0/oms10g ACTION=patchsetConfigure MODE=perform
COMPONENT_XML={oracle.sysman.top.oms.10_2_0_5_0.xml}
RESPONSE_FILE=/u01/app/oracle/product/10.2.0/oms10g/config.rsp
perform - mode is starting for action: patchsetConfigure
perform - mode finished for action: patchsetConfigure
You can see the log file: /u01/app/oracle/product/10.2.0/oms10g/cfgtoollogs/oui/configActions2009-03-
26_03-48-32-PM.log
10.2.0.5 OMS patch configuration done
[oracle@Grid-EM ~]$
9. Running Enterprise Manager Grid Control 10.2.0.5
The first task is to determine which ports are used by Grid Control by examining the contents of the port list file.
Once we have the address we can log onto the home page with the user sysman.
The final task is to configure the database for monitoring.
First examine the port list file and find the EM port.
[oracle@Grid-EM ~]$ cat /u01/app/oracle/product/10.2.0/oms10g/install/portlist.ini ;OracleAS Components reserve the following ports at install time. ;As a post-installation step, you can reconfigure a component to use a different port. ;Those changes will not be visible in this file. [System] Host Name = Grid-EM.cougar.eu.com [Ports] Oracle HTTP Server port = 7777 Oracle HTTP Server Listen port = 7778 Oracle HTTP Server SSL port = 8250 Oracle HTTP Server Listen (SSL) port = 4444 Oracle Notification Server Request port = 6003 Oracle Notification Server Local port = 6101 Oracle Notification Server Remote port = 6200 ASG port = 7890 Oracle HTTP Server Diagnostic port = 7200 Application Server Control RMI port = 1850 Log Loader port = 44000 Java Object Cache port = 7000 DCM Discovery port = 7100 Oracle Management Agent Port = 1157 Application Server Control port = 1156 Web Cache HTTP Listen port = 7777 Web Cache HTTP Listen (SSL) port = 8250 Web Cache Administration port = 9400 Web Cache Invalidation port = 9401 Web Cache Statistics port = 9402 Enterprise Manager Central Console Port = 4889 Enterprise Manager Central Console Secure Port = 1159 [oracle@Grid-EM ~]$
Next you need to edit the local hosts file to provide name resolution. Note that the WEB Site will not resolve to the IP Address.
# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 172.16.47.98 grid-db.cougar.eu.com grid-db 172.16.47.99 grid-em.cougar.eu.com grid-em
Connect to Enterprise Manager as the sysman user with the password that was entered in the response files.
10. Install Enterprise Manager Grid Control Agent
The final step is to install the agents.
Install EM 10g Agent Rel 5 (10.2.0.5)
Log onto the server as the Oracle account and change the directory to the location of the Enterprise Manager Grid Control Agent installation files; from there run the runInstaller command.
Launch the Oracle Universal Installer and select the Advanced Installation method. Note that the only subsequent option is to install an Additional Management Agent.
Set the Parent Directory to /u01/app/oracle/product/10.2.0. Note that this is different than the Base Directory.
Product–Specific Prerequisite Checks--these must all pass.
Specify Oracle Management Service Location:
| Description | Value |
| Management Service Host Name: | grid-em.cougar.eu.com |
| Management Service Port: | 4889 |
Specify Agent Registration Password; this is the password that was used in the response file previously:
| Description | Value |
| Password: | Its-a-secret |
Configuration Script
Once the binaries have been installed, some scripts are created that need to be run as the user root:
[root@Grid-DB u02]#
[root@Grid-DB u02]# /u01/app/oracle/product/10.2.0/agent10g/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/10.2.0/agent10g
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]:
Entries will be added to the /etc/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.
Finished product-specific root actions.
[root@Grid-DB u02]#
Configuration Assistants will run automatically once the root scripts have been run.
Configure Database
When you connect to the Databases Target, the oemgc database will be shown as down/unavailable because it has not been registered with the Grid Control Management Service.
Connect to Grid Control.
Configure the Database.
View the Database Properties.
Congratulations; you have just successfully installed 10.2.0.5 Enterprise Manager Grid Control.
Mike Revitt is an Oracle Architect with 20 years experience with Oracle, currently focussing on high availability, consolidation, scalability and virtualisation with considerable experience in Oracle grid and Oracle VM.
转载请标明出处【Installing Oracle Enterprise Manager 10g Grid Control Rel 5 on Oracle Database 11g and Linux 】。
《www.micoder.cc》
虚拟化云计算,系统运维,安全技术服务.
| Tags： | [阅读全文...] |
最新评论