Oracle 安装配置


1  平台: 

      suse enterprise linux  11

Logging In to the System as root

Before you install the Oracle software, you must complete several tasks as theroot user. To log in as the root user, complete one of the following procedures:

Note:

You must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed
  • Following are the steps for installing the software from an X Window System workstation or X terminal:

    1. Start a local terminal session, for example, an X terminal (xterm).

    2. If you are not installing the software on the local system, then enter the following command to enable the remote host to display X applications on the local X server:

      $ xhost fully_qualified_remote_host_name
      

      For example:

      $ xhost somehost.us.example.com
      
    3. If you are not installing the software on the local system, then use the ssh, rlogin, or telnet command to connect to the system where you want to install the software:

      $ telnet fully_qualified_remote_host_name
      
    4. If you are not logged in as the root user, then enter the following command to switch user toroot:

      $ sudo sh
      password:
      #
      
  • Following are the steps for installing the software from a PC or other system with X server software:

    Note:

    If necessary, refer to your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order.
    1. Start the X server software.

    2. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.

    3. Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm).

    4. If you are not logged in as the root user on the remote system, then enter the following command to switch user toroot:

      $ sudo sh
      password:
      #
      

3 Checking the Hardware Requirements

The system must meet the following minimum hardware requirements:

  • Memory Requirements

  • System Architecture

  • Disk Space Requirements

3.1 Memory Requirements

The following are the memory requirements for installing Oracle Database 11g release 2 (11.2):

  • At least 1 GB of RAM

    To determine the RAM size, enter the following command:

    # grep MemTotal /proc/meminfo
    

    If the size of the RAM is less than the required size, then you must install more memory before continuing.

  • The following table describes the relationship between installed RAM and the configured swap space requirement:

    Note:

    On Linux, the HugePages feature allocates non-swappable memory for large page tables using memory-mapped files. If you enable HugePages, then you should deduct the memory allocated to HugePages from the available RAM before calculating swap space.
    Available RAMSwap Space Required
    Between 1 GB and 2 GB1.5 times the size of RAM
    Between 2 GB and 16 GBEqual to the size of RAM
    More than 16 GB16 GB

  • To determine whether the system architecture can run the software, enter the following command:

    # grep "model name" /proc/cpuinfo
    

    Note:

    This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install. If you do not see the expected output, then you cannot install the software on this system.

To determine the size of the configured swap space, enter the following command:

# grep SwapTotal /proc/meminfo

If necessary, refer to the operating system documentation for information about how to configure additional swap space.

To determine the available RAM and swap space, enter the following command:

# free

Note:

Oracle recommends that you take multiple values for the available RAM and swap space before finalizing a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.

Automatic Memory Management

Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/dev/shm)and file descriptors. The shared memory should be sized to be at least the greater ofMEMORY_MAX_TARGET and MEMORY_TARGET for each Oracle instance on that computer.

To determine the amount of shared memory available, enter the following command:

# df -k /dev/shm/

Note:

MEMORY_MAX_TARGET and MEMORY_TARGET cannot be used when LOCK_SGA is enabled or with HugePages on Linux.

3.2 System Architecture

To determine whether the system architecture can run the software, enter the following command:

# uname -m

Note:

This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install. If you do not see the expected output, then you cannot install the software on this system.

3.3 Disk Space Requirements

The following are the disk space requirements for installing Oracle Database 11g Release 2 (11.2):

  • At least 1 GB of disk space in the /tmp directory

    To determine the amount of disk space available in the /tmp directory, enter the following command:

    # df -h /tmp
    

    If there is less than 1 GB of free disk space available in the /tmp directory, then complete one of the following steps:

    • Delete unnecessary files from the /tmp directory to meet the disk space requirement.

    • Set the TMP and TMPDIR environment variables when setting theoracle user's environment.

      See Also:

      "Configuring the oracle User's Environment" for more information about setting TMP and TMPDIR
    • Extend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.

  • To determine the amount of free disk space on the system, enter the following command:

    # df -h
    
  • The following tables describe the disk space requirements for software files, and data files for each installation type on Linux x86-64:

    Installation TypeRequirement for Software Files (GB)
    Enterprise Edition4.35
    Standard Edition3.73

    Installation TypeRequirement for Data Files (GB)
    Enterprise Edition1.68
    Standard Edition1.48

    Additional disk space, either on a file system or on an Automatic Storage Management disk group is required for the fast recovery area if you choose to configure automated backups.

4 Checking the Software Requirements

Depending on the products that you intend to install, verify that the following softwares are installed on the system.

  • Operating System Requirements

  • Kernel Requirements

  • Package Requirements

  • Compiler Requirements

  • Additional Software Requirements

Note:

Oracle Universal Installer performs checks on the system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.

4.1 Operating System Requirements

The following are the operating system requirements for Oracle Database 11g Release 2 (11.2) for Linux x86-64:

  • Asianux 2.0

  • Asianux 3.0

  • Oracle Enterprise Linux 4.0 Update 7 or later

  • Oracle Enterprise Linux 5.0

  • Red Hat Enterprise Linux 4.0 Update 7 or later

  • Red Hat Enterprise Linux 5.0

  • SUSE Linux Enterprise Server 10.0

  • SUSE Linux Enterprise Server 11.0

Starting with Oracle Database 11g Release 2 (11.2), the Security Enhanced Linux (SE Linux) feature is supported for Oracle Enterprise Linux 4.0, Red Hat Enterprise Linux 4.0, Oracle Enterprise Linux 5.0, and Red Hat Enterprise Linux 5.0.

To determine the distribution and version of Linux installed, enter the following command:

# cat /proc/version

Note:

Only the distributions and versions listed in the earlier list are supported. Do not install the software on other versions of Linux.

4.2 Kernel Requirements

The following are the kernel requirements for Oracle Database 11g Release 2 (11.2):

  • For Asianux 2, Oracle Enterprise Linux 4.0, and Red Hat Enterprise Linux 4.0:

    2.6.9 or later

  • For Asianux 3, Oracle Enterprise Linux 5.0, and Red Hat Enterprise Linux 5.0:

    2.6.18 or later

  • For SUSE 10:

    2.6.16.21 or later

  • On SUSE Linux Enterprise Server 11:

    2.6.27.19 or later

To determine whether the required kernel is installed, enter the following command:

# uname -r

The following is a sample output displayed by running this command on an Oracle Enterprise Linux 5.0 system:

2.6.18-128.el5PAE

In this example, the output shows the kernel version (2.6.18) and errata level (-128.el5PAE) on the system.

If the kernel version does not meet the requirement specified earlier in this section, then contact the operating system vendor for information about obtaining and installing kernel updates.

4.3 Package Requirements

The following are the list of packages required for Oracle Database 11g Release 2 (11.2):

Note:

  • Oracle recommends that you install your Linux operating system with the default software packages (RPMs), unless you specifically intend to perform a minimal installation, and follow the directions for performing such an installation to ensure that you have all required packages for Oracle software.

  • Oracle recommends that you do not customize RPMs during a default operating system installation. A default installation includes most required packages, and will help you to limit manual checks of package dependencies.

  • If you did not perform a default Linux installation, you intend to use LDAP, and you want to use the scriptsodisrvreg, oidca, or schemasync, then install the Korn shell RPM for your Linux distribution.

  • You must install the packages (or later versions) listed in the following table. Also, ensure that the list of RPMs and all the prerequisites for these RPMs are installed.

  • The following or later version of packages for Asianux 2, Oracle Enterprise Linux 4.0, and Red Hat Enterprise Linux 4.0 should be installed:

  • The following or later version of packages for SUSE Linux Enterprise Server 11 should be installed:

    binutils-2.19
    gcc-4.3
    gcc-32bit-4.3
    gcc-c++-4.3
    glibc-2.9
    glibc-32bit-2.9
    glibc-devel-2.9
    glibc-devel-32bit-2.9
    ksh-93t
    libaio-0.3.104
    libaio-32bit-0.3.104
    libaio-devel-0.3.104
    libaio-devel-32bit-0.3.104
    libstdc++33-3.3.3
    libstdc++33-32bit-3.3.3
    libstdc++43-4.3.3_20081022
    libstdc++43-32bit-4.3.3_20081022
    libstdc++43-devel-4.3.3_20081022
    libstdc++43-devel-32bit-4.3.3_20081022
    libgcc43-4.3.3_20081022
    libstdc++-devel-4.3
    make-3.81
    sysstat-8.1.5
    

To determine whether the required packages are installed, enter commands similar to the following:

# rpm -q package_name

If a package is not installed, then install it from the Linux distribution media or download the required package version from the Linux vendor's Web site.

4.4 Compiler Requirements

The following are the compiler requirements for Pro*C/C++ , Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) with Oracle Database 11g Release 2 (11.2):

Intel C++ Compiler 10.1 or later and the version of GNU C and C++ compilers listed under"Package Requirements" are supported with these products.

Note:

Intel Compiler v10.1 can be used only with gcc 3.4.5 or gcc 4.0 or gcc 4.1 standard template libraries to build Oracle C++ Call Interface (OCCI) applications.

Oracle XML Developer's Kit is supported with the same compilers as OCCI.

4.5 Additional Software Requirements

Depending on the components you want to use, you must ensure that the following software are installed:

  • Oracle ODBC Drivers

  • Oracle JDBC/OCI Drivers

  • Oracle Messaging Gateway

  • Browser Requirements

4.5.1 Browser Requirements

Web browsers must support Java Script, and the HTML 4.0 and CSS 1.0 standards. The following Web browsers are supported for Oracle Enterprise Manager Database Control:

  • Netscape Navigator 8.1

  • Netscape Navigator 9.0

  • Microsoft Internet Explorer 6.0 SP2

  • Microsoft Internet Explorer 7.0

  • Microsoft Internet Explorer 7.0 SP1

  • Microsoft Internet Explorer 8.0

  • Firefox 2.0

  • Firefox 3.0.7

  • Safari 3.0.4

  • Safari 3.1

  • Safari 3.2

5 Creating Required Operating System Groups and Users

The following local operating system groups and users are required if you are installing Oracle Database:

  • The Oracle Inventory group (typically, oinstall)

  • The OSDBA group (typically, dba)

  • The Oracle software owner (typically, oracle)

  • The OSOPER group (optional. Typically, oper)

To determine whether these groups and users already exist, and if necessary, to create them, follow these steps:

  1. To determine whether the oinstall group exists, enter the following command:

    # more /etc/oraInst.loc
    

    If the output of this command shows the oinstall group name, then the group already exists.

    If the oraInst.loc file exists, then the output from this command is similar to the following:

    inventory_loc=/u01/app/oraInventory
    inst_group=oinstall
    

    The inst_group parameter shows the name of the Oracle Inventory group,oinstall.

  2. To determine whether the dba group exists, enter the following command:

    # grep dba /etc/group
    

    If the output from this commands shows the dba group name, then the group already exists.

  3. If necessary, enter the following commands to create the oinstall anddba groups:

    # /usr/sbin/groupadd oinstall
    # /usr/sbin/groupadd dba
    
  4. To determine whether the oracle user exists and belongs to the correct groups, enter the following command:

    # id oracle
    

    If the oracle user exists, then this command displays information about the groups to which the user belongs. The output should be similar to the following, indicating thatoinstall is the primary group and dba is a secondary group:

    uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
    
  5. If necessary, complete one of the following actions:

    • If the oracle user exists, but its primary group is not oinstall or it is not a member of thedba group, then enter the following command:

      # /usr/sbin/usermod -g oinstall -G dba oracle
      
    • If the oracle user does not exist, enter the following command to create it:

      # /usr/sbin/useradd -g oinstall -G dba oracle
      

      This command creates the oracle user and specifies oinstall as the primary group anddba as the secondary group.

  6. Enter the following command to set the password of the oracle user:

    # passwd oracle
    

6 Configuring Kernel Parameters

Verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown. The procedure following the table describes how to verify and set the values.

Note:

The kernel parameter and shell limit values shown in the following section are minimum values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. Refer to the operating system documentation for more information about tuning kernel parameters.
ParameterMinimum ValueFile
semmsl

semmns

semopm

semmni

250

32000

100

128

/proc/sys/kernel/sem
shmall2097152/proc/sys/kernel/shmall
shmmaxEither 4 GB - 1 byte, or half the size of physical memory (in bytes), whichever is lower.

Default: 536870912

/proc/sys/kernel/shmmax
shmmni4096/proc/sys/kernel/shmmni
file-max512 * PROCESSES/proc/sys/fs/file-max
ip_local_port_rangeMinimum: 9000

Maximum: 65500

/proc/sys/net/ipv4/ip_local_port_range
rmem_default262144/proc/sys/net/core/rmem_default
rmem_max4194304/proc/sys/net/core/rmem_max
wmem_default262144/proc/sys/net/core/wmem_default
wmem_max1048576/proc/sys/net/core/wmem_max
aio-max-nrMaximum: 1048576

Note: This value limits concurrent outstanding requests and should be set to avoid I/O subsystem failures.

/proc/sys/fs/aio-max-nr

Note:

If the current value of any parameter is higher than the value listed in this table, then do not change the value of that parameter.

To view the current value specified for these kernel parameters, and to change them if necessary:

  • Enter commands similar to the following to view the current values of the kernel parameters:

    Note:

    Make a note of the current values and identify any values that you must change.
    ParameterCommand
    semmsl, semmns,semopm, and semmni# /sbin/sysctl -a | grep sem

    This command displays the value of the semaphore parameters in the order listed.

    shmall, shmmax, andshmmni# /sbin/sysctl -a | grep shm
    file-max# /sbin/sysctl -a | grep file-max
    ip_local_port_range# /sbin/sysctl -a | grep ip_local_port_range
    rmem_default# /sbin/sysctl -a | grep rmem_default
    rmem_max# /sbin/sysctl -a | grep rmem_max
    wmem_default# /sbin/sysctl -a | grep wmem_default
    wmem_max# /sbin/sysctl -a | grep wmem_max

  • If the value of any kernel parameter is different from the recommended value, then complete the following steps:

    1. Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

      Note:

      Include lines only for the kernel parameter values that you want to change. For the semaphore parameters ( kernel.sem), you must specify all four values. However, if any of the current values are larger than the minimum value, then specify the larger value.
      fs.aio-max-nr = 1048576
      fs.file-max = 6815744
      kernel.shmall = 2097152
      kernel.shmmax = 536870912
      kernel.shmmni = 4096
      kernel.sem = 250 32000 100 128
      net.ipv4.ip_local_port_range = 9000 65500
      net.core.rmem_default = 262144
      net.core.rmem_max = 4194304
      net.core.wmem_default = 262144
      net.core.wmem_max = 1048586
      

      Note:

      The minimum value required for shmmax is 0.5 GB. However, Oracle recommends that you set the value of shmmax to 2.0 GB for optimum performance of the system.

      By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system. However, on SUSE Linux Enterprise Server systems, enter the following command to ensure that the system reads the/etc/sysctl.conf file when it restarts:

      # /sbin/chkconfig boot.sysctl on
      
    2. Enter the following command to change the current values of the kernel parameters:

      # /sbin/sysctl -p
      

      Review the output from this command to verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then enter this command again.

    3. Enter the command /sbin/sysctl -a to confirm that the values are set correctly.

    4. On SUSE systems only, enter the following command to cause the system to read the/etc/sysctl.conf file when it restarts:

      # /sbin/chkconfig boot.sysctl on
      
    5. On SUSE systems only, you must enter the GID of the oinstall group as the value for the parameter/proc/sys/vm/hugetlb_shm_group. Doing this grants members of oinstall a group permission to create shared memory segments.

      For example, where the oinstall group GID is 501:

      # echo 501 > /proc/sys/vm/hugetlb_shm_group
      

      After running this command, use vi to add the following text to /etc/sysctl.conf, and enable the boot.sysctl script to run on system restart:

      vm.hugetlb_shm_group=501
      

      Note:

      Only one group can be defined as the vm.hugetlb_shm_group.
    6. After updating the values of kernel parameters in the /etc/sysctl.conf file, either restart the computer, or run the commandsysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.

Setting Shell Limits for the oracle User

To improve the performance of the software, you must increase the following shell limits for theoracle user:

Shell LimitItem in limits.confHard Limit
Maximum number of open file descriptorsnofile65536
Maximum number of processes available to a single usernproc16384
Maximum size of the stack segment of the processstack10240

To increase the shell limits:

  1. Add the following lines in the /etc/security/limits.conf file:

    oracle           soft    nproc   2047
    oracle           hard    nproc   16384
    oracle           soft    nofile  1024
    oracle           hard    nofile  65536
    
  2. Add the following line to the /etc/pam.d/login file, if it does not already exist:

    session    required     pam_limits.so
    
  3. Depending on the oracle user's default shell, make the following changes to the default shell startup file:

    • For the Bourne, Bash, or Korn shell, add the following lines in the /etc/profile file (or the/etc/profile.local file on SUSE Linux Enterprise Server systems):

      if [ $USER = "oracle" ]; then
              if [ $SHELL = "/bin/ksh" ]; then
                    ulimit -p 16384
                    ulimit -n 65536
              else
                    ulimit -u 16384 -n 65536
              fi
      fi
      
    • For the C shell, add the following lines in the /etc/csh.login file (or the/etc/csh.login.local file on SUSE Linux Enterprise Server systems):

      if ( $USER == "oracle" ) then
              limit maxproc 16384
              limit descriptors 65536
      endif
      

7 Creating Required Directories

Create directories with names similar to the following, and specify the correct owner, group, and permissions for them:

  • The Oracle base directory

  • An optional Oracle data file directory

The Oracle base directory must have 3 GB of free disk space, or 4 GB of free disk space if you choose not to create a separate Oracle data file directory.

Note:

If you do not want to create a separate Oracle data file directory, then you can install the data files in a subdirectory of the Oracle base directory. However, this is not recommended for production databases.

To create the Oracle base directory:

  1. Enter the following command to display information about all mounted file systems:

    # df -k
    

    This command displays information about all the file systems mounted on the system, including:

    • The physical device name

    • The total amount, used amount, and available amount of disk space

    • The mount point directory for that file system

  2. From the display, identify either one or two file systems that meet the disk space requirements mentioned earlier in this section.

  3. Note the name of the mount point directory for each file system that you identified.

  4. Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:

    # mkdir -p /mount_point/app/
    # chown -R oracle:oinstall /mount_point/app/
    # chmod -R 775 /mount_point/app/
    

    For example:

    # mkdir -p /u01/app/
    # chown -R oracle:oinstall /u01/app/
    # chmod -R 775 /u01/app/
    

8 Configuring the oracle User's Environment

You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer, you must configure the environment of theoracle user. To configure the environment, you must:

  • Set the default file mode creation mask (umask) to 022 in the shell startup file.

  • Set the DISPLAY environment variable.

To set the oracle user's environment:

  1. Start a new terminal session, for example, an X terminal (xterm).

  2. Enter the following command to ensure that X Window applications can display on this system:

    $ xhost fully_qualified_remote_host_name
    

    For example:

    $ xhost somehost.us.example.com
    
  3. Complete one of the following steps:

    • If the terminal session is not connected to the system where you want to install the software, then log in to that system as theoracle user.

    • If the terminal session is connected to the system where you want to install the software, then switch user tooracle:

      $ su - oracle
      
  4. To determine the default shell for the oracle user, enter the following command:

    $ echo $SHELL
    
  5. Open the oracle user's shell startup file in any text editor:

    • Bash shell (bash) on SUSE Linux Enterprise Server:

      $ vi .profile
      
    • Bourne shell (sh), Bash shell on Red Hat (bash), or Korn shell (ksh):

      $ vi .bash_profile
      
    • C shell (csh or tcsh):

      % vi .login
      
  6. Enter or edit the following line in the shell startup file, specifying a value of022 for the default file mode creation mask:

    umask 022
    
  7. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then remove the corresponding lines from the file.

  8. Save the file and exit from the editor.

  9. To run the shell startup script, enter the following command:

    • Bash shell on Red Hat:

      $ . ./.bash_profile
      
    • Bourne shell, Bash shell on SUSE Linux Enterprise Server, or Korn shell:

      $ . ./.profile
      
    • C shell:

      % source ./.login
      
  10. If you are not installing the software on the local system, then enter a command similar to the following to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      

    In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).

  11. If you determined that the /tmp directory had insufficient free disk space when checking the hardware requirements, then identify a file system with the required amount of free space and set theTMP and TMPDIR environment variables as follows:

    1. Use the df -k command to identify a suitable file system with sufficient free space.

    2. If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:

      # sudo mkdir /mount_point/tmp
      # sudo chmod a+wr /mount_point/tmp
      # exit
      
    3. Enter commands similar to the following to set the TMP and TMPDIR environment variables:

      Bourne, Bash, or Korn shell:

      $ TMP=/mount_point/tmp
      $ TMPDIR=/mount_point/tmp
      $ export TMP TMPDIR
      

      C shell:

      % setenv TMP /mount_point/tmp
      % setenv TMPDIR /mount_point/tmp
      
  12. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:

    • Bourne, Bash, or Korn shell:

      $ ORACLE_BASE=/u01/app/oracle
      $ ORACLE_SID=sales
      $ export ORACLE_BASE ORACLE_SID
      
    • C shell:

      % setenv ORACLE_BASE /u01/app/oracle
      % setenv ORACLE_SID sales
      

    In these examples, /u01/app/oracle is the Oracle base directory that you created or identified earlier andsales is the name that you want to call the database (typically no more than five characters).

  13. Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:

    Bourne, Bash, or Korn shell:

    $ unset ORACLE_HOME
    $ unset TNS_ADMIN
    

    C shell:

    % unsetenv ORACLE_HOME
    % unsetenv TNS_ADMIN
    
  14. To verify that the environment has been set correctly, enter the following commands:

    $ umask
    $ env | more
    

    Verify that the umask command displays a value of 22,022, or 0022 and the environment variables that you set in this section have the correct values.

9 Mounting the Product Disc

On most Linux systems, the disk mounts automatically when you insert it into the installation media. If the disk does not mount automatically, then follow these steps to mount it:

  1. Enter a command similar to the following to eject the currently mounted disc, then remove it from the drive:

    • Asianux, Oracle Enterprise Linux, and Red Hat Enterprise Linux:

      $ sudo eject /mnt/dvd
      
    • SUSE Linux Enterprise Server:

      # eject /media/dvd
      

    In these examples, /mnt/dvd and /media/dvd are the mount point directories for the disc drive.

  2. Insert the DVD into the disc drive.

  3. To verify that the disc mounted automatically, enter a command similar to the following:

    • Asianux, Oracle Enterprise Linux, and Red Hat Enterprise Linux:

      # ls /mnt/dvd
      
    • SUSE Linux Enterprise Server:

      # ls /media/dvd
      
  4. If this command fails to display the contents of the disc, then enter a command similar to the following:

    • Asianux, Oracle Enterprise Linux, and Red Hat Enterprise Linux:

      # mount -t iso9660 /dev/dvd /mnt/dvd
      
    • SUSE Linux Enterprise Server:

      # mount -t iso9660 /dev/dvd /media/dvd
      

    In these examples, /mnt/dvd and /media/dvd are the mount point directories for the disc drive.

10 Installing Oracle Database

After configuring the oracle user's environment, start Oracle Universal Installer and install Oracle Database as follows:

  1. To start Oracle Universal Installer, enter the following command:

    $ /mount_point/db/runInstaller
    

    If Oracle Universal Installer does not start, then refer to Oracle Database Installation Guide for Linux for information about how to troubleshoot X Window display problems.

  2. The following table describes the recommended action for each Oracle Universal Installer screen. Use the following guidelines to complete the installation:

    • If you need more assistance, or if you want to choose an option that is not a default, then clickHelp for additional information.

    • If you encounter errors while installing or linking the software, then refer toOracle Database Installation Guide for Linux for information about troubleshooting.

    Note:

    If you have completed the tasks listed previously, then you can complete the installation by choosing the default values on most screens.
    ScreenRecommended Action
    Configure Security UpdatesEnter your e-mail address, preferably your My Oracle Support (formerly OracleMetaLink) e-mail address or user name in theEmail field.

    You can select the I wish to receive security updates via My Oracle Support check box to receive security updates.

    Enter your My Oracle Support (formerly OracleMetaLink) password in theMy Oracle Support Password field.

    Click Next.

    Select Installation OptionSelect Create and Configure a Database from the following list of available options, then clickNext:
    • Create and Configure a Database

    • Install Database Software Only

    • Upgrade an Existing Database

    System ClassSelect Server Class from the following options to install the database, and clickNext.
    • Desktop Class: Choose this option if you are installing on a laptop or desktop class system.

    • Server Class: Choose this option if you are installing on a server class system, such as what you would use when deploying Oracle in a production data center.

    Grid Installation OptionsSelect Single instance database installation for the type of database installation you want to perform, and clickNext.
    • Single instance database installation: This option installs the database and the listener.

    • Real Application Clusters database installation: This option installs Oracle Real Application Clusters and the listener.

    Select Install TypeSelect Typical Installation as the installation type from the following options, and then clickNext:
    • Typical Installation: This installation method is selected by default. It lets you quickly install Oracle Database using minimal input.

    • Advanced Installation: This installation method enables to perform more complex installations.

    Typical Install ConfigurationEnter the following information as per your requirements:

    Oracle base: The Oracle base path appears by default. You can change the path based on your requirement.

    Software location: In the Software Location section, accept the default values or enter the Oracle home name and directory path in which you want to install Oracle components. The directory path should not contain spaces.

    Storage Type: Select File System, or Automatic Storage Management as the database storage option.

    Database file location: If you select File System as your storage type, then clickBrowse and specify a database file location.

    ASMSNMP Password: If you select Automatic Storage Management as your Storage Type, then specify the password for the ASMSNMP user.

    Database Edition: Select the database edition that you want to install.

    OSDBA Group: The OSDBA group is selected by default. You can also select the OSDBA group from the list.

    Global database name: Specify the Global Database Name using the following syntax:

    database_name.domain
    

    For example, sales.us.example.com

    Administrative password: Enter the password for the privileged database account.

    Confirm Password: Reenter, and confirm the password for the privileged database account.

    Click Next to continue.

    Create InventoryThis screen is displayed only during the first installation of Oracle products on a system.

    Specify the full path of the Oracle Inventory directory. Ensure that the operating system group selected isoinstall. Click Next to continue.

    Perform Prerequisite ChecksVerify that all of the prerequisite checks succeed, and then clickNext.

    Oracle Universal Installer checks the system to verify that it is configured correctly to run Oracle software. If you have completed all of the preinstallation steps in this guide, all of the checks should pass.

    If a check fails, then review the cause of the failure listed for that check on the screen. If possible, rectify the problem and rerun the check. Alternatively, if you are satisfied that your system meets the requirements, then you can select the check box for the failed check to manually verify the requirement.

    SummaryReview the information displayed on this screen, and then clickFinish.

    Note: Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file by clickingSave Response File. Later, this file can be used for a silent installation.

    Install productThis screen states the progress of a database installation. After the database is installed, you are prompted to execute some root configuration script for new inventory as theroot user. Click Next.

    This screen then displays the status information for the configuration assistants that configure the software and create a database.

    Finally, a message is displayed at the end of Database Configuration Assistant process, and clickOK.

    Execute the root.sh script as the root user to complete the installation, and clickOK.

    FinishThis screen is shown automatically when all the configuration tools are successful.

    Click Close.


          以上转自oracle官方文档,只为个人保存用,请勿转载..........


评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值