Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for hp-ux PA-RISC (64-bit), Linux x86, and Solaris Operating Environment (SPARC 32-bit) Part Number B10874-04 |
|
|
View PDF |
This chapter describes how to plan each Oracle Collaboration Suite installation.This chapter describes how to plan each Oracle Collaboration Suite installation.
This chapter contains these topics:
Additional Hardware Requirements for Oracle Web Conferencing
Additional Software Requirements for Oracle Web Conferencing
This section contains these topics:
Table 2-1 describes the minimum hardware requirements for each installation of Oracle Collaboration Suite.
Table 2-1 Oracle Collaboration Suite Hardware Requirements Foot 1
Requirement | Value |
---|---|
Solaris Operating Environment (SPARC 32-bit) CPUFoot 2 | SPARC Processor |
hp-ux PA-RISC (64-bit) CPU2 | HP 9000 Series hp-ux processor for hp-ux 11.0 (64-bit)
HP 9000 Series hp-ux processor for hp-ux 11.11 (64-bit) |
Linux x86 CPU2 | Pentium II 233 MHz or better (32-bit) |
Monitor | 256 color viewing capability |
/var/tmp Directory Space |
Oracle Collaboration Suite: 33 MB
Oracle9iAS Infrastructure: 7 MB Oracle Collaboration Suite Information Storage: 34 MB |
Swap Space | 2 GB |
Memory
(minimum requirement) |
Oracle Collaboration Suite: 512 MB
Oracle9iAS Infrastructure: 512 MB Oracle Collaboration Suite information storage: 512 MB Note: Allocate additional memory depending on the applications and the number of users on the systems. Additional memory for Oracle Collaboration Suite information storage installations on hp-ux PA-RISC (64-bit) is required. If you are installing Oracle Real Application Clusters on a cluster with Hyper Messaging Protocol (HMP), each Oracle shadow process using HMP requires an additional 0.3 MB of memory. |
Disk Space for Solaris Operating Environment (SPARC 32-bit) | Oracle Collaboration Suite: 1.84 GB
Oracle9iAS Infrastructure: 3.96 GB Oracle Collaboration Suite Information Storage: 4.25 GB Note: While the Install Actions log file lists required disk space for the information storage database at 2.38 GB, the file does not consider the space necessary to create the database, nor does it consider the space necessary for middle tier applications deployed against the database. |
Disk Space for hp-ux PA-RISC (64-bit) | Oracle Collaboration Suite: 4.8 GB
Oracle9iAS Infrastructure: 5.9 GB Oracle Collaboration Suite Information Storage: 4.3 GB |
Disk Space for Linux x86 | Oracle Collaboration Suite: 2.5 GB
Oracle9iAS Infrastructure: 4.2 GB Oracle Collaboration Suite Information Storage: 3.8 GB |
Note: Regardless of the operating system, disk space must be available on a single disk. Oracle Collaboration Suite does not support spanning the installation over multiple disks. |
Note: If you are performing an upgrade, the Oracle Collaboration Suite upgrade assistant creates four new tablespaces for Oracle Email. See Oracle Email Pre-Upgrade Tasks for information about space requirements for these additional tablespaces. |
Use the following command to determine the amount of random access memory installed on Solaris Operating Environment (SPARC 32-bit):
prompt> /usr/sbin/prtconf | grep "Memory size"
Use the following command to determine the amount of random access memory installed on hp-ux PA-RISC (64-bit):
prompt> grep MemTotal /proc/meminfo
Use the following command to determine the amount of random access memory installed on Linux x86:
prompt> /usr/sbin/dmesg | grep "Physical"
Table 2-2 lists the commands to determine the amount of swap space currently configured in your system. Enter one of the commands listed in Table 2-2, according to your platform.
Table 2-2 Determining Swap Space
Platform | Command |
---|---|
Solaris Operating Environment (SPARC 32-bit) | prompt> /usr/sbin/swap -1 |
hp-ux PA-RISC (64-bit) | prompt> /usr/sbin/swapinfo -a |
Linux x86 | prompt> /sbin/swapon -s |
From the output of the command that you enter, divide the value shown in the BLOCKS column by 2.
There are several hardware sizing considerations for Oracle Web Conferencing. The Oracle Web Conferencing Sizing Guide has complete information about these considerations. This section provides information about required hardware for the Voice Conversion Server used by Oracle Web Conferencing to support streaming voice data during conferences or playback of recorded conferences with voice data.
The Voice Conversion server must be installed on a computer with Microsoft Windows 2000 Server SP4 or above, with the following basic configuration:
2.4 GHz Intel Processor
512 MB SDRAM
20 GB disk
In addition, you need specialized telephony hardware. You need a T1 or E1 trunk, and a media processing board from Intel / Dialogic to support the trunk. The T1/E1 protocol supported by Oracle Web Conferencing is robbed-bit /CAS (Channel Associated Signaling). The following tables list hardware and sizing recommendations depending on the the number of concurrent voice conferences, the type of and number of trunk lines, and the number of Voice Conversion Servers.
Table 2-3 Sizing Recommendations for Voice Conversion Using T1
Concurrent Voice Conferences | T1 Lines | Voice Servers | Dialogic Hardware Needed per Voice Server |
---|---|---|---|
12 | 1 | 1 | D/240JCT-T1 |
24 | 1 | 1 | D/480JCT-T1 |
48 | 2 | 1 | 2 x D/480JCT-T1 |
96 | 4 | 2 | 2 x D/480JCT-T1 |
192 | 8 | 4 | 2 x D/480JCT-T1 |
Table 2-4 Sizing Recommendations for Voice Conversion Using E1
Concurrent Voice Conferences | T1 Lines | Voice Servers | Dialogic Hardware Needed per Voice Server |
---|---|---|---|
15 | 1 | 1 | D/300JCT-E1 |
30 | 1 | 1 | D/300JCT-E1 |
60 | 2 | 1 | 2 x D/600JCT-E1 |
120 | 4 | 2 | 2 x D/600JCT-E1 |
240 | 8 | 4 | 2 x D/600JCT-E1 |
See Also: Oracle Web Conferencing Sizing Guide for specific information on sizing requirements for your system |
Table 2-5 lists the operating system version required by each platform, and the command to determine the current operating system version.
Table 2-5 Operating System Versions and Requirements
Platform | Operating System Requirements | Command |
---|---|---|
Solaris Operating Environment (SPARC 32-bit) |
|
prompt> uname -a |
hp-ux PA-RISC (64-bit) |
|
prompt> uname -a |
Linux x86 |
|
prompt> uname -a
|
Your operating system can require the installation of patches and packages. Several of the patches listed in the following tables have dependency patches that must also be installed. See the readme
files included with the patches and packages for additional information. When downloading a specific patch or package, verify dependencies and download the dependency patches or packages, if required.
Note: Your operating system must include thesendmail program. |
This section contains these topics:
Required hp-ux PA-RISC (64-bit) Patches for Oracle9iAS Infrastructure and Oracle Collaboration Suite
Required hp-ux PA-RISC (64-bit) Patches for Oracle Collaboration Suite Information Storage
Operating System Requirements to Support Real Application Clusters
Table 2-6 lists the locations from which to download the operating system patches for each platform.
Table 2-6 Operating System Patch Download Locations
Platform | Download Location |
---|---|
Solaris Operating Environment (SPARC 32-bit) | Download the patches at
http://sunsolve.sun.com/ |
hp-ux PA-RISC (64-bit) | Download patch bundles at
http://www.software.hp.com/SUPPORT_PLUS Download individual patches at http://itresourcecenter.hp.com |
Linux x86 | Contact Linux vendor for downloading patches |
Table 2-7 lists the commands to determine if a specific patch is installed for each platform.
Table 2-8 lists the operating system patches you must install for Oracle9iAS Infrastructure installation and Oracle Collaboration Suite installation on Solaris Operating Environment (SPARC 32-bit).
There are no required operating system patches you must install for Oracle Collaboration Suite information storage installation on Solaris Operating Environment (SPARC 32-bit).
Install the following operating system patches for Oracle9iAS Infrastructure and Oracle Collaboration Suite installations on hp-ux PA-RISC (64-bit).
Table 2-9 Patches and Packages for Oracle9iAS Infrastructure and Oracle Collaboration Suite
Operating System | Packages and Patches |
---|---|
hp-ux 11.0 PA-RISC (64-bit) |
|
hp-ux 11.11 PA-RISC (64-bit) |
|
Install the operating system patches listed in Table 2-9 for Oracle Collaboration Suite information storage installation on hp-ux PA-RISC (64-bit).
Table 2-10 lists the operating system packages and patches required to support Real Application Clusters.
Table 2-10 Patches and Packages for Real Application Clusters
Platform | Packages and Patches |
---|---|
Solaris Operating Environment (SPARC 32-bit) | racpatch |
hp-ux PA-RISC for 11.0 (64-bit) |
|
hp-ux PA-RISC for 11.11 (64-bit) |
|
Linux x86 | Not Applicable |
Note: For Sun Clusters, installracpatch as described in "Additional root User Information for Solaris Operating Environment (SPARC 32-bit)". |
Table 2-11 lists required or recommended JRE patches.
Table 2-11 JRE Patches
Platform | Patch | Required or Recommended |
---|---|---|
Solaris 8 | Not Applicable | Not Applicable |
hp-ux PA-RISC (64-bit) | PHCO_23792
PHCO_24148 PHKL_25475 PHNE_23456 PHNE_24034 PHSS_24303 |
Recommended
Recommended Recommended Recommended Recommended Recommended |
Linux x86 | Not Applicable | Not Applicable |
Table 2-12 lists the required operating system and font packages for Solaris Operating Environment (SPARC 32-bit).
Table 2-12 Required Operating System and Font Packages for Solaris Operating Environment (SPARC 32-bit)
Package Type | Required Packages |
---|---|
Operating system | SUNWarc , SUNWbtool , SUNWhea , SUNWlibm , SUNWlibms , SUNWsprot, and SUNWtoo |
Font packages for Java | SUNWi1of and SUNWxwfnt are required for all locations. You may need to obtain additional font packages to support font styles used at your location. A list of Solaris Operating Environment (SPARC 32-bit) font packages is available at: http://java.sun.com/j2se/1.3/font-requirements.html . |
To check whether an operating systems package is installed, enter:
prompt> pkginfo -p package_name
where package_name
is the name of the package that you want to check.
Table 2-13 lists additional software required for all platforms:
Table 2-13 Additional Required Operating System Requirements
Software | Requirement |
---|---|
X Server and Window Manager | Use any X Server and window manager supported by your UNIX operating system.
For Hummingbird Exceed, use a native window manager. For WRQ Reflections, allow a remote window manager. To determine if your X Window System is working properly on your local system, enter the following command:
The X clock should appear on your monitor. |
Required executables | The following executables must be present: make , ar , ld , and nm . |
Oracle Web Conferencing uses a Document Conversion Server to convert Microsoft Office documents into HTML or other compatible formats for sharing during conferences. The server must reside on a separate computer from the middle tier, and it must have Microsoft Windows NT and Microsoft Office 2000 or Microsoft Office XP.
Oracle Web Conferencing also uses a Voice Conversion Server to support streaming voice data during conferences or playback of recorded conferences with voice data. The server requires Microsoft Windows 2000 Server SP4 or above, and Intel Dialogic System Software 5.1.1 SP1 or above.
See Also: Oracle Web Conferencing Sizing Guide for more details about required hardware and software |
See Also: "Additional Hardware Requirements for Oracle Web Conferencing" for voice conversion server hardware requirements |
The Oracle Collaboration Suite user interface is available in the following languages: Arabic, Brazilian Portuguese, Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Portuguese, Simplified Chinese, Spanish, Swedish, Traditional Chinese, and Turkish.
Oracle Calendar server administration tools have an English interface but support entering data in all Oracle Collaboration Suite supported languages.
The Oracle Calendar clients are available only in English with the following exceptions:
Oracle Connector for Outlook: All Oracle Collaboration Suite supported languages, except Arabic
Oracle Calendar Web client: All Oracle Collaboration Suite supported languages, except Arabic
Oracle Calendar desktop client for Windows: English, French, German, and Japanese
Oracle Calendar Sync for Palm for Windows: English, French, German, and Japanese
Oracle Calendar Sync for Pocket PC for Windows: English, French, German, and Japanese
You can view Oracle Collaboration Suite documentation online using a Web browser or Portable Document Format (PDF) Viewer.
Table 2-14 lists the requirements for viewing Oracle Collaboration Suite online documentation.
Table 2-14 Online Documentation Requirements
See Also: Oracle Collaboration Suite Documentation Roadmap |
Following installation, Oracle Universal Installer creates a file named portlist.ini
showing the ports assigned during the installation of Oracle Collaboration Suite components. The installation process automatically detects any port conflicts and selects an alternate port in the range allocated for that component. The file is located at:
$ORACLE_HOME/install/portlist.ini
Many Oracle Collaboration Suite components require a Web browser. All Oracle Collaboration Suite installations require an Oracle9iAS Infrastructure and Oracle9i database. A complete list of certified software, including certified Oracle9iAS Infrastructure releases, database releases, and Web browsers for Oracle Collaboration Suite is located at OracleMetaLink:
http://metalink.oracle.com
Before installing Oracle Collaboration Suite, Oracle Corporation recommends that you read Oracle Collaboration Suite Release Notes, available in the doc
directory of each Oracle Collaboration Suite installation CD-ROM and on Oracle Technology Network. See Oracle Collaboration Suite Documentation Roadmap for more information about Oracle Collaboration Suite documentation. Although this document is accurate at the time of publication, you can access the latest information and documentation on Oracle Technology Network:
http://otn.oracle.com/
This section contains these topics:
Real Application Clusters for Oracle Collaboration Suite Information Storage Installation
Configuring Kernel Parameters for Oracle Collaboration Suite
Configuring Kernel Parameters for Oracle Collaboration Suite Information Storage
Table 2-15 explains how to set and unset environment variables.
Table 2-15 Setting and Unsetting Environment Variables
To... | C shell | Bourne/Korn shell |
---|---|---|
Set an environment variable |
prompt> setenv VARIABLE value |
prompt> VARIABLE=value;export VARIABLE |
Unset an environment variable |
prompt> unsetenv VARIABLE |
prompt> unset VARIABLE |
Note: You do not need to set the environment variablesLD_LIBRARY_PATH , ORACLE_HOME , SHLIB_PATH , TMP , TMPDIR , and TNS_ADMIN . |
Before starting Oracle Universal Installer, set the DISPLAY
environment variable to refer to the X Server that displays Oracle Universal Installer. The format of the DISPLAY
environment variable is:
hostname:display_number.screen_number
Oracle Collaboration Suite requires a running X Server to properly create graphics for Oracle Universal Installer, Web applications, and management tools. The frame buffer X Server installed with your operating system requires that you remain logged in and have the frame buffer running at all times. If you do not want to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).
Oracle Universal Installer configures this instance to use the same X Server from the installation process for applications and management tools. This X Server must either always be running or you must reconfigure Oracle Collaboration Suite to use another X Server that is always running after the installation completes.
See Also:
|
Installing From a Remote Computer
Setting the DISPLAY
environment variable enables you to run Oracle Universal Installer remotely from another workstation. On the system where you launch Oracle Universal Installer, set DISPLAY
to the system name or IP address of your local workstation.
Note: You can use a PC X emulator to run the install if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start Oracle Universal Installer. See the X emulator documentation for instructions on how to change the color model or visual settings. |
If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting Oracle Universal Installer, then run the commands on your local workstations as listed in Table 2-16.
Table 2-16 DISPLAY Environment Variable Commands
If you are installing on hp-ux, you must manually create symbolic links before performing the installation.
To create the required links:
Log into the system as the root user.
Change directory to /usr/lib.
Enter the following commands to create the symbolic links:
# 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
Oracle Universal Installer requires that the fully-qualified hostname information appear in the configuration files for your computer. A fully-qualified hostname includes both the name of the system and its domain.
Failure to properly configure the hostname information in the listed files may result in runtime errors during Oracle Collaboration Suite installation.
Verify that /etc/hosts
has the following format:
ip_address fully_qualified_hostname short_hostname aliases
The following example shows a properly configured /etc/hosts
file:
148.87.9.44 oasdocs.us.oracle.com oasdocs oracleinstall
Verify that the hostname
command returns this fully-qualified hostname before starting the install.
Solaris Operating Environment (SPARC 32-bit) installations require that the following additional files be configured with the fully-qualified hostname:
/etc/nodename
/etc/inet/hosts
/etc/hostname*
/etc/net/ticlts/hosts
/etc/net/ticots/hosts
/etc/net/ticotsord/hosts
/etc/inet/ipnodes
Note: The hostname can appear in each of these files more than once. You must add the domain information to every occurrence of the hostname. The only exceptions are/etc/hosts and /etc/inet/hosts files, where the domain information only needs to be added once, immediately after the Internet Protocol (IP) address. |
The installation process requires a special UNIX account and several special groups. See the following subsections for more information:
UNIX Group Name for the Oracle Universal Installer Inventory
UNIX Group Names for Privileged Groups
Note: You must use the same operating system user account when adding additional Oracle Collaboration Suite installations on the same host. |
Use the admintool
or groupadd
utility to create a group name such as oinstall
. The oinstall
group owns the Oracle Universal Installer oraInventory
directory. The oracle
user account that runs the installation must have the oinstall
group as its primary group.
Note: The UNIX group name must not exceed 8 characters, otherwise the Oracle Calendar configuration assistant will fail. |
For more information about these utilities, see your operating system documentation.
The oracle
account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.
Create an oracle
account with the properties listed in Table 2-17.
Table 2-17 Oracle Account Properties
Variable | Property |
---|---|
Login Name | Select any name to access the account. This document refers to the name as the oracle account. |
Group Identifier | The oinstall group is used in this document. |
Home Directory | Select a home directory consistent with other user home directories. |
Login Shell | The default shell can be either the C, Bourne, or Korn shell. |
Note: Use theoracle account only for installing and maintaining Oracle software. Never use it for purposes unrelated to Oracle Universal Installer. Do not use root as the oracle account. |
Two privileged groups are required for Oracle9iAS Infrastructure installation and Oracle Collaboration Suite information storage installation:
These privileged groups are not required for Oracle Collaboration Suite installation.
Oracle documentation refers to these groups as OSOPER
and OSDBA
, respectively. Databases use these groups for operating system authentication. This is necessary in situations where the database is shut down and database authentication is unavailable.
The privileges of these groups are given to either a single UNIX group or two corresponding UNIX groups. There are two ways to choose which groups get the privileges:
If the oracle
account is a member of the dba
group before starting Oracle Universal Installer, then dba
is given the privileges of both OSOPER
and OSDBA
.
If the oracle
account is not a member of the dba
group, then Oracle Universal Installer prompts you for the group names that get these privileges.
Table 2-18 lists the privileges for the OSOPER
and OSDBA
groups.
Table 2-18 Privileges for the OSOPER and OSDBA Groups
Group | Privileges |
---|---|
OSOPER |
Permits the user to perform STARTUP , SHUTDOWN , ALTER DATABASE OPEN/MOUNT , ALTER DATABASE BACKUP , ARCHIVE LOG , and RECOVER , and includes the RESTRICTED SESSION privilege. |
OSDBA |
Contains all system privileges with ADMIN OPTION , and the OSOPER role; permits CREATE DATABASE and time-based recover. |
Perform the following preinstallation steps to install Real Application Clusters.
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information about preinstallation steps for Real Application Clusters. This manual is available on Oracle Technology Network athttp://otn.oracle.com/ |
Log in as the root
user.
Ensure that you have the OSDBA
group defined in the /etc/group
file on all nodes in the cluster. The OSDBA
group name and number, and OSOPER
group if you plan to designate one, must be identical for all nodes of a UNIX cluster accessing a single database. The default UNIX group name for the OSDBA
group is dba
.
Create the oracle
account on each node of the cluster so that the account:
Has the ORAINVENTORY
group as the primary group
Has the dba
group as the secondary group
Is used only to install and update Oracle software
Has write permissions on remote directories
Create a mount point directory on each node to serve as the top of the Oracle software directory structure so that:
The name of the mount point on each node is identical to that on the initial node
The oracle
account has read, write, and execute privileges
Set up user equivalence by adding entries for all nodes in the cluster on the node from which to run Oracle Universal Installer, including the local node, to either the .rhosts
file of the oracle
account or the /etc/hosts.equiv
file.
Check user equivalence by executing a remote command on every node as the oracle
user. For example, enter:
Solaris Operating Environment (SPARC 32-bit) and Linux x86:
prompt> rsh another_host pwd
hp-ux PA-RISC (64-bit):
prompt> remsh another_host pwd
Check RCP equivalence by copying a small file from every node to every node. For example, enter:
prompt> rcp /tmp/dummy_file another_host:/tmp/dummy_file
This is required for Oracle Universal Installer to install Oracle software on all selected nodes of the cluster.
If you are installing Oracle Real Application Clusters on Solaris Operating Environment (SPARC 32-bit), hp-ux PA-RISC (64-bit), or Linux x86 then you must complete additional steps as the root
user. See the appropriate sections for your platform:
Additional root User Information for Solaris Operating Environment (SPARC 32-bit)
Apply the Oracle patch for Sun Cluster software that is provided on Disk 1 of the Oracle Collaboration Suite Information Storage CD-ROM set. To install the patch, follow the instructions provided in the README.udlm
file in the racpatch
directory on the CD-ROM. This patch provides the Cluster Membership Monitor (CMM) that is required before you install Oracle Real Application Clusters.
Start CMM by restarting the Cluster Management Software.
For the first node, enter the following commands:
prompt> cd /opt/SUNWcluster/bin prompt> scadmin startcluster cluster_name
Run the following commands on each of the other nodes in the cluster:
prompt> cd /opt/SUNWcluster/bin prompt> scadmin startnode cluster_name
See Also: Sun Cluster 3.0 documentation for more information about thescadmin command |
Additional root User Information for hp-ux PA-RISC (64-bit)
Start MC/ServiceGuard by entering the following command:
prompt> /usr/sbin/cmruncl
See Also:
|
Additional root User Information for Linux x86
Set the CONFIG_WATCHDOG_NOWAYOUT
parameter to Y
. In most kernels, Y
is a default value. For more information, see the generic Linux x86 documentation.
Load the watchdog
module with an appropriate margin.
insmod softdog soft_margin=10
See Also: A97297-01, Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for UNIX Systems: AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, Linux Intel, and Sun Solaris, available on Oracle Technology Network on how to calculate thesoft_margin value |
Add the necessary information to the /etc/hosts
file on each node. The following information should be presented (entry for public IP address of the local node and entry for private IP address for each node, including local):
public_IP_address local_hotname_with_domain local_hostname_alias private_IP_address cluster_node_private_hostname private_IP_address cluster_node1_private_hostname private_IP_address cluster_node2_private_hostname ......
Create the raw partition with 4 MB on the shared storage. This partition is to be used by the Oracle Cluster Manager as a quorum partition. Bind this partition on each server on the cluster to the same device, for example, to /dev/raw1
.
Log in as the oracle
account.
If you are performing the preinstallation steps on hp-ux PA-RISC (64-bit), then verify that MC/ServiceGuard is running by entering the following command:
prompt> /usr/sbin/cmviewcl
Verify that the Cluster Membership Monitor is running. Table 2-19 lists the appropriate command for each platform.
Table 2-19 Command to Verify Cluster Membership Monitor is Running
Platform | Command |
---|---|
Solaris Operating Environment (SPARC 32-bit) |
prompt> ps -ef | grep clustd
|
hp-ux PA-RISC (64-bit) | prompt> /usr/sbin/cmviewcl |
Linux x86 |
prompt> ps -efl | egrep 'watchdogd | oracm'
|
Check for user equivalence of the oracle
account by performing a remote login (rlogin
) to each node in the cluster.
If you are prompted for a password, the oracle
account does not have user equivalence. Ensure that you gave the same attributes to the oracle
user on all the nodes in the cluster. Oracle Universal Installer cannot use the rcp
command to copy Oracle products to the remote directories without user equivalence.
If you have not set up user equivalence, you must perform Step 6 in "Steps to Perform as the root User for Real Application Clusters Installation".
Create at least one shared configuration file as an information repository for the database server configuration. If your platform supports the Cluster File System, skip this step.
Create a shared raw device of at least 100 MB for the Server Management (SRVM) configuration. Oracle Universal Installer prompts you for the name of this shared file on the Shared Configuration File Name Page. Alternatively, set the environment variable SRVM_SHARED_CONFIG
to the absolute path name of the shared raw device from which Oracle Universal Installer can retrieve the configuration file.
See Also: Oracle9i Real Application Clusters Setup and Configuration for more information about setting up a shared configuration file |
Before you install Real Application Clusters, you must install Oracle Cluster Manager. Install Real Application Clusters in the same $ORACLE_HOME
where Oracle Cluster Manager is installed.
See Also: Oracle9i Release 2 Database Server Patch Set 2 with Cluster Manager Patch for Linux-32 Patch Set Notes Patch Set version 9.2.0.3.0 for detailed installation and configuration steps for Oracle Cluster Manager on Linux x86 |
Perform the following steps to install Oracle Cluster Manager:
Navigate to the cluster_manager
subdirectory in Disk1 of the Oracle Collaboration Suite Information Storage CD.
Start the Oracle Universal Installer.
Enter the Oracle home directory in the destination where you want to install the Oracle Real Application Clusters option.
Select the product Oracle Cluster Manager from the Available Products screen.
Enter the list of Private node names in the Private Node Names Information screen.
Enter the list of Public node names in the Public Node Names Information screen.
Oracle Cluster Manager is now installed on the nodes. At the end of installation, a screen appears asking whether to run the cmstart.sh
script as the root
user on all the nodes of the cluster selected in the installation. After this script is run, the Oracle Cluster Manager is started on all the nodes.
After the installation of Oracle Cluster Manager, restart Oracle Universal Installer and proceed to install other Oracle components as required.
See Also: Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for more information about how to start and configure Oracle Cluster Manager |
The Oracle9iAS Metadata Repository installation requires you to configure your system kernel parameters. Compliance with this requirement is especially important for production environments. Review your kernel parameter settings to ensure that they meet Oracle9iAS Metadata Repository and Oracle Internet Directory requirements. You may experience errors during installation or operational errors after installation if this is not completed.
If you change the kernel settings, you must restart your system in order for kernel changes to take effect.
See appropriate tables for the kernel parameters for your platform:
For Solaris Operating Environment (SPARC 32-bit), use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification number and owner.
Use a text editor such as vi
to change the kernel parameter settings in the /etc/system
file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels Oracle9i requires, then do not change the settings. If the levels are too low, change them to levels at least as high as those in the table. If you change the settings, save the /etc/system
file and restart the system.
Example 2-1 Example Settings in /etc/system for Solaris Operating Environment (SPARC 32-bit)
set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=256 set semsys:seminfo_semmsl=256 set semsys:seminfo_semmnu=4096 set rlim_fd_max=1024 set rlim_fd_cur=1024
Table 2-20 shows the kernel parameters and their required minimum settings.
Table 2-20 Kernel Parameter Settings for Solaris Operating Environment (SPARC 32-bit)
Kernel | Setting | Definition |
---|---|---|
rlim_fd_cur |
1024 |
Number of open files for each process |
rlim_fd_max |
4117 |
Maximum number of open files for each process |
semmni |
554 |
Maximum number of semaphore sets in the entire system |
semmns |
1024 |
Maximum semaphores on the system. This setting is a minimum recommended value for an initial installation only.
The |
semmsl |
256 |
Minimum recommended value for an initial installation only. The semmsl parameter should be set to 10 plus the largest init sid .ora PROCESSES parameter of any Oracle database on the system. |
semopm |
12 |
Maximum number of System V semaphore operations per semop call. This parameter refers to the number of sembufs in the sops array that is provided to the semop system call. |
semume | 42 | Maximum number of System V semaphore undo structures that can be used by any one process. |
semvmx | 32767 | Maximum value of a semaphore. |
semaem | 16384 | Maximum value to which a semaphore's value in an undo structure can be set. |
shmmax |
4294967295 |
Maximum allowable size of one shared memory segment. (4294967295 is equal to 4 GB.) |
shmmin |
1 |
Minimum allowable size of a single shared memory segment |
shmmni |
117 |
Maximum number of shared memory segments in the entire system |
shmseg |
17 |
Maximum number of shared memory segments one process can attach |
msgmni | 3774 | Maximum number of message queue identifiers |
msgmax | 4096 | Maximum message size |
msgmnb | 360000 | Maximum number of bytes in a message queue |
msgtql | 2500 | Maxuimum number of message headers |
For hp-ux PA-RISC (64-bit), you can use the System Administrator's Menu (SAM) to configure the hp-ux PA-RISC (64-bit) kernel as required by your application. The parameters in Table 2-21 are those recommended for a general user running a typical Oracle Collaboration Suite instance on hp-ux PA-RISC (64-bit). You might need to change the values depending on your application needs and the type of system on which you are working. See Table 2-21 to determine if your system's shared memory and semaphore kernel parameters are set correctly for Oracle Collaboration Suite. Use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner.
The parameters in Table 2-21 are the recommended values for running Oracle Collaboration Suite on hp-ux PA-RISC (64-bit):
Table 2-21 shows the kernel parameters and their required minimum settings.
Table 2-21 Kernel Parameter Settings for hp-ux PA-RISC (64-bit)
Kernel | Parameter Setting | Definition |
---|---|---|
ksi_alloc_max |
(nproc * 8) |
The system wide limit of a queued signal that can be allocated. |
max_thread_proc |
256 |
The maximum number of kernel threads allowed for each process. You may need to increase the value if required by your application. Setting it to a default or low value may lead to an out-of-memory error for certain applications. |
maxdsiz |
1073741824 bytes |
Refers to the maximum data segment size in bytes 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 in bytes for 64-bit systems. Setting this value too low may cause the processes to run out of memory. |
maxssiz |
134217728 bytes |
The maximum stack segment size in bytes for 32-bit systems. |
maxssiz_64BIT |
1073741824 |
The maximum stack segment size in bytes for 64-bit systems. |
maxswapchunks |
16384 |
The maximum number of swap chunks where swchunk is the swap chunk size (1 KB blocks). swchunk is 2048 by default. It specifies the maximum amount of configurable swap space on the system. |
maxuprc |
3686 |
The maximum number of user processes. |
msgmap |
6598 |
The maximum number of message map entries. |
msgmni |
6846 |
The number of message queue identifiers. |
msgseg |
32767 |
The number of segments available for messages. |
msgtql |
6596 |
The number of message headers. |
ncallout |
(nproc + 16) |
The maximum number of pending timeouts. |
ncsize |
((8 * nproc + 2048) + vx_ncsize) |
The Directory Name Lookup Cache (DNLC) space needed for inodes. vx_ncsize is 1024 by default. |
nfile |
1634888 |
The maximum number of open files. |
nflocks |
4096 |
The maximum number of file locks available on the system. |
ninode |
(8 * nproc + 2048) |
The maximum number of open inodes. |
nkthread |
10034 |
The maximum number of kernel threads supported by the system. |
nproc |
4195 |
The maximum number of processes. |
semmap |
4098 |
The maximum number of semaphore map entries. |
semmni |
4138 |
The maximum number of semaphore sets in the entire system. |
semmns |
8360 |
The maximum number of semaphores in the system. The default value of semmns is 128 , which is, in most cases, too low for Oracle Collaboration Suite software. |
semmnu |
4092 |
The number of semaphore undo structures. |
semvmx |
32768 |
The maximum value of a semaphore. |
shmmax |
4294967295 |
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 |
530 |
The maximum number of shared memory segments in the entire system. |
shmseg |
32 |
The maximum number of shared memory segments one process can attach. |
vps_ceiling |
64 |
The maximum system-selected page size in kilobytes. |
maxfiles |
2048 |
Soft file limit per process |
maxfiles_lim |
3861 |
Hard file limit per process |
msgmax |
32767 |
Maximum message size |
msgmnb |
65535 |
Maximum number of bytes on the message queue |
msgssz |
159 |
Message segment size |
semume |
42 |
Semaphore undo entries per process |
For Linux x86, use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner. You can modify the kernel parameters by using the /proc
file system. Perform the following steps to modify the kernel parameters by using the /proc
file system.
Log in as the root
user.
Change to the /proc/sys/kernel
directory.
Review the current semaphore parameter values in the sem
file by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat sem
The output lists the values for the semmsl
, semmns
, semopm
, and semmni
parameters, respectively as shown in the following example:
250 32000 32 128
Modify the parameter values by using the following command syntax:
prompt> echo semmsl_value semmns_value semopm_value semmni_value > sem
Replace the parameter variables with the values for your system in the order that they are entered in the preceding example, as follows:
prompt> echo 250 32000 100 142 > sem
Review the current shared memory parameters by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat shared_memory_parameter
In the preceding example, the variable shared_memory_parameter
is either the shmmax
or shmmni
parameter. The parameter name must be entered in lowercase letters.
Modify the shared memory parameter by using the echo
utility, as in the following examples:
To modify the shmmax
parameter:
prompt> echo 4294967295 > shmmax
To modify the shmmni
parameter:
prompt> echo 4096 > shmmni
To modify the shmall
parameter:
prompt> echo 3279547 > shmall
Write a script to initialize these values during system startup, and include the script in your system initialization files.
See Also: Your system vendor's documentation for more information about script files and initialization files |
Set the File Handles by using the following command:
prompt> echo 65536 > /proc/sys/fs/file-max prompt> ulimit -n 65536
Set the Sockets to /proc/sys/net/ipv4/ip_local_port_range
:
prompt> echo 10000 65000 > /proc/sys/net/ipv4/ip_local_port_range
Set the Process by using ulimit
-u
. This gives you the number of processes for each user. For example:
ulimit -u 16384
Table 2-22 lists the minimum values required to run Oracle Collaboration Suite on Linux x86.
Table 2-22 Kernel Parameter Settings for Linux x86
Kernel | Parameter Setting | Definition |
---|---|---|
semmni |
142 |
The maximum number of semaphore sets in the entire system. |
semmns |
32000 |
The maximum number of semaphores on the system. This setting is a minimum recommended value for an initial installation only. The semmns parameter should be set to the sum of the init sid .ora PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database. |
semopm |
100 |
The maximum number of operations for each semop call. |
semmsl |
250 |
The minimum recommended number of semaphores for each id for an initial installation only. The semmsl parameter should be set to 10 plus the largest init sid .ora PROCESSES parameter of any Oracle database on the system. |
shmmax |
4294967295 |
The maximum allowable size of one shared memory segment. It is 2 GB for SMP kernel. The recommended size is half the RAM size. |
shmmni |
4096 |
The maximum number of shared memory segments in the entire system. |
shmall |
3279547 |
Total amount of shared memory available |
msgmni |
2878 |
Number of message queue identifiers |
msgmax |
8192 |
Maximum message size |
msgmnb' |
65535 |
Maximum number of bytes on the message queue |
file-max |
327679 |
Maximum number of files |
The Oracle Collaboration Suite installation requires you to configure your system kernel parameters. Compliance with this requirement is especially important for production environments. Review your kernel parameter settings to ensure that they meet Oracle Collaboration Suite requirements. You may experience errors during installation or operational errors after installation if this is not completed.
If you change the kernel parameter settings, you must restart your system in order for kernel changes to take effect.
See appropriate tables for the kernel parameters for your platform:
For Solaris Operating Environment (SPARC 32-bit), use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification number and owner.
Use a text editor such as vi
to change the kernel parameter settings in the /etc/system
file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels Oracle9i requires, then do not change the settings. If the levels are too low, change them to levels at least as high as those in the table. If you change the settings, save the /etc/system
file and restart the system.
Example 2-2 Example Settings in /etc/system for Solaris Operating Environment (SPARC 32-bit)
set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=256 set semsys:seminfo_semmsl=256 set semsys:seminfo_semmnu=4096 set rlim_fd_max=1024 set rlim_fd_cur=1024
Table 2-23 shows the kernel parameters and their minimum recommended settings.
Table 2-23 Kernel Parameter Settings for Solaris Operating Environment (SPARC 32-bit)
Kernel | Setting | Definition |
---|---|---|
rlim_fd_cur |
1024 |
The number of open files for each process. |
rlim_fd_max |
4117 |
The maximum number of open files for each process. |
semmni |
554 |
The maximum number of semaphore sets in the entire system. |
semmns |
1024 |
The maximum semaphores on the system. This setting is a minimum recommended value for an initial installation only.
The |
semmsl |
256 |
The minimum recommended value for an initial installation only. The semmsl parameter should be set to 10 plus the largest init sid .ora PROCESSES parameter of any Oracle database on the system. |
shmmax |
4294967295 |
The maximum allowable size of one shared memory segment. 4 GB = 4294967295. |
shmmin |
1 |
The minimum allowable size of a single shared memory segment. |
shmmni |
117 |
The maximum number of shared memory segments in the entire system. |
shmseg |
17 |
The maximum number of shared memory segments one process can attach. |
msgmni |
3774 |
The maximum number of message queue identifiers. |
msgmax |
4096 |
The maximum message size. |
msgmnb |
360000 |
The maximum number of bytes in a message queue. |
msgtql |
2500 |
The maximum number of message headers. |
For hp-ux PA-RISC (64-bit), you can use the System Administrator's Menu (SAM) to configure the hp-ux PA-RISC (64-bit) kernel as required by your application. The parameters in Table 2-24 are those recommended for a general user running a typical Oracle Collaboration Suite instance on hp-ux PA-RISC (64-bit). You might need to change the values depending on your application needs and the type of system on which you are working. See Table 2-24 to determine if your system's shared memory and semaphore kernel parameters are set correctly for Oracle Collaboration Suite. Use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner.
The parameters in Table 2-24 are the recommended minimum values for running Oracle Collaboration Suite on hp-ux PA-RISC (64-bit):
Table 2-24 Kernel Parameter Settings for hp-ux PA-RISC (64-bit)
Kernel | Parameter Setting | Definition |
---|---|---|
ksi_alloc_max |
(nproc * 8) |
The system wide limit of a queued signal that can be allocated. |
max_thread_proc |
256 |
The maximum number of kernel threads allowed for each process. You may need to increase the value if required by your application. Setting it to a default or low value may lead to an out-of-memory error for certain applications. |
maxdsiz |
1073741824 bytes |
Refers to the maximum data segment size in bytes 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 in bytes for 64-bit systems. Setting this value too low may cause the processes to run out of memory. |
maxssiz |
134217728 bytes |
The maximum stack segment size in bytes for 32-bit systems. |
maxssiz_64BIT |
1073741824 |
The maximum stack segment size in bytes for 64-bit systems. |
maxswapchunks |
16384 |
The maximum number of swap chunks where swchunk is the swap chunk size (1 KB blocks). swchunk is 2048 by default. It specifies the maximum amount of configurable swap space on the system. |
maxuprc |
3686 |
The maximum number of user processes. |
msgmap |
6598 |
The maximum number of message map entries. |
msgmni |
6846 |
The number of message queue identifiers. |
msgseg |
32767 |
The number of segments available for messages. |
msgtql |
6596 |
The number of message headers. |
ncallout |
(nproc + 16) |
The maximum number of pending timeouts. |
ncsize |
((8 * nproc + 2048) + vx_ncsize) |
The Directory Name Lookup Cache (DNLC) space needed for inodes. vx_ncsize is 1024 by default. |
nfile |
1634888 |
The maximum number of open files. |
nflocks |
4096 |
The maximum number of file locks available on the system. |
ninode |
(8 * nproc + 2048) |
The maximum number of open inodes. |
nkthread |
10034 |
The maximum number of kernel threads supported by the system. |
nproc |
4195 |
The maximum number of processes. |
semmap |
4098 |
The maximum number of semaphore map entries. |
semmni |
4138 |
The maximum number of semaphore sets in the entire system. |
semmns |
8360 |
The maximum number of semaphores in the system. The default value of semmns is 128 , which is, in most cases, too low for Oracle Collaboration Suite software. |
semmnu |
4092 |
The number of semaphore undo structures. |
semvmx |
32768 |
The maximum value of a semaphore. |
shmmax |
4294967295 |
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 |
530 |
The maximum number of shared memory segments in the entire system. |
shmseg |
32 |
The maximum number of shared memory segments one process can attach. |
vps_ceiling |
64 |
The maximum system-selected page size in kilobytes. |
maxfiles |
2048 |
Soft file limit per process |
maxfiles_lim |
3861 |
Hard file limit per process |
msgmax |
32767 |
Maximum message size |
msgmnb |
65535 |
Maximum number of bytes on the message queue |
msgssz |
159 |
Message segment size |
semume |
42 |
Semaphore undo entries per process |
For Linux x86, use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner. You can modify the kernel parameters by using the /proc
file system. Perform the following steps to modify the kernel parameters by using the /proc
file system.
Log in as the root
user.
Change to the /proc/sys/kernel
directory.
Review the current semaphore parameter values in the sem
file by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat sem
The output lists the values for the semmsl
, semmns
, semopm
, and semmni
parameters, respectively as shown in the following example:
250 32000 32 128
Modify the parameter values by using the following command syntax:
prompt> echo semmsl_value semmns_value semopm_value semmni_value > sem
Replace the parameter variables with the values for your system in the order that they are entered in the preceding example, as follows:
prompt> echo 250 32000 100 142 > sem
Review the current shared memory parameters by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat shared_memory_parameter
In the preceding example, the variable shared_memory_parameter
is either the shmmax
or shmmni
parameter. The parameter name must be entered in lowercase letters.
Modify the shared memory parameter by using the echo
utility, as in the following examples:
To modify the shmmax
parameter:
prompt> echo 4294967295 > shmmax
To modify the shmmni
parameter:
prompt> echo 4096 > shmmni
To modify the shmall
parameter:
prompt> echo 3279547 > shmall
Write a script to initialize these values during system startup, and include the script in your system initialization files.
See Also: Your system vendor's documentation for more information about script files and initialization files |
Set the File Handles by using the following command:
prompt> echo 65536 > /proc/sys/fs/file-max prompt> ulimit -n 65536
Set the Sockets to /proc/sys/net/ipv4/ip_local_port_range
:
prompt> echo 10000 65000 > /proc/sys/net/ipv4/ip_local_port_range
Set the Process by using ulimit
-u
. This gives you the number of processes for each user. For example:
ulimit -u 16384
Table 2-25 lists the minimum values required to run Oracle Collaboration Suite on Linux x86.
Table 2-25 Kernel Parameter Settings for Linux x86
Kernel | Parameter Setting | Definition |
---|---|---|
semmni |
142 |
The maximum number of semaphore sets in the entire system. |
semmns |
32000 |
The maximum number of semaphores on the system. This setting is a minimum recommended value for an initial installation only. The semmns parameter should be set to the sum of the init sid .ora PROCESSES parameter for each Oracle database, adding the largest one twice, and then adding an additional 10 for each database. |
semopm |
100 |
The maximum number of operations for each semop call. |
semmsl |
250 |
The minimum recommended number of semaphores for each id for an initial installation only. The semmsl parameter should be set to 10 plus the largest init sid .ora PROCESSES parameter of any Oracle database on the system. |
shmmax |
4294967295 |
The maximum allowable size of one shared memory segment. It is 2 GB for SMP kernel. The recommended size is half the RAM size. |
shmmni |
4096 |
The maximum number of shared memory segments in the entire system. |
shmall |
3279547 |
Total amount of shared memory available |
msgmni |
2878 |
Number of message queue identifiers |
msgmax |
8192 |
Maximum message size |
msgmnb |
65535 |
Maximum number of bytes on the message queue |
file-max |
327679 |
Maximum number of files |
Oracle Collaboration Suite information storage uses UNIX resources such as shared memory, swap memory, and semaphore extensively for interprocess communication. If your parameter settings are insufficient for Oracle Collaboration Suite information storage, then you experience problems during installation and instance startup.The greater the amount of data you can store in memory, the faster your database operates. In addition, by maintaining data in memory, the UNIX kernel reduces disk I/O activity.
Review your kernel parameter settings to ensure that they meet Oracle Collaboration Suite information storage requirements. If you do not do this, you may experience errors during installation, or operational errors after installation. These are the recommended kernel parameter requirements for a typical Oracle Collaboration Suite information storage environment.If you have previously tuned your kernel parameters to levels that meet your application needs, then continue to use these values. A system restart is necessary if you change the kernel settings for the kernel changes to take effect.
Refer to the appropriate tables for the kernel parameters for your platform:
For Solaris Operating Environment (SPARC 32-bit), use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification number and owner.
Use a text editor such as vi
to change the kernel parameter settings in the /etc/system
file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels Oracle Collaboration Suite information storage requires, then do not change the settings. If the levels are too low, change them to levels at least as high as those in the table. If you change the settings, save the /etc/system
file and restart the system.
Example 2-3 Example Settings in /etc/system for Solaris Operating Environment (SPARC 32-bit)
set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=256 set semsys:seminfo_semmsl=256 set semsys:seminfo_semmnu=4096 set rlim_fd_max=1024 set rlim_fd_cur=1024
Table 2-26 lists the minimum values required to run Oracle Collaboration Suite information storage on Solaris Operating Environment (SPARC 32-bit).
Table 2-26 Kernel Parameter Settings for Solaris Operating Environment (SPARC 32-bit)
Kernel | Parameter Setting | Definition |
---|---|---|
rlim_fd_cur |
1024 |
The number of open files for each process. |
rlim_fd_max |
1024 |
The maximum number of open files for each process. |
semmni |
100 |
Defines the maximum number of semaphore sets in the entire system. |
semmns |
1024 |
Defines the maximum semaphores on the system. This setting is a minimum recommended value, for initial installation only.
The |
semmsl |
256 |
Defines the minimum recommended value, for initial installation only. The semmsl parameter should be set to 10 plus the largest init sid .ora PROCESSES parameter of any Oracle database on the system. |
shmmax |
4294967295 |
Defines the maximum allowable size of one shared memory segment.
4 GB = 4294967295 |
shmmin |
1 |
Defines the minimum allowable size of a single shared memory segment. |
shmmni |
100 |
Defines the maximum number of shared memory segments in the entire system. |
shmseg |
10 |
Defines the maximum number of shared memory segments one process can attach. |
For hp-ux PA-RISC (64-bit), you can use the System Administrator's Menu (SAM) to configure the hp-ux PA-RISC (64-bit) kernel as required by your application. The parameters in Table 2-27 are those recommended for a general user running a typical Oracle Collaboration Suite information storage single database instance on hp-ux PA-RISC (64-bit). You may need to change the values based on your application needs and the type of system on which you are working. Refer to the following table to determine if your system shared memory and semaphore kernel parameters are set correctly for Oracle Collaboration Suite information storage. Use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification numbers and owner.
The parameter settings in Table 2-27 show the recommended values to run Oracle Collaboration Suite information storage on hp-ux PA-RISC (64-bit).
Table 2-27 Kernel Parameter Settings for hp-ux PA-RISC (64-bit)
Kernel | Parameter Setting | Definition |
---|---|---|
ksi_alloc_max |
(nproc * 8) |
Defines the system wide limit of queued signals that can be allocated. |
max_thread_proc |
256 |
Defines the maximum number of kernel threads allowed for each process. You may need to increase the value if required by your application. Setting it to a default or low value may lead to an out of memory error for certain applications. |
maxdsiz |
1073741824 bytes |
Refers to the maximum data segment size in bytes 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 in bytes 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 bytes |
Defines the maximum stack segment size in bytes for 64-bit systems. |
maxswapchunk |
16384 |
Defines the maximum number of swap chunks where swchunk is the swap chunk size (1 KB blocks). swchunk is 2048 by default. It specifies the maximum amount of configurable swap space on the system. |
maxuprc |
((nproc * 9)/10) |
Defines the maximum number of user processes. |
msgmap |
(msgtql + 2) |
Defines the maximum number of message map entries. |
msgmni |
nproc |
Defines the number of message queue identifiers. |
msgseg |
32767 |
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.
|
nfile |
(15 * nproc + 2048) |
Defines the maximum number of open files. |
nflock |
4096 |
Defines the maximum number of file locks available on the system. |
ninode |
(8 * nproc + 2048) |
Defines the maximum number of open inodes. |
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 |
(semmni + 2) |
Defines the maximum number of semaphore map entries. |
semmni |
4138 |
Defines the maximum number of semaphore sets in the entire system. |
semmns |
8360 |
Defines the maximum number of semaphores in the system. The default value of semmns is 128 , which is, in most cases, too low for Oracle Collaboration Suite information storage. |
semmnu |
(nproc - 4) |
Defines the number of semaphore undo structures. |
semvmx |
32768 |
Defines the maximum value of a semaphore. |
shmmax |
4294967295 |
Defines the maximum allowable size of one shared memory segment.
The |
shmmni |
530 |
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. |
For Linux x86, use the ipcs
command to obtain a list of the system's current shared memory segments and semaphore sets, and their identification numbers and owner.
Perform the following steps to modify the kernel parameters by using the /proc
file system.
Log in as the root user.
Change to the /proc/sys/kernel
directory.
Review the current semaphore parameter values in the sem
file by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat sem
The output lists the values for the semmsl
, semmns
, semopm
, and semmni
parameters, respectively, as shown in the following example:
250 32000 32 128
Modify the parameter values by using the following command syntax:
prompt> echo semmsl_value semmns_value semopm_value semmni_value > sem
Replace the parameter variables with the values for your system in the order that they are entered in the preceding example. For example:
prompt> echo 1000 32000 100 150 > sem
Review the current shared memory parameters by using the cat
or more
utility. For example, using the cat
utility, enter the following command:
prompt> cat shared_memory_parameter
In the preceding example, the variable shared_memory_parameter
is either the shmmax
or shmmni
parameter. The parameter name must be entered in lowercase letters.
Modify the shared memory parameter by using the echo
utility. For example, to modify the shmmax
parameter, enter the following command:
prompt> echo 4294967295 > shmmax
Modify the shared memory parameter by using the echo
utility. For example, to modify the shmmni
parameter, enter the following command:
prompt> echo 4096 > shmmni
Modify the shared memory parameter by using the echo
utility. For example, to modify the shmall
parameter, enter the following command:
prompt> echo 2097152 > shmall
Write a script to initialize these values during system startup, and include the script in your system init
files.
See Also: Your system vendor's documentation for more information about script files andinit files |
Set File Handles by using ulimit -n
and /proc/sys/fs/file-max
.
prompt> echo 65536 > /proc/sys/fs/file-max prompt> ulimit -n 65536
Set the Sockets to /proc/sys/net/ipv4/ip_local_port_range
.
prompt> echo 1024 65000 > /proc/sys/net/ipv4/ip_local_port_range
Set the Process limit
by using ulimit
-u
. This gives you the number of processes for each user.
ulimit -u 16384
Table 2-28 shows the minimum values required to run Oracle Collaboration Suite information storage on Linux x86.
Table 2-28 Kernel Parameter Settings for Linux x86
Kernel | Parameter Setting | Definition |
---|---|---|
semmni |
142 |
Defines the maximum number of semaphore sets in the entire system. |
semmns |
32000 |
Defines the maximum semaphores on the system. This setting is a minimum recommended value, for initial installation only.
The |
semopm |
100 |
Defines the maximum number of operations for each semop call. |
semmsl |
250 |
Defines the minimum recommended value, for initial installation only. |
shmmax |
4294967295 |
Maximum allowable size of one shared memory segment. 2 GB for SMP kernel. The recommended size is half the RAM size. |
shmmni |
4096 |
Maximum number of shared memory segments in the entire system. |
shmall |
3279547 |
Total amount of shared memory available |
msgmni |
2878 |
Number of message queue identifiers |
msgmax |
8192 |
Maximum message size |
msgmnb |
65535 |
Maximum number of bytes on the message queue |
file-max |
327679 |
Maximum number of files |
Although Oracle Corporation recommends that you install the Oracle9iAS Infrastructure, Oracle Collaboration Suite information storage database, and Oracle Collaboration Suite middle tier on separate computers for better performance, you can install Oracle Collaboration Suite on one computer. A single-computer installation DVD is provided in the CD pack for Linux and Windows platforms. For other platforms, you can perform a single-computer installation using the CD-ROM sets in the CD pack.
See Also: http://otn.oracle.com/software/products/cs/files/README.html for information about single-computer installations on Windows and http://otn.oracle.com/software/products/cs/files/readme _linux.html for information about single-computer installations on Linux |
Note: The Oracle Web Conferencing document conversion server and voice conversion server must be installed on a separate computer from the Oracle Collaboration Suite middle tier. Additionally, Oracle Corporation recommends that you install the Oracle Web Conferencing document conversion server and voice conversion server on separate computers. Both the Oracle Web Conferencing document conversion server and voice conversion server must be installed on Windows platforms. |
See Also: The Oracle Web Conferencing Administrator's Guide for more information about the Oracle Web Conferencing document and voice conversion servers |