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 1.4, "Oracle Components That Work With Oracle Database Lite"
Section 1.9, "Mounting the Installation CD-ROM For UNIX Systems"
For the latest information and patches, refer to OracleMetaLink at the following Web site:
http://metalink.oracle.com
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
The following sections detail the supported components and technologies:
Section 1.3.2, "Certified Application Server Configurations"
Section 1.3.3, "Supported Technologies for the Mobile Server"
Section 1.3.6, "Certified Oracle RDBMS to Use With Oracle Database Lite"
You can install the Mobile Server on the following platforms:
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
Red Hat Enterprise Linux AS/ES 2.1
Red Hat Enterprise Linux Advanced Server 3.0
SUSE 9
Sun SPARC Solaris 2.6, 7.0, 8.0, 9.0
HP-UX 11.0 (64-bit)
HP-UX 11i (11.11) PA-RISC or higher
HP Tru64 UNIX 5.1B with Patch Kit 2 or higher
AIX 5L version 5.2, Maintenance Level 1 or higher
The following lists accepted configuration options with a middle-tier application server:
Standalone Mobile Server, which uses an Embedded OC4J (version 9.0.4) container
OracleAS 10g (9.0.4.0.0), as long as Oracle Database Lite is installed in the same ORACLE_HOME
The following are the versions of the supported technologies used with the Mobile Server of Oracle Database Lite. For certified technologies for the different supported platforms, see sections Section 1.3.7 through Section 1.3.12.
You can only use Internet Explorer 6.0 as the browser for Oracle Database Lite.
Use one of the following database versions with Oracle Database Lite: Oracle 8.1.7.4, Oracle 9.0.1, Oracle 9.2, Oracle 10g Release 1 (10.1.0) and Oracle 10g Release 2 (10.2.0).
The following sections describe the certified and supported platforms and technologies for the Oracle Database Lite Web:
Section 1.3.7.1, "Certified Platforms for Oracle Database Lite Web"
Section 1.3.7.2, "Supported Technologies for Oracle Database Lite Web"
Section 1.3.7.3, "Certified Technologies for Oracle Database Lite Web"
The following platforms are certified for Oracle Database Lite Web:
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
Microsoft Windows XP Tablet PC
You can use the following technologies with Oracle Database Lite Web:
JavaSoft Java Runtime Edition 1.4.2
Java Servlets 2.2
JDBC 1.2
Oracle Java Server Pages Version 9.0.2.0.0
Oracle UIX version 2.1.7
Oracle XML Parser 9.0.3.0.0
Struts version 1.1 is certified for use with Oracle Database Lite Web.
The following sections describe the platforms and technologies for Branch Office:
Microsoft Windows NT 4.0 with Service Pack 6a
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
JavaSoft Java Runtime Edition 1.4.2
Java Servlets 2.2
JDBC 1.2
Oracle Java Server Pages Version 9.0.2.0.0
Oracle UIX version 2.1.7
Oracle XML Parser 9.0.3.0.0
The following sections describe the supported and certified platforms and technologies for BC4J:
Section 1.3.9.1, "Certified Platforms for Oracle Database Lite BC4J"
Section 1.3.9.2, "Supported Technologies for Oracle Database Lite BC4J"
Section 1.3.9.3, "Certified Technologies for Oracle Database Lite BC4J"
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
Microsoft Windows XP Tablet PC
JavaSoft Java Runtime Edition 1.4.2
Java Servlets 2.2
JDBC 1.2
Oracle Java Server Pages Version 9.0.2.0.0
Oracle UIX version 2.1.7
Oracle XML Parser 9.0.3.0.0
The following sections describe the supported and certified technologies for Oracle Database Lite WIN32:
Section 1.3.10.1, "Certified Platforms for Oracle Database Lite WIN32"
Section 1.3.10.2, "Supported Technologies for Oracle Database Lite WIN32"
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
Microsoft Windows XP Tablet PC
JavaSoft Java Runtime Edition 1.4.2
JDBC 1.2
ADO.Net 1.1 – requires Microsoft .Net Framework 1.1
ODBC 2.0, 3.51
SQL92
The following sections describe the supported and certified platforms and technologies for the Oracle Database Lite WinCE:
Section 1.3.11.1, "Supported Platforms for Oracle Database Lite WinCE"
Section 1.3.11.2, "Supported Technologies for Oracle Database Lite WinCE"
Section 1.3.11.3, "Certified Technologies for Oracle Database Lite WinCE"
Table 1-2 provides the full list of supported platforms for Pocket PC:
Table 1-2 Pocket PC Supported Platforms
| Product Name | WinCE Version | Chipsets | Oracle Database Lite Version |
|---|---|---|---|
| Pocket PC 2000 | 3.0.9348 | ARM | Oracle Lite PPC2000 ARM olite.us.pocket_pc.arm.cab |
| Pocket PC 2002 | 3.0.11171 | ARM | Oracle Lite PPC2000 ARM olite.us.pocket_pc.arm.cab |
| Pocket PC 2003 Windows Mobile 2003 | 4.20.1081 | ARM V4 | Oracle Lite PPC2003 ARMV4 olite.us.ppc2003.armv4.cab |
| XScale | Oracle Lite PPC2003 XScale olite.us.ppc2003.xscale.cab | ||
| X86 Emulator | Oracle Lite PPC2003 Emulator olite.us.ppc2003.x86.cab | ||
| WindowsCE .Net 4.2 | 4.20 | olite.us.stdsdk420.armv4.cab | |
| Windows Mobile 2003 2nd Edition | 4.21.1088 | ARM V4 | Oracle Lite PPC2003 ARMV4 olite.us.ppc2003.armv4.cab |
| XScale | Oracle Lite PPC2003 XScale olite.us.ppc2003.xscale.cab | ||
| X86 Emulator | Oracle Lite PPC2003 Emulator olite.us.ppc2003.x86.cab |
ODBC 2.0
ADOCE 1.0 (WinCE 3.0 only)
JDBC 1.2
ADO.Net 1.1 (Requires Microsoft Compact .Net Framework 1.0 + Service Pack 2)
Microsoft ActiveSync version 3.7.1.
Java support: Certified against CrEme 3.24
CrEme 3.24 is based on JavaSoft's PersonalJava Technology specification. This is not a J2ME CDC stack. Currently, the product has not been certified against a CDC stack. J2ME CLDC stack is never supported, as it does not include the required JNI and JDBC support necessary for Oracle Database Lite.
Java Stored Procedures are not supported on Windows CE.
The following sections describe the supported and certified platforms and technologies for Oracle Database Lite PALM:
Section 1.3.12.1, "Certified Platforms for Oracle Database Lite PALM"
Section 1.3.12.2, "Certified Platforms for Oracle Database Lite PALM"
Section 1.3.12.3, "Supported Technologies for Oracle Database Lite PALM"
Palm OS 3.5
Palm OS 4.0
Palm OS 5.x
Palm Desktop 4.1
Mobile Development Kit
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition
Microsoft Windows XP Professional Edition with Service Pack 2
JavaSoft Java Development Kit 1.4.2
Java Servlets 2.2
JDBC 1.2
Oracle Java Server Pages Version 9.0.2.0.0
Oracle UIX version 2.1.7
Oracle XML Parser 9.0.3.0.0
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:
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, which is not installed with Oracle Database Lite—This is the recommended configuration for production environments. If you choose to use the Oracle Application Server 10g (OracleAS) as your middle-tier, then you must install it before installing Oracle Database Lite.
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.
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:
Section 1.5.1, "Hardware Requirements For Your Mobile Clients"
Section 1.5.2, "Software Requirements For Your Mobile Clients"
The hardware requirements for your Mobile Clients are described in the following table:
Table 1-3 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 |
The software requirements for your Mobile Clients are described in the following table:
Table 1-4 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.2 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 Pocket PC/ Windows CE | 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.2 for the Windows operating system. This is constantly under review and published on the JDK download page on the Sun Microsystems Web site.
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:
The hardware requirements for each component of Oracle Database Lite for Windows NT, Windows 2000, or Windows XP are described in the following table:
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-6 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 | When installed on top of Oracle9iAS version 9.0.4 standalone or OracleAS 10g, use JDK 1.4.2 or higher |
| Mobile Development Kit | Windows NT Server 4.0 SP6a, Windows 2000, Windows XP, or Windows 2003 | When installed on top of Oracle9iAS version 9.0.4 standalone or OracleAS 10g, use JDK 1.4.2 or higher |
You should install all of the patches required for the JDK 1.4.2 for the Windows operating system. This is constantly under review and published on the JDK download page on the Sun Microsystems Web site.
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:
Table 1-7 lists the minimum hardware requirements for OracleAS UNIX-based systems.
Table 1-7 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 |
Use the following operating system requirements for installing Oracle Database Lite as a standalone product:
Table 1-8 lists the operating system requirements for Sun SPARC-based systems.
Table 1-9 lists the operating system requirements for AIX-based systems.
Table 1-10 lists the operating system requirements for HP-based systems.
Table 1-12 lists the operating system requirements for Linux-based systems.
Table 1-15 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-8 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-9 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-10 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-11 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-12 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-13 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-14 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-15 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:
HP Tru64 UNIX V5.1BPK2 (BL22 ERP Kit - Fix for multiple applications may be granted an exclusive lock on the same file:
Tru64 UNIX V5.1B PK2/BL22 Early Release Patch - Fix for Potential Application Core Dump:
HP Tru64 UNIX - Problem with IP Multicast Packets:
HP Tru64 UNIX 5.1B PK2 BL22 Fixes for AdvFS Panic in _OtsMove; and Possible Memory Corruption:
|
| 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. |
For all UNIX systems, you must have the JDK installed. When you are installed on top of Oracle9iAS 9.0.4 standalone or OracleAS 10g, install JDK 1.4.2 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.
This section describes the following system configurations for UNIX-based systems:
The following sections describe the environment variables that must be set before starting Oracle Universal Installer:
|
Note: Ensure yourPATH, 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-16 for the name of the library path environment variable for your platform. |
Table 1-16 lists the names of the library path environment variables for each platform.
Table 1-16 Library Path Environment Variable
| Platform | Library Path Environment Variable |
|---|---|
| Tru64, Linux | LD_LIBRARY_PATH |
| HP | SHLIB_PATH and LD_LIBRARY_PATH |
| AIX | LIBPATH |
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.
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 installed on top of Oracle9iAS version 9.0.4 standalone or OracleAS 10g, use JDK 1.4.2 or higher.
Table 1-17 provides examples for the location where the JDK 1.4.2 could be installed on the system.
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 theopmn.xml file. This is a post-installation step that is described in . |
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:
|
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 |
During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the requirements listed in Section 1.7.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 |
The following UNIX account and groups are required for the installation process:
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.
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-18.
Table 1-18 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 useroot as the oracle account. |
Depending on your operating system, see one of the following sections for information on checking the software requirements:
Section 1.8.3.1, "Configuring Shell Limits and System Configuration Parameters on AIX"
Section 1.8.3.3, "Configuring the Kernel Parameters on Linux"
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.
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.
| 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:
Enter the smit command: #smit chuser
In the User Name field, enter the user name of the Oracle software owner, such as oracle.
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.
Press F10 to exit.
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.
Enter the smit command: #smit chgsys
Verify that the value shown for Maximum number of PROCESSES allowed per user is greater than or equal to 2048.
Press F10 to exit.
Ensure that the ARG_MAX setting is set to the maximum value for AIX 5L:
Check the ARG_MAX setting, as follows:
prompt> getconf ARG_MAX
If the value is less than 524288, then run the following command as the root user:
#chdev -l sys0 -a ncargs=128
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.
To view or modify the current value or formula specified for these kernel parameters, do the following:
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
Start System Administration Manager (SAM): #/usr/sbin/sam
Choose the Kernel Configuration area, then choose the Configurable Parameters area.
Check and possibly modify the value or formula specified for each of these parameters.
Exit from SAM.
If you modified the value specified for any parameter, then reboot the system with the following: # /sbin/shutdown -r -now
If necessary, when the system restarts, log in and switch the user to root.
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.
To view or modify the current value specified for these kernel parameters, do the following:
Enter the following command to view the current value of the file-max kernel parameter:
# /sbin/sysctl -a | grep file-max
To modify the value, do the following:
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.
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.
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
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-22 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:
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
Add the following line to the /etc/pam.d/login file, if it does not already exist:
session required /lib/security/pam_limits.so
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
Refer to these mounting procedures during installation as necessary:
Mount the disk to begin the installation. Follow these steps to mount the Oracle Database Lite CD-ROM manually:
Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.
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
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
Mount the CD-ROM drive on the mount point directory by entering the following commands:
# mount options device_name cdrom_mount_point_directory
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. |
Mount the disk to begin the installation. Follow these steps to mount the Oracle Database Lite CD-ROM manually:
Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.
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
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
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
Log in as the root user with the following command:
$ su root
Enter the following commands:
# nohup /usr/sbin/pfs_mountd & # nohup /usr/sbin/pfsd &
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
Log out of the root account.
# exit
Follow these steps to unmount the CD-ROM:
Change to your system's root directory and log in as the root user:
$ cd / $ su root
To unmount the CD-ROM, enter the following command:
# /usr/sbin/pfs_umount /SD_CDROM
Remove the CD-ROM from the CD-ROM drive:
# /usr/sbin/pfs_umount /SD_CDROM
Use the following instructions to mount the CD-ROM for Linux.
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.9.3.2.
To mount the Oracle Database Lite CD-ROM manually, use the following steps:
Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.
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
Mount the CD-ROM drive on the mount point directory by using the following commands:
# mount options device_name cdrom_mount_point_directory
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:
Change directory to the root directory of your system and log in as the root user by using the following commands:
$ cd / $ su root
Unmount the CD-ROM by entering the following command:
# umount cdrom_mount_point_directory
Remove the CD-ROM from the CD-ROM drive.
Follow these steps to mount the Oracle Database Lite CD-ROM manually:
Place the Oracle Database Lite CD-ROM Disk in the CD-ROM drive.
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
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
Mount the CD-ROM drive on the mount point directory, by using the following command:
# mount options device_name cdrom_mount_point_directory
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:
Change directory to the root directory of your system and log in as the root user by using the following commands:
$ cd / $ su root
Unmount the CD-ROM by entering the following command:
# umount cdrom_mount_point_directory
Remove the CD-ROM from the CD-ROM drive.
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.
In order to define where the tablespace is located, you must modify the consolidator_o8a.sql file before you install the Mobile Server. See the "Synchronization Tablespace Layout" section in the Performance chapter of the Oracle Database Lite Administration and Deployment Guide for more information.