Database Reference
In-Depth Information
Ensure you read the additional certification information for your platform by clicking on the link named after
your platform to find out more about mandatory patches for the OMS, or the operating system or both. In the
remaining chapter Linux x86-64 will be used for the management host and repository database server. For this
chapter it is assumed that a suitable and certified database is available for the installation of the repository. Refer back
to the section “Sizing considerations” for more information about the repository database.
Whichever operating system you choose, please ensure that you download the software for your platform, and
unzip it in a suitable location. This chapter assumes that
/mnt
has been used to mount the installation media via NFS.
Preparing the Linux Operating System
As with the database, the operating system must be prepared for the installation of the Management Service. Before
you begin to be more serious about the installation process you should consider which user account will own the
OMS installation. In most situations this will be the Oracle account, which is created similar to a database installation.
First, create the inventory group-
oinstall
, then the oracle account if they have not already been created by the build
process. Please consult your standards document to check if there are fixed numeric IDs for these groups, especially
if you are using directory services. For any Oracle deployment it is very desirable to use the same user and group IDs
throughout the enterprise. Alternatively you could simply use the RDBMS preinstall RPM which will always create the
oracle user and groups in the same way.
[root@oem12oms1 ~]# groupadd oinstall
[root@oem12oms1 ~]# useradd -g oinstall -G oinstall oracle
[root@oem12oms1 ~]# passwd oracle
Note that groups
dba
and
oper
are not needed for the installation of a Management Service. In the next step you
should review the use of SELinux and iptables for host-based firewalls. Configuration of these is outside the scope
of this section, for the sake of simplicity it is assumed that the firewalls are deactivated, and SELinux is in permissive
mode. A production system should obviously be better protected, and you have to check with the security team about
the correct settings!
You can either go through the list of prerequisites manually or use the prerequisite checker which is part of the
installation source. In order to run the prerequisite check, change to the location where you unzipped the installation
media. The prerequisite checker resides in the
./install
directory, and has to be invoked as in this example:
[oracle@oem12oms1 stage]$ ./install/runInstaller -prereqchecker \
> PREREQ_CONFIG_LOCATION=../stage/prereq \
> -entryPoint oracle.sysman.top.em_noseed_Core -prereqLogLoc /tmp -silent
Starting Oracle Prerequisite Checker...
[...]
Oracle Prerequisite Checker version Version 11.1.0.9.0 Production
Copyright (C) 1999, 2012, Oracle. All rights reserved.
Starting execution of Prerequisites...
Total No of checks: 11
Performing check for CertifiedVersions
S_CHECK_CERTIFIED_VERSIONS
Expected result: One of enterprise-5.6,enterprise-6.2,enterprise-6.0,redhat-6.2,
redhat-6.0,redhat-5.6,enterprise-5.5,enterprise-5.4,enterprise-5.3,enterprise-5.2,
enterprise-5.1,enterprise-5,asianux-3,redhat-5.5,redhat-5.4,redhat-5.3,redhat-5.3,
redhat-5.2,redhat-5.1,redhat-5,SuSE-11,SuSE-10
Actual Result: enterprise-5.6
Check complete. The overall result of this check is: Passed
Search WWH ::
Custom Search