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


3 Upgrade Your Oracle Database Lite

If you have Oracle9i Lite version 5.0.2.x, you must upgrade to the latest version. This chapter discusses the steps for upgrading your software in the following sections:

3.1 Understand Desupported Devices

The following devices are not supported in Oracle Database Lite 10g:

WinCE devices WinCE devices WinCE devices WinCE devices
HPC_Pro\us\arm HPC_Pro\us\sh3 HPC_Pro\us\sh4 HPC_Pro\us\mips
HPC_Pro\cn\arm HPC_Pro\cn\sh3 HPC_Pro\cn\sh4 HPC_Pro\cn\mips
HPC_Pro\ja\arm HPC_Pro\ja\sh3 HPC_Pro\ja\sh4 HPC_Pro\ja\mips
HPC_Pro\ka\arm HPC_Pro\ka\sh3 HPC_Pro\ka\sh4 HPC_Pro\ka\mips
Pocket_PC\us\sh3 Pocket_PC\us\sh4 Pocket_PC\us\mips Pocket_PC\cn\sh3
Pocket_PC\cn\sh4 Pocket_PC\cn\mips Pocket_PC\ja\sh3 Pocket_PC\ja\sh4
Pocket_PC\ja\mips Pocket_PC\ko\sh3 Pocket_PC\ko\sh4 Pocket_PC\ko\mips

3.2 Upgrade Your Oracle Database Lite Installation

In order to upgrade your Oracle Database Lite Installation, you must first install the current version of Oracle Database Lite in a separate Oracle home than your 5.0.2.x version.


Upgrading Oracle Database Lite version 5.0.1.x or previous versions is not supported with this process. You must first upgrade to 5.0.2.x before starting this process.

Before you start the installation, you should remove the data for the 5.0.2.x samples from the Mobile Server Repository by dropping the MASTER schema on the back-end database. The 5.0.2.x samples will not work with Oracle Database Lite 10g. If you want the new samples, then when you install Oracle Database Lite 10g, make sure that you click Yes to install the samples. This installs the samples on the Mobile Server and downloads the data for the samples in the back-end database for the Mobile Server Repository.

If you have multiple Mobile Servers that use the same Mobile Server Repository on a back-end database, you must shut down all of these Mobile Servers before you start the upgrade. Then, upgrade one of these Mobile Servers and the Mobile Server Repository. After this upgrade completes successfully, you can upgrade each additional Mobile Server that uses the Repository. After all of the shared Mobile Servers are upgraded, you can restart them.

See Chapter 2, "Installation of Oracle Database Lite" for instructions on how to install Oracle Database Lite. When the Repository Wizard is executed, see Section 3.3, "Upgrade Your Mobile Server Repository" for directions on how to upgrade the repository on the back-end database.

3.3 Upgrade Your Mobile Server Repository

During installation of Oracle Database Lite 10g, the Repository Wizard detects if you have a 5.0.2.x version of Oracle Database Lite installed and starts the upgrade process, as follows:


If you need to start the Repository Wizard outside of the install process, execute ORACLE_HOME\Mobile\Server\admin\repwizard

  1. Enter the SYSTEM password. Click Next.

  2. Select the schema that you are going to upgrade. Click Next.

  3. Enter the password for the Mobile Server Repository—MOBILEADMIN—and click Yes for installing sample applications. Click Next.

  4. A summary screen appears. Click Next.

  5. After the repository is upgraded, click Finish.

To upgrade each individual Mobile Server, follow the instructions in Section 3.2, "Upgrade Your Oracle Database Lite Installation".

3.4 Upgrade Your Existing Applications

Once you have installed the Oracle Database Lite 10g in a new Oracle home and the Repository Wizard has upgraded the Mobile Server Repository successfully, you must execute the Application Upgrade Assistant to upgrade your existing applications.

The Application Upgrade Assistant moves the applications from the 5.0.2.x Oracle home to your new 10g Oracle home. In addition, the assistant transforms your Mobile applications to the new application model. In previous versions, you could create a single Mobile application for all platforms with a single dataset. In 10g, you must create a single Mobile application for each platform, each with its own dataset. Thus, if you have the myapp application, the Application Upgrade Assistant will transform your myapp application into the following:

Each application is upgraded with the dataset and access rights that was in the original application.

In addition, Oracle Database Lite 10g uses OC4J for all middle-tier functionality. Thus, all Mobile Web applications must now be contained within a J2EE WAR or JAR file. The Application Upgrade Assistant converts your applications by adding the required XML files and packages your Web applications into a WAR file and publishes these applications. However, for all future applications, you must create the XML files and package them into a WAR or JAR file.

The Application Upgrade Assistant is located in the following locations:

On the command-line, supply the Mobile Server Repository Name, the Mobile Server Repository Password, the old Oracle home and the new Oracle home. For example, on a Windows system, where the repository name is mobileadmin, its password is manager, the old Oracle home is c:\oracle\ora502 and the new Oracle home is c:\oracle\ora10g, execute as follows:

ApplicationUpgradeAssistant mobileadmin manager c:\oracle\ora502 c:\oracle\ora10g

3.4.1 Manual Upgrade Instructions For Web-to-Go Applications in Retrieving the OraUserProfile Class

In previous versions, Web-to-Go applications retrieved the OraUserProfile class as follows:

OraUserProfile p = ((OraHttpServletRequest)req).getUserProfile();

For Oracle Database Lite 10g, all existing and future Mobile applications must retrieve the OraUserProfile class with the following lines:

HttpSession s = request.getSession(true); 
OraUserProfile p = (OraUserProfile)s.getAttribute ("x-mobileserver-user"); 

You must manually modify all existing Mobile applications to use the new method of retrieving the OraUserProfile class and then republish the application to complete the upgrade process for your 5.0.2.x Mobile applications.

3.5 Use the Appropriate Context for Your Mobile Server

The servlet context that you use for all Web-to-Go applications is changed for this version. You must add the /webtogo/ servlet context to all URLs for your Web-to-Go applications. For example, in the past, you tested your Mobile Server using <hostname:port>/sample1/hello. For Oracle Database Lite 10g, enter <hostname:port>/webtogo/sample1/hello.

3.6 Migrate Your Users From the Mobile Server Repostory to the Oracle Internet Directory

If you want, you can use the Oracle Internet Directory (OID) for storing and retrieving user information, instead of the Mobile Server Repository. To facilitate using OID, you must first migrate all user information from the repository into OID. Once migrated, you can use OID instead of the repository.

OID is part of the Oracle9iAS or OracleAS application server.

Migrate your existing users in the repository to the OID through the oiduser tool, which is located in ORACLE_HOME\mobile\server\bin. The oiduser tool migrates your existing users with either randomly-generated passwords or a common password.

  1. Migrate the user information using the oiduser tool, for either randomly-generated passwords or a common password, as follows:

    1. To use randomly-generated passwords for each user, execute the oiduser tool without the -P option, as follows:

      oiduser <Oracle_Home> <Mobile Server Repository username> <Mobile Server Repository password> <OID port number> <OID host name> <OID password>

      For example, the default setting would be:

      oiduser <Oracle_Home> mobileadmin manager 389 welcome1
    2. To use a common password for all users, provide the common password with the -P option, as follows:

      oiduser <Oracle_Home> <Mobile Server Repository username> <Mobile Server Repository password> <-P> <common password> <OID port number> <OID host name> <OID password>

      where the common password is specified by you.

    Executing oiduser generates three files: mobile_oid_user, oiduserfile.Idif and user.dat. The user.dat file contains a list of users and the passwords created for them in step 1 or 2. This file is strictly for informational purposes.

  2. Copy the mobile_oid_user and oiduserfile.Idif files to the same directory in the application infrastructure machine where OID is installed. You can copy them to any directory, as the mobile_oid_user is an executable that uses the oiduserfile.Idif file.


    The mobile_oid_user executable requires that the ldapadd executable is in the PATH. The ldapadd executable is part of the application server installation.

  3. Execute the mobile_oid_user file from the command-line on the application server infrastructure machine. This creates the Oracle Database Lite users in the OID.

    All users from the Mobile Server Repository are now migrated to the OID with the passwords, as designated in step 1.

  4. Restart both the application server and the Mobile Server.

3.7 Remove the 5.0.2.x Installation

Once you have completed all of the upgrade exercises, you can now remove the 5.0.2.x version of the Oracle Database Lite from your system. This is not a required step, but is recommended for clarity in the future.

  1. Start up the Oracle Universal Installer by double-clicking on setup.exe.

  2. On the File Locations screen, enter the Oracle home and path for the 5.0.2.x installation. Click Installed Products.

  3. On the Inventory screen, select the '+' next to the Oracle home for your 5.0.2.x installation. Then, click the box next to the 5.0.2.x installation that you are going to remove. Click Remove.

  4. On the Confirmation screen, click Yes.

  5. When the removal is complete, click Close.

  6. To exit the Installer, click Exit.

  7. Optionally, you can go into your directories and remove the directory where the 5.0.2.x installation existed.

3.8 New Consolidator Sequence Properties Added During Upgrade

Any upgrade from a previous version of the Mobile Server upgrades the Consolidator Sequences to a new Sequence model, which contains additional property information. The new Sequence properties have the following default values:

You can modify any of these properties through the Java modifySequence API, which is described fully in the Consolidator Admin API Specification JavaDoc.