| Oracle® Audit Vault Collection Agent Installation Guide Release 10.3 Part Number E23588-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Audit Vault Collection Agent Installation Guide Release 10.3 Part Number E23588-04 |
|
|
PDF · Mobi · ePub |
This chapter describes Oracle Audit Vault collection agent preinstallation requirements. This chapter includes the following sections:
Preinstallation Requirements for Linux and UNIX-Based Platforms
Preinstallation Requirements for the Microsoft Windows 64-Bit (x64) Platform
Oracle Audit Vault Collection Agent Hardware and Software Certification
This section describes the following preinstallation tasks:
To plan the installation process, you must be familiar with the features of Oracle Audit Vault. Oracle Audit Vault Administrator's Guide discusses the basic features of Oracle Audit Vault.
Before you install the Oracle software, you must complete several tasks described in the sections that follow as the root user. Log in to your system as the root user.
This section describes the following preinstallation tasks:
The system must meet the following minimum hardware requirements:
At least 512 MB of available physical memory (RAM)
Swap space of 1024 MB or twice the size of RAM
400 MB of disk space in the /tmp directory
1 GB of disk space is required for the Oracle Audit Vault collection agent software.
Minimum display requirements is a resolution of 1024 x 768 or higher.
To ensure that the system meets these requirements, perform the following tasks.
To determine the physical RAM size, enter the following command:
# grep MemTotal /proc/meminfo
If the size of the physical RAM is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# grep SwapTotal /proc/meminfo
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
To determine the available RAM and swap space, enter the following command:
# free
Note:
Oracle recommends that you take multiple values for the available RAM and swap space before determining a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.To determine the amount of disk space available in the /tmp directory, enter the following command:
# df -k /tmp
If there is less than 400 MB of free disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TEMP and TMPDIR environment variables when setting the oracle user's environment to point to a directory path with at least 400 MB available.
Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# df -k
To determine whether the system architecture can run the software, enter the following command:
# grep "model name" /proc/cpuinfo
Note:
This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install. If you do not see the expected output, then you cannot install the software on this system.Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.
Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at
https://support.oracle.com
If you do not have a current Oracle Support Services contract, then you can access the same information at
http://www.oracle.com/technology/support/metalink/content.html
Note:
Oracle recommends that you install your Linux operating system with the default software packages (RPMs), unless you specifically intend to perform a minimal installation, and follow the directions for performing such an installation to ensure that you have all required packages for Oracle software.
Oracle recommends that you do not customize RPMs during a default operating system installation. A default installation includes most required packages, and helps you to limit manual checks of package dependencies.
If you did not perform a default Linux installation, you intend to use LDAP, and you want to use the scripts odisrvreg, oidca, or schemasync, then install the Korn shell RPM for the Linux distribution.
You must install the packages (or later versions) listed in the following table. Also, ensure that the list of RPMs and all of the prerequisites for these RPMs are installed.
Important:
If you are using Oracle Unbreakable Enterprise Kernel, then all required kernel packages are installed as part of the Oracle Unbreakable Enterprise Kernel installation
To ensure that the system meets these requirements, perform the following tasks.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /proc/version
Note:
Only the distributions and versions listed in the previous table are supported. Do not install the software on other versions of Linux.To determine whether the required kernel is installed, enter the following command:
# uname -r
The following is a sample output displayed by running this command on an Oracle Linux 5.0 system:
2.6.18-128.el5PAE
In this example, the output shows the kernel version (2.6.18) and errata level (-128.el5PAE) on the system.
If the kernel version does not meet the requirement specified earlier in this section, then contact the operating system vendor for information about obtaining and installing kernel updates.
To determine whether the required packages are installed, enter commands similar to the following:
# rpm -q package_name
If a package is not installed, then install it from your Linux distribution media or download the required package version from the Web site of your Linux vendor.
This section describes the following preinstallation tasks:
Checking the Hardware Requirements for Solaris Operating System (SPARC 64-Bit)
Checking the Operating System Requirements for Solaris Operating Systems (SPARC 64-Bit)
The system must meet the following minimum hardware requirements:
At least 512 MB of available physical memory (RAM)
Swap space of 1024 MB or twice the size of RAM
400 MB of disk space in the /tmp directory
1 GB of disk space for the Oracle Audit Vault collection agent software
To ensure that the system meets these requirements, perform the following tasks.
To determine the physical RAM size, enter the following command:
# /usr/sbin/prtconf | grep "Memory size"
If the size of the physical RAM is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swap -s
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
To determine the amount of disk space available in the /tmp directory, enter the following command:
# df -k /tmp # df -h /tmp (on Solaris 10)
If there is less than 400 MB of free disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment to point to a directory path with at least 400 MB available.
Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# df -k # df -h (on Solaris 10)
To determine whether the system architecture can run the software, enter the following command:
# /bin/isainfo -kv
Note:
The following is the expected output of this command:64-bit sparcv9 kernel modules
If you do not see the expected output, then you cannot install the software on this system.
Verify that the following software is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.
Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at
https://support.oracle.com
If you do not have a current Oracle Support Services contract, then you can access the same information at
http://www.oracle.com/technology/support/metalink/content.html
| Item | Requirement |
|---|---|
| Operating system | One of the following 64-bit operating system versions:
|
| Packages |
SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs (ISO8859-1) SUNWi15cs (ISO8859-15) SUNWxwfnt SUNWcslYou may also require additional font packages for Java, depending on your locale. Refer to the following Web site for more information: http://java.sun.com/j2se/1.4.2/font-requirements.html |
To ensure that the system meets these requirements, perform the following tasks.
To determine which version of Solaris is installed, enter the following command:
# uname -r 5.10
In this example, the version shown is Oracle Solaris 10 (5.10). If necessary, refer to your operating system documentation for information about upgrading the operating system.
To determine whether the required packages are installed, enter a command similar to the following:
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot \ SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
If a package is not installed, then install it. Refer to your operating system or software documentation for information about installing packages.
You can use the following command to verify the update level of the operating system:
$ cat /etc/release
In addition, you must verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed.| Installation Type or Product | Requirement |
|---|---|
| All installations | Patches for Oracle Solaris 10: :
|
| Pro*C/C++, Pro*FORTRAN, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) | Patches For Oracle Solaris 10:
|
| Database Smart Flash Cache (An Enterprise Edition only feature) | The following patches are required for Oracle Solaris on SPARC (64-Bit) if you are using the flash cache feature:
125555-03 140796-01 140899-01 141016-01 139555-08 141414-10 141736-05 |
To determine whether an operating system patch is installed, enter a command similar to the following:
# /usr/sbin/patchadd -p | grep patch_number(without version number)
For example, to determine if any version of the 119963 patch is installed, use the following command:
# /usr/sbin/patchadd -p | grep 119963
If an operating system patch is not installed, then download it from the My Oracle Support Web site and install it:
https://support.oracle.com/
This section describes the following preinstallation tasks:
The system must meet the following minimum hardware requirements:
At least 512 MB of available physical memory (RAM)
Swap space of 1024 MB or twice the size of RAM
400 MB of disk space in the /tmp directory
Up to 1.5 GB of disk space required for the Oracle Audit Vault collection agent software.
To ensure that the system meets these requirements, perform the following tasks.
To determine the physical RAM size, enter the following command:
# /usr/sbin/lsattr -E -l sys0 -a realmem
If the size of the physical RAM is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/lsps -a
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
To determine the amount of disk space available in the /tmp directory, enter the following command:
# df -k /tmp
If there is less than 400 MB of free disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment to point to a directory path with at least 400 MB available.
Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# df -k
To determine whether the system architecture can run the software, enter the following command:
# /usr/bin/getconf HARDWARE_BITMODE 64
Note:
The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.
Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at
https://support.oracle.com
If you do not have a current Oracle Support Services contract, then you can access the same information at
http://www.oracle.com/technology/support/metalink/content.html
| Item | Requirement |
|---|---|
| Operating system | The following operating system versions and maintenance level are required:
AIX 5L V5.3 TL 09 SP1 ("5300-09-01"), 64 bit kernel AIX 6.1 TL 02 SP1 ("6100-02-01), 64-bit kernel AIX 7.1 TL 0 SP1 ("7100-00-01"), 64-bit kernel |
| Operating system file sets: | The following operating system file sets are required for AIX 5L:
bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat 5.3.9.0 or later bos.perf.perfstat bos.perf.proctools xlC.aix50.rte:10.1.0.0 or later gpfs.base 3.2.1.8 or later The following operating system filesets are required for AIX 6.1: bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat 6.1.2.1 or later bos.perf.perfstat bos.perf.proctools xlC.aix61.rte:10.1.0.0 or later xlC.rte.10.1.0.0 or later gpfs.base 3.2.1.8 or later The following operating system filesets are required for AIX 7.1: bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat bos.perf.perfstat bos.perf.proctools xlC.aix61.rte:10.1.0.0 or later xlC.rte:10.1.0.0 or later gpfs.base 3.3.0.11 or later |
| PL/SQL native compilation | One of the following:
Note: If you do not install the IBM XL C/C++ Enterprise Edition V7.0 compiler, you must install the IBM XL C/C++ Enterprise Edition V7.0 for AIX Run-time Environment Component. The run-time environment file sets can be downloaded with no license requirements from |
| Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) |
Note: If you do not install the IBM XL C/C++ Enterprise Edition V7.0 compiler, you must install the IBM XL C/C++ Enterprise Edition V7.0 for AIX Run-time Environment Component.The minimum recommended runtime environment for AIX 5.3 and AIX 6.1 is available at the following URL: IBM XL C/C++ for AIX, V10.1 Runtime Environment
|
| Oracle JDBC/OCI Drivers | You can use the following optional IBM JDK versions with the Oracle JDBC/OCI drivers; however, they are not required for the installation:
Note: IBM JDK 1.5 is installed with this release. |
To ensure that the system meets these requirements, perform the following tasks.
To determine the version of AIX installed, enter the following command:
# oslevel -s
For AIX 5L: If the operating system version is lower than AIX 5.3 Technology Level 9 SP 1, then upgrade your operating system to this or a later, level.
For AIX 6.1: If the operating system version is lower than AIX 6.1 Technology Level 2 SP 1, then upgrade your operating system to this or a later, level.
For AIX 7.1: If the operating system version is lower than AIX 7.1 Technology Level 0 SP 1, then upgrade your operating system to this or a later, level.
AIX maintenance packages are available from the following Web site:
To determine whether the required file sets are installed and committed, enter a command similar to the following:
# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \ bos.perf.libperfstat bos.perf.proctools
If a file set is not installed and committed, then install it. Refer to your operating system or software documentation for information about installing file sets.
In addition, you must verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed.To ensure that the system meets these requirements, perform the following tasks:
To determine whether an APAR is installed, enter a command similar to the following:
# /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319"
If an APAR is not installed, then download it from the following Web site and install it:
If you require a Fix pack (formerly CSD) for WebSphere MQ, then refer to the following Web site for download and installation information:
http://www-947.ibm.com/support/entry/portal/Downloads/Software/WebSphere/WebSphere_MQ
This section describes the following preinstallation tasks:
The system must meet the following minimum hardware requirements:
At least 512 MB of available physical memory (RAM)
Swap space of 1024 MB or twice the size of RAM
400 MB of disk space in the /tmp directory
1.5 GB of disk space for the Oracle Audit Vault collection agent software
To ensure that the system meets these requirements, perform the following tasks.
To determine the physical RAM size, enter the following command:
# /usr/contrib/bin/machinfo | grep -i Memory
If the size of the physical RAM is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swapinfo -a
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
To determine the amount of disk space available in the /tmp directory, enter the following command:
# bdf /tmp
If there is less than 400 MB of free disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment to point to a directory path with at least 400 MB available.
Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# bdf
To determine whether the system architecture can run the software, enter the following command:
# /bin/getconf KERNEL_BITS
Note:
The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.Verify that the following software, or a later version, is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.
Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at
https://support.oracle.com
If you do not have a current Oracle Support Services contract, then you can access the same information at
http://www.oracle.com/technology/support/metalink/content.html
To ensure that the system meets these requirements, perform the following tasks.
To determine which version of HP-UX is installed, enter the following command:
# uname -a
HP-UX hostname B.11.31 ia64 4156074294 unlimited-user license
In this example, the version of HP-UX 11i is 11.31.
To determine whether a bundle, product, or file set is installed, enter a command similar to the following, where level is bundle, product, or fileset:
# /usr/sbin/swlist -l level | more
If a required bundle, product, or file set is not installed, then you must install it. Refer to your operating system or software documentation for information about installing products.
In addition, you must verify that the following patches, or their later versions, are installed on the system. The procedure following the table describes how to check these requirements.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed.| Installation Type or Product | Requirement |
|---|---|
| All installations | The following operating system patches are required for HP-UX 11i V3 (11.31)::
The following operating system patch is required for HP-UX 11i V3 (11.31) VERITAS File System:
Note: The VERITAS file system is optional. This patch is required only if you want to use a VERITAS File System 5.0. |
| PL/SQL native compilation, Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) | The following C and C++ patches:
|
To determine whether a patch is installed, enter a command similar to the following:
# /usr/sbin/swlist -l patch | grep PHSS_37959
Alternatively, to list all installed patches, enter the following command:
# /usr/sbin/swlist -l patch | more
If a required patch is not installed, then download it from the following Web site and install it:
If the Web site shows a more recent version of the patch, then download and install that version.
Kernel Parameters
The following Kernel Parameters are obsolete on HP-UX 11i v3 (11.31):
maxswapchunks msgmap ncallout semmap vx_ncsize
Creating Required Symbolic Links
Note:
This task is required only if the Motif 2.1 Development Environment package (X11MotifDevKit.MOTIF21-PRG) is not installed.To enable you to successfully relink Oracle products after installing this software, enter the following commands to create the required X library symbolic links in the /usr/lib directory:
# cd /usr/lib # ln -s libX11.3 libX11.sl # ln -s libXIE.2 libXIE.sl # ln -s libXext.3 libXext.sl # ln -s libXhp11.3 libXhp11.sl # ln -s libXi.3 libXi.sl # ln -s libXm.4 libXm.sl # ln -s libXp.2 libXp.sl # ln -s libXt.3 libXt.sl # ln -s libXtst.2 libXtst.sl
Depending on whether you are installing Oracle software for the first time on this system and on the products that you are installing, you may need to create the following operating system group and user:
The Oracle Inventory group (oinstall)
You must create this group the first time you install Oracle software on the system. The usual name chosen for this group is oinstall. This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.
Note:
If Oracle software is already installed on the system, then the existing Oracle Inventory group must be the primary group of the operating system user that you use to install new Oracle software. The following sections describe how to identify an existing Oracle Inventory group.The Oracle software owner user (typically, oracle)
You must create this user the first time you install Oracle software on the system. This user owns all software installed during the installation. This user must have the Oracle Inventory group as its primary group.
Note:
In Oracle documentation, this user is referred to as theoracle user.All installations of Oracle software on the system require a single Oracle Inventory group. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users for separate installations. By using different groups for different installations, members of these different groups have DBA privileges only on the associated databases, rather than on all databases on the system.
Note:
The following topics describe how to create local users and groups. As an alternative to creating local users and groups, you could create the appropriate users and groups in a directory service, for example, Network Information Services (NIS). For information about using directory services, contact your system administrator or see your operating system documentation.The following topics describe how to create the required operating system users and groups:
You must create the Oracle Inventory group if it does not already exist. The following topics describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary.
Determining Whether the Oracle Inventory Group Exists
When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group and the path of the Oracle Inventory directory.
To determine whether the Oracle Inventory group exists, enter the following command:
For SPARC (64-Bit)
# more /var/opt/oracle/oraInst.loc
For AIX Systems
# more /etc/oraInst.loc
For Linux x86-64
# more /etc/oraInst.loc
For HP-UX Itanium
# more /var/opt/oracle/oraInst.loc
If the output of this command shows the oinstall group name, then the group already exists.
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inst_group parameter shows the name of the Oracle Inventory group, oinstall.
Creating the Oracle Inventory Group on All Systems Except AIX Systems
If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering the following command:
# /usr/sbin/groupadd oinstall
Creating the Oracle Inventory Group on AIX Systems
If the oraInst.loc file does not exist, then create the Oracle Inventory group by using the following procedure:
Enter the following command:
# smit security
Choose the appropriate menu items to create the oinstall group.
Press F10 to exit.
You must create an Oracle software owner user in the following circumstances:
If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system
If an Oracle software owner user exists, but you want to use a different operating system user, with a different group membership, to give database administrative privileges to those groups in a new Oracle installation
To determine whether an Oracle software owner user named oracle exists, enter the following command:
For SPARC (64-Bit)
# id -a oracle
For AIX Systems
# id oracle
For Linux x86-64
# id oracle
For HP-UX Itanium
# id oracle
If the oracle user exists, then the output from this command is similar to the following:
uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
If the user exists, then determine whether you want to use the existing user or create another oracle user. If you want to use the existing user, then ensure that the primary group of the user is the Oracle Inventory group.
Note:
If necessary, contact your system administrator before using or modifying an existing user.Refer to one of the following sections for more information:
To modify an existing user, see Section 2.1.7.2.3.
To create a user, refer to the following section.
If the Oracle software owner user does not exist or if you need a new Oracle software owner user, then create it as follows. In the following procedure, use the user name oracle unless a user with that name already exists.
To create the oracle user, enter a command similar to the following:
# /usr/sbin/useradd -g oinstall oracle
In this command:
The -g option specifies the primary group, which must be the Oracle Inventory group, for example, oinstall.
Set the password of the oracle user:
# passwd oracle
See Section 2.1.7.3 to continue.
If the oracle user exists, but its primary group is not oinstall or it is not a member of the appropriate OSDBA or OSOPER groups, then enter a command similar to the following to modify it. Specify the primary group using the -g option and any required secondary group using the -G option:
# /usr/sbin/usermod -g oinstall oracle
See Section 2.1.7.3 to continue.
If the Oracle software owner user does not exist or if you require a new Oracle software owner user, then create it as follows. In the following procedure, use the user name oracle unless a user with that name already exists.
# smit security
Choose the appropriate menu items to create the oracle user, specifying the following information:
In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.
Press F10 to exit.
Set the password of the oracle user:
# passwd oracle
See Section 2.1.7.3 to continue.
If the oracle user exists, but its primary group is not oinstall, then you can modify it as follows:
Enter the following command:
# smit security
Choose the appropriate menu items to modify the oracle user.
In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.
Press F10 to exit.
See Section 2.1.7.3 to continue.
Before installing the software, perform the following procedure to verify that the nobody user exists on the system:
To determine whether the user exists, enter the following command:
# id nobody
If this command displays information about the nobody user, then you do not have to create that user.
If the nobody user does not exist, then enter the following command to create it:
For All Systems Except AIX Systems
# /usr/sbin/useradd nobody
For AIX Systems
# smit security
Specify the appropriate options to create an unprivileged nobody user, then press F10 to exit.
You must identify or create the following directories for the Oracle software:
The Oracle base directory is a top-level directory for Oracle software installations. On Linux and UNIX-based systems, the Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:
/mount_point/app/oracle_sw_owner
mount_point is the mount point directory for the file system that will contain the Oracle software.
The examples in this guide use /u01 for the mount point directory. However, you could choose another mount point directory, such as /oracle or /opt/oracle.
oracle_sw_owner is the operating system user name of the Oracle software owner, for example, oracle.
You can use the same Oracle base directory for more than one installation, or you can create separate Oracle base directories for different installations. If different operating system users install Oracle software on the same system, then each user must create a separate Oracle base directory. The following example Oracle base directories could all exist on the same system:
/u01/app/oracle /u01/app/orauser /opt/oracle/app/oracle
The following sections describe how to identify existing Oracle base directories that may be suitable for your installation and how to create an Oracle base directory if necessary.
Regardless of whether you create an Oracle base directory or decide to use an existing one, you must set the ORACLE_BASE environment variable to specify the full path to this directory.
The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required by, and shared by, all Oracle software installations on a single system. The first time you install Oracle software on a system, Oracle Universal Installer prompts you to specify the path to this directory. Oracle recommends that you choose the following path:
oracle_base/oraInventory
Oracle Universal Installer creates the directory that you specify and sets the correct owner, group, and permissions for it. You do not need to create it.
Note:
All Oracle software installations rely on this directory. Ensure that you back it up regularly.Do not delete this directory unless you have completely removed all Oracle software from the system.
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory and a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:
oracle_base/product/10.2.3/av_1
Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not need to create this directory.
Before starting the installation, you must either identify an existing Oracle base directory or if required, create one. This section contains the following topics:
Note:
You can choose to create an Oracle base directory, even if other Oracle base directories exist on the system.Existing Oracle base directories may not have paths that comply with Optimal Flexible Architecture (OFA) guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, then you can usually identify the Oracle base directories, as follows:
To identify an existing Oracle Inventory directory
Enter the following command to view the contents of the oraInst.loc file:
For SPARC (64-Bit)
# more /var/opt/oracle/oraInst.loc
For AIX Systems
# more /etc/oraInst.loc
For Linux x86-64
# more /etc/oraInst.loc
For HP-UX Itanium
# more /var/opt/oracle/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inventory_loc parameter identifies the Oracle Inventory directory (oraInventory). The parent directory of the oraInventory directory is typically an Oracle base directory. In the previous example, /u01/app/oracle is an Oracle base directory.
To identify existing Oracle home directories
Enter the following command to view the contents of the oratab file:
For SPARC (64-Bit)
# more /var/opt/oracle/oratab
For AIX Systems
# more /etc/oratab
For Linux x86-64
# more /etc/oratab
For HP-UX Itanium
# more /etc/oratab
If the oratab file exists, then it contains lines similar to the following:
*:/u03/app/oracle/product/1.0.0/db_1:N *:/opt/orauser/infra_904:N *:/oracle/9.2.0:N
The directory paths you specify on each line identify Oracle base directories. Directory paths that end with the user name of the Oracle software owner that you want to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, then you could choose one of the following directories from the previous example:
/u03/app/oracle /oracle
Note:
If possible, choose a directory path similar to the first (/u03/app/oracle). This path complies with the OFA guidelines.Before deciding to use an existing Oracle base directory for this installation, ensure that it satisfies the following conditions:
It should not be on the same file system as the operating system.
It must have sufficient free disk space as described in the hardware requirements section of each respective platform.
To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:
For SPARC (64-Bit)
# df -k oracle_base_path
For AIX Systems
# df -k oracle_base_path
For Linux x86-64
# df -h oracle_base_path
For HP-UX Itanium
# bdf oracle_base_path
If an Oracle base directory does not exist on the system or if you want to create an Oracle base directory, then complete the steps in Section 2.1.9.2.
Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space.
To identify an appropriate file system:
Use the df -k or bdf command to determine the free disk space on each mounted file system.
From the display, identify a file system that has appropriate free space.
Note the name of the mount point directory for the file system that you identified.
To create the Oracle base directory and specify the correct owner, group, and permissions for it:
Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified, and set the appropriate owner, group, and permissions on them:
# mkdir -p /mount_point/app/oracle_sw_owner # chown -R oracle:oinstall /mount_point/app/oracle_sw_owner # chmod -R 775 /mount_point/app/oracle_sw_owner
For example, if the mount point you identify is /u01 and oracle is the user name of the Oracle software owner, then the recommended Oracle base directory path is:
/u01/app/oracle
When you configure the environment of the oracle user (see Section 2.1.7), set the ORACLE_BASE environment variable to specify the Oracle base directory that you created.
Before you begin the Oracle Audit Vault collection agent installation, you should check to see that the DISPLAY environment variable is set to a proper value. For example, for the Bourne, Bash, or Korn shell, you would enter the following commands, where myhost.us.example.com is your host name:
$ export DISPLAY=myhost.us.example.com:1.0
For example, for the C shell, you would enter the following command, where myhost.us.example.com is your host name:
% setenv DISPLAY myhost.us.example.com:1.0
Ensure the NLS_LANG environment variable is not set.
For example, for C shell:
unsetenv NLS_LANG
For example, for Bourne, Bash, or Korn shells:
unset NLS_LANG
This section describes the following preinstallation tasks:
Checking the Hardware Requirements for the Microsoft Windows 64-Bit (x64) Platform
Checking the Software Requirements for the Microsoft Windows 64-Bit (x64) Platform
Table 2-1 shows the Microsoft Windows Server platforms that Oracle Audit Vault collection agent supports for 32-bit versus 64-bit operating systems.
Table 2-1 Audit Vault Collection Agent Support for Microsoft Windows Server Platforms
| Platform | 32-Bit | 64-Bit |
|---|---|---|
|
Microsoft Windows Server 2003 |
32-Bit Collection Agent |
32-Bit Collection Agent |
|
Microsoft Windows Server 2008 |
Not Supported |
64-Bit Collection Agent |
Table 2-2 lists the required hardware components for Oracle Audit Vault collection agent.
Table 2-2 Hardware Requirements
| Requirement | Minimum Value |
|---|---|
|
Physical memory (RAM) |
512 MB minimum, 1 GB recommended |
|
Virtual memory |
Double the amount of RAM |
|
Hard disk space |
453 MB |
|
Video adapter |
256 colors |
|
Screen Resolution |
1024 X 768 minimum |
|
Processor |
AMD64, or Intel Extended memory (EM64T) |
This section lists system requirements for Microsoft Windows platforms that use the NT File System (NTFS) file systems. FAT32 space requirements are slightly larger. Oracle recommends installing Oracle components on NTFS.
The NTFS system requirements listed in this section are more accurate than the hard disk values reported by the Oracle Universal Installer Summary window. The Summary window does not include the space required for the size of compressed files that are expanded on the hard drive.
The hard disk requirements for Oracle Database Client components include space required to install Java Run-time Environment (JRE) and Oracle Universal Installer on the partition where the operating system is installed. If sufficient space is not detected, then the installation fails and an error message appears.
Table 2-3 lists the space requirements for NTFS.
See Also:
"NTFS File System and Microsoft Windows Registry Permissions" in Oracle Database Platform Guide for Microsoft Windows (x64)To ensure that the system meets these requirements, follow these steps:
Determine the physical RAM size. For a computer using Microsoft Windows 2003, for example, open System in the Microsoft Windows Control Panel and select the General tab.
On a Microsoft Windows Server 2008 computer, click System and Security in the Windows Control Panel, then click System.
If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.
Determine the size of the configured virtual memory (also known as paging file size). For a computer using Microsoft Windows 2003, for example, open System in the Control Panel, select the Advanced tab, and click Settings in the Performance section. Then select the Advanced tab.
On a Microsoft Windows Server 2008 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Settings in the Performance section. Then select the Advanced tab on Performance Options page.
The virtual memory is listed in the Virtual Memory section.
If necessary, see your operating system documentation for information about how to configure additional virtual memory.
Determine the amount of free disk space on the system. For a computer using Microsoft Windows 2003, for example, open My Computer, right-click the drive where the Oracle software is to be installed, and choose Properties.
On a Microsoft Windows Server 2008 computer, right-click My Computer and click Open.
Determine the amount of disk space available in the temp directory. This is equivalent to the total amount of free disk space, minus what will be needed for the Oracle software to be installed.
If less than 125 MB of disk space is available in the temp directory, then delete all unnecessary files. If the temp disk space is still less than 125 MB, then set the TEMP or TMP environment variable to point to a different hard drive. For a computer using Microsoft Windows 2003, for example, open System in the Control Panel, select the Advanced tab, and click Environment Variables.
On a Microsoft Windows Server 2008 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Environment Variables.
Table 2-4 lists the software requirements for Oracle Audit Vault collection agent.
Table 2-4 Software Requirements
| Requirement | Value |
|---|---|
|
System architecture |
Processor: AMD64, or Intel Extended memory (EM64T) For additional information, visit My Oracle Support at |
|
Operating system |
Oracle Audit Vault collection agent for x64 Microsoft Windows is supported on the following operating systems:
Note: Microsoft Windows Multilingual User Interface Pack is supported on Microsoft Windows Server 2003. |
|
Network protocol |
The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:
|
The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. This Web site also provides compatible client and database versions, patches, and workaround information for bugs. The My Oracle Support Web site is available at the following URL:
You must register online before using My Oracle Support. After logging in, refer to Article ID 848402.1 for information on the certification matrix.
|
 Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|