Skip Headers
Oracle® Database Lite Getting Started Guide
10g (10.0.0)
Part No. B14138-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

1 Pre-Installation Requirements

Before you install, you must check to see that you have the correct hardware and software necessary for using Oracle Database Lite on your operating system. The requirements for each type of operating system are detailed in the following sections:

1.1 Include the Latest Patches

For the latest information and patches, refer to OracleMetaLink at the following Web site:

http://metalink.oracle.com

1.2 Release Notes

We recommend reading Oracle Database Lite Release Notes before installing Oracle Database Lite. Oracle Database Lite Release Notes are available as part of the documentation shipped with Oracle Database Lite. The most up-to-date version is also available at OTN at the following Web site:

http://otn.oracle.com/documentation/index.html

1.3 Oracle Components That Work With Oracle Database Lite

Since Oracle Database Lite stores and retrieves your information in an Oracle database, you must have a back-end Oracle database version 8.1.7 or higher, either the Standard or Enterprise Edition.

If you do not want to have the datafile for your Oracle Database Lite applications stored in the default location in the Oracle database, then modify the database configuration file to include the directory where you want your datafile stored. Configure the default directory for new tablespace in the db_create_file_dest parameter the database configuration file. Once updated, restart the Oracle database. This must be done before installing Oracle Database Lite. Refer to your database administration guide for details on how to modify the db_create_file_dest parameter.

In addition, Oracle Database Lite uses a middle-tier to communicate between the clients and the back-end database. You use one of the following as the middle-tier:

For more information about how Oracle Database Lite works with the middle-tier and the back-end database, see Section 2.1 "The Mobile Server Environment" in the Oracle Database Lite Administration and Deployment Guide.

1.4 System Requirements For Mobile Clients

Before you install, you must check to see that you have the correct hardware and software necessary for your Mobile Clients. The requirements for both are detailed in the following sections:

1.4.1 Hardware Requirements For Your Mobile Clients

The hardware requirements for your Mobile Clients are described in the following table:

Table 1-1 Hardware Requirements for Mobile Clients

Component Hardware Requirements for this Component
Mobile Client for Win32 CPU: Pentium III 360 MHz

Disk Space: 30 MB

RAM: 128 MB

Mobile Client for Web-to-Go CPU: Pentium III 360 MHz

Disk Space: 40 MB

RAM: 128 MB

Mobile Client for Palm CPU: 68328 and 68328Z

Disk Space: N/A

RAM: 5 MB

Mobile Client for Windows CE/Pocket PC CPU: ARM, XScale or x86

Storage Space: 8 MB

RAM: 16 MB

Branch Office CPU: Pentium III 360 MHz

Disk Space: 40 MB

RAM: 128 MB


1.4.2 Software Requirements For Your Mobile Clients

The software requirements for your Mobile Clients are described in the following table:

Table 1-2 Software Requirements for Mobile Clients

Component Operating System Other Software Requirements
Mobile Client for Win32 Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003 JDK 1.4.1 or higher

Microsoft .NET Framework 1.1

Mobile Client for Web-to-Go Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003
Mobile Client for Palm Palm OS 3.5, Palm OS 4.0, Palm OS 5 .x N/A
Mobile Client for Windows CE/Pocket PC Windows CE 3.0 or 3.0.1 If using JDBC, use the CrEme JDK version 3.24 from NSIcom.

ActiveSync version 3.7.1 or later.

Microsoft .NET Compact Framework 1.0

Branch Office Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003

You should install all of the patches required for the JDK 1.4.1 for the Windows operating system. This is constantly under review and published on the JDK download page on the Sun Microsystems Web site.

1.5 System Requirements For Windows Systems

Before you install, you must check to see that you have the correct hardware and software necessary for your Windows machines that use Oracle Database Lite. The requirements for both are detailed in the following sections:

1.5.1 Hardware Requirements For Windows

The hardware requirements for each component of Oracle Database Lite for Windows NT, Windows 2000, or Windows XP are described in the following table:

Table 1-3 Hardware Requirements for Windows

Component Hardware Requirements for this Component
Mobile Server CPU: Pentium III 1 GHz

Disk Space: 500 MB

RAM: 256 MB

Mobile Development Kit CPU: Pentium III 1GHz

Disk Space: 200 MB

RAM: 256 MB


1.5.2 Software Requirements For Windows

The software requirements for each component of Oracle Database Lite for Windows NT, Windows 2000, or Windows XP are described in the following table:

Table 1-4 Software Requirements for Windows

Component Operating System Other Software Requirements
Mobile Server Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003 If installed on top of Oracle9iAS version 9.0.2, use JDK 1.3. If installed on top of Oracle9iAS version 9.0.4 or OracleAS 10g, use JDK 1.4.1 or higher
Mobile Development Kit Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003 If installed on top of Oracle9iAS version 9.0.2, use JDK 1.3. If installed on top of Oracle9iAS version 9.0.4 or OracleAS 10g, use JDK 1.4.1 or higher

You should install all of the patches required for the JDK 1.3 or 1.4.1 for the Windows operating system. This is constantly under review and published on the JDK download page on the Sun Microsystems Web site.

1.6 System Requirements For UNIX Systems

Before you install, you must check to see that you have the correct hardware and software necessary for your UNIX machines that use Oracle Database Lite. The requirements for both are detailed in the following sections:

1.6.1 Hardware Requirements For UNIX Systems

Table 1-5 lists the minimum hardware requirements for OracleAS UNIX-based systems.

Table 1-5 Minimum Hardware Requirements for UNIX Systems

Item Minimum Requirement
display 256 color display
Sun SPARC CPU Sun SPARC Ultra 1 or higher
AIX CPU All AIX-compatible processors (64-bit)
HP CPU HP 9000 Series HP-UX processor for HP-UX 11.0 (64-bit)
Linux CPU Pentium II 233 MHz or better (32-bit)
Tru64 CPU Alpha processor (64-bit)
Memory 512 MB
Disk space for Sun SPARC 1 GB
Disk space for AIX 1 GB
Disk space for HP 1 GB
Disk space for Linux 1 GB
Disk space for Tru64 1 GB
TMP or swap space 1 GB

1.6.2 Operating System Requirements For UNIX

Use the following operating system requirements for installing Oracle Database Lite as a standalone product:

  • Table 1-6 lists the operating system requirements for Sun SPARC-based systems.

  • Table 1-7 lists the operating system requirements for AIX-based systems.

  • Table 1-8 lists the operating system requirements for HP-based systems.

  • Table 1-10 lists the operating system requirements for Linux-based systems.

  • Table 1-13 lists the operating system requirements for Tru64-based systems.

For the latest information on operating system requirements, refer to OracleMetaLink at the following Web site:

http://metalink.oracle.com

Table 1-6 Operating System Requirements for Sun SPARC-Based Systems

Item Requirement
Operating System Sun Solaris 2.6, Solaris 7, or Solaris 8
Window Manager Use any supported Sun Solaris window manager that supports Motif.

Table 1-7 Operating System Requirements for AIX-Based Systems

Item Requirement
Operating System AIX 5L version 5.2, Maintenance Level 1 or higher
Window Manager Use any supported IBM AIX window manager that supports Motif, such as dtwm, twm, and olwm.

Table 1-8 Operating System Requirements for HP-Based Systems

Item Requirement
Operating System HP-UX 11.0 (64-bit)
Quality Pack For HP-UX 11.0 (64 bit), install the Quality Pack Sept 2002 (QPK11000 B.11.00.58.5) or higher.
Patches PHKL_27813 s700_800 11.00 POSIX AIO;getdirentries;MVFS;rcp;mmap/IDS patch
Window Manager X Windows must be installed on the system from where the Installer is run. Use any supported X Windows server with support for Motif, such as dtwm, twm, and mwm.

Table 1-9 Operating System Requirements for HP-Based Systems

Item Requirement
Operating System HP-UX 11i (11.11) PA-RISC or higher
Quality Pack Dec 2001 Consolidate Patches (Dec01GQPK11i_Aux_Patch B.03.02.06) or higher.
Patches PHNE_28089 s700_800 11.11 cumulative ARPA Transport patch
Window Manager X Windows must be installed on the system from where the Installer is run. Use any supported X Windows server with support for Motif, such as dtwm, twm, and mwm.

Table 1-10 Operating System Requirements for Red Hat Enterprise Linux AS/ES 2.1

Item Requirement
Operating System Red Hat Enterprise Linux AS/ES 2.1
Patches Red Hat Patches Errata 25 kernel or a higher errata patch that is approved by Red Hat
Software Packages pdksh-5.2.14-13

Table 1-11 Operating System Requirements for Red Hat Enterprise Linux AS 3.0

Item Requirement
Operating System Red Hat Enterprise Linux Advanced Server 3.0

The minimum supported kernel and glibc versions are 2.4.21-4-EL and glibc-2.3.2-95.3

Patches Apply patch 3006854, which is downloadable from OracleMetaLink.
Software packages pdksh-5.2.14

Table 1-12 Operating System Requirements for UnitedLinux

Item Requirement
Operating System UnitedLinux 1.0
Patches SP2a: The minimum supported kernel and glibc versions are 2.4.19 and glibc-2.2.5-179.

SP3: The minimum supported kernel and glibc versions are 2.4.21 and glibc-2.2.5-213

Software packages pdksh-5.2.14

Table 1-13 Operating System Requirements for Tru64-Based Systems

Item Requirement
Operating System HP Tru64 UNIX 5.1B with Patch Kit 2 or higher
Operating system subsets OSFCMPLRS, OSFLIBA, OSFPGMR, OSFSER, OSFX11
Patches Patch Kit 2 or higher:

T64V51BB22AS0002-20030415

HP Tru64 UNIX V5.1BPK2 (BL22 ERP Kit - Fix for multiple applications may be granted an exclusive lock on the same file:

T64KIT0021665-V51BB22-E-20040220

Tru64 UNIX V5.1B PK2/BL22 Early Release Patch - Fix for Potential Application Core Dump:

T64KIT0021681-V51BB22-E-20040223

HP Tru64 UNIX - Problem with IP Multicast Packets:

T64KIT0019662-V51BB22-E-20030818

HP Tru64 UNIX 5.1B PK2 BL22 Fixes for AdvFS Panic in _OtsMove; and Possible Memory Corruption:

T64KIT0020879-V51BB22-E-20031125

Window Manager X Windows must be installed on the system from where the Installer is run. Use any supported X Windows server with support for Motif, such as dtwm, twm, and mwm.

The X environments, Basic X environments (OSF 11), and X Servers (OSFSER) are required to run graphical products.


1.6.3 Software Requirements For UNIX Systems

For all UNIX systems, you must have the JDK installed. If you are installing on top of Oracle9iAS version 9.0.2, install the JDK 1.3; if you are installed on top of Oracle9iAS 9.0.4 or OracleAS 10g, install JDK 1.4.1 or higher. You should install all of the patches required for your JDK version for the appropriate operating system. This is constantly under review and published on the JDK download page on the appropriate operating system Web site.

1.7 Recommended System Configuration For UNIX

This section describes the following system configurations for UNIX-based systems:

1.7.1 Setting UNIX Environment Variables

The following sections describe the environment variables that must be set before starting Oracle Universal Installer:


Note:

Ensure your PATH, CLASSPATH and library path environment variables do not exceed 1024 characters. Longer values might generate errors such as "Word too long" during installation.

Refer to Table 1-14 for the name of the library path environment variable for your platform.


Table 1-14 lists the names of the library path environment variables for each platform.

Table 1-14 Library Path Environment Variable

Platform Library Path Environment Variable
Tru64, Linux LD_LIBRARY_PATH
HP SHLIB_PATH and LD_LIBRARY_PATH
AIX LIBPATH

1.7.1.1 ORACLE_HOME

The Oracle home directory is the root directory in which Oracle software is installed. There are limits to the length of the values of the CLASSPATH values with JDK. If the ORACLE_HOME path is long, this will result in a long CLASSPATH and might cause problems running Oracle Database Lite. The workaround is to shorten ORACLE_HOME path.

The ORACLE_HOME environment variable must be set before starting the installer, which must be set to the directory where you want to install.

1.7.1.2 JAVA13_HOME

The JAVA13_HOME environment variable must be set to the directory where the Java Development Kit has been installed. If the JDK has not been installed, please install it before proceeding with the installation. If the Oracle Database Lite is installed on top of Oracle9iAS version 9.0.2, use JDK 1.3. If installed on top of Oracle9iAS version 9.0.4 or OracleAS 10g, use JDK 1.4.1 or higher.

Table 1-15 provides examples for the location where the JDK 1.3.1 could be installed on the system.

Table 1-15 JAVA13_HOME Environment Variables

Platform Sample JAVA13_HOME Environment Variable
Tru64 /usr/opt/java131
HP /opt/java/java.1.3.1.02
AIX /usr/java131

1.7.1.3 DISPLAY

Set the DISPLAY environment variable to refer to the X Server that will display the installer. The format of the DISPLAY environment variable is:

hostname:display_number.screen_number

For example, set the DISPLAY environment variable, as follows:

setenv DISPLAY myhost:0.0

Oracle Database Lite requires a running X server to properly create graphics for the installer, Web applications, and management tools. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running at all times. If you do not want to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).


See Also:

  • Your operating system documentation for more information on the DISPLAY environment variable.

  • Oracle Technology Network (http://otn.oracle.com) for further information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".


1.7.1.3.1 Installing From a Remote Machine

Setting the DISPLAY environment variable enables you to run the Oracle Universal Installer remotely from another workstation. On the system where you launch the Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.


Note:

You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting the installer, then run the commands on your local workstations as listed in the following table.

Shell Types On the Server Where the Installer is Running In the Session on Your Workstation
C Shell
prompt> setenv DISPLAY hostname:0.0
prompt> xhost +server_name
Bourne/Korn Shell
prompt> DISPLAY=hostname:0.0;export DISPLAY
prompt> xhost +server_name

1.7.1.4 TMP and TMPDIR

During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the requirements listed in Section 1.6.1, "Hardware Requirements For UNIX Systems" before installing Oracle Database Lite. The installation may fail if you do not have sufficient space. The installer checks for the TMP and TMPDIR environment variable to locate the temporary directory. If the TMP environment variable is not set, then the installer uses the /tmp directory. If the TMPDIR environment variable is not set, then the installer uses the /var/tmp directory. Set the TMP and TMPDIR environment variable using the commands in the following table.

C Shell Bourne/Korn Shell
prompt> setenv TMP full_path prompt> TMP=full_path;export TMP
prompt> setenv TMPDIR full_path prompt> TMPDIR=full_path;export TMPDIR

1.7.2 Creating UNIX Accounts and Groups

The following UNIX account and groups are required for the installation process:

1.7.2.1 UNIX Group Name For the Oracle Universal Installer Inventory

Use the admintool or groupadd utility to create a group name. In the following text the group name is oinstall. The oinstall group will own Oracle Universal Installer's oraInventory directory. The oracle user account that runs the installer must have the oinstall group as its primary group.

For more information on these utilities, refer to your operating system documentation.

1.7.2.2 UNIX Account to Own Oracle Software

The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.

Create an oracle account with the properties listed in Table 1-16.

Table 1-16 Oracle Account Properties

Variable Property
Login Name Select any name to access the account. This document refers to the name as the oracle account.
Group Identifier The oinstall group.
Home Directory Select a home directory consistent with other user home directories.
Login Shell The default shell can be either the C, Bourne, or Korn shell.


Note:

Do not use root as the oracle account.

1.7.3 Configuring Kernel Parameters and Shell Limits for UNIX

Depending on your operating system, see one of the following sections for information on checking the software requirements:

1.7.3.1 Configuring Shell Limits and System Configuration Parameters on AIX

On AIX systems, you do not need to configure kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

1.7.3.1.1 Configuring Shell Limits for AIX Systems

Verify that the shell limits shown in the following table are set to the values shown. The procedure following the table describes how to verify and set the values.

Table 1-17 Shell Limits

Shell Limits as shown in smit Recommended Value
Soft FILE size -1 (Unlimited)
Soft CPU time -1 (Unlimited) -- this is the default value
Soft DATA segment -1 (Unlimited)
Soft STACK size -1 (Unlimited)

To view or change the current value specified for these shell limits, follow these steps:

  1. Enter the smit command: #smit chuser

  2. In the User Name field, enter the user name of the Oracle software owner, such as oracle.

  3. Scroll down the list and verify that the value shown for the soft limits listed in the previous table is -1. If necessary, modify the existing value to be -1.

  4. Press F10 to exit.

1.7.3.1.2 Configure System Configuration Parameters for AIX

Verify that the Maximum number of processes allowed for each user is set to 2048 or greater. The procedure following the table describes how to verify and set the value.

  1. Enter the smit command: #smit chgsys

  2. Verify that the value shown for Maximum number of PROCESSES allowed per user is greater than or equal to 2048.

  3. Press F10 to exit.

Ensure that the ARG_MAX setting is set to the maximum value for AIX 5L:

  1. Check the ARG_MAX setting, as follows:

    prompt> getconf ARG_MAX
    
    
  2. If the value is less than 524288, then run the following command as the root user:

    #chdev -l sys0 -a ncargs=128
    

1.7.3.2 Configuring Kernel Parameters on HP-UX

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

Table 1-18 Kernel Parameters for HP-UX

Parameter Recommended Formula or Value
nfile 3000
nproc 2048

To view or modify the current value or formula specified for these kernel parameters, do the following:

  1. Optionally, set the DISPLAY environment variable to specify the display of the local system, as follows:

    • Bourne, Bash, or Korn shell:

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

      $ setenv DISPLAY localhost:0.0
      
  2. Start System Administration Manager (SAM): #/usr/sbin/sam

  3. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

  4. Check and possibly modify the value or formula specified for each of these parameters.

  5. Exit from SAM.

  6. If you modified the value specified for any parameter, then reboot the system with the following: # /sbin/shutdown -r -now

  7. If necessary, when the system restarts, log in and switch the user to root.

1.7.3.3 Configuring the Kernel Parameters on Linux

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedures following the table describe how to verify and set the values.

Table 1-19 Kernel Parameters on Linux

Parameter Value File
file-max 131072 /proc/sys/fs/file-max

To view or modify the current value specified for these kernel parameters, do the following:

  1. Enter the following command to view the current value of the file-max kernel parameter:

    # /sbin/sysctl -a | grep file-max
    
    
  2. To modify the value, do the following:

    1. Create or edit the /etc/sysctl.conf file and add the following.

      fs.file-max = 131072
      
      

      By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.

    2. Change the current values of the kernel parameter with the following command:

      # /sbin/sysctl -p
      
      

      Review the output from this command to verify that the values are correct. If the values are incorrect, then perform these steps again.

    3. On UnitedLinux only, enter the following command to cause the system to read the /etc/sysctl.conf file when it reboots:

      # chkconfig boot.sysctl on
      

1.7.3.4 Set Shell Limits for the User oracle

To improve the performance of the software on Linux systems, you must increase the following shell limits for the oracle user, depending on the user's default shell:

Table 1-20 Shell Limits for Linux Systems

Bourne or Bash Shell Limit Korn Shell Limit C or tcsh Shell Limit Hard Limit
nofile nofile descriptors 16384
noproc processes maxproc 16384

To increase the shell limits, do the following:

  1. Add the following lines to the /etc/security/limits.conf file, where the arrow (->) represents the tab character:

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

    session required /lib/security/pam_limits.so
    
    
  3. Depending on the oracle user's default shell, make the following changes to the default shell start-up file:

    • For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:

      if [ $USER = "oracle" ]; then
         if [ $SHELL = "/bin/ksh" ]; then
           ulimit -p 16384
           ulimit -n 16384
         else
           ulimit -u 16384 -n 16384
         fi
      fi
      
      
    • For the C or tcsh shell, add the following lines to the /etc/csh.login file:

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

1.8 Mounting the Installation CD-ROM For UNIX Systems

Refer to these mounting procedures during installation as necessary:

1.8.1 Mounting CD-ROMs For AIX

Mount the disk to begin the installation. Follow these steps to mount the Oracle Database Lite CD-ROM manually:

  1. Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.

  2. Log in as the root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:

    $ su root
    # mkdir cdrom_mount_point_directory
    
    
  3. Determine the CD-ROM device name by entering the following command:

    # lsdev -Cc cdrom
    
    

    The output should be similar to the following:

    cd0 Available 10-60-00-4, 0 SCSI Multimedia CD-ROM Drive
    
    
  4. Mount the CD-ROM drive on the mount point directory by entering the following commands:

    # mount options device_name cdrom_mount_point_directory
    
    
  5. Exit the root account:

    # exit
    
    

Example 1-1 shows how to mount the CD-ROM manually for AIX. In the following example, /dev/cd0 is the CD-ROM device and /cdrom is the mount point.

Example 1-1 Mounting the CD-ROM manually for AIX

$ su root
# mkdir /cdrom
# mount -rv cdrfs /dev/cd0 /cdrom
# exit

Caution:

Do not run the Installer while the CD-ROM directory is the current directory or you will be unable to unmount the current CD-ROM when prompted to do so.

1.8.2 Mounting CD-ROMs For HP

Mount the disk to begin the installation. Follow these steps to mount the Oracle Database Lite CD-ROM manually:

  1. Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.

  2. Log in as the root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:

    $ su root
    # mkdir cdrom_mount_point_directory
    
    
  3. Determine the CD-ROM device name by entering the following command:

    # ioscan -fun -C disk
    
    

    The output should be similar to the following:

    disk  10 10/12/5.2.0  sdisk  CLAIMED  DEVICE  TOSHIBA CD-ROM
    XM-5701TA /dev/dsk/c4t2d0   /dev/rdsk/c4t2d0
    
    
  4. If there is not already an entry in the /etc/pfs_fstab file for your CD-ROM device, you must add one. As the root user, use a text editor to add a line, in the following format, to the /etc/pfs_fstab file:

    device_file mount_point filesystem_type translation_method
    
    

    In the preceding format, the first entry is the CD-ROM device, the second entry is the mount point, and the third entry indicates that the CD-ROM to be mounted is in ISO9660 format with Rockridge extensions.

    The device_file in this example is /dev/dsk/c4t2d0. For a CD-ROM device with the path /dev/dsk/c4t2d0, you would enter the following:

    /dev/dsk/c4t2d0 /SD_CDROM pfs-rrip xlat=unix 1 0
    
    
  5. Log in as the root user with the following command:

    $ su root
    
    
  6. Enter the following commands:

    # nohup /usr/sbin/pfs_mountd &
    # nohup /usr/sbin/pfsd &
    
    
  7. Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive and mount the CD-ROM by entering the following command:

    # /usr/sbin/pfs_mount /SD_CDROM
    
    
  8. Log out of the root account.

    # exit
    
    

Follow these steps to unmount the CD-ROM:

  1. Change to your system's root directory and log in as the root user:

    $ cd /
    $ su root
    
    
  2. To unmount the CD-ROM, enter the following command:

    # /usr/sbin/pfs_umount /SD_CDROM
    
    
  3. Remove the CD-ROM from the CD-ROM drive:

    # /usr/sbin/pfs_umount /SD_CDROM
    
    

1.8.3 Mounting CD-ROMs For Linux

Use the following instructions to mount the CD-ROM for Linux.

1.8.3.1 Mounting CD-ROMs For Linux With Auto Mounting Software

Mount the disk to begin the installation. If you are using auto mounting software, the CD-ROM is mounted automatically to the directory specified in your auto mount configuration when you insert it into the CD-ROM drive.

To check whether you have auto mounting software, enter the following command:

$ ps -aux | grep automount

If you have auto mounting software, the output must be similar to the following:

root 628 0.0 0.2 1148 588 ? S 17:32 0:00 /usr/sbin/automount /misc file /etc/auto.misc

In the preceding output, the /etc/auto.misc section defines the directory under the /misc file where the CD-ROM will be mounted.

  • If the auto mounting software is running and configured properly, the CD-ROM is mounted automatically.

  • If no lines are returned, the auto mounting software is not running, and you will have to mount the CD-ROM manually. Proceed to Section 1.8.3.2.

1.8.3.2 Mounting CD-ROMs For Linux Manually

To mount the Oracle Database Lite CD-ROM manually, use the following steps:

  1. Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.

  2. Log in as the root user and, if necessary, create a CD-ROM mount point directory by using the following commands:

    $ su root
    # mkdir cdrom_mount_point_directory
    
    
  3. Mount the CD-ROM drive on the mount point directory by using the following commands:

    # mount options device_name cdrom_mount_point_directory
    
    
  4. Exit the root account.

    # exit
    
    

    If you are unsure of the correct device name, consult your system administrator. Typically, the device name is /dev/cdrom.

Example 1-2 shows how to mount the CD-ROM manually for Linux.

Example 1-2 Mounting the CD-ROM For Linux Manually

$ su root
# mkdir /cdrom
# mount -t iso9660 /dev/cdrom /cdrom
# exit

Follow these steps to unmount the CD-ROM:

  1. Change directory to the root directory of your system and log in as the root user by using the following commands:

    $ cd /
    $ su root
    
  2. Unmount the CD-ROM by entering the following command:

    # umount cdrom_mount_point_directory
    
    
  3. Remove the CD-ROM from the CD-ROM drive.

1.8.4 Mounting CD-ROMs For Tru64

Follow these steps to mount the Oracle Database Lite CD-ROM manually:

  1. Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.

  2. Log in as the root user and create a CD-ROM mount point directory, if one does not already exist, by using the following commands:

    $ su root
    # mkdir cdrom_mount_point_directory
    
    
  3. Determine the CD-ROM device name by entering the following command:

    $ ls /dev/disk/cdrom*c
    
    

    The command should return a line similar to the following:

    /dev/disk/cdrom0c
    
    
  4. Mount the CD-ROM drive on the mount point directory, by using the following command:

    # mount options device_name cdrom_mount_point_directory
    
    
  5. Exit the root account.

    # exit
    
    

Example 1-3 shows how to mount the CD-ROM manually for Tru64.

Example 1-3 Mounting the CD-ROM For tru64 Manually.

$ su root
# mkdir /cdrom
# mount -t cdfs -r -o nodefperm, noversion, rrip /dev/disk/cdrom0c /cdrom
# exit

Follow these steps to unmount the next CD-ROM:

  1. Change directory to the root directory of your system and log in as the root user by using the following commands:

    $ cd /
    $ su root
    
    
  2. Unmount the CD-ROM by entering the following command:

    # umount cdrom_mount_point_directory
    
    
  3. Remove the CD-ROM from the CD-ROM drive.