Oracle9i Quick Installation Procedure

HP-UX 11.0 (64-bit) Operating System Patches	Status
Dec 2000 patch bundle	Required
PHCO_23092	Required
PHCO_23770	Required
PHKL_23919 Required for Oracle Real Application Clusters and Oracle Parallel Fail Safe.	Required
PHKL_23226	Required
PHNE_23249 Note: Refer to the special installation instructions to install any additional required patches	Required
PHSS_23377 until July 2001. Patch PHSS_23377 is an interim patch. It is available until July 2001 at the following FTP site: ftp://hprc.external.hp.com/ This patch will be superseded by general release patch PHSS_23440, which is available at the HP individual patch site at the end of June, 2001	Required
hyperfabric driver: 11.00.12 (HP-UX 11.0)	Required only if your system has an older hyperfabric driver version.

Important Pre-installation step:

Due to a known HP bug (Doc.id. KBRC00003627), the default HP-UX 64 operating system installation does not create a few required X-library symbolic links. These links must be created manually before starting Oracle9i installation. To create these links, you must have superuser privileges, as the links are to be created in the /usr/lib directory. After enabling superuser privileges, run the following commands to create the required links:
```
$  cd /usr/lib 
$  ln -s  /usr/lib/libX11.3 libX11.sl 
$  ln -s  /usr/lib/libXIE.2 libXIE.sl 
$  ln -s  /usr/lib/libXext.3 libXext.sl 
$  ln -s  /usr/lib/libXhp11.3 libXhp11.sl 
$  ln -s  /usr/lib/libXi.3 libXi.sl 
$  ln -s  /usr/lib/libXm.4 libXm.sl 
$  ln -s  /usr/lib/libXp.2 libXp.sl 
$  ln -s  /usr/lib/libXt.3 libXt.sl 
$  ln -s  /usr/lib/libXtst.2 libXtst.sl 
```

Operating System Software Requirements

OS Software Requirements

OS Software	Requirements
Operating System Packages	None.
X Server and Window Manager	Use any X server supported by your UNIX operating system vendor. Use any Motif-based window manager supported by your UNIX operating system vendor. For Hummingbird eXceed, use native window manager. For WRQ Reflections, allow remote window manager. To determine if your X windows system is working properly on your local system, enter the following command: `$ xclock`
Required Executables	The `make`, `ar`, `cc`, `ld`, and `nm` executables must be present in the `/usr/ccs/bin` directory.

Operating System Packages

None.

X Server and Window Manager

Use any X server supported by your UNIX operating system vendor. Use any Motif-based window manager supported by your UNIX operating system vendor.

For Hummingbird eXceed, use native window manager.

For WRQ Reflections, allow remote window manager.

To determine if your X windows system is working properly on your local system, enter the following command:

$ xclock

Required Executables

The make, ar, cc, ld, and nm executables must be present in the /usr/ccs/bin directory.

Note:

Non-interactive installation can be done using a response file. Response file templates are located on the Oracle9i CD-ROM Disk 1 in the response directory. It is not possible to install Oracle9i non-interactively without X Window System or an X Window emulator.

Pre-Installation Tasks

Complete the following pre-installation tasks in order to ensure that Oracle9i is properly installed and that you can use the database after installation.

Determine Shell File Size Limit

Oracle9i includes native support for files greater than 2 GB. However, your operating system shell may impose a file size limit.

To determine if your shell will impose a file size limit, use the following command:

Bourne (sh) / Korn (ksh) Shell

$ ulimit -f

Multiply the file (blocks) value by 512 to obtain the maximum file size in bytes imposed by the shell. For example, if file (blocks) is set to 2097148, the maximum size of the file that you can fully access will be 1 GB.

C (csh) Shell

% ulimit filesize

This will return the file size limit in kilobytes.

If you need assistance changing the value for the shell file size limit, contact your operating system vendor or your system administrator.

Review Kernel Parameters

Oracle9i uses UNIX resources such as shared memory, swap memory and semaphores extensively for interprocess communication. If your kernel parameter settings are insufficient for Oracle9i, you will experience problems during installation and instance startup. The greater the amount of data you can store in memory, the faster your database will operate. In addition, by maintaining data in memory, the UNIX kernel reduces disk I/O activity.

Use the System Administrator's Menu (SAM) to configure the HP kernel with the minimum requirements. Refer to the following table to determine if your system shared memory and semaphore kernel parameters are set high enough for Oracle9i.

Use the ipcs command to obtain a list of the system's current shared memory and semaphore segments, and their identification number and owner.

The parameters in the following table are the minimum values required to run Oracle9i with a single database instance.

Kernel Parameter	Setting	Purpose
KSI_ALLOC_MAX	(NPROC * 8)	Defines the system wide limit of queued signal that can be allocated.
MAXDSIZ	1073741824 bytes	Refers to the maximum data segment size for 32-bit systems. Setting this value too low may cause the processes to run out of memory.
MAXDSIZ_64	2147483648 bytes	Refers to the maximum data segment size for 64-bit systems. Setting this value too low may cause the processes to run out of memory.
MAXSSIZ	134217728 bytes	Defines the maximum stack segment size in bytes for 32-bit systems.
MAXSSIZ_64BIT	1073741824	Defines the maximum stack segment size in bytes for 64-bit systems.
MAXSWAPCHUNKS	(available memory)/2	Defines the maximum number of swap chunks where SWCHUNK is the swap chunk size (1 KB blocks). SWCHUNK is 2048 by default.
MAXUPRC	(NPROC + 2)	Defines maximum number of user processes.
MSGMAP	(NPROC + 2)	Defines the maximum number of message map entries.
MSGMNI	NPROC	Defines the number of message queue identifiers.
MSGSEG	(NPROC * 4)	Defines the number of segments available for messages.
MSGTQL	NPROC	Defines the number of message headers.
NCALLOUT	(NPROC + 16)	Defines the maximum number of pending timeouts.
NCSIZE	((8 * NPROC + 2048) + VX_NCSIZE)	Defines the Directory Name Lookup Cache (DNLC) space needed for inodes. VX_NCSIZE is by default 1024.
NFILE	(15 * NPROC + 2048)	Defines the maximum number of open files.
NFLOCKS	NPROC	Defines the maximum number of files locks available on the system.
NINODE	(8 * NPROC + 2048)	Defines the maximum number of file locks.
NKTHREAD	(((NPROC * 7) / 4) + 16)	Defines the maximum number of kernel threads supported by the system.
NPROC	4096	Defines the maximum number of processes.
SEMMAP	((NPROC * 2) + 2)	Defines the maximum number of semaphore map entries.
SEMMNI	(NPROC * 2)	Defines the maximum number of semaphore sets in the entire system.
SEMMNS	(NPROC * 2) * 2	Sets the number of semaphores in the system. The default value of SEMMNS is 128, which is, in most cases, too low for Oracle9i software.
SEMMNU	(NPROC - 4)	Defines the number of semaphore undo structures.
SEMVMX	32768	Defines the maximum value of a semaphore.
SHMMAX	Available physical memory	Defines the maximum allowable size of one shared memory segment. The SHMMAX setting should be large enough to hold the entire SGA in one shared memory segment. A low setting can cause creation of multiple shared memory segments which may lead to performance degradation.
SHMMNI	512	Defines the maximum number of shared memory segments in the entire system.
SHMSEG	32	Defines the maximum number of shared memory segments one process can attach.
VPS_CEILING	64	Defines the maximum System-Selected Page Size in kilobytes.
Note: These are minimum kernel requirements for Oracle9i. If you have previously tuned your kernel parameters to levels equal to or higher than these values, continue to use the higher values. A system restart is necessary for kernel changes to take effect.

Complete root user set-up tasks:

Create database administrator groups by using the System Administrator's Menu (SAM).

The OSDBA group, typically dba.
The optional OSOPER, group, typically oper.
The optional ORAINVENTORY group, typically oinstall.

Grant the OSDBA group RTSCHED, RTPRIO and MLOCK privileges.

A new HP scheduling policy called SCHED_NOAGE enhances Oracle9i's performance by scheduling Oracle processes so that they do not increase or decrease in priority, or become preempted.

The RTSCHED and RTPRIO privileges grant Oracle the ability to change its process scheduling policy to SCHED_NOAGE and also tell Oracle what priority level it should use when setting the policy. The MLOCK privilege grants Oracle the ability to execute asynch I/Os through the HP asynch driver. Without this privilege, Oracle9i generates trace files with the following error message: "Ioctl ASYNCH_CONFIG error, errno = 1".

As root, do the following:
If it does not already exist, create the /etc/privgroup file. Add the following line to the file:
```
dba MLOCK RTSCHED RTPRIO
```

Use the following command syntax to assign these privileges:

#setpriv groupname privileges

In the preceding command, groupname is the name of the group that receives the privileges, and privileges are the privileges that are granted to the group.

For example, to set the privileges for the OSDBA group, which is typically named dba, enter the following command:

#setprivgrp dba MLOCK RTSCHED RTPRIO

See Also:

For more information about system privileges, the OSDBA and OSOPER privileges, and how they may be used for Oracle9i administration, refer to Oracle9i Database Administrator's Guide.

For more information about system privileges and roles, refer to the GRANT command in the Oracle9i SQL Reference Manual.

For more information about the ORAINVENTORY group, the oraInventory directory, and sharing Oracle repository information while preserving separate DBA access to databases, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Create UNIX Groups for Database Administrators" in Chapter 2.

Create the oracle and APACHE accounts using the System Administrator's Menu (SAM).

The oracle account should have the following characteristics:

The APACHE account should have the following characteristics:

The primary group is the ORAINVENTORY group.

The secondary group is a group in which only APACHE is a member.

The account has minimum privileges.

See Also:

For more information on security and ownership of Apache processes, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Create a UNIX Account to Own the Apache Server" in Chapter 2.

Oracle Corporation has updates on maintaining security with Oracle products and Apache at the following site:

http://www.oracle.com/support

For more information on Apache configuration and examples, refer to Apache version 1.3 User's Guide.

Create mount points for the Oracle software and database.

Basic installation requires at least two mount points: one for the software and at least one for the database files. At a minimum, allow 850 MB for the software mount point and 450 MB for the database mount point.

Optimal Flexible Architecture (OFA)-Compliant installation requires at least four mount points: one for the software and at least three for database files.

Note:

For more information on issues to consider in creating mount points, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Create Mount Points" in Chapter 2.

Set system environment variables.

If it does not already exist, create a local bin directory, such as /usr/local/bin or /opt/bin. Set and verify that this directory is included in each user's PATH statement, and that users have execute permissions on the directory.

Determine if your X Window system is working properly on your local system. On the system where you will run the Oracle Universal Installer, set DISPLAY to that system's name, or the IP address, X server, and screen.

Use the database server's name, or the IP address, X server, and screen only if you are performing the installation from your database server's X Window console. If you are not sure what the X server and screen should be set to, use 0 (zero) for both.

Note:

If you receive an error similar to "Failed to connect to server," "Connection refused by server," or "Can't open display" when starting the installer, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems.

Set a temporary directory path for the TMPDIR variable with at least 20 MB of free space where the installer has write permission. Example: /var/tmp

See Also:

For more information about required and optional environmental variables, PATH settings and OFA settings, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Set Environment Variables" in Chapter 2.

Additional pre-installation tasks must be completed for Oracle tools, precompilers, networking and other products. For information about required setup tasks for additional Oracle components, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Precompilers and Tools" in Chapter 2.

Set Oracle environment variables by adding an entry similar to the following example to each user startup .profile file for the Bourne or Korn shells, or .login file for the C shell.

Note:

If you have existing Oracle home directories in your directory path, Oracle Corporation recommends that you set up a new one for Oracle9i.

For the NLS_LANG variable, enter the language environment you prefer to use. The following example assumes American English.

# Oracle Environment

ORACLE_HOME=/opt/oracle/product/9.0.1; export ORACLE_HOME
ORACLE_SID=dia2; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
TNS_ADMIN=/export/home/oracle/config/9.0.1; export TNS_ADMIN
NLS_LANG=AMERICAN_AMERICA.UTF8; export NLS_LANG
ORA_NLS33;$oracle_home/ocommon/nls/admin/data; export ORA_NLS33
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib:$ORACLE_HOME \

/rdbms/lib
SHLIB_PATH=ORACLE_HOME/lib32:$ORACLE_HOME /rdbms/lib32
export LD_LIBRARY_PATH	
export SHLIB_PATH
# Set shell search paths: 

PATH=/bin:/usr/bin:/usr/sbin:/etc:/opt/bin:/usr/ccs/bin:/usr/local \

/bin:$ORACLE_HOME/bin
export PATH

#CLASSPATH must include the following JRE locations:

CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib

Note:

DO NOT MODIFY THE JRE SYMBOLIC LINK AFTER ORACLE9i IS INSTALLED. The JRE shipped with Oracle9i is required by Oracle software. Do not modify this JRE unless it is done through a patch provided by Oracle Support. The inventory can contain multiple versions of the JRE, each of which can be used by one or more products or releases. The oraInventory file keeps an inventory of installed products and other installation information. Products in an Oracle home directory access required JREs through a symbolic link in the $ORACLE_HOME/JRE directory to the actual location of a JRE within the inventory.

Create the /var/opt/oracle directory and make it owned by the oracle account. After installation, this directory will contain a few small text files that briefly describe the Oracle software installations and databases on the server. These commands will create the directory and give it appropriate permissions:

$ mkdir /var/opt/oracle
$ chown oracle:dba /var/opt/oracle
$ chmod 755 /var/opt/oracle

CAUTION:

Additional pre-installation tasks must be completed for Oracle tools, precompilers, networking and other products.

Installation Tasks

Complete these tasks to perform a standard Oracle9i Database installation on your server and create a seed database. Oracle Corporation strongly recommends that you install a seed database to use as a prototype for configuring databases that conform to your needs.

Mount the Oracle9i CD-ROM.

There are multiple CD-ROMs included with Oracle9i. Mount Disk 1 to begin installation. Mount subsequent disks when prompted to do so. Place the Oracle9i CD-ROM Disk 1 in the CD-ROM drive. You must have root privileges to mount or unmount the CD-ROM manually. Be sure to unmount the CD-ROM before removing it from the drive by using the umount command.

If volume management is available the CD-ROM will mount automatically to the /cdrom/orcl901_1 directory when you insert it into the CD-ROM drive. To check if volume management is available use the following command:

% ps -e | grep vold

This should return a line similar to:

404 ?       16:03 vold

If no lines are returned, then volume management is not running and CD-ROM will need to be mounted manually.

Follow these steps to mount the Oracle9i CD-ROM manually:

Place the Oracle9i CD-ROM in the CD-ROM drive.
Log in as the root user and create a CD-ROM mount point if one does not already exist:
```
% su root
# mkdir cdrom_mount_point_directory
```
Mount the CD-ROM drive on the mount point directory, then exit the root account by using the following commands.
```
# mount options device_name cdrom_mount_point_directory
# exit
```

If you are unsure of the correct device_name, consult with your system administrator.

Note:

If you run the installer while the current working directory is in the CD-ROM, follow these steps to mount the next CD-ROM:

Change directory to the root directory of your system and log in as the root user by using the following commands:
```
$ cd /
$ su root
```
Unmount and remove the CD-ROM from the CD-ROM drive using the following command:
```
# umount cdrom_mount_point_directory
```
Insert and mount the next CD-ROM into the CD-ROM drive by using the following command:
```
# mount options device_name cdrom_mount_point_
directory
```
Enter the correct mount point in the Installation dialog box.
Click OK to continue.

Run the Oracle Universal Installer.

Log in as the oracle account.
Start the installer by typing in the path where the installer executable is located. Do not try to run the installer executable from within the oracle9i directory. If you do, installation will fail. The following is an example of the correct command syntax:
```
/cdrom/oracle9i/runInstaller
```
In order to ensure that you do not have problems with your installation, Oracle Corporation strongly recommends that you review Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Installation" in Chapter 3.
The Welcome window appears. Click Next.
If this is the first installation of any Oracle9i products on the database server, the Inventory Location window appears. Specify a base directory where you want to install the files, and click OK.
The UNIX Group Name window appears. Specify the group that will have permission to update Oracle software on the system. Enter the ORAINVENTORY group, or the OSDBA group if you chose not to create ORAINVENTORY. Click Next.
If pre-installation tasks were not completed, a window opens prompting you to run the orainstRoot.sh script. Oracle Corporation does not recommend this procedure, but running this script will allow you to complete the installation.
The File Locations window appears. Do not change text in the Source field. The Destination field will have the Oracle home directory path setting you defined during pre-installation.

Specify the group that has permission to update Oracle software on your system, which should be ORAINVENTORY. If you have previously installed Oracle9i products on your system, the installer obtains the UNIX group name information from its records, which are stored in the /var/opt/oracle/oraInst.loc file.
Click Next. The Available Products window appears.

Select Oracle9i Database and click Next.
The Installation Types window appears. Select Oracle9i Enterprise Edition or Standard Edition Installation. For information about installation types, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Oracle9i Installation Planning" in Chapter 1.
The Component Locations window appears. Click Next.
If you assigned the OSDBA group to a group with a different name than dba, then you are prompted to confirm the OSDBA group name. Confirm that the name is correct, and click Next.
The Database Configuration window appears. Select General Purpose and click Next.
If you have existing Oracle databases on your server prior to Oracle9i, then the installer prompts you to indicate if you want to run the Oracle Data Migration Assistant immediately after installation is complete. Make your selection, and click Next.

The Database Identification window appears.

Enter the Global Database Name and SID (system identifier) name in the provided fields for the seed database that will be created. Give your database a global name that is the same as the SID, with your domain name appended.

For example, if your domain is acme.com, and your database is to be used for sales, a suitable Global Database Name is sales.acme.com, with the SID name sales.

Note:

As the SID is incorporated into many file names, Oracle Corporation recommends restricting it to no more than four characters to avoid file name problems on different operating systems.

Click Next. The Database File Location window appears.

Enter the name of one of the mount points you chose for holding a database. The seed database will be installed in one directory under this mount point. Use the Browse... button to navigate to the mount point if necessary.
Click Next. The Database Character Set window appears. Choose the database character set to be used. Click Next.
The Summary window appears. Review your selections to confirm they are correct.
Click Install. The Install window appears. Wait for the products you have selected to be installed.

You will be prompted to insert the subsequent CD-ROMs.
The Setup Privileges window appears, and prompts you to run the root.sh script.

The installer creates the root.sh script during installation in the $ORACLE_HOME directory, and prompts you to run the script after products are installed in order to set necessary file permissions for Oracle products, and to perform other root-related configuration activities. At this point, if you choose, you may review the script before running it.

Open another window, log in to the database server as root user, and enter the following commands:
```
# cd $ORACLE_HOME
# ./root.sh
```
When prompted, specify the local bin directory. This is the directory you created in pre-installation step 5. If you neglected to do this step, the root.sh script creates one for you.
The Configuration Tools, Apache Web Server Configuration Assistant, and Oracle Net Configuration Assistant windows open after you run the root.sh script. These configuration assistants help to create and configure your database and network environments. The Configuration Tools window displays the results of running these assistants. No information needs to be provided for these installation steps.

The Database Configuration Assistant window opens. A Progress window opens and indicates actions the installer performs as it creates the seed database.

See Also:

For more information on database environment types, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Oracle9i Database Configurations" in Chapter 1.

Upon completing seed database configuration, the Database Configuration Assistant opens an alert window and shows the initial passwords for the SYS and SYSTEM database roles. Make a note of these passwords. Click the Password Management button to change the passwords for increased security. Click OK.
The End of Installation window appears. Click Exit to exit the installer. Click Exit to exit the installer, or click Next Install to install additional products.

Post-Installation Tasks

Post-installation tasks vary according to product installation types and according to individual preferences for database configuration.

See Also:

For more information about post-installation tasks, commands to unlock system administration roles, and additional product installation or configuration tasks, refer to Oracle9i Installation Guide Release 1 (9.0.1) for UNIX Systems, "Post-Installation" in Chapter 4.

Using the Seed Database to Learn About Oracle9i

The Oracle9i seed database is running after installation is complete. If you have not used Oracle products before, use the seed database to familiarize yourself with the products. Oracle Corporation recommends that you begin by looking at the following documentation:

Oracle9i Database Concepts Guide
Oracle9i Database Administrator's Guide
SQL*Plus User's Guide and Reference

These books outline the fundamentals of database use and administration. The documentation can be found online at the following site:

http://docs.oracle.com

Shutting Down the Seed Database

To shut down the database enter the following commands:

$ sqlplus "/ as sysdba"
SQL> shutdown immediate
SQL> exit

Oracle9i

Purpose of this Procedure

Requirements

Pre-Installation Tasks

Determine Shell File Size Limit

Review Kernel Parameters

Complete root user set-up tasks:

Installation Tasks

Post-Installation Tasks

Using the Seed Database to Learn About Oracle9i

Shutting Down the Seed Database