Install DB10gR2 on RHEL5

Installation requirements:

1. Installing required packages

The minimum required packages given here are sufficient only if Linux has been installed without customizing the package selection. This list is based upon a "default-RPMs" installation of RHEL AS/ES 5. Additional RPMs may be needed if a "less-than-default-RPMs" installation of RHEL AS/ES 5 is performed. For more information, please refer to Note 376183.1 "Defining a "default RPMs" installation of the RHEL OS".

The version numbers for these packages given below are the minimum version required. If you have the packages with higher versions than the versions mentioned in below example, you can install the higher version packages.

(i) gcc-c++-4.1.1-52.el5.i386.rpm and all its dependent packages. The dependent packages are

gcc-4.1.1-52.el5.i386.rpm

libstdc++-devel-4.1.1-52.el5.i386.rpm

glibc-devel-2.5-12.i386.rpm

glibc-headers-2.5-12.i386.rpm

libgomp-4.1.1-52.el5.i386.rpm

(ii) libXp-1.0.0-8.i386.rpm

(iii) compat-libstdc++-296-2.96-138.i386.rpm

(iv) compat-libstdc++-33-3.2.3-61.i386.rpm

Install all these packages from the directory Server in CD#2 of RHEL 5 by the single command.

# rpm -ivh gcc-c++-4.1.1-52.el5.i386.rpm gcc-4.1.1-52.el5.i386.rpm

libstdc++-devel-4.1.1-52.el5.i386.rpm glibc-devel-2.5-12.i386.rpm

glibc-headers-2.5-12.i386.rpm libgomp-4.1.1-52.el5.i386.rpm

libXp-1.0.0-8.i386.rpm compat-libstdc++-296-2.96-138.i386.rpm

compat-libstdc++-33-3.2.3-61.i386.rpm

(v) compat-db-4.2.52-5.1.i386.rpm

This package is available in the directory Server in CD#3 of RHEL 5. Install this package by the command

# rpm -ivh compat-db-4.2.52-5.1.i386.rpm

2. Set the kernel parameters

Add the following the lines in the file /etc/sysctl.conf

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

fs.file-max = 65536

net.ipv4.ip_local_port_range = 1024 65000

net.core.rmem_default = 1048576

net.core.rmem_max = 1048576

net.core.wmem_default = 262144

net.core.wmem_max = 262144

To place these changes into effect, execute the command

# sysctl -p

3. Create Oracle user and groups

# groupadd oinstall

# groupadd dba

# useradd -g oinstall -G dba oracle

# passwd oracle

4. Create the required directories for Oracle Base and change the ownership

For example

# mkdir -p /u01/app/oracle

# chown -R oracle:oinstall /u01/app/oracle

5. Set the session limits for Oracle user

Add the following lines to the /etc/security/limits.conf file

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

Add the following line in the /etc/pam.d/login file

session required pam_limits.so

Add the following lines to the /etc/profile.

if [ $USER = "oracle" ]; then

if [ $SHELL = "/bin/ksh" ]; then

ulimit -p 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

fi

6. Configure the Oracle user's environment

Configuring the oracle User's Environment, using the appropriate section of "Oracle® Database Quick Installation Guide 10g Release 2 (10.2) for Linux x86". Note that setting $ORACLE_BASE (not $ORACLE_HOME) in the environment will ease a couple of entries in the Oracle Universal Installer.

For example, if oracle user is using bash shell, and has the home directory as /home/oracle,

The following lines to be added to /home/oracle/.bash_profile

export ORACLE_BASE=/u01/app/oracle

export ORACLE_SID=orcl

unset ORACLE_HOME

7. Invoking OUI

Log in as Oracle user and start installation by any one of the following methods. This is required because Oracle 10.2 expects the OS to be RHEL 3 or RHEL 4.

Method 1:

$ ./runInstaller -ignoreSysPrereqs

Method 2:

Copy the oraparam.ini from the installation source install/oraparam.ini to /tmp directory.

Edit the file /tmp/oraparam.ini

Change the following section :

Before

[Certified Versions]

Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2

After

[Certified Versions]

Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2,redhat-5

Now invoke the runInstaller as follows :

$ ./runInstaller -paramFile /tmp/oraparam.ini

Step by step, EBS R12 Installation on Sparc

Operating System Required Maintenance Tools

Solaris (SPARC) ar, ld, make, X Display Server
Use the following command to check the operating system version:
 $ uname -r
Use the following command to check the maintenance update level:
 $ cat /etc/release
Required Patches
Operating System R Required Patches

Solaris 10 (5.10) 125100-04 or higher:
120473-05 or higher:

Use the following command to retrieve the list of operating system patches already applied:
 $ showrev -p | sort > patchList
Use the following command to check for a specific patch:
 $ /usr/sbin/patchadd -p | grep patch_number (without version number)
For example, to check for patch 123456-01, enter::
 $ /usr/sbin/patchadd -p | grep 123456
The following table lists the required packages for Solaris 8 (5.8), 9 (5.9), 10 (5.10).
Operating System Required Packages
Solaris 8 (5.8), 9 (5.9) • SUNWsprox
Solaris 8 (5.8), 9 (5.9), 10 (5.10) • SUNWarc
• SUNWbtool
• SUNWhea
• SUNWlibm
• SUNWlibms
• SUNWsprot
• SUNWtoo
• SUNWi1of
• SUNWi1cs
• SUNWi15cs
• SUNWxwfnt
Use the following command to check for existing packages:
$ pkginfo
Software Requirements
The following maintenance tools must be installed on all machines, and their locations specified both in the PATH of the account that runs Rapid Install and in the PATH of the accounts that will own the database tier and application tier file systems.
• ar
• ld
• make
• X Display Server
Other Requirements
The following are other requirements for Solaris Operating System (SPARC).
ulimit Value Settings
Verify that the owner of the Oracle Application Server and Oracle Database server file systems have the following 'ulimit' values:
• time (seconds) = unlimited
• file (blocks) = unlimited
• data (kbytes) = unlimited
• stack (kbytes) = unlimited
• memory (kbytes) = unlimited
• coredump (blocks) = unlimited
• nofiles (descriptors) = 65536
Use the following command to check the ulimit settings:
 $ ulimit –a

Operating System Parameter Value
Solaris 10 (5.10) rlim_fd_max 65536
noexec_user_stack 1
semsys:seminfo_semmni 100
semsys:seminfo_semmsl 256
shmsys:shminfo_shmmax 4294967295
shmsys:shminfo_shmmni 100

Check the /etc/system file to verify the kernel settings.

Host Names Settings
Verify that the /etc/hosts file is formatted as follows:
127.0.0.1 localhost.localdomain localhost
.

Disk Space Requirements

Node: Space Required:

Applications node file system (includes AS 28 GB
10.1.2 ORACLE_HOME, AS 10.1.3
ORACLE_HOME, COMMON_TOP,
APPL_TOP, and INST_TOP)

Database node file system (Fresh install) 45 GB

Database node file system (Vision Demo 133 GB
database)


Stage area
For a production database install, running Rapid Install from a stage area requires at
least 33 GB to accommodate the file system and database files in the stage area.

Temporary directories and files
For installation time temporary disk space, Rapid Install uses the temporary directory
defined by the TMPDIR variable (on UNIX)

Important: You should ensure there is at least 500 MB of free temporary
space when carrying out an installation.

For UNIX users
The operating system user that owns the database node file system and starts the
database node services is called the oracle user.

The operating system user that owns the
Applications node file system and starts the Applications node services is called the
applmgr user.

Single-user UNIX installations
In order to prepare for a single-user installation, you must first create an oracle user
account and log in as the oracle user to run Rapid Install. The account should be created
with a default shell that is compatible with the Bourne shell.

Multi-user UNIX installations
In order to prepare for a multi-user installation, you must first create an oracle user
account and an applmgr user account. Both should be created with a default shell that is
compatible with the Bourne shell. Log in as root to run Rapid Install. Then specify the
oracle user as the Oracle OS user, and the applmgr user as the Apps OS user.
The oracle user is the account that owns the database node technology stack (10g R2
ORACLE_HOME) and the database files. The default name for the oracle user is
ora. For example, for a production (PROD) environment, the default Oracle OS
username might be oraprod.

The applmgr user is the account that owns the Applications node technology stack
(APPL_TOP, COMMON_TOP, 10.1.2 ORACLE_HOME, and 10.1.3 ORACLE HOME).
The default name is appl. For example, for a Vision Demo (VIS) environment, the
default Apps OS username might be applvis.

On machines containing multiple nodes, you can assign one user account to be the
owner of the database node file system, and another to be the owner of the Applications
node file system. For this type of install, Rapid Install can install both nodes in one run
if the install is started by the root user. If you are installing on a machine with only one
node to install, or with all nodes sharing the same user, you can run the install as either
the root user or the specific user for those nodes.

Creating the Stage Area Directory
To create the stage area directory, run the adautostg.pl script.
Follow these steps to set up a stage area installation:

1. Log in as the operating system user with sufficient privileges to mount, unmount,
and eject the DVD. This user must also have write privileges to the stage area that
you set up.
2. Insert the Start Here disk in the DVD-ROM drive.
3. Mount the DVD (conditional).
If your system runs on a UNIX platform, and if you do not use AutoMount, you
must mount the Start Here disk now.
4. Verify software version (perl).
You must have perl 5.0053 or higher installed, and it must be in your PATH. Use
the following commands to identify the perl version and its location. The command
is the same for both UNIX and Windows platforms:

 perl –v

If perl is not installed, you may download it from http://www.perl.com.

5. On UNIX, set the environment variable DISPLAY to an active and authorized
display.
6. Run the adautostg.pl script.
UNIX:
 $ cd
 $ perl /mnt/cdrom/Disk1/rapidwiz/adautostg.pl

7. Set up the stage area directory.
At the prompt for the stage directory, enter the name of the system top-level
directory. The Rapid wizard stage12 directory will be created in this path. For
example, if you enter /u01 as the top-level directory, the resulting directory path
will be /u01/stage12.

8. Indicate the components to be staged.
The script prompts you to choose the components that you want to stage:
1. Oracle Applications
2. Oracle Database technology stack (RDBMS)
3. Oracle Applications database (Databases)
4. Oracle Applications technology stack (Tools)
5. APPL_TOP
Enter one or more components, separating each one with a space. You can indicate
that you want to stage only the database technology stack, only the APPL_TOP, and
so on.
If you choose 1 (the default), all the main components will be staged.
9. Insert the Rapid Install DVD.
Insert the relevant DVD, as required in the prompt. The system message lists the
files it has copied and their location in the stage area directory.

Stage Area Directory Structure
The stage area created by adautostg.pl looks like this: a top-level directory ,
with subdirectories startCD, oraApps, oraDB, oraAS, and oraAppDB.




Starting Rapid Install
Once the stage directory is created, start Rapid Install as described in the following
section.


UNIX:
Example

 $ cd /u01/Stage12/startCD/Disk1/rapidwiz
 $ ./rapidwiz

Using an Alias For the Host Machine
If you want to use an alias (not the actual name of the host machine), use the
-servername parameter when you start Rapid Install.

UNIX:
Example

 $ rapidwiz -servername

Restarting the Installation
If the installation process terminates before completion, you can use the -restart
parameter to run Rapid Install again.

UNIX:
Example

 $ rapidwiz –restart

Installing a New Technology Stack
Rapid Install can a install new technology stack for the database tier (Oracle10g R2) or
the Applications node (Oracle Application Server 10g) in an existing system. To access
the Rapid Install screen flow for a technology stack installation, use the -techstack
parameter when you start Rapid Install.

UNIX:
Example

 $ rapidwiz –techstack




Note: The scripts for these services are located in $INST_TOP/admin/scripts.



Set Up Printers
To register printers in the Printers form of Oracle Applications, the system
administrator must know each printer's operating system name. To determine the
names, do the following:

UNIX:
At the command prompt, enter:
Example

 $ lpstat -p



Post Installation Steps:
Perform the following steps after installing or upgrading to Release 12 and before allowing users to access the system.
LD_LIBRARY_PATH Environment Variable
Dynamic libraries are used as part of the relinking and execution processes. The LD_LIBRARY_PATH environment variable is used by Oracle Applications to locate the required dynamic libraries at runtime. Rapid Install sets LD_LIBRARY_PATH as follows:
On each application tier server node:
LD_LIBRARY_PATH is set in three places:
• $APPL_TOP/admin/adovars.env
• $ORA_CONFIG_HOME/10.1.2/.env, in the 10.1.2 Oracle home directory
• $ORA_CONFIG_HOME/10.1.3/.env, in the 10.1.3 Oracle home directory
To change the value in any of the application tier locations, use the Edit Parameters function of the OAM AutoConfig tool to update the following fields (as required). Then, run AutoConfig (adautocfg.sh) to implement the changes.
Location Parameter
adovars LD_LIBRARY_PATH
10.1.3 Oracle Home LD_LIBRARY_PATH
Tools Oracle Home LD_LIBRARY_PATH

On the database server node:
LD_LIBRARY_PATH is set in $ORACLE_HOME/.env.
Net Service Listeners in Multi-user Installations
Net Service Listeners use the /var/tmp/.oracle directory to store temporary files. To give all users in a multi-user installation write privileges, update /var/tmp/.oracle with 777 permissions:
$ chmod 777 /var/tmp/.oracle

Create DQM Indexes
If you installed the Release 12 Vision Demo Database, create DQM indexes using the following steps:
1. Log on to Oracle Applications with the "Trading Community Manager" responsibility.
2. Click Control > Request > Run.
3. Select the Single Request option.
4. Enter "DQM Staging Program" name.
5. Enter the following parameters:
o Number of Parallel Staging Workers: 4
o Staging Command: CREATE_INDEXES
o Continue Previous Execution: NO
o Index Creation: SERIAL
6. Click Submit.

Steps to Schedule a Concurrent Request

1. In the Navigator window, select the Run function in the requests menu item and click the Open button or press Alt+ O

2. Ensure that the Single Request option button is selected and click the OK button or press Alt+ O

3. Select the name of the request you want to run from the list of available requests.

4. Optionally, define the parameter values for the request in the Parameter dialog box.

5. Click the schedule button or press Alt +D to define the submission schedule for the request.

6. Select a type of schedule in the Schedule dialog box, specify the schedule details, and click the OK button or press Alt +O.

7. Optionally, select the Options button to define completion options for the request.

8. Click the submit button or press Alt +M to submit the request.

9. Select the Yes button in the Decision dialog box to submit another request.