Skip Headers
Oracle® Audit Vault Server Installation Guide
Release 10.2.3 for AIX

Part Number E12406-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Oracle Audit Vault Server Preinstallation Requirements

This chapter describes the following Oracle Audit Vault Server preinstallation requirements. This chapter includes the following sections:

2.1 Becoming Familiar with the Features of Oracle Audit Vault

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.

2.2 Logging In to the System as the root User

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.

2.3 Checking the Hardware Requirements

The system must meet the following minimum hardware requirements:

To ensure that the system meets these requirements:

  1. 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.

  2. 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.

  3. 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.

    • Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.

  4. To determine the amount of free disk space on the system, enter the following command:

    # df -k
    
  5. 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.

2.4 Checking the Operating System Requirements

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.

Note:

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 OracleMetaLink Web site for the most up-to-date list of certified hardware platforms and operating system versions. The OracleMetaLink Web site is available at
https://metalink.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 version 5.2, Maintenance Level 04 or later

AIX 5L version 5.3, Maintenance Level 02 or later

Operating system filesets: The following operating system filesets are required:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
xlC.aix50.rte:7.0.0.4 or later
xlC.rte:7.0.0.1 or later
PL/SQL native compilation One of the following:
  • IBM XL C/C++ Enterprise Edition V7.0 for AIX PTF (7.0.0.2)

  • gcc 3.3.2

Note: If you do not install install the IBM XL C/C++ Enterprise Edition V7.0 compiler, you need to install the IBM XL C/C++ Enterprise Edition V7.0 for AIX Runtime Environment Component. The runtime environment file sets can be downloaded with no license requirements from the following link:

http://www-1.ibm.com/support/docview.wss?uid=swg24009788

Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK)

Note: If you do not install install the IBM XL C/C++ Enterprise Edition V7.0 compiler, you need to install the IBM XL C/C++ Enterprise Edition V7.0 for AIX Runtime Environment Component. The runtime environment file sets can be downloaded with no license requirements from the following link:

http://www-1.ibm.com/support/docview.wss?uid=swg24009788

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:
  • JDK 1.4.2 (64-bit)

  • JDK 1.3.1.11 (32-bit)

  • JDK 1.2.2.18

Note: IBM JDK 1.4.2 (32-bit) is installed with this release.


To ensure that the system meets these requirements:

  1. To determine the version of AIX installed, enter the following command:

    # oslevel -r
    

    If the operating system version is lower than AIX 5.2.0.0 Maintenance Level 1 (5200-01), then upgrade your operating system to this level. AIX 5L version 5.2 maintenance packages are available from the following Web site:

    http://www-912.ibm.com/eserver/support/fixes/

  2. To determine whether the required filesets 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 fileset is not installed and committed, then install it. Refer to your operating system or software documentation for information about installing filesets.

In addition, you need to 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 Authorized Problem Analysis Reports (APARs) for AIX 5L v5.2 ML 04:
  • IY63133: large percentage of CPU time spent in ldata_balance routine

  • IY64978: deadlock with concurrent renaming and unlinking under JFS

  • IY63366: dlsym returns null even for valid symbol in AIX520 ML-4

  • IY64691: chvg -b can cause corruption and crash

  • IY64737: AIO can hang in knotunlock

  • IY65001: mklvcopy on a striped lv is failing to update lvcb

All installations Authorized Problem Analysis Reports (APARs) for AIX 5L v5.3 ML 02:
  • IY58143: REQUIRED UPDATE FOR AIX 5.3

  • IY59386: libdepend.mk files are all empty

  • IY60930: Unable to delete network routes

  • IY66513: LDR_CNTRL turns on undesirable option when initialized with incorrect value

  • IY70159: krtl relocation problem

  • IY68989: eFix for write to mmapped space hangs

PL/SQL native compilation, Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) May 2005 XL C/C++ Enterprise Edition V7.0 for AIX PTF (7.0.0.2):
  • IY64361: Exception in putdiag_no_handler() when -O is specified

  • IY65361: May 2005 XL C Enterprise Edition V7.0 for AIX PTF

  • IY65362: MAY 2005 XL C/C++ Enterprise Edition V7 for AIX

Oracle JDBC/OCI Drivers Note: These APARs are required only if you are using the associated JDK version.

APAR required for JDK 1.4.2 (64-bit):

  • IY63533: DK 1.4.2 64-bit SR1 caix64142-20040917

APARs required for JDK 1.3.1.11 (32-bit):

  • IY58350: SDK 1.3.1 32-BIT SR7P : CA131IFX-20040721A

  • IY65305: JAVA142 32-BIT PTF : CA142IFX-20041203

APAR required for JDK 1.2.2.18:

  • IY40034: SDK 1.2.2 PTF: CA122-20030115


To ensure that the system meets these requirements:

  1. To determine whether an APAR is installed, enter a command similar to the following:

    # /usr/sbin/instfix -i -k "IY63133 IY64978 IY63366 IY64691 IY65001 IY64737 \ 
      IY64361 IY65305 IY58350 IY63533"
    

    If an APAR is not installed, then download it from the following Web site and install it:

    http://www-912.ibm.com/eserver/support/fixes/

  2. If you require a CSD for WebSphere MQ, then refer to the following Web site for download and installation information:

    http://www.ibm.com/software/integration/wmq/support/

2.5 Checking the Network Setup

Typically, the computer on which you want to install Oracle Audit Vault is connected to the network, has local storage to contain the Oracle Audit Vault installation, has a display monitor, and has a CD-ROM or DVD drive.

This section describes how to install Oracle Audit Vault on computers that do not meet the typical scenario. It covers the following cases:

2.5.1 Configuring Name Resolution

When you run Oracle Universal Installer, an error might occur if name resolution is not set up. To avoid this error, before you begin installation, you must ensure that host names are resolved only through the /etc/hosts file.

To ensure that host names are resolved only through the /etc/hosts file:

  1. Verify that the /etc/hosts file is used for name resolution. You can do this by checking the hosts file entry in the netsvc.conf file as follows:

    # cat /etc/netsvc.conf | grep hosts
    

    Ensure that the hosts keyword is configured properly for hostname resolution in the environment.

  2. Verify that the domain name has not been set dynamically by using the domainname command as follows:

    # domainname
    

    This command should not return any results.

  3. Verify that the hosts file contains the fully qualified host name by using the following command:

    # cat /etc/hosts | grep `eval hostname`
    

    The output of this command should contain an entry for the fully qualified host name and for the localhost.

    For example:

    192.168.100.16    myhost.us.mycompany.com   myhost
    127.0.0.1         localhost                 localhost.localdomain
    

    If the hosts file does not contain the fully qualified host name, then open the file and make the required changes in it.

2.5.2 Installing on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing enables a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.

In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign that computer a unique IP address.

Audit Vault cannot be installed in an environment where the IP addresses of the Audit Vault Server or the Audit Vault Agent can change. If your environment uses DHCP, ensure that all Audit Vault systems use static IP addresses.

2.5.3 Installing on Multi-homed Computers

You can install Oracle Audit Vault on a multi-homed computer. A multiple-homed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name. In addition, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If the ORACLE_HOSTNAME environment variable is not set and you are installing Oracle Audit Vault on a computer that has multiple network cards, then Oracle Universal Installer determines the host name by using the first entry in the /etc/hosts file.

Clients must be able to access the computer either by using this host name or by using aliases for this host name. To verify this, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both tests must be successful.

Setting the ORACLE_HOSTNAME Environment Variable

Use the following procedure to set the ORACLE_HOSTNAME environment variable.

For example, if the fully qualified host name is somehost.us.acme.com, then enter one of the following commands:

Bourne, Bash, or Korn shell:

$ ORACLE_HOSTNAME=somehost.us.acme.com
$ export ORACLE_HOSTNAME

C shell:

% setenv ORACLE_HOSTNAME somehost.us.acme.com

2.5.4 Installing on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP address. The naming service resolves all of those aliases to the same computer. Before installing Oracle Audit Vault on a computer with multiple aliases, set the ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.

2.6 Creating the Required Operating System Groups and Users

Depending on whether or not this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create several operating system groups and users.

The following operating system groups and user are required if you are installing Oracle Audit Vault:

The following operating system group and user are required for all installations:

A single Oracle Inventory group is required for all installations of Oracle software on the system. 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, OSDBA groups, and OSOPER groups (other than oracle, dba, and oper) 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.

See Also:

Oracle Database Administrator's Guide for more information about the OSDBA group and the SYSDBA and SYSOPER privileges

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:

2.6.1 Creating the Oracle Inventory Group

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:

# more /etc/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

If the oraInst.loc file does not exist, then create the Oracle Inventory group by using the following procedure:

  1. Enter the following command:

    # smit security
    
  2. Choose the appropriate menu items to create the oinstall group.

  3. Press F10 to exit.

2.6.2 Creating the OSDBA Group

You must create an OSDBA group in the following circumstances:

  • An OSDBA group does not exist, for example, if this is the first installation of Oracle software on the system

  • An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges in a new Oracle installation

If the OSDBA group does not exist or if you need a new OSDBA group, then create it as follows.

In the following procedure, use the group name dba unless a group with that name already exists.

  1. Enter the following command:

    # smit security
    
  2. Choose the appropriate menu items to create the dba group.

  3. Press F10 to exit.

2.6.3 Creating an OSOPER Group (Optional)

Create an OSOPER group only if you want to identify a group of operating system users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, then you must create it in the following circumstances:

  • If an OSOPER group does not exist, for example, if this is the first installation of Oracle software on the system

  • If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation

If you need a new OSOPER group, then create it as follows.

In the following procedure, use the group name oper unless a group with that name already exists.

    1. Enter the following command:

      # smit security
      
    2. Choose the appropriate menu items to create the oper group.

    3. Press F10 to exit.

2.6.4 Creating the Oracle Software Owner User

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

2.6.4.1 Determining Whether an Oracle Software Owner User Exists

To determine whether an Oracle software owner user named oracle exists, enter the following command:

# 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 software owner (oracle) user. If you want to use the existing user, then ensure that the primary group of the user is the Oracle Inventory group and that it is a member of the appropriate OSDBA and OSOPER groups.

Note:

If necessary, contact your system administrator before using or modifying an existing user.

See one of the following sections for more information:

  • To modify an existing Oracle software owner user, see Section 2.6.4.3.

  • To create an Oracle software owner user, see the following section.

2.6.4.2 Creating an Oracle Software Owner User

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.

  1. Enter the following command:

    # smit security
    
  2. 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.

    • In the Group SET field, specify the OSDBA group and if required, the OSOPER group. For example, dba or dba,oper.

      Note:

      The UID for the oracle user must be less than 65536.
  3. Press F10 to exit.

  4. Set the password of the oracle user:

    # passwd oracle
    

See Section 2.6.5 to continue

2.6.4.3 Modifying an Oracle Software Owner User

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 you can modify it as follows:

  1. Enter the following command:

    # smit security
    
  2. Choose the appropriate menu items to modify the oracle user.

  3. In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.

  4. In the Group SET field, specify the required secondary groups, for example dba and oper.

  5. Press F10 to exit.

2.6.5 Verifying that the User nobody Exists

Before installing the software, perform the following procedure to verify that the nobody user exists on the system:

  1. 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.

  2. If the nobody user does not exist, then enter the following command to create it:

    # smit security
    

    Specify the appropriate options to create an unprivileged nobody user, then press F10 to exit.

2.7 Configure Shell Limits and System Configuration Parameters

Note:

The parameter and shell limit values shown in this section are recommended values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. See your operating system documentation for more information about tuning kernel parameters.

Oracle recommends that you set shell limits and system configuration parameters as described in the following sections:

2.7.1 Configure Shell Limits

Verify that the shell limits shown in the following table are set to the values shown. The procedure following the table describes how to verify and set the values.

Shell Limit (As Shown in smit) Recommended Value
Soft FILE size -1 (Unlimited)
Soft CPU time -1 (Unlimited)

Note: This is the default value.

Soft DATA segment -1 (Unlimited)
Soft STACK size -1 (Unlimited)

To view the current value specified for these shell limits, and to change them if necessary:

  1. Enter the following command:

    # smit chuser
    
  2. In the User NAME field, enter the user name of the Oracle software owner, for example oracle.

  3. Scroll down the list and verify that the value shown for the soft limits listed in the previous table is -1.

    If necessary, edit the existing value.

  4. When you have finished making changes, press F10 to exit.

2.7.2 Configure System Configuration Parameters

Verify that the maximum number of processes allowed for each user is set to 2048 or greater:

Note:

For production systems, this value should be at least 128 plus the sum of the PROCESSES and PARALLEL_MAX_SERVERS initialization parameters for each database running on the system.
  1. Enter the following command:

    # smit chgsys
    
  2. Verify that the value shown for Maximum number of PROCESSES allowed for each user is greater than or equal to 2048.

    If necessary, edit the existing value.

  3. When you have finished making changes, press F10 to exit.

2.8 Identifying the Required Software Directories

You must identify or create the following directories for the Oracle software:

2.8.1 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. On AIX 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

In this example:

  • 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 topics describe how to identify existing Oracle base directories that might 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.

2.8.2 Oracle Inventory 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.

2.8.3 Oracle Home Directory

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.2/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.

2.9 Identifying or Creating an Oracle Base 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.

2.9.1 Identifying an Existing Oracle Base Directory

Existing Oracle base directories might 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:

    # more /etc/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:

    # 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 specified on each line identify Oracle home 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 table in Section 2.3.

    To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:

    # df -k 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.9.2.

2.9.2 Creating an Oracle Base Directory

Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space, as indicated in the table in Section 2.3.

To identify an appropriate file system:

  1. Use the df -k command to determine the free disk space on each mounted file system.

  2. From the display, identify a file system that has appropriate free space.

  3. 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:

  1. 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
    
  2. When you configure the environment of the oracle user (see Section 2.6.4), set the ORACLE_BASE environment variable to specify the Oracle base directory that you created.

2.10 Creating Directories for Oracle Audit Vault Database Files

If you choose to place the Oracle Audit Vault database files on a file system, then use the following guidelines when deciding where to place them:

2.11 Setting the DISPLAY Environment Variable

Before you begin the Audit Vault Server 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.oracle.com is your host name:

$ DISPLAY=myhost.us.oracle.com:1.0
$ export DISPLAY

For example, for the C shell, you would enter the following command, where myhost.us.oracle.com is your host name:

% setenv DISPLAY myhost.us.oracle.com:1.0