Release 8.0.4
Part Number A56097-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Installation Guide Release 8.0.4 Part Number A56097-01 |
|
This chapter describes starting the Installer and creating a new Oracle8 Server installation.
This chapter does not discuss using the Installer for tasks other than a creating a new installation (such as installing a patch or relinking executables). For instructions on other Installer procedures and for installation troubleshooting, see Appendix A, "Using the Oracle Installer".
Perform the following tasks to run the Installer:
The Oracle Product Installation CD-ROM is in RockRidge format. If you are using Solaris Volume Management software (available by default on Solaris 2.x), the CD-ROM is mounted automatically to /cdrom/oracle when you put it into the disk drive, and you can proceed to Start the Installer.
If you are not using the Solaris volume management software, you must mount the CD-ROM manually. You must have root privileges to mount or unmount the CD-ROM manually. Be sure to unmount the CD-ROM before removing it from the drive.
root user and create a CD-ROM mount point directory:
$ su root # mkdir /cdrom # mount -r -F hsfs device_name /cdrom # exit
The Installer can be run in either Motif mode or character mode. To start the Installer:
cd cdrom_ mount_point_directory/orainst.
./orainst for character mode, or./orainst /m for Motif mode. If you are using Motif mode, make sure you set the DISPLAY to your current workstation.
| warning:
Do not run the Installer as the root user. |
The Installer can record responses from one installation session, then use those responses for subsequent installations. This "silent mode" can be useful for performing numerous, similar installations. See Appendix A, "Using the Oracle Installer" for more information.
The Installer session is a series of prompts, each displayed in its own window.
The initial Installer prompts appear for any Installer session, regardless of the task you are performing or products you want to install. You may select a default installation, or a custom installation.
If you select a default installation and decide to create a database, the Installer copies prebuilt data files to the specified mount points, which automatically creates a database by reusing the data files shipped on the CD and creates new control files. This saves time of loading the data dictionary creation scripts.
| Note:
Prebuilt data files are only used for a default installation. |
The Installer offers a choice between a custom or default installation. If you specify the default path, the Installer displays the settings it will use and asks you to confirm them.
| Note:
The default path assumes you are installing from CD-ROM. If you are installing from a staging area, you cannot use the default installation path. |
Specify the activity for which you want to use the Installer:
The Installer offers two basic options for installing software: Install New Product (with or without database object creation), and Add/Upgrade Software. You can install the Oracle8 Server using either option.
The Install New Product option creates an OFA-compliant directory structure. The Add/Upgrade Software option does not enforce OFA compliance, and does not let you create database objects in the same Installer session.
This prompt appears only if the Installer is unable to access the /var/opt/oracle/oratab file. Refer to "Tasks to Perform as the root User" in Chapter 2 to create the oratab file.
Use Legato Storage Manager when creating a database. Because the Legato daemon must run as the root user, installation of LSM is completed while running the root.sh script. Refer to Post Installation Steps for Legato Storage Manager (LSM) in Chapter 4.
If ORACLE_BASE is set in the environment, the Installer prompts you to confirm the setting for it and for ORACLE_HOME. If ORACLE_BASE is not set, the Installer prompts you for a software mount point, and to complete the pathname to the ORACLE_HOME directory.
The ORACLE_SID environment variable is an Oracle system identifier, which is the name of the Oracle Server instance.
The Installer creates four log files as records of the Installer session, one for each of the following categories of action: operating system, Installer, SQL, and makefile. The default location for installation logs is under the $ORACLE_HOME/orainst directory. If installation logs already exist, the Installer saves them as filename.old.
Specify whether you are installing from CD-ROM or from a staging area. If you are installing from a staging area, you are further prompted to specify temporary or permanent staging area. The Installer deletes temporary staging areas as it proceeds through the installation. (See Appendix A for more information about staging areas.)
Specify a language for receiving screen messages from Oracle products with National Language Support (NLS). Note that this is the default language only; users and client applications can also set the language in which messages are displayed at the session level. Installer prompts and messages are always displayed in American English.
| Note:
Appendix C, "National Language Support" lists the available character sets. |
The Installer creates the script root.sh under the $ORACLE_HOME/orainst directory. The script must be run by the root user, following the installation. If a root.sh script already exists, the Installer asks whether to append new actions to it, or create a new script. In general, you should create a new file, unless you have a specific reason for appending actions to the existing file.
The Software Asset Manager tracks the size of the distribution you have selected and the space available in the destination directory (the ORACLE_HOME directory). Select the products you want to install from the Available Products window and select the Install button. Depending on the products you select, you might see Installer prompts in addition to those described in this chapter.
Some products in the Software Asset Manager are grouped under categories, such as "Protocol Adapters" or "Precompilers". Categories are indicated by a plus sign to the left of the name. To expand a category name into its composite products, double-click on the category name (select and press [Return] in character mode).
| Note:
None of the products in a category are installed if you only select the category name. You must select the composite products individually. |
The Software Asset Manager screen is explained in detail in Appendix A.
The Installer displays the choices for a user group to be assigned Oracle DBA privileges. The default is the primary group for the oracle account. If this group is named anything other than dba, the Installer will relink the oracle executable after installation.
You can choose to give the more limited Oracle OPERATOR privileges to a separate UNIX group, which the Installer calls the OSOPER group. The default is the group you specified as the OSDBA group, in which case no separate user group is granted OPERATOR privileges. If you choose a group other than dba, the Installer relinks the oracle executable.
If you created a group for OPERATOR privileges in Chapter 2, "Setting the Environment", enter the name at the prompt. If not, accept the default.
The instance name, or sid, should be a unique identifier, not more than four characters long. The instance name is specified by the environment variable ORACLE_SID. In single-instance installations, it is generally the same as the value of the DB_NAME initialization parameter.
The following prompts appear only if you use the Installer to create a database.
Specify whether storage is on raw devices or a file system. Only Oracle Parallel Server requires raw devices, though raw devices can also be used with single instance installations.
If you are installing the Server (RDBMS), indicate if you want to follow the OFA recommendation to spread database objects across three mount points. While it is possible to specify a single mount point, or three mount points on the same drive, Oracle Corporation strongly recommends you spread your database across at least three, independent devices. If you accept this prompt, control and redo log files are spread across the mount points you specify.
Oracle Corporation recommends that the database mount points you specify at this prompt be different from the software mount point you specified during the initial Installer prompts (see page 3-5).
Table 3-1 summarizes the default size and placement for the database the Installer creates. Remember that the database is intended as a sample database. You can customize the location of any file during installation, as well as the size of redo log or database files, but the database is not optimized for your environment. It is not intended as a production database.
Specify a storage character set for the database. The default is US7ASCII. Do not specify any character set other than the default, unless you set the environment variable ORA_NLS33 during pre-installation.
The storage character set you specify cannot be changed without recreating the database. However, Oracle NLS supports client applications using different character sets than the storage set. See Appendix C, "National Language Support" for a list of supported character sets.
Specify the national character set for the database. This is a second character set that can be used with specially declared columns. The default is the character set you specified as the database character set.
The default password for the SYSTEM account is manager. The default password for the SYS account is change_on_install. Oracle Corporation recommends that you change both these passwords at this point.
The Installer asks if you want to set passwords for the UNIX groups to which you assigned Oracle DBA and OPERATOR privileges. Setting these passwords enables password authentication on SYSDBA and SYSOPER connections.
To connect to the database as SYSDBA or SYSOPER, a user must be a member of a UNIX group to which you assigned the DBA or OPERATOR roles, and enter the password you supply here.
| Note:
You can specify the passwords for the DBA and the OPERATOR roles manually with the |
The Multi-Threaded Server (MTS) lets you conserve the number of processes and amount of memory for certain types of applications. MTS is best suited for systems with limited memory, running online transaction processing (OLTP) applications with few long-running transactions. Oracle InterOffice is an example of an application that is well suited to MTS.
Because a long-running transaction ties up an MTS process for the duration of the transaction, MTS is not recommended for systems where long-running transactions are common, such as decision support systems.
The Installer session for Oracle Parallel Server differs somewhat from that of a single-instance installation.
Oracle Parallel Server can only use database objects that reside on raw volumes. Database objects should not be created on file systems.
You will be prompted for the pathnames of the raw volumes during the installation.
For information on creating raw volumes, refer to "Pre-Installation Steps for Oracle Parallel Server Option" on page 2-13.
Indicate whether you want to install on all nodes of the cluster at once, or only on the initial node. If you install only on the initial node, you must install on the other nodes in subsequent Installer sessions using the Install Oracle8 on Cluster option.
If you specify installation on all the nodes in the cluster, the Installer prompts you for the hostname and the ORACLE_HOME directory of the remote nodes (specify each node individually). You must enter a blank line at the List of Nodes screen after you have entered the remote nodes.
Oracle documentation comes in two categories: operating system-specific and product (sometimes called generic). Operating system-specific documentation is included on the software CD-ROM and can be installed during the software installation. Product documentation is provided on a separate CD-ROM, and can only be installed ina separate Installer session.
Product documentation can be installed on a per-product basis. For example, to install all product documentation for the current release of the server, select the Install Online Documentation option, then choose the Oracle8 Server as a product.
Both operating system-specific and product documentation are available in HTML and PDF formats.
To install operating system-specific documentation, select UNIX Documentation from the list of available products during a software installation.
To install product documentation, use the following procedure:
Accessing installed documentation is discussed in Chapter 4, "Configuring the Oracle8 System".
Following installation, the Installer returns to the Software Asset Manager screen. Verify that all products selected are listed as installed products. Exit the Installer and go to Chapter 4, "Configuring the Oracle8 System".
To create a database using the Installer, exit and restart the Installer, then choose the Create/Upgrade Database Objects option. Database creation prompts are described beginning on page 3-7.
