Skip Headers
Oracle® Database Lite Administration and Deployment Guide
10g (10.0.0)
Part No. B12262-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

A Troubleshooting FAQ's

This document contains frequently asked questions for troubleshooting the Mobile Server. Topics include:

A.1 Inspecting Files in the Mobile Server Repository

You can use the Mobile Server shell utility (wsh) to inspect and modify the Mobile Server Repository interactively. Start the Command Prompt and enter the following.

wsh -L system/x@olite-db

OR

wsh -o <adminuser>/<adminuser's password>@o8db

For example, you could enter the following sample codes at the command prompt.

wsh -o administrator/admin@webtogo.worldwsh -L system/x@webtogo

This displays the Mobile Server Repository prompt.

The following table lists commands that are available for inspecting and altering the Mobile Server Repository.

Table A-1 describes available commands for inspecting and altering the Mobile Server Repository.

Table A-1 Commands to Inspect and Alter the Mobile Server Repository

Command Definition
dir Displays a list of files in a directory.
copy Copies one or more files to another location.
cp Copies one or more files to another location.
edit Launches Notepad for editing a file.
del Deletes one or more files.
rm Deletes one or more files.
cd Displays the name or changes the current directory.
md Creates a directory.
rd Removes (deletes) a directory. Use the option -s to remove a directory including all subdirectories.
type Displays the contents of a text file or files.
exit Quits the command shell.
quit Quits the command shell.
help Provides help information for shell commands.
sync Synchronizes the file system with the database.

A.2 Running the Mobile Server in Debug Mode

If you experience any difficulty with the Mobile Server running with the Oracle9iAS or the standalone Mobile Server, you can run the Mobile Server in debug mode.

To run the Mobile Server in debug mode, perform the following steps.

  1. Shut down the Mobile Server and Oracle9iAS or the standalone Mobile Server.

  2. Verify in the file webtogo.ora that the following [DEBUG] parameters contain the specified values.

    Table A-1 describes Debug parameters that are available in the webtogo.ora file.

    Table A-2 Debug Parameters

    Parameter Name Value
    TRACE_ENABLE YES
    TRACE_REMOTE_MACHINE <debug_client> where <debug_client> is the name of the machine to which you want Oracle9iAS to send debugging messages.
    TRACE_REMOTE_PORT 100

  3. Start the Command Prompt on the Debug machine and enter the following command.

    wsh -m 100

    In the above command, wsh is the application, -m enables the monitoring feature, and 100 specifies the port to monitor.

  4. Restart the Mobile Server.


    Note:

    If you are running the standalone Mobile Server instead of the Oracle9iAS, you can debug your Mobile Server by specifying -d0 on the Command Line. For example, webtogo -d0.

A.3 First Synchronization Causes Browser to Timeout

The Problem

The duration of the first synchronization process, between the client and the server may take a very long time (For example, upwards of 45 minutes), causing Microsoft's Internet Explorer browser to time out.

The Solution

This solution is available only for Microsoft's Internet Explorer. For the Mobile Client for Web-to-Go, change the ReceiveTimeout value for a particular registry key on Windows 32. The following paragraphs provide the location of this parameter and specifies how to change its value.

  1. If you want to change the ReceiveTimeout value (that is, the number of milliseconds that the browser will wait to receive the data from the server), uncomment the following two lines in the REGISTRY section of the file setup.ini. This file is downloaded to the client from the server when the Mobile Client for Web-to-Go is first installed on the client machine.

    #KEY: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\       Internet Settings#VALUEDWORD: ReceiveTimeout = 40000000
    
    
  2. To uncomment the two lines, remove the hash marks in front of the KEY and VALUEDWORD statements and then change the ReceiveTimeout value to the desired value in milliseconds. In the example given below, the timeout value is 40000 seconds.

    wsh -o mobileadmin/manager@webtogo.worldcd setupedit setup.ini
    
    
  3. When you modify the file setup.ini in the Mobile Server Repository, the next time that the file is downloaded to the Mobile Client, these two lines will be uncommented.

A.4 Accessing the Client Database Offline

When you go offline, after being online, and you need to access your client database, use your mobile user's password, not the password manager. It is the password that you enter when you logged in, before going offline.

If you do not use your mobile user's password when you try to access your client database offline, you will receive the following error message.

[POL-5150] access violation

For example, if you log in as JOHN/JOHN on a Windows 32 machine with contains a Mobile Client for Web-to-Go, and JOHN goes offline, the user database created for JOHN on the client machine requires JOHN's password for access.

If you use msql to access the user database, start the Command Prompt and enter the following statement.

msql system/john@jdbc:polite:john_todo

In this example, JOHN's password is john, and the DSN name that was created automatically on the client for the user name JOHN is john_todo.

Syntax

The following syntax enables you to access the user database.

msql system/<mobile user's password>@jdbc:polite:<dsn created for the user>

To find the DSN name, use the ODBC Admin tool on your client machine.

A.5 Accessing Schema Changes to a Published Application

To include the schema evolution changes in your existing application, you must republish the application. If one or more of the application tables has changed and you want these changes to be reflected on the client, you must republish the application using the Packaging Wizard. For more information on how to publish your applications, see the Oracle Database Lite Developer’s Guide.