Oracle8i Parallel Server Setup and Configuration Guide Release 8.1.5 A67439-01 |
|
This chapter describes using the Oracle Universal Installer to install a new Oracle8i Enterprise Edition and the Oracle Parallel Server Option installation.
Specific topics discussed are:
The type of installation and the type of database you choose to install determines the how you proceed with installation and configuration decisions.
When you run Oracle Universal Installer, you can choose to install Oracle8i Enterprise Edition and the Oracle Parallel Server Option with the following installation types:
During installation, software components are installed on the node from which the Oracle Universal Installer is run, and pushed to the other selected nodes in the cluster.
To install Oracle8i Enterprise Edition and the Oracle Parallel Server Option:
The Oracle Universal Installer will not make Oracle Parallel Server Option visible unless Cluster Manager clusterware was properly configured. See your OSD vendor documentation for further information.
The node on which you are running the installation is selected whether or not you select it.
If the list of nodes does not includes nodes you expect, the vendor-supplied clusterware is either not installed, running, or configured properly. See your vendor documentation for further information.
If clusterware is not installed, click Previous in the Oracle Universal Installer, install Cluster Manager on those nodes, then click Next in the Oracle Universal Installer. The nodes should now be listed.
Each instance will have a SID that consists of the common prefix entered here and a thread ID that is automatically generated. For example, if OP is entered, the first instance in the cluster will have a SID of OP1, and the second instance will have a SID of OP2.
During installation no message appears to indicate components are installed to the other nodes.
If you choose a Typical installation type, the Oracle Database Configuration Assistant is run automatically to create the database with no user input. The information entered in the Database Identification page is used by the Oracle Database Configuration Assistant to identify the database and each instance's SID.
The Oracle Database Configuration Assistant verifies the raw devices file names were created for each tablespace that will be created. Raw devices and file names should have been configured in "Setting Up Raw Devices". If the file names were not set up, the Oracle Database Configuration Assistant will fail to create the database.
Among the files installed, Typical results in the creation of these files:
See "Understanding the Initialization Files" for further information about these files.
Note: If the Oracle Database Creation Assistant fails to create the database, see "Cleaning Up the Registry After an Oracle Database Configuration Assistant Failure on Windows NT". |
During the a Custom installation, the following products run, prompting for user input:
The Net8 Configuration Assistant prompts you to configure the network. The Net8 Configuration Assistant only allows you to configure some aspects of the network for the node the Oracle Universal Installer is running on. Follow these recommendations:
If you do not choose the registered port of 1521, you must configure the LOCAL_LISTENER parameter in the INITDB_NAME.ORA file and resolve it with a net service name entry in the TNSNAMES.ORA file. For further information about configuring non-default port numbers in LISTENER.ORA, see Chapter 6, "Configuring Naming Methods and the Listener" in the Net8 Administrator's Guide.
Note:
See "Configuring Net8 for Nodes" to complete network configuration for this node and other nodes in the cluster.
The information entered in the Database Identification page is used by the Oracle Database Configuration Assistant to identify the database name and each instance's SID.
The Oracle Database Configuration Assistant verifies the raw devices file names were created for each tablespace that will be created. Raw devices and file names should have been configured in "Setting Up Raw Devices". If the file names were not set up, the Oracle Database Configuration Assistant will fail to create the database.
If you chose a Custom installation type, you are prompted with a choice to create a database:
See "Creating the Database" to create a database with the Oracle Database Configuration Assistant after installation.
If you choose to create a database using the Oracle Database Configuration Assistant, the following page appears:
Respond to instructions in each Oracle Configuration Database Assistant page, then click Next when you are ready to continue to the next screen. When the last page displays, click Finish to start the creation of the Oracle Parallel Server database.
If the Oracle Universal Installer detects an earlier version of an Oracle database on your hard drive, you will prompted to migrate or upgrade the database to release 8.1. Do not click the Migrate an Existing Database check box, as the Oracle Data Migration Assistant does not support Oracle Parallel Server. Use the Migration utility to migrate after installation, as described in the Oracle8i Migration guide.
Note: Migrating or upgrading on Windows NT involves disabling the OraclePGMSService and dealing with the Operating System Dependent layer. The handling of the Operating System Dependent layer can be quite involved, especially during a migration. These instructions are not covered in the Oracle8i Migration guide. See Oracle8i Parallel Server Getting Started for Windows NT for complete migration and upgrade steps. |
Take note of the following:
Like a regular Oracle8i Enterprise Edition database, the Oracle Parallel Server Option on UNIX supports multiple Oracle homes, a feature that allows you to install one or more releases on the same machine (in multiple Oracle home directories). Windows NT supports multiple Oracle homes, but all the Oracle homes must contain the same release of the Oracle8i Enterprise Edition and the Oracle Parallel Server Option.
Both UNIX and Windows NT require that each node have only one copy of the vendor-supplied Operating System Dependent layer active.