| Oracle® Database Installation Guide 11g Release 2 (11.2) for HP-UX Part Number E10851-04 |
|
|
View PDF |
| Oracle® Database Installation Guide 11g Release 2 (11.2) for HP-UX Part Number E10851-04 |
|
|
View PDF |
This chapter describes the tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:
Note:
This guide contains information required to install Oracle Database 11g Release 2 (11.2) on various platforms. Ensure that you review information related to the platform on which you intend to install Oracle Database 11g.
If you want to use Automatic Storage Management or Oracle Restart, then you must first install Oracle grid infrastructure for a standalone server and then install Oracle Database.
See Also:
"Requirements for Oracle Grid Infrastructure Installation" for installation requirements for Oracle grid infrastructure
"Pre-installation Requirements" section in Oracle Configuration Manager Installation and Administration Guide and Oracle Configuration Manager Prerequisites for preinstallation requirements for Oracle Configuration Manager
Appendix A, "Country Codes", in Oracle Configuration Manager Installation and Administration Guide for a list of valid country codes that can be used while installing Oracle Configuration Manager
Before you install the Oracle software, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures:
Note:
Unless you intend to complete a silent-mode installation, you must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.For more information about silent-mode installations, refer to Appendix A.
Following are the steps for installing the software from an X Window System workstation or X terminal:
Start a local terminal session, for example, an X terminal (xterm).
If you are not installing the software on the local system, then enter the following command to enable the remote host to display X applications on the local X server:
$ xhost fully_qualified_remote_host_name
For example:
$ xhost somehost.us.example.com
If you are not installing the software on the local system, then use the ssh, rlogin, or telnet command to connect to the system where you want to install the software:
$ telnet fully_qualified_remote_host_name
If you are not logged in as the root user, then enter the following command to switch user to root:
$ sudo sh password: #
Following are the steps for installing the software from a PC or other system with X server software:
Note:
If necessary, refer to the X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order.Start the X server software.
Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm).
If you are not logged in as the root user on the remote system, then enter the following command to switch user to root:
$ sudo sh password: #
The system must meet the following minimum hardware requirements:
The following are the memory requirements for installing Oracle Database 11g Release 2:
At least 4 GB of RAM
To determine the RAM size, enter the following command:
On HP-UX PA-RISC
# grep "Physical:" /var/adm/syslog/syslog.log
On HP-UX Itanium
# /usr/contrib/bin/machinfo | grep -i Memory
If the size of the RAM is less than the required size, then you must install more memory before continuing.
The following table describes the relationship between installed RAM and the configured swap space requirement:
| RAM | Swap Space |
|---|---|
| Between 4 GB and 8 GB | 2 times the size of RAM |
| Between 8 GB and 32 GB | 1.5 times the size of RAM |
| More than 32 GB | 32 GB |
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swapinfo -a
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
Note:
Oracle recommends that you take multiple values for the available RAM and swap space before finalizing a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.The following are the disk space requirements for installing Oracle Database 11g Release 2 (11.2):
At least 1 GB of disk space in the /tmp directory
To determine the amount of disk space available in the /tmp directory, enter the following command:
# bdf /tmp
If the free disk space available in the /tmp directory is less than what is required, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment.
See Also:
"Configuring the oracle User's Environment" for more information on settingTMP and TMPDIRExtend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# bdf
The following tables describe the disk space requirements for software files, and data files for each installation type on HP-UX Itanium systems:
| Installation Type | Requirement for Software Files (GB) |
|---|---|
| Enterprise Edition | 6.89 |
| Standard Edition | 6.09 |
| Custom (Enterprise Edition + custom install options) | 6.89 |
| Installation Type | Disk Space for Data Files (GB) |
|---|---|
| Enterprise Edition | 1.69 |
| Standard Edition | 1.48 |
| Custom (Enterprise Edition + custom install options) | 1.81 |
The following tables describe the disk space requirements for software files, and data files for each installation type on HP-UX PA-RISC systems:
| Installation Type | Requirement for Software Files (GB) |
|---|---|
| Enterprise Edition | 8.20 |
| Standard Edition | 8.00 |
| Custom (Enterprise Edition + custom install options) | 8.20 |
| Installation Type | Disk Space for Data Files (GB) |
|---|---|
| Enterprise Edition | 2.72 |
| Standard Edition | 2.68 |
| Custom (Enterprise Edition + custom install options) | 2.76 |
Additional disk space, either on a file system or on an Automatic Storage Management disk group is required for the fast recovery area if you choose to configure automated backups.
The minimum display requirement for Oracle Database 11g Release 2 (11.2) is a resolution of 1024 x 768 or higher.
Depending on the products that you intend to install, verify that the following softwares are installed on the system.
Note:
This guide contains information required to install Oracle Database 11g Release 2 (11.2) on various platforms. Ensure that you review information related to the platform on which you intend to install Oracle Database 11g.
Oracle Universal Installer performs checks on the system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.
The following are the operating system requirements for Oracle Database 11g Release 2 (11.2) on HP-UX Itanium and HP-UX PA-RISC systems:
HP-UX 11i V3 patch Bundle Sep/ 2008 (B.11.31.0809.326a) or higher
To determine the distribution and version of HP-UX installed, enter the following command:
# uname -a
HP-UX hostname B.11.31 U ia64 4156074294 unlimited-user license
In this example, the version of HP-UX 11i is 11.31.
Verify that the system meets the minimum patch bundle requirements using the following command:
# /usr/sbin/swlist -l bundle |grep QPK
The QPK (Quality Pack) bundles have version numbers of the form B.11.31.0809.326a (for the September 2008 release), B.11.31.0903.334a (for the March 2009 release), and so on.
If a required bundle, product, or fileset is not installed, then you must install it. Refer to your operating system or software documentation for information about installing products.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed.The following are the compiler requirements for HP-UX systems Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) with Oracle Database 11g Release 2 (11.2):
On HP-UX PA RISC:
HP ANSI C B.11.31.04 (Swlist Bundle - C.11.31.04) - September 2008
aC++ A.03.85 (Swlist Bundle - C.11.31.04) - September 2008
On HP-UX Itanium:
Depending on the components you want to use, you must ensure that the following software are installed:
See Also:
Chapter 2, "Oracle Application Express Installation Requirements" and "Recommended Pre-installation Tasks" in Oracle Application Express Installation GuideOracle ODBC driver on HP UX Itanium is certified with ODBC Driver Manager 2.2.14. You can download and install the Driver Manager from the following link:
You do not require ODBC Driver Manager to install Oracle Database.
To use ODBC, you must also install gcc 3.4.5 or later .
You can use thefollowing JDK versions:
HPUX JDK 6.0.05
HPUX JDK 5.0.15
Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with the following software:
If you require a CSD for WebSphere MQ, then refer to the following Web site for download and installation information:
The following products are certified for use with:
Pro* COBOL
Micro Focus Server Express 5.1
Pro* FORTRAN
HP FORTRAN/90 - Sep 2008 - release
Web browsers must support JavaScript, and the HTML 4.0 and CSS 1.0 standards. The following browsers meet these requirements for Oracle Enterprise Manager Database Control:
Netscape Navigator 8.1
Netscape Navigator 9.0
Microsoft Internet Explorer 6.0 SP2
Microsoft Internet Explorer 7.0
Microsoft Internet Explorer 7.0 SP1
Microsoft Internet Explorer 8.0
Firefox 2.0
Firefox 3.0.7
Safari 3.0.4
Safari 3.1
Safari 3.2
If you want to install Oracle Database Vault, then set the DB_BLOCK_SIZE initialization parameter to 4096 or larger. If the value is less than 4096, then you cannot change it. The only way to change the DB_BLOCK_SIZE value is by re-creating the database.
The following, or later, patches and bundles are required for Oracle Database 11g Release 2 (11.2) for HP-UX systems.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, then determine whether a more recent version is installed before installing the version listed. The installer will check for superseding patches.For HP-UX Itanium:
| Installation Type or Product | Requirement |
|---|---|
| All installations | For HP-UX 11i V3 (11.31):
|
| Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) | Patch for HP-UX 11i V3 (11.31) on HP-UX Itanium:
PHSS_39824 - 11.31 HP C/aC++ Compiler (A.06.23) patch |
| VERITAS File System | PHKL_39773: 11.31 VRTS 5.0 GARP6 VRTSvxfs Kernel Patch
Note: The VERITAS file system is optional. This patch is required only if you want to use a VERITAS File System 5.0. |
For HP-UX PA-RISC:
| Installation Type or Product | Requirement |
|---|---|
| All installations | For HP-UX 11i V3 (11.31):
|
| VERITAS File System | PHKL_39773: 11.31 VRTS 5.0 GARP6 VRTSvxfs Kernel Patch.
Note: This patch has no other dependencies. It is included in the September 2009 update of HP-UX 11.31. It is needed only when VxFS 5.0 is installled. |
To ensure that the system meets these requirements:
To determine whether a patch is installed, enter a command similar to the following:
# /usr/sbin/swlist -l patch | grep PHSS_37959
Alternatively, to list all installed patches, enter the following command:
# /usr/sbin/swlist -l patch | more
If a required patch is not installed, then download it from the following Web site and install it:
http://itresourcecenter.hp.com
If the Web site displays a recent version of the patch, then download and install that version.
During installation, for certain prerequisite check failures, you can click Fix & Check Again to generate a fixup script (runfixup.sh). You can run this script as a root user to complete the required preinstallation steps.
The fixup script does the following:
Checks and sets kernel parameters to values required for successful installation, including:
Shared memory parameters
Open file descriptor and UDP send/receive parameters
Oracle recommends that you do not modify the contents of the generated fixup script.
Note:
Using fixup scripts will not ensure that all the prerequisites for installing Oracle Database are satisfied. You must still verify that all the preinstallation requirements are met to ensure a successful installation.Typically, the computer on which you want to install Oracle Database is connected to the network. The computer has local storage, to store the Oracle Database installation. It also contains a display monitor, and DVD drive. This section describes how to install Oracle Database on computers that do not meet the typical scenario. It covers the following cases:
Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing enables a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.
In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign a unique IP address to the newly added computer.
You can install Oracle Database on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name. In addition, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name. If ORACLE_HOSTNAME is not set and you are installing on a computer that has multiple network cards, then Oracle Universal Installer determines the host name from the /etc/hosts file.
Clients must be able to access the computer either by using this host name or by using aliases for this host name. To verify this, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both tests must be successful.
Setting the ORACLE_HOSTNAME Environment Variable
Use the following procedure to set the ORACLE_HOSTNAME environment variable. For example, if the fully qualified host name is somehost.us.example.com, then enter one of the following commands:
In Bourne, Bash, or Korn shell:
$ ORACLE_HOSTNAME=somehost.us.example.com $ export ORACLE_HOSTNAME
In C shell:
% setenv ORACLE_HOSTNAME somehost.us.example.com
A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.
You can install Oracle Database on a non-networked computer. If the computer, such as a laptop, is configured for DHCP and you plan to connect the computer to the network after the Oracle Database installation, then use the ping command on the computer on which you want to install the database to check if the computer can connect to itself. Perform this step by first using only the host name and then using the fully qualified name, which should be in the /etc/hosts file.
Note:
When you run theping command on the computer itself, the ping command should return the IP address of the computer.If the ping command fails, then contact the system administrator.
Connecting the Computer to the Network after Installation
If you connect the computer to a network after installation, then the Oracle Database instance on the computer can work with other instances on the network. The computer can use a static IP or DHCP, depending on the network to which you are connected.
Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create several operating system groups and users.
If you prefer to allocate operating system user privileges so that you can use one administrative user and one group for operating system authentication for all administrative privileges, then you can use the oracle user as the installation owner, and use one group as the primary group for any user requiring administrative privileges for Automatic Storage Management, and Oracle Database administration. This group must also be the Oracle Inventory group. To simplify using the defaults for Oracle tools the group name should be oinstall.
You can also create custom configuration groups and users based on job role separation. A custom configuration is a configuration with groups and users that divide access privileges granted by membership in separate operating system groups and users. You can create a single user (for example, oracle) to own both Oracle database, and Oracle grid infrastructure installations. Alternatively, you can create a separate user (for example, grid) to own the Oracle grid infrastructure installation.
Creating Custom Configuration Groups and Users for Job Roles
Creating Database Operating System Groups and Users with Job Role Separation
Note:
In Oracle documentation, a user created to own only Oracle grid infrastructure software installations is called thegrid user. A user created to own either all Oracle installations, or only Oracle database installations, is called the oracle user.This section provides an overview of how to create users and groups to divide access privileges by job roles. Log in as root to create these groups and users.
Oracle recommends that you create one software owner to own each Oracle software installation (typically, oracle, for the database software and grid for the Oracle Restart owner user). You must create at least one software owner the first time you install Oracle software on the system.
Oracle software owners must have the Oracle Inventory group as their primary group, so that each Oracle software installation owner can write to the Central Inventory. The database software owner (typically, oracle) must also have the OSDBA group of the grid infrastructure home so that database instances can log on to Automatic Storage Management, and (if you create it) the OSOPER group as secondary groups. In Oracle documentation, the Oracle software owner users are referred to as oracle users.
For Oracle grid infrastructure only, the grid user (grid) needs to be in the OSDBA group of every database home.
See Also:
Oracle Database Administrator's Guide for more information about the OSDBA, OSASM and OSOPER groups, and theSYSDBA, SYSASM and SYSOPER privilegesCreate the following operating system groups if you are installing Oracle Database:
The OSDBA group (typically, dba)
You must create this group the first time you install Oracle Database software on the system. This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege). The name used for this group in Oracle code examples is dba.
The OSOPER group for Oracle Database (typically, oper)
This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of database administrative privileges (the SYSOPER privilege). This group cannot directly connect as SYSOPER, unless explicitly granted. However, they will have the privileges granted by the SYSOPER privilege. By default, even members of the OSDBA group have all privileges granted by the SYSOPER privilege.
Oracle Universal Installer prompts you to specify the name of this group. The usual name chosen for this group is oper.
Create the following operating system groups if you are installing Oracle grid infrastructure:
Note:
You can designate a unique group, separate from database administrator groups, or you can use the same group as the OSASM and OSDBA group, to grant system privileges to administer both the ASM instances and Oracle Database instances.The OSDBA group for Automatic Storage Management (typically, asmdba)
The OSDBA group for Automatic Storage Management can be the same group used as the OSDBA group for the database, or you can create a separate OSDBA group for Automatic Storage Management (typically, asmdba) to provide administrative access to Automatic Storage Management instances.
The Oracle grid infrastructure software owner (typically, grid) must be a member of the OSDBA group. Membership in the OSDBA group allows access to the files managed by Automatic Storage Management. If you have a separate OSDBA group for Automatic Storage Management, then the Oracle Restart software owner must be a member of the OSDBA group for each database and the OSDBA group for Automatic Storage Management.
The OSASM group for Automatic Storage Management (typically, asmadmin)
SYSASM privileges for Automatic Storage Management files provide administrator privileges for storage file. In Oracle documentation, the operating system group whose members are granted SYSASM privileges is called the OSASM group, and in command lines, is referred to as asmadmin. Automatic Storage Management can support multiple databases.
Members of the OSASM group can use SQL to connect to an Automatic Storage Management instance as SYSASM using operating system authentication. The SYSASM privileges permit mounting and dismounting disk groups, and other storage administration tasks. SYSASM privileges provide no access privileges on an RDBMS instance.
If you do not designate a separate group as the OSASM group, then the OSDBA group you define is also by default the OSASM group.
The OSOPER group for Automatic Storage Management (typically, asmoper)
This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of Oracle instance administrative privileges (the SYSOPER for ASM privilege), including starting up and stopping the Oracle ASM instance. By default, members of the OSASM group also have all privileges granted by the SYSOPER for ASM privilege.
If you want to have an OSOPER for ASM group, then the grid infrastructure owner must be a member of this group.
The following sections describe how to create the required operating system user and groups:
Note:
If necessary, contact your system administrator before using or modifying an existing user.Oracle recommends that you do not use the UID and GID defaults on each node, as group and user IDs likely will be different on each node. Instead, provide common assigned group and user IDs, and confirm that they are unused on any node before you create or modify groups and users.
When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group (typically, oinstall), and the path of the Oracle Inventory directory.
You can configure one group to be the access control group for the Oracle Inventory, for database administrators (OSDBA), and for all other access control groups used by Oracle software for operating system authentication. However, this group then must be the primary group for all users granted administrative privileges.
Log in as root, and use the following instructions to locate or create the Oracle Inventory group and a software owner:
Determining Whether the Oracle Inventory Group Exists
An oraInst.loc file has contents similar to the following:
inventory_loc=central_inventory_location inst_group=group
In the preceding example, central_inventory_location is the location of the Oracle Central Inventory, and group is the name of the group that has permissions to write to the central inventory.
If you have an existing Oracle Inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations, and ensure that all Oracle software users you intend to use for installation have permissions to write to this directory.
To determine if the Oracle Inventory group exist, enter the following command:
# grep oinstall /etc/group
To determine whether the oraInst.loc file exists, enter the following command:
# more /var/opt/oracle/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oraInventory inst_group=oinstall
In the previous output example:
The inventory_loc group shows the location of the Oracle Inventory
The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall).
Creating the Oracle Inventory Group
If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering the following command:
# /usr/sbin/groupadd oinstall
You must create an OSDBA group in the following circumstances:
An OSDBA group does not exist, for example, if this is the first installation of Oracle Database software on the system
An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges for a new Oracle Database installation
If the OSDBA group does not exist or if you require a new OSDBA group, then create it as follows. In the following procedure, use the group name dba unless a group with that name already exists:
# /usr/sbin/groupadd -g 502 dba
Create an OSOPER group only if you want to identify a group of operating system users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, then you must create it in the following circumstances:
If an OSOPER group does not exist; for example, if this is the first installation of Oracle Database software on the system
If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation
If you require a new OSOPER group (typically, oper), then create it as follows. In the following, use the group name oper unless a group with that name already exists:
# /usr/sbin/groupadd -g 505 oper
If the OSASM group does not exist or if you require a new OSASM group, then create it as follows. In the following procedure, use the group name asmadmin unless a group with that name already exists:
# /usr/sbin/groupadd -g 504 asmadmin
If you require a new OSDBA group for Automatic Storage Management, then create it as follows. In the following procedure, use the group name asmdba unless a group with that name already exists:
# /usr/sbin/groupadd -g 506 asmdba
If you require an OSOPER group, then create it as follows. In the following procedure, use the group name asmoper unless a group with that name already exists:
# /usr/sbin/groupadd -g 505 asmoper
You must create an Oracle software owner user in the following circumstances:
If an Oracle software owner user does not exist; for example, if this is the first installation of Oracle software on the system.
If an Oracle software owner user exists, but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation.
If you have created an Oracle software owner for Oracle grid infrastructure, such as grid, and you want to create a separate Oracle software owner for Oracle Database software, such as oracle.
To determine whether an Oracle software owner user named oracle, or grid exists, enter a command similar to the following (in this case, to determine if oracle exists):
# id oracle
If the user exists, then the output from this command is similar to the following:
uid=501(oracle) gid=501(oinstall) groups=502(dba),503(oper)
Determine whether you want to use the existing user, or create another user. If you want to use the existing user, then ensure that the user's primary group is the Oracle Inventory group (oinstall) and that it is a member of the appropriate OSDBA and OSOPER groups. Refer to one of the following sections for more information:
Note:
If necessary, contact your system administrator before using or modifying an existing user.If the Oracle software owner user does not exist, or if you require a new Oracle software owner user, such as oracle or grid, then create it as described in this section (in this case to create the oracle user).
In the following procedure, use the user name oracle unless a user with that name already exists:
To create an oracle user, enter a command similar to the following:
# /usr/sbin/useradd -u 502 -g oinstall -G dba,asmdba,[oper] oracle
In the preceding command:
The -u option specifies the user ID. Using this command flag is optional, as you can allow the system to provide you with an automatically generated user ID number. However, you must make note of the oracle user ID number, as you require it later during preinstallation.
The -g option specifies the primary group, which must be the Oracle Inventory group--for example, oinstall
The -G option specifies the secondary groups, which must include the OSDBA group, and, if required, the OSOPER and ASMDBA groups. For example: dba, or asmdba,oper
Set the password of the oracle user:
# passwd oracle
If the oracle user exists, but its primary group is not oinstall, or it is not a member of the appropriate OSDBA or OSOPER groups, then modify it as follows:
Specify the primary group using the -g option and any required secondary group using the -G option:
# /usr/sbin/usermod -g oinstall -G dba,asmdba[,oper] oracle
During installation, you can generate and run the Fixup script to check and set the kernel parameter values required for successful installation of the database. This script updates required kernel packages if necessary to minimum values.
If you cannot use the Fixup scripts, then verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown. The procedure following the table describes how to verify and set the values manually.
Note:
The kernel parameter and shell limit values shown in the following section are minimum values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. Refer to the operating system documentation for more information about tuning kernel parameters.Note:
If the current value for any parameter is higher than the value listed in this table, then do not change the value of that parameter. The following kernel parameters are obsolete on HP-UX 11.31. You need not specify values for these parameters:msgmap
ncallout
msgseg
To display the current value or formula specified for these kernel parameters, and to change them if necessary:
For HP-UX PA RISC:
Follow these steps:
Optionally, set the DISPLAY environment variable to specify the display of the local system:
Bourne, Bash, or Korn shell:
# DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
# setenv DISPLAY local_host:0.0
Start System Administration Manager (SAM):
# /usr/sbin/sam
Choose the Kernel Configuration area, then choose the Configurable Parameters area.
Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.
If necessary, refer to the SAM online Help for more information about completing this step.
If necessary, when the system restarts, log in and switch user to root.
For HP-UX Itanium:
Enter the following command to start the kcweb application:
# /usr/sbin/kcweb -F
Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.
If necessary, refer to the kcweb online Help for more information about completing this step.
Note:
If you modify the value of a parameter that is not dynamic, then you must restart the system.You must identify or create the following directories for the Oracle software:
Note:
Ensure that the paths you select for Oracle software, such as the Oracle home path and the Oracle base path, use only ASCII characters. Because installation owner names are used by default for some path, this ASCII character restriction applies to user names, file names, and directory names.The Oracle base directory is a top-level directory for Oracle software installations. The Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:
/mount_point/app/software_owner
mount_point is the mount point directory for the file system that will contain the Oracle software.
The examples in this guide use /u01 for the mount point directory. However, you can choose another mount point directory, such as /oracle or /opt/oracle.
software_owner is the operating system user name of the software owner installing the Oracle software, for example oracle, or grid.
Note:
If you start a database instance usingspfile with ORACLE_BASE environment variable set, then its value is automatically stored in spfile. If you unset ORACLE_BASE environment variable subsequently and start the instance afresh, then database uses the value of Oracle base stored in spfile.You must specify the Oracle base folder that contains all Oracle products.
Note:
If you have an existing Oracle base, then you can select it from the Use existing list. By default, the list contains the existing value for Oracle base preselected. Refer to "Installing the Oracle Database Software" for further information.If you do not have an Oracle base, then you can create one by editing the text in the list box.
You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations. If different operating system users install Oracle software on the same system, then each user must create a separate Oracle base directory. The following are examples of Oracle base directories that can exist on the same system:
/u01/app/oracle /u01/app/orauser /opt/oracle/app/oracle
Refer to "Creating an Oracle Base Directory" for information on creating an Oracle base directory.
The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required and shared by all Oracle software installations on a single system. If you have an existing Oracle Inventory path, then Oracle Universal Installer continues to use that Oracle Inventory.
The first time you install Oracle software on a system, Oracle Universal Installer checks if you have created an OFA-compliant directory structure with the format u[01-09]/app, such as /u01/app, and that the user running the installation has permissions to write to that path. If this is true, then Oracle Universal Installer creates the Oracle Inventory directory similar to /u[01-09]/app/oraInventory. For example:
/u01/app/oraInventory
If you have set the environment variable ORACLE_BASE for the oracle user, then Oracle Universal Installer creates the Oracle Inventory directory similar to $ORACLE_BASE/../oraInventory. For example, if ORACLE_BASE is set to /opt/oracle/11, then the Oracle Inventory directory is created similar to /opt/oracle/oraInventory.
If you have neither created an OFA-compliant path nor set ORACLE_BASE, then the Oracle Inventory directory is placed in the home directory of the user that is performing the installation. For example:
/home/oracle/oraInventory
Oracle Universal Installer creates the directory that you specify and sets the correct owner, group, and permissions for it. You do not need to create it.
Note:
All Oracle software installations rely on this directory. Ensure that you back it up regularly.
Do not delete this directory unless you have completely removed all Oracle software from the system.
By default, the Oracle Inventory directory is not installed under the Oracle Base directory. This is because all Oracle software installations share a common Oracle Inventory, so there is only one Oracle Inventory for all users. Whereas, there is a separate Oracle Base for each user.
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products or different releases of the same Oracle product in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory as well as a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:
oracle_base/product/11.2.0/dbhome_1
Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not need to create this directory.
Note:
During installation, you must not specify an existing directory that has predefined permissions applied to it as the Oracle home directory. If you do, then you may experience installation failure due to file and group ownership permission errors.Before starting the installation, you must either identify an existing Oracle base directory or if required, create one. This section contains information about the following:
Note:
You can choose to create an Oracle base directory, even if other Oracle base directories exist on the system.Existing Oracle base directories may not have paths that comply with OFA (Optimal Flexible Architecture) guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, then you can usually identify the Oracle base directories, as follows:
Identifying an existing Oracle Inventory directory. Refer to "Creating the Oracle Inventory Group" for more information.
Note:
Oracle recommends that you do not put theoraInventory directory under Oracle base for a new installation. However, if you have an existing installation, then you should follow the steps suggested in this section.Identifying an existing Oracle home directory
Enter the following command to display the contents of the oratab file:
# more /etc/oratab
If the oratab file exists, then it contains lines similar to the following:
*:/u03/app/oracle/product/11.2.0/dbhome_1:N *:/opt/orauser/infra_904:N *:/oracle/9.2.0:N
The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner that you want to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, then you can choose one of the following directories listed in the previous example:
/u03/app/oracle /oracle
Note:
If possible, choose a directory path similar to the first one (/u03/app/oracle). This path complies with the OFA guidelines.Identifying an existing Oracle base directory
After you have located the Oracle home directory, you can run the following command to confirm the location of Oracle base:
cat inventory/ContentsXML/oraclehomeproperties.xml
Before deciding to use an existing Oracle base directory for this installation, ensure that it satisfies the following conditions:
It should not be on the same file system as the operating system.
To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:
# bdf oracle_base_path
To continue:
If an Oracle base directory exists and you want to use it, then refer to the "Choosing a Storage Option for Oracle Database and Recovery Files" section.
When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.
If an Oracle base directory does not exist on the system or if you want to create an Oracle base directory, then refer to the following section.
Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space.
To identify an appropriate file system:
To determine the free disk space on each mounted file system use the following command:
# bdf
From the display, identify a file system that has appropriate free space.
The file system that you identify can be a local file system, a cluster file system, or an NFS file system on a certified NAS device.
Note the name of the mount point directory for the file system that you identified.
To create the Oracle base directory and specify the correct owner, group, and permissions for it:
Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:
# mkdir -p /mount_point/app/oracle_sw_owner # chown -R oracle:oinstall /mount_point/app/oracle_sw_owner # chmod -R 775 /mount_point/app/oracle_sw_owner
For example:
# mkdir -p /u01/app/oracle # chown -R oracle:oinstall /u01/app/oracle # chmod -R 775 /u01/app/oracle
When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the Oracle base directory that you have created.
Oracle Database files include data files, control files, redo log files, the server parameter file, and the password file. For all installations, you must choose the storage option that you want to use for Oracle Database files. If you want to enable automated backups during the installation, then you must also choose the storage option that you want to use for recovery files (the fast recovery area). You do not have to use the same storage option for each file type.
Note:
Database files and recovery files are supported on file systems and Automatic Storage Management.Use the following guidelines when choosing the storage options that you want to use for each file type:
You can choose any combination of the supported storage options for each file type.
Determine whether you want to use Automatic Storage Management for Oracle Database files, recovery files, or both. Refer to "Step 1: Identifying Storage Requirements for Automatic Storage Management" for more information.
For more information about these storage options, refer to the "Database Storage Options" section.
For information about how to configure disk storage before you start the installation, refer to one of the following sections depending on your choice:
To use a file system for database or recovery file storage, refer to the "Creating Directories for Oracle Database or Recovery Files" section.
To use Automatic Storage Management for database or recovery file storage, refer to the "Preparing Disks for an Automatic Storage Management Installation" section.
To identify disk groups and determine the free disk space that they contain, refer to the "Using an Automatic Storage Management Disk Group" section.
This section contains the following topics:
If you choose to place the Oracle Database files on a file system, then use the following guidelines when deciding where to place them:
The default path suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory.
You can choose either a single file system or more than one file system to store the database files:
If you want to use a single file system, then choose a file system on a physical device that is dedicated to the database.
For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.
If you want to use more than one file system, then choose file systems on separate physical devices that are dedicated to the database.
This method enables you to distribute physical input-output operations and create separate control files on different devices for increased reliability. It also enables you to fully implement the OFA guidelines. You can choose the Advanced database creation option to implement this method.
If you intend to create a preconfigured database during the installation, then the file system (or file systems) that you choose must have at least 2 GB of free disk space.
For production databases, you must estimate the disk space requirement depending on the use that you want to make of the database.
For optimum performance, the file systems that you choose should be on physical devices that are used only by the database.
The oracle user must have write permissions to create the files in the path that you specify.
Note:
You must perform this procedure only if you want to place the Oracle Database or recovery files on a separate file system to the Oracle base directory.To create directories for the Oracle database, or recovery files on separate file systems to the Oracle base directory:
Use the following to determine the free disk space on each mounted file system:
# bdf
From the display, identify the file systems that you want to use:
| File Type | File System Requirements |
|---|---|
| Database files | Choose either:
|
| Recovery files | Choose a file system with at least 2.4 GB of free disk space |
If you are using the same file system for more than one type of file, then add the disk space requirements for each type to determine the total disk space requirement.
Note the names of the mount point directories for the file systems that you identified.
Enter commands similar to the following to create the recommended subdirectories in each of the mount point directories and set the appropriate owner, group, and permissions on them:
Database file directory:
# mkdir /mount_point/oradata # chown oracle:oinstall /mount_point/oradata # chmod 775 /mount_point/oradata
The default location for Database file directory is $ORACLE_BASE/oradata.
Recovery file directory (fast recovery area):
# mkdir /mount_point/recovery_area # chown oracle:oinstall /mount_point/recovery_area # chmod 775 /mount_point/recovery_area
The default fast recovery area is $ORACLE_BASE/recovery_area. However, Oracle recommends that you keep the fast recovery area on a separate physical disk than that of the database file directory. This will enable you use the fast recovery area to retrieve data if the disk containing oradata is unusable due to any reasons.
If you also want to use Automatic Storage Management for storage, then refer to the following section:
"Preparing Disks for an Automatic Storage Management Installation", else refer to the "Stopping Existing Oracle Processes" section.
Note:
If you are installing additional Oracle Database 11g products in an existing Oracle home, then stop all processes running in the Oracle home. You must complete this task to enable Oracle Universal Installer to relink certain executables and libraries.Consider the following before you install Oracle grid infrastructure or Oracle Database:
If you plan to use Oracle Restart, you must install the grid infrastructure before you install the database. As such, when you perform a database installation, then the database must use the same listener created during the grid infrastructure installation and you do not have to perform the steps listed in this section.
The default listener and any additional listeners must run from the grid infrastructure home. Refer to "Configuring the oracle User's Environment" to continue.
If you have an existing Oracle Database 11g Release 2 (11.2) running on Oracle Automatic Storage Management, then stop any existing Oracle ASM instance. After you finish installing the grid infrastructure software, start the Oracle ASM instance again.
If you choose to create a database during the installation, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. However, if an existing Oracle Net listener process is using the same port or key value, Oracle Universal Installer will look for the next available free port (for example, 1522) and will configure and start the new listener on this available free port.
To determine whether an existing listener process is running and to shut it down, if necessary:
Switch user to oracle:
# su - oracle
Enter the following command to determine whether a listener process is running and to identify its name and the Oracle home directory in which it is installed:
$ ps -ef | grep tnslsnr
This command displays information about the Oracle Net listeners running on the system:
... oracle_home1/bin/tnslsnr LISTENER -inherit
In this example, oracle_home1 is the Oracle home directory where the listener is installed and LISTENER is the listener name.
Note:
If no Oracle Net listeners are running, then refer to the "Configuring the oracle User's Environment" section to continue.On the command prompt, set the ORACLE_HOME environment variable to specify the appropriate Oracle home directory for the listener:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=oracle_home1
$ export ORACLE_HOME
C or tcsh shell:
% setenv ORACLE_HOME oracle_home1
Enter the following command to identify the TCP/IP port number and IPC key value that the listener is using:
$ $ORACLE_HOME/bin/lsnrctl status listenername
Note:
If the listener uses the default nameLISTENER, then you do not have to specify the listener name in this command.Enter a command similar to the following to stop the listener process:
$ $ORACLE_HOME/bin/lsnrctl stop listenername
Repeat this procedure to stop all listeners running on this system.
You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer you must configure the environment of the oracle user. To configure the environment, you must:
Caution:
The Bash shell is not supported on HP-UX Itanium. Use shell programs supported by your operating system vendor. If you use a shell program that is not supported by your operating system, then you can encounter errors during installation.To set the oracle user's environment:
Start a new terminal session, for example, an X terminal (xterm).
Enter the following command to ensure that X Window applications can display on this system:
$ xhost fully_qualified_remote_host_name
For example:
$ xhost somehost.us.example.com
If you are not already logged in to the system where you want to install the software, then log in to that system as the oracle user.
If you are not logged in as the oracle user, then switch user to oracle:
$ su - oracle
To determine the default shell for the oracle user, enter the following command:
$ echo $SHELL
To run the shell startup script, enter one of the following commands:
Bash shell:
$ . ./.bash_profile
Bourne or Korn shell:
$ . ./.profile
C shell:
% source ./.login
If you are not installing the software on the local computer, then run the following command on the remote machine to set the DISPLAY variable:
Bourne, Bash or Korn shell:
$ export DISPLAY=local_host:0.0
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the local computer that you want to use to display Oracle Universal Installer.
Run the following command on the remote machine to check if the shell and the DISPLAY environmental variable are set correctly:
echo $SHELL echo $DISPLAY
Now to enable X applications, run the following commands on the local computer:
$ xhost + fully_qualified_remote_host_name
To verify that X applications display is set properly, run a X11 based program that comes with the operating system such as xclock:
$ xclock
In this example, you can find xclock at /usr/X11R6/bin/xclocks. If the DISPLAY variable is set properly, then you can see xclock on your computer screen.
See Also:
PC-X Server or operating system vendor documents for further assistanceIf you determined that the /tmp directory has less than 1 GB of free disk space, then identify a file system with at least 1 GB of free space and set the TMP and TMPDIR environment variables to specify a temporary directory on this file system:
To determine the free disk space on each mounted file system use the following command:
# df -h /tmp
If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:
$ sudo mkdir /mount_point/tmp $ sudo chmod a+wr /mount_point/tmp # exit
Enter commands similar to the following to set the TMP and TMPDIR environment variables:
Bourne, Bash, or Korn shell:
$ TMP=/mount_point/tmp $ TMPDIR=/mount_point/tmp $ export TMP TMPDIR
C shell:
% setenv TMP /mount_point/tmp % setenv TMPDIR /mount_point/tmp
Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_BASE=/u01/app/oracle $ ORACLE_SID=sales $ export ORACLE_BASE ORACLE_SID
C shell:
% setenv ORACLE_BASE /u01/app/oracle % setenv ORACLE_SID sales
In this example, /u01/app/oracle is the Oracle base directory that you created or identified earlier and sales is the name that you want to call the database (typically no more than five characters).
Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell:
$ unset ORACLE_HOME $ unset TNS_ADMIN
C shell:
% unsetenv ORACLE_HOME % unsetenv TNS_ADMIN
Note:
If theORACLE_HOME environment variable is set, then Oracle Universal Installer uses the value that it specifies as the default path for the Oracle home directory. However, if you set the ORACLE_BASE environment variable, then Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by Oracle Universal Installer.See Also:
"Configuring the User's Environment" for information about setting the grid infrastructure software owner user's environment
|
 Copyright © 1996, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|