Skip Headers
Oracle® Business Intelligence Installation Guide
10g Release 2 (10.1.2) for AIX 5L Based Systems (64-Bit)
B25208-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

3 Detailed Reports Services Requirements

Before installing Oracle Business Intelligence, ensure that your computer meets the requirements for Reports Services described in this chapter.

This chapter contains the following sections:

3.1 About Specifying an SMTP Server for Reports Services

During installation, the Provide Outgoing Mail Server Information screen appears. Enter the outgoing mail (SMTP) server to be used by Forms and Reports Services.

Example: smtp.oracle.com


Note:

This field is optional. However, you cannot distribute reports through e-mail until you have configured the mail server information. Refer to Oracle Application Server Reports Services Publishing Reports to the Web for more information on specifying the outgoing mail server information.

3.2 New Element for Specifying Port Numbers for CORBA Communication

Oracle Reports 10g Release 2 (10.1.2) introduces the ORBPorts element in the server configuration file to allow you to explicitly specify the port numbers used by Reports Server and engines for communication through CORBA. You can specify either a range of ports or individual ports separated by commas. For example:

<ORBPorts value="15000-15010"/> (Range of values)

<ORBPorts value="15000,16000,17000,18000"/> (Comma-separated values)

By default, the ORBPorts element is not present in the server configuration file. If this element is missing, Reports Server chooses a random port for CORBA communication. For more information about the ORBPorts element, see the chapter "Configuring OracleAS Reports Services" in the Oracle Application Server Reports Services Publishing Reports to the Web manual.


Note:

The ORBPorts element should be defined only if your administrator has enabled TCP port filtering on your server where Reports Server is running. If port filtering is enabled, your administrator can open few ports for Reports Server, then use ORBPorts to specify them in the server configuration file for Reports Server and engine communication. If any of the ports are not available, Reports Server or engines may fail to start and an error displays.

3.3 Hardware Requirements

This section provides the system requirements for running Oracle Application Server 10g Forms and Reports Services. The installer checks many of these requirements at the start of the installation process and warns you if any of them is not met. To save time, you can manually check only the ones that are not checked by the installer. Refer to the appropriate table to see which requirements are not checked by the installer.

You can also run the system checks performed by the installer without doing an installation, by running the runInstaller command as shown. The runInstaller command is on the Oracle Application Server 10g Forms and Reports Services CD-ROM (Disk 1) or DVD (in the application_server directory).

CD-ROM:

prompt> mount_point/1012disk1/runInstaller -executeSysPrereqs

DVD:

prompt> mount_point/application_server/runInstaller -executeSysPrereqs

The results are displayed on the screen as well as written to a log file.

For more information on the types of checks performed, refer to Section 3.12, "Prerequisite Checks Performed by the Installer".

Table 3-1 System Requirements

Item Requirement

Network

You can install Oracle Application Server on a computer that is connected to a network, or on a "standalone" computer (not connected to the network).

If you are installing Oracle Application Server on a standalone computer, you can connect the computer to a network after installation. You have to perform some configuration tasks when you connect it to the network.

Refer to Oracle Application Server Administrator's Guide for details.

Checked by Installer: No

Hostname

Ensure that your hostnames are not longer than 255 characters.

Processor type

All AIX Common Hardware Reference Platform processors (64-bit)

If the processor is a 64-bit processor, the following command returns the value 64:

# /usr/bin/getconf HARDWARE_BITMODE

To make sure the processor is a Common Hardware Reference Platform processor, run the following command as the root user and make sure it returns the value chrp:

# bootinfo -p

Disk space

OracleAS Infrastructure: 4.12 GB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 1.7 GB

  • Portal and Wireless: 3.1 GB

  • Business Intelligence and Forms: 3.99 GB

OracleAS Developer Kits: 2.2 GB

The installer may display inaccurate disk space requirement figures. Refer to the figures listed above for disk space requirements.

To determine the amount of free disk space, use the bdf command:

prompt> bdf dir

Replace dir with the Oracle home directory or with the parent directory if the Oracle home directory does not exist yet. For example, if you plan to install Oracle Application Server in /opt/oracle/infra, you can replace dir with /opt/oracle or /opt/oracle/infra.

Checked by Installer: No

Operating System

AIX 5L Based Systems

IP

The IP address of the computer must be static. Oracle Application Server does not support AIX systems using DHCP.

Memory

The memory requirements provided for the various installation types represents enough physical memory to install and run Oracle Application Server. However, for most production sites, you should configure at least 1 GB of physical memory. For sites with substantial traffic, increasing the amount of memory further may improve your performance. For Java applications, you should either increase the maximum heap allocated to the OC4J processes, or configure additional OC4J processes to utilize this memory. Refer to Oracle Application Server Performance Guide for details.

In determining the optimal amount of memory for your installation, the best practice is to load test your site. Resource requirements can vary substantially for different applications and different usage patterns. In addition, some operating system utilities for monitoring memory can overstate memory usage (partially due to the representation of shared memory). The preferred method for determining memory requirements is to monitor the improvement in performance resulting from the addition of physical memory in your load test. Refer to your platform vendor documentation for information on how to configure memory and processor resources for testing purposes.

OracleAS Infrastructure 10g:

  • OracleAS Metadata Repository and Identity Management: 1 GB

  • Identity Management only: 512 MB

  • OracleAS Metadata Repository only: 750 MB

Oracle Application Server middle tier:

  • J2EE and Web Cache: 512 MB

  • Portal and Wireless: 1 GB

  • Business Intelligence and Forms: 1 GB

OracleAS Developer Kits 10g: 256 MB, but 512 MB recommended

To determine the amount of memory, enter the following command:

# /usr/sbin/lsattr -E -l sys0 -a realmem

Space in /tmp directory

400 MB

To determine the amount of free disk space in the /tmp directory, enter the following command:

prompt> df -k /tmp

If the /tmp directory does not have enough free space, you can specify a different directory by setting the TMP environment variable. Refer to Section 3.9.5, "TMP and TMPDIR" for details.

Swap Space

1.5 GB of available swap space

To determine the amount of available swap space, enter the following command:

# /usr/sbin/lsps -a

If necessary, see your operating system documentation for information on how to configure additional swap space.

Monitor

256 color display

To determine your monitor's display capabilities, run the following command:

prompt> /usr/X11R6/bin/xdpyinfo

Look for the "depths" line. You need a depth of at least 8 (bits per pixel).


3.3.1 Memory Requirements for Running Multiple Instances on the Same Computer

If you plan to run OracleAS Infrastructure 10g and a middle tier on the same computer, ensure the computer meets the memory requirements listed in Section 3.3.

These values have been tested against a small number of users. If you have many users, you might have to increase the amount of memory.

3.3.2 Installing from the Console or X Windows

If you are performing the installation from the console or X Windows, then add the following line to the /etc/pamd.d/xdm file:

session required pam_limits.so

3.3.3 Tips for Reducing Memory Usage

If you need to reduce memory consumption:

  • Configure only the components that you need.

  • Choose the smallest middle tier type that contains the components that you need.

  • After installation, start up only the components that you need. See the Oracle Application Server Administrator's Guide for details.

  • Run Application Server Control only when you need to administer an instance. In most cases, you do not need Application Server Control running all the time.

    If you are running multiple Oracle Application Server 10g Forms and Reports Services instances on one computer, each Application Server Control can consume a lot of memory. Running Application Server Control only when you need it can free up memory for other components.

3.4 Software Requirements

Depending on the version of AIX you are using, refer to the following sections for the corresponding software requirements:

3.4.1 Software Requirements for AIX 5L Version 5.2

Table 3-2 lists the software requirements for AIX 5L version 5.2.

Table 3-2 Software Requirements for AIX 5L Version 5.2

Item Requirements

Maintenance Level

04 or higher

Filesets

bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
X11.motif.lib

Patches (All Filesets)

IY65001 mklvcopy on a striped lv is failing to update lvcb

IY64978 deadlock with concurrent renaming and unlinking

IY64737 knot lock not released properly

IY64691 chvg -b can cause corruption and crash

IY63366 dlsym returns NULL even for valid symbol

IY63133 Performance degredation with many CPUS and volume group

IY69518 chvg -L / extendvg anomaly

IY75901 extendvg can cause corruption after IY69518

IY59082 systems hang with JFS2 and heavy load


Before installing AIX-based systems running AIX 5L version 5.2, complete the following step:

  1. Check that AIX 5L version 5.2, Maintenance Level 04 or higher is installed by entering the oslevel -r command, as shown in the following example:

    # oslevel -r
    5200-04
    
    

    In this example, the version of AIX is 5.2, Maintenance Level 04.

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

    https://techsupport.services.ibm.com/server/aix.fdc
    
    
  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 X11.motif.lib
    
    

    For the list of filesets required for AIX 5L version 5.2, refer to Table 3-2

    If a fileset is not installed and committed, then install it. Refer to your operating system or software documentation for information on installing filesets.

  3. Check that the patches mentioned in Table 3-2 are installed. To determine whether an authorized program analysis report (APAR) is installed, enter a command similar to the following:

    # /usr/sbin/instfix -i -k "IY22854 IY26778 ..."
    
    

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

    https://techsupport.services.ibm.com/server/aix.fdc
    

3.4.2 Software Requirements for AIX 5L Version 5.3

Table 3-3 lists the software requirements for AIX 5L version 5.3.

Table 3-3 Software Requriements for AIX 5L version 5.3

Item Requirements

Maintenance Level

02 or higher

Filesets

bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
X11.motif.lib

Patches

IY70159 : KRTL relocation problem

IY66513 : Parsing of LDR_CNTRL value fails

IY68989 : write to mmapped space hangs


Following are the steps to check if the parameters mentioned in Table 3-3 are installed on the system or not:

  1. Check that AIX 5.3, Maintenance Level 02 or higher is installed by entering the oslevel -r command, as shown in the following example:

    # oslevel -r
    5300-02
    
    

    In this example, the version of AIX is 5.3, Maintenance Level 04.

    If the operating system version is lower than AIX 5.3.0.0 Maintenance Level 2 (5300-02), then upgrade the operating system to this level. AIX 5L version 5.3 maintenance packages are available from the following Web site:

    https://techsupport.services.ibm.com/server/aix.fdc
    
    
  2. To determine whether the required filesets are installed and committed, enter following command:

    # lslpp -l bos.adt.base bos.adt.lib bos.adt.libm \ 
    bos.perf.perfstat bos.perf.libperfstat X11.motif.lib
    
    

    For the list of filesets required for AIX 5L version 5.3, refer to Table 3-3

    If a fileset is not installed and committed, then install it. Refer to your operating system or software documentation for information on installing filesets.

  3. Check that the patches mentioned in Table 3-3 are installed. To determine whether an authorized program analysis report (APAR) is installed, enter a command similar to the following:

    # /usr/sbin/instfix -i -k "IY66513 IY70159 IY66513 IY60930 IY59386"
    
    

    If an APAR or one of its fileset is not installed, then download it from the following Web site and install it:

    https://techsupport.services.ibm.com/server/aix.fdc
    

3.5 Configuring Shell Limits and System Configuration Parameters

For AIX, you do not need to configure kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

3.5.1 Configure Shell Limits

The following table lists the shell limits that you need to set for AIX. 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:

  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.

3.5.2 Configure System Configuration Parameters

Verify that the maximum number of processes allowed per user is set to 2048 or higher. The procedure following the table describes how to verify and set the value.


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

Make sure that the ARG_MAX setting is set to the maximum value for AIX 5L:

  1. Check the ARG_MAX value setting:

    prompt> getconf ARG_MAX
    
    
  2. If the value is less than 524288, run the following command as the root user:

    # chdev -l sys0 -a ncargs=128
    
    

3.6 Ports

Many Oracle Business Intelligence components, such as Oracle HTTP Server, OracleAS Web Cache, and Oracle Enterprise Manager 10g, use ports. You can have the installer assign default port numbers, or use port numbers that you specify.

Why the Default Port for Oracle HTTP Server Is Port 7777 and Not Port 80?

By default, the installer configures Oracle HTTP Server to use port 7777, not port 80. Port 7777 is the default port because on UNIX, components that use port numbers lower than 1024 require additional steps to be done as the root user before the components can run. Because the installer does not have root access, it has to use a port greater than 1024.

If you want Oracle HTTP Server to use a different port, such as port 80, use the static ports feature, which enables you to specify port numbers for components. Although you can change the port number after installation, it is easier to set the port number during installation.

3.6.1 Checking If a Port Is in Use

To check if a port is being used, run the netstat command as follows:

prompt> netstat -an | grep portnum

3.6.2 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. Refer to Appendix C, "Default Port Numbers" for a list of the default port numbers and ranges. Make sure that at least one port is available in the port range for each component. If the installer is unable to find a free port in the range, then the installation fails.

3.6.3 Using Custom Port Numbers (the Static Ports Feature)

To instruct the installer to assign custom port numbers for components:

  1. Create a file containing the component names and port numbers. Section 3.6.3.1, "Format of the staticports.ini File" describes the file format. This file is typically called staticports.ini, but you can name it anything you want.

  2. In the installer, on the Specify Port Configuration Options screen, select Manual and enter the complete path to the staticports.ini file.

    If you do not specify the complete path to the file, the installer will not be able to find the file. The installer then assigns default ports for all the components, and it does this without displaying any warning.


Difference from Previous Release:

In 10g (9.0.4), you used command-line options to specify the staticports.ini file. In this release, you specify the file in the new Specify Port Configuration Options screen.

3.6.3.1 Format of the staticports.ini File

The staticports.ini file has the following format. Replace port_num with the port number that you want to use for the component.

# J2EE and Web Cache
Oracle HTTP Server port = port_num
Oracle HTTP Server Listen port = port_num
Oracle HTTP Server SSL port = port_num
Oracle HTTP Server Listen (SSL) port = port_num
Oracle HTTP Server Diagnostic port = port_num
Java Object Cache port = port_num
DCM Java Object Cache port = port_num
DCM Discovery port = port_num
Oracle Notification Server Request port = port_num
Oracle Notification Server Local port = port_num
Oracle Notification Server Remote port = port_num
Application Server Control port = port_num
Application Server Control RMI port = port_num
Oracle Management Agent port = port_num
Web Cache HTTP Listen port = port_num
Web Cache HTTP Listen (SSL) port = port_num
Web Cache Administration port = port_num
Web Cache Invalidation port = port_num
Web Cache Statistics port = port_num
Log Loader port = port_num
ASG port = port_num

# Business Intelligence and Forms
Reports Services SQL*Net port = port_num
Reports Services discoveryService port = port_num
Reports Services bridge port = port_num

# Infrastructure
Oracle Internet Directory port = port_num
Oracle Internet Directory (SSL) port = port_num
Oracle Certificate Authority SSL Server Authentication port = port_num
Oracle Certificate Authority SSL Mutual Authentication port = port_num
Ultra Search HTTP port number = port_num

The easiest way to create the file is to use the staticports.ini file on the CD-ROM (Disk 1) or DVD as a template:

  1. Copy the staticports.ini file from the CD-ROM or DVD to your hard disk.

    Table 3-4 Location of the staticports.ini File on CD-ROM and DVD

    Media Location of staticports.ini File

    CD-ROM

    mount_point: Disk 1/1012disk1/stage/Response/staticports.ini

    DVD

    mount_point/application_server/stage/Response/staticports.ini


  2. Edit the local copy (the file on the hard disk) to include the required port numbers.

    You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.

    The following example sets the Application Server Control port and some OracleAS Web Cache ports. For components not specified, the installer assigns the default port numbers.

    Application Server Control port = 2000
    Web Cache Administration port = 2001
    Web Cache Invalidation port = 2002
    Web Cache Statistics port = 2003
    
    

    When installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to see the assigned ports.

The installer verifies that the ports specified in the file are available by checking the memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.

If the installer detects that a specified port is not available, it displays an alert. The installer does not assign a port that is not available. To fix this:

  1. Edit the staticports.ini file to specify a different port, or shut down the application using the port.

  2. Click Retry. The installer re-reads the staticports.ini file and verifies the entries in the file again.

Using portlist.ini as the staticports.ini File

The staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after a Oracle Business Intelligence installation. If you have installed Oracle Business Intelligence and want to use the same port numbers in another installation, use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

The portlist.ini file is located in the ORACLE_HOME\install\ directory.

However, note this difference: in staticports.ini, the Oracle Management Agent port line corresponds to the Enterprise Manager Agent port line in portlist.ini.

3.6.3.2 Error Conditions that Cause the Installer to Use Default Ports Instead of Specified Ports

Check the staticports.ini file carefully because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:

  • If you specify the same port for more than one component, the installer uses the specified port for the first component, but for the other components, it uses the components' default ports. The installer does not warn you if you have specified the same port for multiple components.

  • If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.

  • If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case-sensitive. The installer does not display a warning for lines with unrecognized names.

  • If you specify a non-numeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.

  • If you specify a relative path to the staticports.ini file (for example, ./staticports.ini or just staticports.ini), the installer will not find the file. The installer continues without displaying a warning and assigns default ports to all components. You must specify a complete path to the staticports.ini file.

3.6.3.3 Ports for Oracle HTTP Server and OracleAS Web Cache

Ensure that you understand the following when setting ports for these components.

In the httpd.conf file for Oracle HTTP Server, the Port and the Listen directives specify the ports used by OracleAS Web Cache and Oracle HTTP Server. The correct lines in the staticports.ini file for setting these ports depend on the components that you are configuring.

If You Are Configuring OracleAS Web Cache and Oracle HTTP Server

  1. Set the port for OracleAS Web Cache.

    OracleAS Web Cache uses the port specified by the Port directive (Figure 3-1). To set this port, use this line in the staticports.ini file:

    Web Cache HTTP Listen port = port_number
    
    

    To configure the SSL port for OracleAS Web Cache, use the following line:

    Web Cache HTTP Listen (SSL) port = port_number
    
    

    You cannot set the port number using the Oracle HTTP Server port line in this case. If the staticports.ini file contains both the Oracle HTTP Server port and the Web Cache HTTP Listen port lines, the Oracle HTTP Server port line is ignored. For example, if you have these lines in staticports.ini:

    Web Cache HTTP Listen port = 7979
    Oracle HTTP Server port = 8080
    
    

    the Port directive is set to 7979.

  2. Set the port for Oracle HTTP Server.

    Oracle HTTP Server uses the port specified by the Listen directive. To set this port, use this line in the staticports.ini file:

    Oracle HTTP Server Listen port = port_number
    
    

    To configure the SSL Listen port, use the following line:

    Oracle HTTP Server Listen (SSL) port = port_number
    
    

Figure 3-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server

Description of Figure 3-1  follows
Description of "Figure 3-1 Configuring Both OracleAS Web Cache and Oracle HTTP Server"

If You Are Configuring Oracle HTTP Server Only (no OracleAS Web Cache)

If you are configuring Oracle HTTP Server only, then Oracle HTTP Server uses both Port and Listen directives (Figure 3-2). In this case, you must set both directives to use the same port number.

To set these ports, use the Oracle HTTP Server port and Oracle HTTP Server Listen port lines in the staticports.ini file. For example:

Oracle HTTP Server port = 8080
Oracle HTTP Server Listen port = 8080

To set the SSL version of these ports, use the following lines. As in the non-SSL version, the port numbers must be the same.

Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443

If you also specify the Web Cache lines in staticports.ini, they are ignored because you are not configuring OracleAS Web Cache.

Figure 3-2 Configuring Only Oracle HTTP Server

Description of Figure 3-2  follows
Description of "Figure 3-2 Configuring Only Oracle HTTP Server"

3.6.3.4 Examples

This section describes some common scenarios for using staticports.ini.

3.6.3.4.1 Configuring Oracle HTTP Server to Use Ports 80 and 443 With OracleAS Web Cache as the Front-End

In this scenario, create a staticports.ini file that includes the following lines:

Web Cache HTTP Listen port = 80
Oracle HTTP Server Listen port = 81
Web Cache HTTP Listen (SSL) port = 443
Oracle HTTP Server Listen (SSL) port = 444

The ports for Oracle HTTP Server Listen and SSL Listen can be any available port. The example uses ports 81 and 444. These port numbers do not have to be less than 1024. If you select port numbers less than 1024, start Oracle HTTP Server and OracleAS Web Cache as the root user.


Note:

Because you are using ports less than 1024, you have to configure Oracle HTTP Server and OracleAS Web Cache to run as the root user. You can perform the configuration during installation or after installation.

If you perform the configuration after installation, then the installer does not start the components (because they are not yet configured).

For details, see these guides: Oracle HTTP Server Administrator's Guide and Oracle Application Server Web Cache Administrator's Guide.


3.6.3.4.2 Configuring Oracle HTTP Server to Use Ports 80 and 443 Without OracleAS Web Cache

In this scenario, create a staticports.ini file that includes the following lines:

Oracle HTTP Server port = 80
Oracle HTTP Server Listen port = 80
Oracle HTTP Server SSL port = 443
Oracle HTTP Server Listen (SSL) port = 443


Note:

Because you are using ports less than 1024, you have to configure Oracle HTTP Server to run as the root user. Refer to the note on page 3-22 for details.

3.7 Operating System Groups

You need to create operating system groups in these situations:

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

3.7.1 Create a Group for the Inventory Directory

If you plan to install Oracle Application Server 10g Forms and Reports Services on a computer that does not have Oracle products, create a group to own the inventory directory. The installer writes its files in the inventory directory to keep track of the Oracle products installed on the computer.

This guide uses the name oinstall for this operating system group.

By having a separate group for the inventory directory, you allow different users to install Oracle products on the computer. Users need write permission for the inventory directory. They can achieve this by belonging to the oinstall group.

For the first time installation of any Oracle product on a computer, the installer displays a screen where you enter a group name for the inventory directory, and a screen where you enter the location of the inventory directory.

The default name of the inventory directory is oraInventory.

If you are unsure if there is already an inventory directory on the computer, look in the /etc/oraInst.loc file This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

3.7.2 Create Groups for Database Administrators

This section applies only if you plan to install the OracleAS Metadata Repository in a new database created by the installer.

When the database is not mounted and database authentication is unavailable, the database uses operating system groups to determine user privileges. The database recognizes these groups and privileges:

Table 3-5 Privileges for the OSDBA and OSOPER Groups

Group Description

OSDBA

This is the database administrator group. Users in this group are granted SYSDBA privileges.

OSOPER

Users in this group are granted SYSOPER privileges, which comprise privileges required for basic maintenance. These include database startup and shutdown, and other privileges required for database operation. SYSOPER privileges are a subset of SYSDBA privileges.


You need to create operating system groups for these groups.

If you want an operating system group called dba to have SYSDBA privileges:

  1. Create the dba group.

  2. Ensure that the user running the installer is a member of the dba group.

If you want a different operating system group to have SYSDBA privileges, or if you want to associate SYSDBA and SYSOPER privileges with different groups, ensure the user running the installer does not belong to the dba group.

If the user running the installer does not belong to the dba group, the installer displays a screen where you can enter the names of groups to have the database administrator privileges. The screen has two fields: one for the OSDBA group and one for the OSOPER group (see Table 3-5). You can enter the same operating system group for both fields.

3.8 Operating System User

Create an operating system user to install and upgrade Oracle products. This guide refers to this user as the oracle user. The oracle user running the installer must have write permission for these directories:

If the computer contains other Oracle products, you might already have a user for this purpose. Look in the /etc/oraInst.loc file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

If you do not already have a user for installing Oracle products, create a user with the following properties:

Table 3-6 Properties of the Operating System User Who Runs the Installer

Item Description

Login name

You can use any name for the user. This guide refers to the user as the oracle user.

Group identifier

The primary group of the oracle user must have write permission for the oraInventory directory. See Section 3.7.1, "Create a Group for the Inventory Directory" for more information about this group.

You can use any name for the group. This guide uses the name oinstall.

Home directory

The home directory for the oracle user can be consistent with the home directories of other users.

Login shell

The default login shell can be the C, Bourne, or Korn shell.


To check which groups an operating system user belongs to, run the groups command with the name of the user. For example:

prompt> groups oracle

For more information about operating system users and groups, see your operating system documentation or contact your system administrator.

3.9 Environment Variables

The operating system user who will be installing Oracle Business Intelligence needs to set (or unset) the environment variables listed in Table 3-7.

Table 3-7 Summary of Environment Variables

Environment Variable Set or Unset

Section 3.9.2, "ORA_NLS33, ORACLE_HOME, and ORACLE_SID"


Does not matter (the installer unsets these two environment variables).

Section 3.9.3, "PATH, CLASSPATH, and LIBPATH"


Must not contain references to directories in any Oracle home directories

Section 3.9.4, "DISPLAY"


Set it to the monitor on which you want to the installer window to appear.

Section 3.9.5, "TMP and TMPDIR"


Optional. If unset, defaults to /tmp.

Section 3.9.6, "TNS_ADMIN"


Must not be set.

Section 3.9.7, "REPORTS_DEFAULT_DISPLAY"


Default set to YES. If set to NO, ensure that you specify the appropriate display.


3.9.1 Tips on Environment Variables

Here are some tips when working with environment variables:

  • If you set environment variables in the file, they may not be read. To ensure environment variables are set to the correct values, check their values in the shell where you run the installer.

  • To check the value of environment variables, use the env command. This command displays all the currently defined environment variables and their values.

    % env
    
    
  • If you use the su command to switch users (for example, switching from the root user to the oracle user), check the environment variables when you are the new user because the environment variables may not be passed to the new user. This can happen even if you run su with the - parameter (su - user).

    # /* root user */
    # su - oracle
    % env
    
    

3.9.2 ORA_NLS33, ORACLE_HOME, and ORACLE_SID

These environment variables must not be set.

3.9.3 PATH, CLASSPATH, and LIBPATH

Edit the PATH, CLASSPATH, and LIBPATH environment variables so that they do not reference any Oracle home directories.

The shared library path environment variable is LIBPATH.

3.9.4 DISPLAY

Set the DISPLAY environment variable to point to the X server that displays the installer. The format of the DISPLAY environment variable is:

hostname:display_number.screen_number

Example (C shell):

% setenv DISPLAY test.mydomain.com:0.0

Example (Bourne or Korn shell):

$ DISPLAY=test.mydomain.com:0.0; export DISPLAY

Oracle Business Intelligence requires a running X server during installation only. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running during installation. If you do not want to do this, then use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).

Visit Oracle Technology Network at http://www.oracle.com/technology/products/ for information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".

3.9.5 TMP and TMPDIR

During installation, the installer needs to write temporary files to a temporary directory. By default, the temporary directory is /tmp.

If you want the installer to use a directory other than /tmp, set the TMP environment variable to the full path of the alternate directory.

Example (C shell):

% setenv TMP /tmp2
% setenv TMPDIR /tmp2

Example (Bourne or Korn shell):

$ TMP=/tmp2; export TMP
$ TMPDIR=/tmp2; export TMPDIR

If you do not set this environment variable, and the default directory does not have enough space, then the installer displays an error message that says the environment variable is not set. You can either set the environment variable to point to a different directory or free up enough space in the default directory. In either case, you have to restart the installation.

3.9.6 TNS_ADMIN

This section describes two requirements:

  • The TNS_ADMIN environment variable must not be set.

  • The /etc directory must not contain a tnsnames.ora file.

These requirements are necessary to prevent conflicts between the Net configuration files for different Oracle products.

If you need to set TNS_ADMIN or have the tnsnames.ora file in /etc, perform the following steps before installing Oracle Business Intelligence.

  1. If you have the tnsnames.ora file in /etc, move the file from these directories to a different directory. Alternatively, you can rename the file.

  2. Make sure the TNS_ADMIN environment variable is not set.

    Example (C shell):

    % unsetenv TNS_ADMIN
    
    

    Example (Bourne or Korn shell):

    $ unset TNS_ADMIN
    
    

After installation, you can merge the contents of the newly created tnsnames.ora file with the existing tnsnames.ora file.

3.9.7 REPORTS_DEFAULT_DISPLAY

The REPORTS_DEFAULT_DISPLAY environment variable specifies whether to implement the following for Oracle Reports:

  • Elimination of dependency on DISPLAY

  • Elimination of dependency on having a valid printer defined for font information

  • ScreenPrinter (screenprinter.ppd) for surface resolution for images and font information

  • Advanced Imaging Support

For Oracle Reports, if REPORTS_DEFAULT_DISPLAY=YES, it overrides any value set for the DISPLAY environment variable. For more information about REPORTS_DEFAULT_DISPLAY, see the Oracle Application Server Reports Services Publishing Reports to the Web manual.


Note:

REPORTS_DEFAULT_DISPLAY is used for Oracle Reports only and is not applicable to the Oracle Application Server installer. The installer continues to use the DISPLAY environment variable even if REPORTS_DEFAULT_DISPLAY is set to YES.

3.10 The /etc/hosts File

Although the contents of the /etc/hosts file affect these items:

the installer provides alternative methods for you to enter the values that you want without editing the hosts file. Refer to the following subsections for details.

3.10.1 Location of the Default Oracle Identity Management Realm

The installer reads the hosts file to construct the location of the default Oracle Identity Management realm. It displays this location in the "Specify Namespace in Internet Directory" screen.

The hosts file should use the following format:

ip_address   fully_qualified_hostname   short_hostname

Example:

123.45.67.89   primaryHost.mydomain.com   primaryHost

In the preceding example, the location of the default Oracle Identity Management realm would look like "dc=mydomain,dc=com".

If the file uses a different format, the installer displays an incorrect value in the screen. For example, if the hosts file contains:

123.45.67.89   primaryHost   primaryHost.mydomain.com  <--- incorrect format

the installer would display "dc=primaryHost,dc=com" as the default Oracle Identity Management realm. This is probably not the value that you want for the default Oracle Identity Management realm.


Tip:

If you need the hosts file to use a different format, you can edit the file to use the required format, perform the installation, then revert the file back to its original format after installation.

If you are unable, or unwilling, to edit the hosts file, you can enter the desired value for the default Oracle Identity Management realm in the Custom Namespace field on the "Specify Namespace in Internet Directory" screen.


3.10.2 Hostname for OracleAS Single Sign-On

If you are installing OracleAS Single Sign-On, and your hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).

If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:

prompt> mount_point/1012disk1/runInstaller OUI_HOSTNAME=myserver.mydomain.com

3.11 Network Topics

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

This section describes the procedure to install Oracle Business Intelligence on computers that do not meet the typical scenario. It covers the following cases:

3.11.1 Installing on Multihomed (Multi-IP) Computers

A multihomed computer is associated with multiple IP addresses. This is achieved by having multiple network cards on the computer. Each IP address is associated with a hostname; additionally, you can set up aliases for the hostname. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the hostname. If ORACLE_HOSTNAME is not set and you are installing Oracle Business Intelligence on a computer that has multiple network cards, Oracle Universal Installer determines the hostname by using the first name in the.

Clients must be able to access the computer using this hostname (or using aliases for this hostname). To check, ping the hostname from the client computers using the short name (hostname only) and the full name (hostname and domain name). Both must work.

3.11.2 Copying CD-ROMs or DVD to Hard Drive, and Installing from the Hard Drive

Instead of installing from the Oracle Business Intelligence CD-ROMs or DVD, you can copy the contents of the CD-ROMs or DVD to a hard drive and install from the hard drive. This might be easier if you plan to install many instances of Oracle Business Intelligence on your network, or if the computers on which you want to install Oracle Business Intelligence do not have CD-ROM or DVD drives.

You can also install from remote CD-ROM or DVD drives. See Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive".)

When you install from the hard drive, the installer does not prompt you to swap CD-ROMs. It can find all the files if they are in the proper locations.

To Copy the CD-ROMs:

  1. Create a parent directory (for example, orafrs) and, under the parent directory, create subdirectories called Disk1, Disk2, and so on. The names of the subdirectories must be DiskN, where N is the CD-ROM number.

  2. Copy the contents of each CD-ROM into the corresponding directory.

To run the installer from the copied files, invoke the runInstaller executable from the Disk1 directory. Run it from the computer that will be running Oracle Business Intelligence.

prompt> /path/to/hard/drive/Disk1/runInstaller

To Copy the orafrs Directory from the DVD

Copy the orafrs directory from the DVD to your hard disk.

prompt> cp -pr /dvd_mount_point/orasolfrs /path/to/hard/drive

To run the installer from the copied files, invoke the runInstaller executable from the computer that will be running Oracle Business Intelligence:

prompt> /path/to/hard/drive/orafrs/runInstaller

3.11.3 Installing from a Remote CD-ROM or DVD Drive

If the computer on which you want to install Oracle Business Intelligence does not have a CD-ROM or DVD drive, you can perform the installation from a remote CD-ROM or DVD drive. Check that you have performed these steps:

  • You need to share the remote CD-ROM or DVD drive through NFS.

    On the remote computer that has the CD-ROM or DVD drive:

    1. CD-ROM: Insert Oracle Business Intelligence Disk 1 into the CD-ROM drive.

      DVD: Insert the Oracle Business Intelligence DVD into the DVD drive.

    2. Share the CD-ROM or DVD drive.

      CD-ROM:

      prompt> su
      Password: root_password
      # share -F nfs -o ro /cdrom/disk1
      
      

      The path /cdrom/disk1 specifies the path to the CD-ROM in the CD-ROM drive. You can use any path you like.

      DVD:

      prompt> su
      Password: root_password
      # share -F nfs -o ro /cdrom
      
      

      The path /cdrom specifies the path to the DVD in the DVD drive. You can use any path you like.

    On the local computer, access the CD-ROM or DVD and run the installer as follows:

    CD-ROM:

    prompt> /net/remote_computer_hostname/cdrom/disk1/runInstaller
    
    

    DVD:

    prompt> /net/remote_computer_hostname/cdrom/orasolfrs/runInstaller
    
    

    Replace remote_computer_hostname with the name of the remote computer.

  • This bullet point, switching CD-ROMs, does not apply to DVDs.

    When the installer prompts you to switch CD-ROMs, you need to unshare the CD-ROM drive, eject the CD-ROM, insert the requested CD-ROM, and share the CD-ROM drive again. If you do not unshare, you will not be able to eject the CD-ROM.


    Note:

    The installer must be running when you are switching CD-ROMs. Do not exit the installer when switching CD-ROMs. If you exit the installer, it is unable to continue from where it left off. In addition, the partial installation that it created is not usable, and may need to be removed manually.

    On the remote computer (which has the CD-ROM drive):

    prompt> su
    Password: root_password
    # unshare /cdrom/disk1
    # eject cdrom
    ... Remove the CD-ROM, and insert the CD-ROM requested by the installer (for
    ... example, Disk 2).
    ... Share the CD-ROM.
    # share -F nfs -o ro /cdrom/disk2
    
    

3.11.4 Installing on Remote Computers

You can run the installer on a remote computer (remote_computer), but have the installer screens display on your local computer (local_computer). The installer installs Forms and Reports Services on the remote computer.

  1. Allow remote_computer to display on local_computer. Run this command on the local computer's console.

    local_computer> xhost +remote_computer
    
    

    If you do not run xhost, you may get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting the installer.

  2. On local_computer, perform a remote login (using telnet or rlogin) to remote_computer. Log on as the oracle user, as described in Section 3.8, "Operating System User". Ensure that the user has set the environment variables correctly, as described in Section 3.9, "Environment Variables".

    local_computer> rlogin -l oracle remote_computer.mydomain.com
    - OR -
    local_computer> telnet remote_computer.mydomain.com
    
    
  3. Set the DISPLAY environment variable on remote_computer to point to local_computer.

    Example (C shell):

    remote_computer> setenv DISPLAY local_computer.mydomain.com:0.0
    
    

    Example (Bourne or Korn shell):

    remote_computer> DISPLAY=local_computer.mydomain.com:0.0; export DISPLAY
    
    
  4. Run the installer. For information on running the installer, see Section 4.1, "Starting the Installer".


    Note:

    You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on changing the color model or visual settings.

If you want to install and run Forms and Reports Services on a remote computer (that is, the remote computer has the hard drive and will run Forms and Reports Services components), but you do not have physical access to the computer, you can still perform the installation on the remote computer if it is running remote control software such as VNC or Symantec pcAnywhere. You also need the remote control software running on your local computer.

You can install Forms and Reports Services on the remote computer in one of these two ways:

  • If you have copied the contents of the Forms and Reports Services CD-ROM or DVD to a hard drive, then you can install from the hard drive.

  • You can insert the CD-ROM or DVD into a drive on your local computer, and install from the CD-ROM or DVD.

Installing from a Hard Drive

If you have copied the contents of the Forms and Reports Services CD-ROM or DVD to a hard drive, then you can install from the hard drive. To install from the hard drive:

  1. Ensure that the remote control software is installed and running on the remote and local computers.

  2. Share the hard drive that contains the Forms and Reports Services CD-ROM or DVD.

  3. On the remote computer, map a drive letter to the shared hard drive. Use the remote control software to do this on the remote computer.

  4. Using the remote control software, run the installer on the remote computer. You can access the installer from the shared hard drive.

Installing from a Remote CD-ROM or DVD Drive

You can insert the CD-ROM or DVD into a drive on your local computer, and install from the CD-ROM or DVD. This is similar to the scenario described in Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive". To install from a remote CD-ROM or DVD:

  1. Ensure that the remote control software is installed and running on the remote and local computers.

  2. On the local computer, share the CD-ROM or DVD drive.

    On the remote computer, map a drive letter to the shared CD-ROM or DVD drive. Use the remote control software to do this on the remote computer.

    These steps are described in Section 3.11.3, "Installing from a Remote CD-ROM or DVD Drive".

  3. Using the remote control software, run the installer on the remote computer. You can access the installer from the shared CD-ROM or DVD drive.

3.11.5 Installing on NFS-Mounted Storage

You cannot install and run Oracle Business Intelligence on Sun computers with standard NFS. You must use a certified NFS-mounted storage system, such as Network Appliance (NetApp) Filers. Oracle Business Intelligence is certified to run on NFS-mounted storage systems.

The NetApp system must be exported to at least the remote install user and remote root user. You can do this using exportfs command:

prompt> exportfs -i /vol/vol1

To check the latest certification list for any updates, visit Oracle Technology Network (http://www.oracle.com/technology).

3.11.6 Running Multiple Instances from One Installation

Oracle Business Intelligence components are intended to be run only on the computer on which they are installed. You cannot run the components on remote computers even though the computers can access the files through NFS.

3.11.7 Support for NIS and NIS+

You can install and run Oracle Business Intelligence in NIS and NIS+ environments. See the Oracle Application Server Installation Guide for more information on these environments.

3.12 Prerequisite Checks Performed by the Installer

Table 3-8 lists the checks performed by the installer:

Table 3-8 Prerequisite Checks Performed by the Installer

Item Description

CPU

Checks that the CPU meets the minimum speed requirement.

Operating system kernel parameters

See Section 3.5, "Configuring Shell Limits and System Configuration Parameters" for a list of required kernel parameters.

Memory

See Table 3-1 for recommended values.

Swap space

See Table 3-1 for recommended values.

TMP space

See Table 3-1 for recommended values.

Instance name

The installer checks that the computer on which you are installing Forms and Reports Services does not already have an instance of the same name.

Oracle home directory name

The installer checks that the Oracle home directory name does not contain any spaces.

Path to Oracle home directory

The installer checks that the path to the Oracle home directory is not longer than 127 characters.

Oracle home directory contents

The installer checks that the Oracle home directory does not contain any files that may interfere with the installation.

Oracle home directory

You should install Forms and Reports Services in a new directory, unless you are expanding middle tier or installing middle tier in an Oracle home that contains Oracle Developer Suite. Here are some examples of installations that are not allowed:

  • Any type of Oracle Application Server 10g into an 8.0, 8i, 9.0.1, or 9.2 database Oracle home

  • Any type of Oracle Application Server 10g into an Oracle Management Service Oracle home

  • Any type of Oracle Application Server 10g into an Oracle Collaboration Suite Oracle home

  • Any type of Oracle Application Server 10g into an Oracle HTTP Server standalone Oracle home

  • Any type of Oracle Application Server 10g into an OracleAS Web Cache standalone Oracle home

  • Any type of Oracle Application Server 10g into an Oracle9i Developer Suite 9.0.2 Oracle home

  • Any type of Oracle Application Server 10g into an Oracle Application Server Containers for J2EE standalone Oracle home

  • Any type of Oracle Application Server 10g into an Oracle9iAS 1.0.2.2 Oracle home

  • Oracle Application Server 10g Forms and Reports Services middle tier into an Oracle9iAS9.0.2 or 9.0.3 middle tier Oracle home

  • OracleAS Developer Kits 10g into an OracleAS Infrastructure 9.0.2 or Release 10g Oracle home

  • OracleAS Developer Kits 10g into an Oracle9iAS middle tier 9.0.2 or 9.0.3 Oracle home

  • OracleAS Developer Kits 10g into an Oracle Developer Suite 9.0.2 or Release 10g Oracle home

  • OracleAS Infrastructure 10g into any Oracle9iAS 9.0.2 Oracle home

  • OracleAS Infrastructure 10g into an Oracle Application Server 10g Forms and Reports Services middle tier or OracleAS Developer Kits 10g Oracle home

  • OracleAS Infrastructure 10g into an Oracle Developer Suite 9.0.2 or Release 10g Oracle home

Port 1521

The installer displays a warning if port 1521 is in use by any application, including database listeners of any version. You must stop the application using port 1521, then click Retry in the warning dialog box.

If a database listener is using port 1521, you may be able to use it for the metadata repository database.

If another application is using port 1521, stop it or configure it to use a different port. Alternatively, you can change the database listener to use a port other than 1521, but you can do this only after installation. See the Oracle Application Server Administrator's Guide for details.

Static port conflicts

The installer checks the ports listed in the staticports.ini file, if specified. See Section 3.6, "Ports".

Monitor

The installer checks that the monitor is configured to display at least 256 colors.

Display permission

The installer checks that the user has permissions to display on the monitor specified by the DISPLAY environment variable.

DISPLAY environment variable

The installer checks that the DISPLAY environment variable is set.

TNS_ADMIN environment variable

The TNS_ADMIN environment variable must not be set.

There must not be a tnsnames.ora file in the /etc directories.

DBCA_RAW_CONFIG environment variable

If you are installing the OracleAS Infrastructure 10g in a Real Application Clusters or OracleAS Active Failover Cluster environment, you need to set this environment variable to point to a file that describes the locations of your raw partitions.

Cluster file system

The installer checks that you are not installing Oracle Application Server 10g Forms and Reports Services in a cluster file system (CFS).

Oracle Enterprise Manager directories are writable

The installer runs this check only if you are expanding a middle tier or reinstalling Forms and Reports Services in the same Oracle home. The installer checks that these directories are writable by the operating system user running the installer:

  • ORACLE_HOME/sysman/emd

  • ORACLE_HOME/sysman/config

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config

Oracle Enterprise Manager files exist

The installer runs this check only if you are expanding a middle tier or if you are reinstalling Forms and Reports Services in the same Oracle home. The installer checks that these files exist:

  • ORACLE_HOME/sysman/config/iasadmin.properties

  • ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml