Skip Headers

Oracle® Database Lite Getting Started Guide Release 10.3 Part Number E12080-02 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| View PDF

# 3 Requirements Before Installation or Development

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:

- Section 3.1, "Include the Latest Patches"

- Section 3.2, "Release Notes"

- Section 3.3, "Supported Components and Technologies"

- Section 3.4, "Installation Requirements for the Oracle Database and Oracle Application Server in Working With Oracle Database Lite"

- Section 3.5, "System Requirements for Mobile Server on Windows"

- Section 3.6, "System Requirements For UNIX Systems"

- Section 3.7, "Recommended System Configuration For UNIX"

- Section 3.8, "System Requirements for Mobile Clients"

- Section 3.9, "System Requirements for Symbian Devices"

- Section 3.10, "Mounting the Installation CD-ROM For UNIX Systems"

- Section 3.11, "Setting Up Location of the Datafile on the Server"

- Section 3.12, "Defining Synchronization Tablespace"

## 3.1 Include the Latest Patches

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

`http://metalink.oracle.com`

## 3.2 Release Notes

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

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

## 3.3 Supported Components and Technologies

The following sections detail the supported components and technologies:

- Section 3.3.1, "Oracle Universal Installer"

- Section 3.3.2, "Certified Oracle RDBMS to Use With Oracle Database Lite"

- Section 3.3.3, "JDK Platform Support"

- Section 3.3.4, "Certified Application Server Configurations"

- Section 3.3.5, "Certified Versions for OID Support"

- Section 3.3.6, "Certified Platforms and Technologies for the Mobile Server"

- Section 3.3.7, "Certified Browsers"

### 3.3.1 Oracle Universal Installer

The version of the Oracle Universal Installer used is 2.3.0.10.0.

### 3.3.2 Certified Oracle RDBMS to Use With Oracle Database Lite

Use one of the following database versions with Oracle Database Lite: Oracle 9.2, Oracle 10g Release 1 (10.1.0), Oracle 10g Release 2 (10.2.0), or Oracle 11g.

### 3.3.3 JDK Platform Support

For all Mobile clients, use JRE 5.0. For the Mobile Server and Mobile Development Kit, the version required depends on what version of OracleAS 10g you are using.

Table 3-1 JDK Version Supported

OracleAS 10g Version Used | JDK Version Supported
--- | ---
Oracle Database Lite Standalone using OC4J Standalone | JDK 5.0
OracleAS 10g version 10.1.2.0.2 | Use either JDK 1.4.2 or 5.0
OracleAS 10g version 10.1.3.5.0 | JDK 5.0
Oracle WebLogic Suite 11g | JDK 1.6
Oracle WebLogic Server 11g Release 1 | JDK 6.0

I nstall the Sun Microsystems JDK before installing the Mobile Server or Mobile Development Kit. If you need to use JDK 5.0 or 6.0 and you already have JDK 1.4.2 installed, then upgrade to version 5.0 as follows:

1. Uninstall the existing JDK version 1.4.2. If you do not remove this version first, then Mobile Server will continue to use version 1.4.2.

2. Install the appropriate JDK version 5.0 or 6.0. After installation, verify that the JDK `bin` directory is in the system path.

The `JAVA_HOME` environment variable must be set to the directory where the Java Development Kit has been installed. However, the Linux platform requires the JAVA15_HOME environment variable. For more information on JAVA15_HOME, see Section 3.7.1.2, "JAVA15_HOME, JAVA_HOME and PATH" for settting the JAVA environment variables on Linux.

### 3.3.4 Certified Application Server Configurations

The following lists accepted configuration options with a middle-tier application server:

- Standalone Oracle Database Lite, which uses an embedded, standalone OC4J (version 10.1.3) container

- Oracle Application Server 10g (10.1.2.0.2 or 10.1.3.5.0 Web Server), as long as Oracle Database Lite is installed in the same `ORACLE_HOME`

- Oracle WebLogic Server 11g Release 1, as long as Oracle Database Lite is installed in the same `WL_HOME`

### 3.3.5 Certified Versions for OID Support

If you want to use OID with your OracleAS on top of the Mobile Server, then the following shows the support for OID:

- When using OracleAS 10.1.2.0.2, then integration is supported with OID 10.1.2.0.2.

- When using OracleAS 10.1.3.0.x, then integration is NOT supported for OID.

- When using OracleAS 10.1.3.5.0, then integration is supported with OID 10.1.4.

### 3.3.6 Certified Platforms and Technologies for the Mobile Server

You can install the Mobile Server on the following platforms:

- Microsoft Windows Vista Ultimate

- Microsoft Windows XP Professional Edition with Service Pack 2 and 3

- Microsoft Windows 2003 (32 bit)

- Redhat Enterprise Linux Advanced Server 3.0 certified on x86

- Redhat Enterprise Linux Advanced Server 4.0 or 5.0, certified on x86 and AMD64

- Oracle Enterprise Linux 4.0, or 5.0, certified on x86 and AMD64

- SUSE 9, certified on x86 and AMD64

- SUSE 10

- Sun SPARC Solaris 8.0, 9.0, or 10.0

- HP-UX 11.0 (64-bit)

- HP-UX 11i PA-RISC Version 11.11, 11.23 and 11.31

- AIX 5L with either Version 5.2 and Maintenance Level 4 or Version 5.3

- AIX 6.1

The following are the versions of the supported technologies used with the Mobile Server of Oracle Database Lite. For certified technologies for the Mobile client platforms, see Section 3.8, "System Requirements for Mobile Clients".

Table 3-2 Supported Technologies for the Mobile Server

Technology | Standalone | OracleAS 10g (10.1.2) | OracleAS 10g (10.1.3) | Oracle WebLogic Server 11g Release 1
--- | --- | --- | --- | ---
Java Version (JDK and JRE) | 5.0 | 1.4.2 or 5.0 | 5.0 | 6.0
OC4J | 10.1.3.4 | 10.1.2 | 10.1.3 | N/A
Servlet | 2.4 | 2.3 | 2.4 | 2.4
UIX | 2.2.24 | 2.2.15 | 2.2.15 | 2.2.24
XML Parser | 10.1.3.0.0 | 10.1.2.0.0 | 10.1.3.0.0 | 10.1.3.0.0
Oracle JSP | 10.1.3.0.0 | 10.1.2.0.0 | 10.1.3.0.0 | 10.1.3.0.0
Oracle JDBC Driver | 10.1.0.5.0 | 10.1.0.5.0 | 10.1.0.5.0 | 10.1.0.5.0

### 3.3.7 Certified Browsers

Internet Explorer 6.0 and Mozilla 1.7.x are certified as browsers for Oracle Database Lite.

## 3.4 Installation Requirements for the Oracle Database and Oracle Application Server in Working With Oracle Database Lite

The following sections describe installation requirements for the Oracle Database and Oracle Application Server:

- Section 3.4.1, "Installation Requirements for the Oracle Database for Working With a Mobile Client"

- Section 3.4.2, "Installation Requirements for Using the Oracle Application Server With Oracle Database Lite"

### 3.4.1 Installation Requirements for the Oracle Database for Working With a Mobile Client

When you synchronize the Mobile client, your changes are updated in an Oracle back-end database. Thus, you must have either the Standard or Enterprise Edition Oracle database to use the synchronization ability of Oracle Database Lite.

### 3.4.2 Installation Requirements for Using the Oracle Application Server With Oracle Database Lite

Oracle Database Lite uses a middle-tier to communicate between the Mobile clients and the back-end Oracle database. Use one of the following as the middle-tier:

- Oracle Database Lite in standalone mode, which is automatically installed with Oracle Database Lite—This is the recommended configuration for development environments. Oracle Database Lite in standalone mode uses the standalone version of Oracle Containers for J2EE (OC4J).

- Oracle Application Server 10g or Oracle WebLogic Server 11g, which are not installed with Oracle Database Lite—These are recommended for production environments. If you choose to use the Oracle Application Server 10g (OracleAS) or the Oracle WebLogic Server 11g as your middle-tier, then you must install it before installing Oracle Database Lite.

When you are installing the Oracle Application Server (OracleAS) or Oracle WebLogic Server in preparation for using Oracle Database Lite, you must perform certain tasks, as described in the following sections:

- Section 3.4.2.1, "Installing OracleAS Version 10.1.2"

- Section 3.4.2.2, "Installing OracleAS Version 10.1.3"

- Section 3.4.2.3, "Installing Oracle WebLogic Server 11g Release 1"

Note:

For more information about how Oracle Database Lite works with the middle-tier and the back-end database, see Chapter 1, "Overview" in the Oracle Database Lite Developer's Guide.

#### 3.4.2.1 Installing OracleAS Version 10.1.2

When installing OracleAS, choose the Integrated Web and J2EE Server installation option.

Perform the following when installing the OracleAS version 10.1.2:

1. On the `Select a product to install` screen, select Oracle Application Server.

2. On the `What type of install do you want?` screen, select the J2EE and Web Cache option from the following options:

   - J2EE and Web Cache

   - Portal and Wireless

   - Business Intelligence and Forms

#### 3.4.2.2 Installing OracleAS Version 10.1.3

When installing OracleAS, choose the Integrated Web and J2EE Server installation option.

In the OracleAS version 10.1.3 install, choose the Advanced Installation Mode. In the second screen, you will see the following options:

1. J2EE Server and Process Management

2. Web Server and Process Management

3. Integrated Web Server, J2EE Server and Process Management

4. Oracle Toplink

Select ONLY option 3, the Integrated Web Server, J2EE Server and Process Management. This option provides all of the functionality that you need. Do not select any of the other options, as then your OracleAS installation will be missing functionality that is necessary for Oracle Database Lite.

#### 3.4.2.3 Installing Oracle WebLogic Server 11g Release 1

Install the Oracle WebLogic Server 11g Release 1 (10.3.2). Before installing Oracle Database Lite, set `ORACLE_HOME` to `WL_HOME`.

## 3.5 System Requirements for Mobile Server on Windows

Before you install the Mobile Server, 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:

- Section 3.5.1, "Hardware Requirements For Windows"

- Section 3.5.2, "Software Requirements For Windows"

- Section 3.5.3, "Defining Password for OracleDatabaseLite User for Branch Office on Windows Machine"

### 3.5.1 Hardware Requirements For Windows

The hardware requirements for each component of Oracle Database Lite for Windows are described in the following table:

Table 3-3 Hardware Requirements for Windows

Component | Hardware Requirements for this Component
--- | ---
Mobile Server Standalone | CPU: Pentium 4, 3 MHz Disk Space: 1 GB RAM: 1 GB Swap Space: 1535 MB
Mobile Server using OracleAS | See the OracleAS documentation for the OC4J container requirements. Swap Space: 1535 MB
Mobile Server using Oracle WebLogic Server | See the "Oracle Fusion Middleware System Requirements and Specifications 11g Release 1" document in the Oracle Fusion Middleware documentation.
Mobile Development Kit | CPU: Pentium 4, 3 MHz Disk Space: 512 MB RAM: 512 MB Swap Space: 1535 MB

Note:

The requirements for Mobile Server is related to the number of users synchronizing and the amount of data transferred.

### 3.5.2 Software Requirements For Windows

The software requirements for each component of Oracle Database Lite for Windows are described in the following table:

Table 3-4 Software Requirements for Windows

Component | Operating System | Other Software Requirements
--- | --- | ---
Mobile Server | Windows Vista Ultimate, Windows XP, or Windows 2003 | For the appropriate JDK version, see Section 3.3.3, "JDK Platform Support".
Mobile Development Kit | Windows Vista Ultimate, Windows XP, or Windows 2003 | For the appropriate JDK version, see Section 3.3.3, "JDK Platform Support".

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

### 3.5.3 Defining Password for OracleDatabaseLite User for Branch Office on Windows Machine

When you install the Branch Office Manager on the Windows machine, it creates the `OracleDatabaseLite` user account with the minimum set of privileges required to execute the Oracle Database Lite software. This prevents Oracle Database Lite Branch Office executing under the `SYSTEM` account, which has broad privileges within the system and can make the system vulnerable.

Both the 'Oracle Lite Multiuser Service' is created as well as the normal Web-to-Go service executes under the privileges of the `OracleDatabaseLite` user. The Oracle Lite Multiuser Server enables remote clients to connect to the Oracle Lite database.

Normally, when installed, the password for the `OracleDatabaseLite` user is randomly generated during the setup. You can either pre-configure this password before the Branch Office installation or modify it after the configuration using one of the following methods:

- Section 3.5.3.1, "Pre-Configuring OracleDatabaseLite User Password Before Branch Office Installation"

- Section 3.5.3.2, "Modifying Existing OracleDatabaseLite User Password After Branch Office Installation"

#### 3.5.3.1 Pre-Configuring OracleDatabaseLite User Password Before Branch Office Installation

To pre-configure the `OracleDatabaseLite` user password, modify the password attribute in the `BOS.INF` file located in the `<ORACLE_HOME>``\mobile_oc4j\j2ee\mobileserver\applications\mobileserver\setup\dmc` directory on the Mobile Server, which is as follows:

    <user name='OracleDatabaseLite' password='aaaa'>
     <file>$OS_DIR$\odbc.ini</file>
     <file>$OS_DIR$\polite.ini</file>
     <registry>MACHINE\SOFTWARE\ODBC\ODBCINST.INI</registry>
    </user>

#### 3.5.3.2 Modifying Existing OracleDatabaseLite User Password After Branch Office Installation

To modify the password of an existing Branch Office installation, perform the following on the Branch Office Windows machine:

1. Modify the password with the Computer Management MMC console, which you can bring up with Control Panel->Administrative Tools-> Computer Management.

2. Set the new password in the Oracle Lite service using the Windows Service control panel.

## 3.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:

- Section 3.6.1, "System Requirements For Linux"

- Section 3.6.2, "System Requirements For Sun SPARC-Based Systems"

- Section 3.6.3, "System Requirements For AIX-Based Systems"

- Section 3.6.4, "System Requirements For HP-Based Systems"

- Section 3.6.5, "Software Requirements For All UNIX Systems"

### 3.6.1 System Requirements For Linux

Table 3-5 lists the minimum hardware requirements for OracleAS Linux-based systems.

Table 3-5 Minimum Hardware Requirements for UNIX Systems

Item | Requirement
--- | ---
Linux | 3 GHz, 1 GB RAM
Disk space for Linux | 1 GB
display | 256 color display
Memory | 512 MB
TMP or swap space | 1 GB

For the operating system, you can use the following Linux operating systems:

- Redhat Enterprise Linux Advanced Server 3.0 certified on x86

- Redhat Enterprise Linux Advanced Server 4.0 or 5.0, certified on x86 and AMD64

- Oracle Enterprise Linux 4.0, or 5.0, certified on x86 and AMD64

Use the following requirements when installing Oracle Database Lite on the Redhat Enterprise Linux AS operating system:

Table 3-6 Operating System Requirements for Redhat Enterprise Linux AS

Item | Requirement
--- | ---
Operating System | For the Mobile Server, you can use Redhat Enterprise Linux Advanced Server version 3, 4 or 5. For using the MDK, you must use version 4. 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

Note:

There are no additional requirements for Redhat Linux 4.0, 5.0 or Suse 9.

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

    http://metalink.oracle.com

### 3.6.2 System Requirements For Sun SPARC-Based Systems

Table 3-7 lists the minimum hardware requirements for OracleAS Sun SPARC-based systems.

Table 3-7 Minimum Hardware Requirements for UNIX Systems

Item | Requirement
--- | ---
Sun SPARC | Sun SPARC Ultra 1 or higher, 300 MHz or better
Disk space for Sun SPARC | 1 GB
Memory | 512 MB
TMP or swap space | 1 GB
display | 256 color display

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

Table 3-8 Operating System Requirements for Sun SPARC-Based Systems

Item | Requirement
--- | ---
Operating System | Sun Solaris 8.0, 9.0, or 10.0
Window Manager | Use any supported Sun Solaris window manager that supports Motif.

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

    http://metalink.oracle.com

### 3.6.3 System Requirements For AIX-Based Systems

Table 3-9 lists the minimum hardware requirements for OracleAS AIX-based systems.

Table 3-9 Minimum Hardware Requirements for UNIX Systems

Item | Requirement
--- | ---
AIX | All AIX-compatible processors (64-bit)
Disk space for AIX | 1 GB
Memory | 512 MB
TMP or swap space | 1 GB
display | 256 color display

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

Table 3-10 Operating System Requirements for AIX-Based Systems

Item | Requirement
--- | ---
Operating System | One of the following AIX versions: AIX 5L with either version 5.2 including Maintenance Level 4 or version 5.3. AIX 6.1
Window Manager | Use any supported IBM AIX window manager that supports Motif, such as `dtwm`, `twm`, and `olwm`.

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

    http://metalink.oracle.com

### 3.6.4 System Requirements For HP-Based Systems

Table 3-11 lists the minimum hardware requirements for OracleAS HP-based systems.

Table 3-11 Minimum Hardware Requirements for UNIX Systems

Item | Requirement
--- | ---
HP | HP 9000 Series HP-UX processor for HP-UX 11.0 (64-bit)
Disk space for HP | 1 GB
Memory | 512 MB
TMP or swap space | 1 GB
display | 256 color display

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

Table 3-12 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 3-13 Operating System Requirements for HP-Based Systems

Item | Requirement
--- | ---
Operating System | HP-UX 11i PA-RISC Version 11.11, 11.23 and 11.31
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`.

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

    http://metalink.oracle.com

### 3.6.5 Software Requirements For All UNIX Systems

For all UNIX systems, you must have the JDK installed. See Section 3.3.3, "JDK Platform Support" for the versions supported.

## 3.7 Recommended System Configuration For UNIX

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

- Section 3.7.1, "Setting UNIX Environment Variables"

- Section 3.7.2, "Pre-Install Requirements Before Installing the MDK on LINUX"

- Section 3.7.3, "Creating UNIX Accounts and Groups"

- Section 3.7.4, "Configuring Kernel Parameters and Shell Limits for UNIX"

### 3.7.1 Setting UNIX Environment Variables

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

- Section 3.7.1.1, "ORACLE_HOME"

- Section 3.7.1.2, "JAVA15_HOME, JAVA_HOME and PATH"

- Section 3.7.1.3, "DISPLAY"

- Section 3.7.1.4, "TMP and TMPDIR"

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 3-14 for the name of the library path environment variable for your platform.

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

Table 3-14 Library Path Environment Variable

Platform | Library Path Environment Variable
--- | ---
Linux | LD_LIBRARY_PATH
HP | SHLIB_PATH and LD_LIBRARY_PATH
AIX | LIBPATH

#### 3.7.1.1 ORACLE_HOME

The Oracle Home directory is the `root` directory in which Oracle software is installed. The `CLASSPATH` contains the entire path you enter for `ORACLE_HOME`; thus, the length of `ORACLE_HOME` effects the length of the `CLASSPATH`. 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.

#### 3.7.1.2 JAVA15_HOME, JAVA_HOME and PATH

The Linux platform requires the `JAVA15_HOME` environment variable 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. For the appropriate JDK version, see Section 3.3.3, "JDK Platform Support".

Before installation of a Linux Mobile Server and the Linux MDK, set `JAVA15_HOME` to the JDK 1.5 home directory. When executing a Linux Mobile Server in standalone mode, set `JAVA15_HOME` to the JDK 1.5 or JDK 1.6 home directory.

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

Table 3-15 JAVA_HOME Environment Variables

Platform | Sample JAVA_HOME Environment Variable
--- | ---
HP | `/opt/java1.5`
AIX | `/usr/java151`

Initialize the JAVA_HOME and PATH environment variables, as follows:

    export JAVA_HOME=$JAVA15_HOME
    export PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin:$PATH

#### 3.7.1.3 DISPLAY

Set the `DISPLAY` environment variable to refer to the X Server that will display the installer and Oracle Database Lite. 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

Note:

In order for the Oracle Database Lite to install correctly, you must add a line to the `opmn.xml` file. This is a post-installation step that is described in Section 4.4.2, "Setup DISPLAY Variable for UNIX Systems in Oracle Application Server".

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

##### 3.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 Host Machine Where the Installer is Running | In the Session on Your Host
--- | --- | ---
C Shell | prompt> setenv DISPLAY <hostname>:0.0 | prompt> xhost +<hostname>
Bourne/Korn Shell | prompt> DISPLAY=<hostname>:0.0;export DISPLAY | prompt> xhost +<hostname>

#### 3.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 3.6, "System 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`

### 3.7.2 Pre-Install Requirements Before Installing the MDK on LINUX

Of all of the UNIX platforms, the MDK is only supported on the Linux platform. But before installing the MDK on your Linux system, modify the following environment variables:

Table 3-16 Linux Environment Variable

Linux Environment Variable | Description
--- | ---
`JDKDIR` | Point to the JDK installation directory
`OLITE_HOME` | `$ORACLE_HOME/mobile/sdk`
`LD_LIBRARY_PATH` | `/usr/lib:$JDKDIR/jre/lib/i386:$JDKDIR/jre/lib/i386/server:$OLITE_HOME/lib:$LD_LIBRARY_PATH`
`CLASSPATH` | `.:$ORACLE_HOME/mobile/sdk/bin/olite40.jar`
`PATH` | `$JDKDIR/bin:$OLITE_HOME/bin:$PATH`

### 3.7.3 Creating UNIX Accounts and Groups

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

- Section 3.7.3.1, "UNIX Group Name For the Oracle Universal Installer Inventory"

- Section 3.7.3.2, "UNIX Account to Own Oracle Software"

#### 3.7.3.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 and `dba` as its secondary group.

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

#### 3.7.3.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 3-17.

Table 3-17 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.

### 3.7.4 Configuring Kernel Parameters and Shell Limits for UNIX

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

- Section 3.7.4.1, "Configuring Shell Limits and System Configuration Parameters on AIX"

- Section 3.7.4.2, "Configuring Kernel Parameters on HP-UX"

- Section 3.7.4.3, "Configuring the Kernel Parameters on Linux"

- Section 3.7.4.4, "Set Shell Limits for the User oracle"

#### 3.7.4.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.

##### 3.7.4.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 3-18 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.

##### 3.7.4.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

#### 3.7.4.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 3-19 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`.

#### 3.7.4.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 3-20 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

#### 3.7.4.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 3-21 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

## 3.8 System Requirements for Mobile Clients

The system requirements for either Mobile client, the SQLite database or the Oracle Lite database, are covered in each of the client guides. For the Oracle Lite Mobile client, see Chapter 1, "System Requirements for the Oracle Lite Database" in the Oracle Database Lite Client Guide. For the SQLite Mobile Client, see Chapter 1, "Installing the SQLite Mobile Client" in the Oracle Database Lite SQLite Mobile Client Guide.

## 3.9 System Requirements for Symbian Devices

If you are preparing to use Symbian devices in your Oracle Database Lite solution, then see Chapter 14, "Using Symbian Devices" in the Oracle Database Lite Developer's Guide for full details on requirements, installation, administration and development for the Symbian platform.

## 3.10 Mounting the Installation CD-ROM For UNIX Systems

Refer to these mounting procedures during installation as necessary:

- Section 3.10.1, "Mounting CD-ROMs For AIX"

- Section 3.10.2, "Mounting CD-ROMs For HP "

- Section 3.10.3, "Mounting CD-ROMs For Linux"

### 3.10.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 3-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 3-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.

### 3.10.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

### 3.10.3 Mounting CD-ROMs For Linux

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

- Section 3.10.3.1, "Mounting CD-ROMs For Linux With Auto Mounting Software"

- Section 3.10.3.2, "Mounting CD-ROMs For Linux Manually"

#### 3.10.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 3.10.3.2.

#### 3.10.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 3-2 shows how to mount the CD-ROM manually for Linux.

Example 3-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.

## 3.11 Setting Up Location of the Datafile on the Server

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 data files in the `db_create_file_dest` parameter. 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.

## 3.12 Defining Synchronization Tablespace

By default, the synchronization tablespace is `SYNCSERVER`, and is stored in the `mobile` `xx``.dbf` file in the default location for the database under `ORACLE_HOME`, where `xx` is a number between 1 and 25. The tablespace name, filename, and file location for the tablespace is defined in the `$ORACLE_HOME/Mobile/Server/admin/consolidator_o8a.sql` script file, which is executed during the Mobile Server installation process. So, if you want to modify the tablespace, there are a few tasks you need to perform BEFORE you install the Mobile Server.

Tablespace layout across multiple disks can improve the performance of Mobile Server data synchronization, as it reduces movement of the disk heads and improves I/O response time.

For full details on how to alter the synchronization tablespace, see Section 1.2.6, "Synchronization Tablespace Layout" in the Oracle Database Lite Troubleshooting and Tuning Guide for more information.