Oracle8i Parallel Server Setup and Configuration Guide Release 2 (8.1.6) A76934-01 |
|
This chapter describes pre-installation requirements for Oracle Parallel Server.
Specific topics discussed are:
Verify that your system meets the installation requirements described in the following sections before you install.
Verify the hardware software requirements for each node:
Each node in a cluster requires the following hardware:
Each node in a cluster requires the following software:
Oracle Enterprise Manager version 2 is a management framework consisting of a Console, a suite of tools and services, and a network of management servers and Oracle Intelligent Agents.
You can run the individual Oracle Enterprise Manager components on separate machines or combine different components on separate machines to collaboratively manage the complete Oracle environment.
The components are listed below:
Oracle Diagnostics Pack includes Oracle Performance Manager application, from which you can choose from a variety of graphic statistical performance charts for parallel servers.
8.1.6, 8.1.5, 8.0.5, 8.0.4, 8.0.3, 7.3.4 on database repository machine
8.1.6 on all Oracle Parallel Server nodes
Oracle Intelligent Agent may be installed from the Oracle8i Enterprise Edition CD-ROM.
Oracle Parallel Server requires a shared disk subsystem to contain shared partitions that are raw. All Oracle8i data, log, and control files are placed on shared raw partitions.
Clusters do not provide access to a shared file system among all nodes of a cluster. As a result, data files, redo log files, and control files are stored on raw devices. All instances share the data files and control files. However, each instance has its own redo log files, but all instances must have access to all log files during recovery.
Make sure you set up raw devices prior to installation If you run Oracle Database Configuration Assistant without setting up raw devices, the database cannot be created.
In order for Oracle Database Configuration Assistant to create the files for the database, a precise number of raw devices must be set up prior to database creation. These raw devices include:
The Typical database creation type available with Oracle Database Configuration Assistant creates the files at the sizes indicated in the table below. Raw partitions should be at least 1 MB larger than the file sizes.
The Custom database creation type available with Oracle Database Configuration Assistant enables you to specify the file and the block size. Ensure that the raw partitions provide enough space to account for the customized sizes.
If you do not plan to create the database with Oracle Database Configuration Assistant, the number of raw devices created depends on the number of the data files, redo log files and control file you plan to create.
The creation of raw devices is operating-system specific, as described in the following sections:
Use the following procedure to create raw devices on UNIX operating systems:
database_object raw_device_file
where database_object represents raw device object, and raw_device_file is the path of the data file, control file or redo log file. Oracle Database Configuration Assistant expects the database objects listed in the table below:
The ASCII file should look like the following example for a two-node cluster:
system1 device/path/op_system1.dbf users1 device/path/op_user1.dbf temp1 device/path/op_temp1.dbf rbs1 device/path/op_rbs1.dbf indx1 device/path/op_indx1.dbf tools1 device/path/op_tools1.dbf drsys1 device/path/op_drsys1.dbf control1 device/path/op_control1.clt control2 device/path/op_control2.clt redo1_1 device/path/op_redo1_1.log redo1_2 device/path/op_redo1_2.log redo2_1 device/path/op_redo2_1.log redo2_2 device/path/op_redo2_2.log
When Oracle Database Configuration Assistant creates the database, it looks for the environment variable, reads in the ASCII file, and uses the file names indicated in the right-hand column of the table as the data files when building the tablespaces.
Windows NT does not support a true distributed file system. Therefore, data files, control files and redo log files reside on unformatted raw devices.
An extended partition points to raw space on the disk that can be assigned multiple logical partitions for the database files.
Because raw devices on Windows NT do not have a file name or drive letter associated with them like a regular file system, an extended partition is first created, which points to raw space on a disk. Multiple logical partitions are then created and assigned symbolic link names using the following format:
\\.\symbolic_link_name.
A symbolic link is simply a name for a logical partition, such as \\.\op_system1
for the SYSTEM tablespace. When the SYSTEM tablespace is created, a copy of the data file is made to \\.\op_system1
, which links to a specific logical partition.
When Oracle Database Configuration Assistant creates the database, it verifies that the symbolic links names have been created and stores the files on the raw devices.
On Windows NT, create logical partitions and symbolic links for the database you are creating.
See Also:
Oracle Parallel Server Administrator's Guide for Windows NT for further information about creating logical partitions and symbolic links |
The Typical database creation type performed by Oracle Database Configuration Assistant requires the following symbolic link names listed in the following table:
Perform the following steps prior to installation:
root
user:
/etc/group
file on all nodes of the cluster. The OSDBA group name and number (and OSOPER group if you plan to designate one during installation) must be identical for all nodes of a UNIX cluster accessing a single database. The default UNIX group name for the OSDBA and OSOPER groups is dba
.
- the account is a member of the OSDBA group
- the account is used only to install and update Oracle software
- the account has write permissions on remote directories
-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
.rhosts
file of the oracle account, or the /etc/hosts.equiv
file.
oracle
account by performing a remote login (rlogin
) to each node in the cluster. If you are prompted for a password, the oracle account has not been given the same attributes on all nodes. Oracle Universal Installer cannot use the rcp
command to copy Oracle products to the remote directories without user equivalence.
|
![]() Copyright © 1999 Oracle Corporation. All Rights Reserved. |
|