Полезная информация

Oracle8 Installation Guide
Release 8.0.5 for Intel-LINUX

A66251-02

Library

Product

Contents

Index

Prev Next

3
Installation Tasks

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".

Starting the Installer

Perform the following tasks to run the Installer:

Mount the Product Installation CD-ROM
Start the Installer

Mount the Product Installation CD-ROM

The Oracle Product Installation CD-ROM is in RockRidge format.

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.

  1. Place the Product Installation CD-ROM in the CD-ROM drive.
  1. Log in as the root user and create a CD-ROM mount point directory:
$ su root# mkdir cdrom_mount_point_directory
  1. Mount the CD-ROM drive on the mount point directory and exit the root account:
# mount options device_name cdrom_mount_point_directory # exit
LINUX Example:
$ su root
# mkdir /cdrom
# chmod 777 /cdrom
# mount -t iso9660 /dev/cdrom /cdrom
# exit

Start the Installer

To start the Installer:

  1. Log in as oracle user.
  1. cd cdrom_ mount_point_directory/orainst.
  2. Start the Installer by entering ./orainst


    warning:

    Do not run the Installer as the root user.

     

Navigating in Character Mode

Use [Tab] key to move to next block.

Use arrow keys to move between fields.

Spacebar selects the current fields.

Non-Interactive Installations

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.

Installer Prompts

The Installer session is a series of prompts, each displayed in its own window.

Initial Installer Prompts

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.


Note:

To choose National Language Support for Oracle products, you must choose the custom installation option. Later in the Installer session you will select your preferred language. The Installer is available in American English only.

 

If you select a default installation and decide to create a database, the Installer copies pre-built data files to the specified mount points. This automatically creates a database by reusing the data files shipped on the CD and it creates new control files. This saves the time of loading the data dictionary creation scripts.


Note:

Pre-built data files are only used for a default installation.

 

Installation Type/README Files

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.

 

Installation Activity Choice

Specify the activity for which you want to use the Installer:

Installation Options

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.

Unable to Access the oratab File

This prompt appears only if the Installer is unable to access the /etc/oratab file. Refer to "Tasks to Perform as the root User" in Chapter 2 to create the oratab file.

Installation Locators

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.

Installation Log Files

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.

Install Source

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.)

National Language Support

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.

 

Location of the root.sh Script

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.

Software Asset Manager

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.

OSDBA Group

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.

OSOPER Group

You can choose to give the more limited Oracle OPERATOR privileges to a separate OS 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.

Instance Name

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.

Database Creation Prompts

The following prompts appear only if you use the Installer to create a database.

Number of Mount Points

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.

Mount Point Locators

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.

Table 3-1 Default Database File Summary
File   Default
Size
 
Minimum Size   Default Location (File System-Based)  

Control Files
(3 Files)

 

50 KB

 

database-
dependent

 

db_mount_point[1-3]/oradata/db_name/control0[1-3].ctl

 

Redo Log Files
(3 Files)

 

500 KB

 

100 KB

 

db_mount_point[1-3]/oradata/db_name/redosid0[1-3].log

 

SYSTEM

 

80 MB

 

5 MB

 

db_mount_point1/oradata/db_name/system01.dbf

 

ROLLBACK

 

15 MB

 

1MB

 

db_mount_point1/oradata/db_name/rbs01.dbf

 

TEMP

 

550 KB

 

260 KB

 

db_mount_point1/oradata/db_name/temp01.dbf

 

USERS

 

1 MB

 

200 KB

 

db_mount_point1/oradata/db_name/users01.dbf

 

TOOLS

 

25 MB

 

1 MB

 

db_mount_point1/oradata/db_name/tools01.dbf

 

Note: db_name is the value of the initialization parameter DB_NAME, which the Installer derives from the instance name you provide during the Installer session.

 

Character Set

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.

National Character Set

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.

SYS and SYSTEM User Passwords

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 dba and operator Group Passwords

The Installer asks if you want to set passwords for the OS 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 OS 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 orapwd utility after installation. You can also use the orapwd utility to disable remote connections.

 

Multi-Threaded Server

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.

Installing Documentation

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 in a separate Installer session.

Both operating system-specific and product documentation are available in HTML and PDF formats.

How to Install Documentation

To install operating system-specific documentation, select LINUX Documentation from the list of available products during a software installation.

To install product documentation, use the following procedure:

  1. Verify that the Installer is installed on the file system. The Installer cannot install files from the documentation CD-ROM unless it is running from the file system. If the Installer is not installed on the file system, install it before attempting to install documentation, following the instructions on page 3-4. Select the Oracle Installer from the Available Products window in the Software Asset Manager. If you have created a staging area, you can also run the Installer from there.
  1. Start the Installer from the local disk (not from CD-ROM).
  2. At the Installation Activity Choice screen, choose the Install, Upgrade, or De-Install Software option.
  3. At the Installation Options screen, choose the Install Documentation Only option.
  4. Indicate HTML, PDF, or both formats.
  5. From the Software Asset Manager screen, select Oracle8 Product Documentation.
  6. Select the Install button. The Installer notifies you when it has completed installing the documentation.

Accessing installed documentation is discussed in Chapter 4, "Configuring the Oracle8 System".

Verifying the Installer Session

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.




Prev

Next
Oracle
Copyright © 1999 Oracle Corporation.

All Rights Reserved.

Library

Product

Contents

Index