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.4, "Oracle Components That Work With Oracle Database Lite"
Section 3.5, "System Requirements for Mobile Server on Windows"
Section 3.8, "System Requirements For Windows Mobile Clients"
Section 3.11, "Mounting the Installation CD-ROM For UNIX Systems"
Section 3.12, "Setting Up Location of the Datafile on the Server"
For the latest information and patches, refer to Oracle MetaLink 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 3.3.2, "Certified Oracle RDBMS to Use With Oracle Database Lite"
Section 3.3.4, "Certified Application Server Configurations and OID Support"
Section 3.3.5, "Certified Platforms and Technologies for the Mobile Server"
The version of the Oracle Universal Installer used is 2.3.0.10.0.
Use one of the following database versions with Oracle Database Lite: Oracle 9.2, Oracle 10g Release 1 (10.1.0) and Oracle 10g Release 2 (10.2.0).
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 |
Use either JDK 1.4.2 or 5.0 |
OracleAS 10g version 10.1.3 |
JDK 5.0 |
Install the Sun Microsystems JDK before installing the Mobile Server or Mobile Development Kit. If you need to use JDK 5.0 and you already have JDK 1.4.2 installed, then upgrade to version 5.0 as follows:
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.
Install the new JDK version 5.0. After installation, verify that the JDK 5.0 bin
directory is in the system path. For Linux/UNIX platforms, verify that the JAVA13_HOME
environment variable points to the JDK 5.0 home directory.
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 or 10.1.3), as long as Oracle Database Lite is installed in the same ORACLE_HOME
If you want to use OID with your Oracle AS on top of the Mobile Server, then the following shows the support for OID:
When you use Oracle AS version 10.1.3.1.0, then integration with OID/SSO with AS 10.1.4 infrastructure is supported.
When you use Oracle AS version 10.1.3.0.x, then integration with OID/SSO is not supported.
When you use Oracle AS version 10.1.2.0.2 , then integration with OID 10.1.2.0.2 is supported.
You can install the Mobile Server on the following platforms:
Microsoft Windows 2000 Professional Edition with Service Pack 4
Microsoft Windows XP Professional Edition with Service Pack 2
Microsoft Windows 2003 (32 bit)
Redhat Enterprise Linux Advanced Server 3.0 or 4.0, certified on x86 and AMD64
SUSE 9, certified on x86 and AMD64
Sun SPARC Solaris 8.0, 9.0, or 10.0
HP-UX 11.0 (64-bit)
HP-UX 11i PA-RISC Version 11.11 and 11.23
AIX 5L with either Version 5.2 and Maintenance Level 4 or Version 5.3
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.2, "Software Requirements For Windows Mobile Clients".
Table 3-2 Supported Technologies for the Mobile Server
Technology | Standalone | OracleAS 10g (10.1.2) | OracleAS 10g (10.1.3) |
---|---|---|---|
Java Version (JDK and JRE) |
5.0 |
1.4.2 or 5.0 |
5.0 |
OC4J |
10.1.3 |
10.1.2 |
10.1.3 |
Servlet |
2.4 |
2.3 |
2.4 |
UIX |
2.2.15 |
2.2.15 |
2.2.15 |
XML Parser |
9.0.3.0.0 |
9.0.3.0.0 |
9.0.3.0.0 |
Oracle JSP |
10.1.3.0.0 |
10.1.2.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 |
Internet Explorer 6.0 and Mozilla 1.7.x are certified as browsers for Oracle Database Lite.
When you synchronize the 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.
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.
When you are installing the Oracle Application Server (OracleAS) in preparation for using Oracle Database Lite, you must choose the Integrated Web and J2EE Server installation option, as follows:
In the OracleAS install, choose the Advanced Installation Mode. In the second screen you will see the following options:
J2EE Server and Process Management
Web Server and Process Management
Integrated Web Server, J2EE Server and Process Management
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.
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.
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:
The hardware requirements for each component of Oracle Database Lite for Windows 2000, Windows XP, or Windows 2003 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 GHz Disk Space: 1 GB RAM: 1 GB |
Mobile Server using OracleAS |
See the OracleAS documentation for the OC4J container requirements. |
Mobile Development Kit |
CPU: Pentium 4, 3 GHz Disk Space: 512 MB RAM: 512 MB |
Note:
The requirements for Mobile Server is related to the number of users synchronizing and the amount of data transferred.The software requirements for each component of Oracle Database Lite for Windows 2000, Windows XP, or Windows 2003 are described in the following table:
Table 3-4 Software Requirements for Windows
Component | Operating System | Other Software Requirements |
---|---|---|
Mobile Server |
Windows 2000, Windows XP, or Windows 2003 |
For the appropriate JDK version, see Section 3.3.3, "JDK Platform Support". |
Mobile Development Kit |
Windows 2000, 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.
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:
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>
To modify the password of an existing Branch Office installation, perform the following on the Branch Office Windows machine:
Modify the password with the Computer Management MMC console, which you can bring up with Control Panel->Administrative Tools-> Computer Management.
Set the new password in the Oracle Lite service using the Windows Service control panel.
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 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 |
The following is the minimum hardware requirements for OracleAS Linux-based systems. Use the following operating system requirements for installing Oracle Database Lite as a standalone product:
Table 3-6 Operating System Requirements for Redhat Enterprise Linux AS 3.0
Item | Requirement |
---|---|
Operating System |
Redhat 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 |
Note:
There are no additional requirements for Redhat Linux 4.0 or Suse 9.For the latest information on operating system requirements, refer to OracleMetaLink at the following Web site:
http://metalink.oracle.com
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
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 |
AIX 5L with either version 5.2 including Maintenance Level 4 or version 5.3 |
Window Manager |
Use any supported IBM AIX window manager that supports Motif, such as |
For the latest information on operating system requirements, refer to OracleMetaLink at the following Web site:
http://metalink.oracle.com
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 |
Table 3-13 Operating System Requirements for HP-Based Systems
Item | Requirement |
---|---|
Operating System |
HP-UX 11i PA-RISC Version 11.11 and 11.23 |
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 |
For the latest information on operating system requirements, refer to OracleMetaLink at the following Web site:
http://metalink.oracle.com
For all UNIX systems, you must have the JDK installed. See Section 3.3.3, "JDK Platform Support" for the versions supported.
This section describes the following system configurations for UNIX-based systems:
Section 3.7.2, "Pre-Install Requirements Before Installing the MDK on LINUX"
Section 3.7.4, "Configuring Kernel Parameters and Shell Limits for UNIX"
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 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 |
|
HP |
|
AIX |
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.
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. For the appropriate JDK version, see Section 3.3.3, "JDK Platform Support".
Table 3-15 provides examples for the location where the JDK could be installed on the system.
Initialize these environment variables, as follows:
export JAVA_HOME=$JAVA13_HOME export PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin:$PATH
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 Section 4.4.1, "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".
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> |
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 |
Of all of the UNIX platforms, the MDK is only support 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 |
---|---|
|
Point to the JDK installation directory |
|
|
|
|
|
|
|
|
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 and dba
as its secondary 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 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 |
Group Identifier |
The |
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 3.7.4.1, "Configuring Shell Limits and System Configuration Parameters on AIX"
Section 3.7.4.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 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:
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
Before you install, you must check to see that you have the correct hardware and software necessary for Windows Mobile Clients. The requirements for both are detailed in the following sections:
Section 3.8.1, "Hardware Requirements For Windows Mobile Clients"
Section 3.8.2, "Software Requirements For Windows Mobile Clients"
The hardware requirements for Windows Mobile Clients are described in the following table:
Table 3-22 Hardware Requirements for Mobile Clients
Component | Hardware Requirements for this Component |
---|---|
Mobile Client for Win32 |
CPU: Pentium 4, 1 GB Disk Space: 30 MB RAM: 256 MB |
Mobile Client for Web-to-Go |
CPU: Pentium 4, 1 GB Disk Space: 70 MB RAM: 512 MB |
Mobile Client for Windows CE/Windows Mobile |
CPU: ARM-based processor or Emulator Storage Space: 8 MB Free program memory: 16 MB It matters what external memory media and file system you use. See Section 3.8.1.1, "What File System and External Memory Media Should You Use for Windows CE?" for more information. |
Branch Office |
CPU: Pentium 4, 1 GB Disk Space: 70 MB RAM: 512 MB |
When you are using a WinCE device, you will probably use some form of external memory media, such as Compact Flash or SD cards. Of these two, the SD card is more reliable in its method of connecting into the device. We have seen some issues of database corruption when using Compact Flash cards, since the card can be removed in the middle of a write without notice.
When you do choose a media, you can also decide on the type of file system you use. We strongly recommend that you use the Transaction-Safe FAT (TFAT) file system over the FAT system, which is the default and more widely used. FAT has some unreliability that was not noticeable in a laptop or desktop situation. However, this unreliability in its ability to flush its buffers fully when writing out to the removable memory does not handle well when the media is removed in the middle of the transaction. Thus, the shortcomings of the FAT file system is being seen more in the WinCE environment with removable memory. The TFAT design provides transaction-safety for data storage. That is, the data that is being written out to the removable media is either completely committed or rolled-back. Thus, the TFAT file system is highly recommended for any removable data—especially for the Oracle Lite database. There is a performance consideration for using the TFAT file system. It is slower than FAT, but also more reliable.
You need to decide whether performance or reliability is your priority. The following is the order of reliability with 1 being the least reliable and 3 being the most reliable:
Compact Flash media with the FAT file system.
SD card media with the FAT file system.
Compact Flash or SD card media with the TFAT file system.
Note:
See the Microsoft Web site for information on how to create the TFAT file system.The software requirements for Windows Mobile Clients are described in the following sections:
Section 3.8.2.1, "Certified Operating Systems and Other Software Requirements"
Section 3.8.2.2, "Supported and Certified Technologies for Windows Mobile Clients"
Section 3.8.2.3, "Supported Platforms for Oracle Database Lite WinCE"
Table 3-23 Software Requirements for Windows Mobile Clients
Mobile Client | Certified Operating System | Other Software Requirements |
---|---|---|
Mobile Client for Win32 |
Windows 2000 Professional Edition with Service Pack 4, Windows XP Professional Edition with Service Pack 2, Windows 2003, or Microsoft Windows XP Tablet PC |
If using any Java APIs, including synchronization or JDBC, use JRE 5.0 If implementing any .NET applications, use Compact Framework .NET 1.1 or 2.0 |
Mobile Client for Web-to-Go |
Windows 2000 Professional Edition with Service Pack 4, Windows XP Professional Edition with Service Pack 2, Windows 2003, or Microsoft Windows XP Tablet PC |
|
Mobile Client for Windows CE |
Windows CE 5.0 See Section 3.8.2.3, "Supported Platforms for Oracle Database Lite WinCE" for full details. |
If using JDBC, use either IBMJ9 or the CrEme JDK version 4.1 from ActiveSync version 3.8 or later. Microsoft .NET Compact Framework 1.0 |
Mobile Client for Windows Mobile |
Windows Mobile 2003 Windows Pocket PC 2003 Windows Mobile 2003, 2nd edition Windows Pocket PC 2003, 2nd edition See Section 3.8.2.3, "Supported Platforms for Oracle Database Lite WinCE" for full details. |
ActiveSync version 3.8 or higher. Microsoft .NET Compact Framework 1.1 If using JDBC, use either IBMJ9 or the CrEme JDK version 4.1 from |
Windows Mobile 5.0 |
ActiveSync version 4.1 or higher. Microsoft .NET Compact Framework 1.1 or 2.0 If using JDBC, use either IBMJ9 or the CrEme JDK version 4.1 from |
|
OC4J |
Windows 2000 Professional Edition with Service Pack 4, Windows XP Professional Edition with Service Pack 2, Windows 2003, or Microsoft Windows XP Tablet PC |
|
Branch Office |
Windows 2000 Professional Edition with Service Pack 4, Windows XP Professional Edition with Service Pack 2, Windows 2003, or Microsoft Windows XP Tablet PC |
You should install all of the patches required for the JDK for the Windows operating system. This is constantly under review and published on the JDK download page on the Sun Microsystems Web site.
The following are the supported and certified technologies for Mobile clients:
Table 3-24 Supported and Certified Technologies for Windows Mobile Clients
Mobile Client | Supported Technologies | Certified Technologies |
---|---|---|
Mobile Client for Win32 |
|
|
Mobile Client for Web-to-Go |
|
Struts version 1.1 is certified for use with Oracle Database Lite Web-to-Go. |
Mobile Client for Windows CE |
|
Oracle Database Lite is certified with the following JVMs on Windows Mobile 2003 Second Edition:
NOTE: Java Stored Procedures are not supported on Windows CE. |
OC4J |
|
|
Branch Office |
Struts version 1.1 |
Table 3-25 provides the full list of supported platforms for Pocket PC and Windows Mobile:
Table 3-25 Pocket PC and Windows Mobile Supported Platforms
Product Name | WinCE Version | Chipsets | Oracle Lite Client CAB file download from Setup page |
---|---|---|---|
Pocket PC 2003 Windows Mobile 2003 |
4.20.1081 |
ARMV4 |
Oracle Lite PPC2003 ARMV4, which uses the |
Windows Mobile 2003 2nd Edition |
4.21.1088 |
ARMV4 |
Oracle Lite PPC2003 ARMV4, which uses the |
Windows Mobile 5 |
5.0 |
ARMV4I |
Oracle Lite PPC50 ARMV4I, which uses the |
If you wish to use the SDK CAB files, which are included in the MDK, for the JAVA, MSQL and utilties, then you can install the client SDK CAB files, which are listed below. See Section 5.2.2, "Use SDK CAB Files for Client Install for Java, MSQL, and Utility Support" for full details.
Table 3-26 Pocket PC and Windows Mobile Supported Platforms
Product Name | WinCE Version | Chipsets | Client CAB file available from MDK |
---|---|---|---|
Windows Mobile 2003 |
4.20.1081 |
ARMV4 |
|
Windows Mobile 2003, 2nd edition |
4.21.1088 |
ARMV4 |
|
Windows Mobile 5 |
5.0 |
ARMV4I |
|
Windows CE Standard SDK 5.0 Edition |
5.0 |
ARMV4I |
|
X86 |
|
For Mobile Client Web-to-Go, Win32, Branch Office and BC4J:
Internet Explorer 6.0 is required when using SSL to synchronize with the Mobile Server.
The product requires the Microsoft C Runtime Library 7.1 (msvcrt71.dll
), which you can download off the Microsoft site or other sites on the Web.
The Mobile Server installation includes the following Mobile Clients for Linux:
Mobile Client for Linux x86
Mobile Client for Linux Web-to-Go
Note:
The Device Manager agent (DMagent
) must be running to successfully uninstall the Linux Client.Before you install, you must check to see that you have the requirements necessary for Linux Mobile Clients. The requirements for both are detailed in the following sections:
Section 3.9.1, "Certified Platforms and Supported Technologies for Linux Mobile Clients"
Section 3.9.2, "Software and Hardware Requirements for Linux Mobile Clients"
Section 3.9.3, "Setting Environment Variables Before Installing the Linux Mobile Client"
Table 3-27 provides the full list of certified and supported platforms for Linux Mobile clients:
Table 3-27 Certified Platforms and Supported Technologies for Linux Mobile Clients
Mobile Client | Certified Platforms | Supported Technologies |
---|---|---|
Oracle Lite Linux Web |
Red Hat Enterprise Linux AS release 4 |
|
Oracle Lite Linux x86 |
Red Hat Enterprise Linux AS release 4 |
|
Note for Oracle Lite Linux WEB: Mozilla version 1.7.x is the preferred internet browser on Linux.
Table 3-28 provides the software and hardware requirements for Linux Mobile clients:
Table 3-28 Software and Hardware Requirements for Linux Mobile Clients
Mobile Client | Hardware Requirement | Software Requirements |
---|---|---|
Mobile Client for Linux Web-to-Go |
CPU: Pentium III 360 MHz Disk Space: 40 MB RAM: 128 MB |
Red Hat Enterprise Linux AS R4 JDK 1.4.2 |
Mobile Client for Linux x86 |
CPU: Pentium III 360 MHz Disk Space: 30 MB RAM: 128 MB |
Red Hat Enterprise Linux AS R4 JDK 1.4.2 |
Set the following environment variables:
Set OLITE_HOME
to where Oracle Database Lite is installed, such as /home/<user>/olite
Set JAVA_HOME
to the Java installation directory
Add the following to the LD_LIBRARY_PATH
$JAVA_HOME/jre/lib/i386 $JAVA_HOME/jre/lib/i386/server $OLITE_HOME/bin
Add $OLITE_HOME/bin
to the PATH
This section details requirements if you are preparing to use Symbian devices in your Oracle Database Lite solution. Your development environment must include Oracle Database Lite 10g as the encompassing platform. For developing native applications with Oracle Database Lite 10g on a Symbian platform, the following devices are supported:
The following devices are supported for the Symbian 7.x platform:
Nokia 6620
Nokia 9500
Motorola M1000 / A1000
Sony Ericsson P910
The following devices are supported for the Symbian 8.x platform:
Nokia 6630, which is also known in Japan as V702NK
Nokia 6680
The following are the supported development environments:
Microsoft Visual Studio 6.0
Microsoft Visual Studio .Net
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 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.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 3.11.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 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:
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.
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.
By default, the synchronization tablespace is SYNCSERVER
, and is stored in the mobile
xx
.dbf
file in the default location for the database instance 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.3, "Synchronization Tablespace Layout" in the Oracle Database Lite Troubleshooting and Tuning Guide for more information.