|
|
 Copyright © 1997, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
Release Notes
Release 10.3
E12094-02
February 2010
The information in this release note pertains to items that did not make it into each book. The information is organized by the book to which it pertains, as follows:
Section 1, "New Features for Oracle Database Lite 10g (10.3.0.3)"
Section 3, "Modifications to the SQLite Mobile Client Guide"
Section 4, "Modifications to the Administration and Deployment Guide"
The following are the new features in this release:
Section 1.3, "Automatic Synchronization Support for Linux Mobile Clients"
Section 1.10, "Authenticating a User by an External Authenticator"
Section 1.11, "Configure Web-to-Go to Use a Particular JVM/JRE"
Section 1.15, "Installing Windows Mobile Client Without Administrator Privileges"
Section 1.18, "Multiple Member Users Using the Same Mobile Client"
Section 1.19, "Store Application Data in Separate Databases"
The Mobile client uses a client database, which in the past could only be the Oracle Lite database. In this release, you can now initiate manual synchronization and, on some platforms, automatic synchronization and device management for devices and platforms that have a SQLite database installed.
For details, see the Oracle Database Lite SQLite Mobile Client Guide.
You can now use the WebLogic Server 11g as the middle-tier application server in your production environment.
Automatic synchronization is supported for the Oracle Lite X86 and Oracle Lite Web Linux Mobile clients.
Passwords can now include alphanumeric characters, and special characters of '$' (dollar sign), '#' (number sign), and '_' (underscore). For more information, see Section 4.3.1.2.1, "Define Username and Password" in the Oracle Database Lite Administration and Deployment Guide.
Previously, there was only a single Job Scheduler to manage all jobs in the Repository of a Mobile Server. Now, you can create multiple Job Schedulers in each Mobile Server or for an independent registered application database.
By default, jobs are not registered for specific Job Schedulers. Instead, all Job Schedulers distribute and execute the registered jobs. All Job Schedulers work in tandem with each other, providing failover to each other. You can manage your jobs by selecting which Job Scheduler on a specified Mobile Server is to execute the job. Or you can start a Standalone Job engine to execute jobs, where a Standalone Job engine exists outside of the Mobile Servers.
For more information, see Chapter 6, "Managing Jobs with the Job Scheduler" in the Oracle Database Lite Administration and Deployment Guide.
The Mobile client can have any number of users, where each provides their respective credentials. The current user swaps in its identity for that device by registering the user before using the Mobile device. Swapping in a new user de-registers the current user, removes the databases of the current user and bootstraps the device with the new user's configuration. Then, performing a synchronization brings down the new user's applications.
For more details, see Section 4.3.1.5, "Swap Users on a Device" in the Oracle Database Lite Administration and Deployment Guide.
You can now create indexes within MDW for your publication item. This is not included in the Quick Start Wizard, but in the main MDW functionality. For more information, see Section 6.4, "Create a Publication Item" in the Oracle Database Lite Developer's Guide.
If SYNC_LOG is set to TRUE, then Sync Agent Logging is enabled and populates C$BG_SYNC_LOG table on the client. See the POLITE.INI Appendix in the Oracle Database Lite Administration and Deployment Guide for more information.
MAX_CONCURRENT and MAX_CONCURRENT_TIMEOUT parameters have been removed from the WEBTOGO.ORA file. Instead, enable maximum concurrent clients by setting RESUME_TIMEOUT=0, which disables resume, and set RESUME_MAX_WAIT and RESUME_MAXACTIVE. This limits the maximum number of concurrently synchronizing clients to RESUME_MAXACTIVE; additional incoming clients wait RESUME_MAX_WAIT before timing out.
See Appendix A, "Configuration Parameters for the WEBTOGO.ORA File" in the Oracle Database Lite Administration and Deployment Guide for more information.
When using WSH scripts to create an external user that will be authenticated by an external authenticator class, you need to set EXTERNALUSER to TRUE. See See Appendix C, "Write Scripts for the Mobile Server with the WSH Tool" in the Oracle Database Lite Administration and Deployment Guide.
Webtogo clients can be configured to execute against a particular version of Java (J2SDK or J2RE). For more information, see Section 6.4.6, "Configure JAVA_HOME for Web-to-Go Clients" in the Oracle Database Lite Client Guide.
You can now install the Mobile Server repository in an Oracle RAC database and configure the Mobile Server and development tools to point to and use this Oracle RAC database.
The Windows Mobile 6.1 platform is now supported.
Previously, only ODBC 2.0 was supported. In this release, ODBC 3.5 is now supported on Windows.
Oracle Database Lite supports 3 conformance levels for ODBC 2.0 and the ODBC 3.5 drivers through Oracle Database Lite—Core, L1, and L2—with the following restrictions:
ODBC 2.0 is the default driver for all Oracle Database Lite components. This will be installed by default, unless otherwise configured.
ODBC 3.5 is available solely for the standalone application that uses an embedded Oracle Lite database. It can be used in development when using Visual Studio 2005, since this version requires ODBC 3.5.
|
Note: You cannot use ODBC 3.5 for any multi-user listener application or for the Mobile Server environment. |
If you want to use the ODBC 3.5 driver for an embedded application on a Mobile client, you must install the ODBC 3.5 driver on the client and configure the ODBC.INI file. See the Oracle Database Lite Getting Started Guide for directions on how to modify the INF file to perform the installation and configuration during the client installation.
When installing the Mobile client, you used to have administrator privileges. To enable the installation to occur for users who do not have administrator privileges, there is now an option to install as the Current User. There are some limitations, as the Current User cannot facilitate multiple users. For details on how to install the Current User, see Chapter 5, "Installing the Mobile Client" in the Oracle Database Lite Getting Started Guide.
In the Mobile Manager, the options for processing error queue transactions is easier. In addition, you can now re-execute just a portion of a previous transaction by creating a whole new transaction out of the desired subset.
If you are in a situation where you do not have network support at the times when you need to synchronize, then you can use file-based synchronization. This uploads/downloads all changes to/from the Mobile client using a file to transport the synchronization changes.
You can now have multiple member users, each with their own username/password, on a single Mobile client. For each Mobile client, the user that installs the Mobile client must have administrator privileges. Once the Mobile client is installed, then you can add members under this user's authority through the Mobile Manager. Each member synchronizes under the user's authority, so the usernames and passwords for both the user and the member are required when synchronizing. See the Oracle Database Lite Administrator's Guide for more information.
By default, all application data is stored in the same database as the Mobile repository. However, you can register other Oracle databases as the repository of the application data. Once registered, then during the publication creation, specify the database where you want the application data to be stored.
|
Note: When you do choose to use a separate database as the repository for the application data, then both this database and the main database (the one where the Mobile repository exists) must be up when synchronization occurs in order for the synchronization to be a success. |
You can now invoke synchronization using the C# API.
We now support Java version 1.6.
For all Mobile clients, use JRE 1.5.1. For the Mobile Server and Mobile Development Kit, the version required depends on what version of OracleAS 10g or WebLogic Server you are using.
The following subjects detail modifications that should be in the Oracle Database Lite Getting Started Guide.
Section 2.1, "Default Ports for UNIX Platform for Mobile Server"
Section 2.2, "Installing Oracle Database Lite on a 64-bit Linux Platform"
Section 2.5, "Cannot Install Over Network With Windows 2003 Service Pack 1"
Section 2.6, "Error Message Received When Installing on Pocket PC Device"
Section 2.8, "Buttons Disabled in MDW for Japanese Language on Windows 2000"
When you install the Mobile Server, you enter the ports. The default ports for the UNIX platform are not as listed in the Getting Started guide. Instead, the default ports are 8895 for an HTTP connection and 4495 for an HTTPS connection.
On a 64-bit Linux operating system, Oracle Database Lite needs to be installed using 32-bit emulation mode in this release. Set 32-bit emulation mode by executing the following command and restart the installation.
linux32 bash
The following strings, which only display during install, are not translated on either Windows or UNIX platforms:
This type of Application Server installation is not supported.
ERROR: TCP/IP port: <port> is already in use. Please enter a different value.
ERROR: TCP/IP port: <port> is invalid. Use only numeric, positive values for TCP/IP port numbers.
The following strings are not translated on the UNIX platform:
WARNING: On UNIX Operating Systems, root access is required to use a TCP/IP port under 1024.
If you received the message "Unable to Locate the JDK Installation" during Oracle Database Lite installation, then your registry keys may be pointing to the incorrect location. At the time of this release, the JDK 1.5 install writes out incorrect registry keys for the location of the JDK Home. To correct the registry keys, perform the following:
At the command prompt enter:
regedit
Check the values of the following registry keys:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.5.0_11\JavaHome My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.5\JavaHome
If the registry keys are set to a number value, such as "1", which is not a valid directory, then modify the registry key to point to the directory where you installed JDK.
The following is an example of a valid directory:
C:\Program Files\Java\jdk1.5.0_11
Reboot the machine.
While running the setup.exe through a network drive on Windows 2003 SP1 machine, you will receive a Windows security alert. In order to overcome this and run the setup.exe you need to do one of the following:
Execute the setup.exe command locally with the Oracle Database Lite CD.
Copy the contents for Oracle Database Lite on to the local disk.
Refer to the Microsoft Web site on how to add the Oracle Database Lite files to the list of the reliable files.
When you install Oracle Database Lite on a Pocket PC device with Pocket PC 2003 (Windows Mobile) Second Edition, Windows Mobile 5 or Windows Mobile 6 operating systems, you may get the following warning.
"The program you have installed may not display properly because it is designed for a previous version of Windows Mobile software."
Ignore the message. Oracle Database Lite works as expected.
The following describes upgrade limitations:
Section 2.7.1, "Upgrading the Mobile Server to Release 10.3.0.3"
Section 2.7.2, "Upgrading Mobile Clients from De-Supported Mobile Client Platforms"
Section 2.7.3, "Upgrading Web-to-Go Clients to Oracle Database Lite 10g Release 3"
Section 2.7.4, "Limitation for Branch Office Upgrade on a Windows Platform"
Section 2.7.5, "Upgrading Branch Office 10g Releases 1 or 2 to version 10g Release 3"
Section 2.7.7, "Upgrade Your Windows Mobile 5 Client Platform"
Section 2.7.8, "Increasing Quota Before Upgrading Repository Wizard from 5.0.2.x to 10.3.0"
Section 2.7.9, "Online Web Application Issue When Upgrading from 5.0.2.x to 10.3"
Section 2.7.10, "Please Wait... Message When Upgrading Branch Office with Oracle Database Lite 10.3"
Before you upgrade your Mobile Server to 10.3.0.3, please ensure that you have applied the latest patch available for your current version of Oracle Lite Database. Check for the latest patch available for your current version of Oracle Lite Database at http://support.oracle.com.
For the Oracle Lite Palm, PPC2003 Emulator, and PPC2000 ARM Mobile client platforms, there is no upgrade option. These client device platforms are no longer supported for Oracle Database Lite.
Table 2 displays how you can migrate the following de-supported Mobile client platforms to currently available platforms:
Table 2 Upgrading De-Supported Mobile Client Platforms
|
De-Supported Client Platform |
Upgrade to this Available Platform |
|
Oracle Lite PPC2003 XScale |
Oracle Lite PPC2003 ARMV4 |
|
Oracle Lite WCESTD42 ARMV4 |
Oracle Lite PPC50 ARMV4I |
During the upgrade process, be sure to not cancel in the middle. If your device is Windows 5.0 or later, then you must perform the following after the CAB files are downloaded to the device:
Tap on the CAB files to extract the files to the device.
Tap on dmagent to execute start the Device Manager.
The following describes what happens for those Mobile client devices that want to continue to use the de-supported platforms:
Any client device that has a de-supported platform is given the option to migrate to the upgrade platform when they execute msync.exe or update.exe.
If you do not want to upgrade the client platform, then these clients can still synchronize with the Mobile Server; however, they will be prompted to upgrade each time.
You can continue to administer de-supported client platforms, as they will still appear in the platform tabs in the Mobile Manager. We will not disable them from your administration management GUI. However, they will not be included in the setup page for you to create new clients using these platforms.
The applications that already exist on the de-supported client platforms will still run as expected. And you may apply any patches for the application. However, you cannot deploy any new applications to that platform.
If you do upgrade the client platform, then you must re-package and re-publish each application as a new application for the new client platform.
If you are upgrading from Oracle Database Lite 10g Releases 1 to Release 3, then upgrade your Web-to-Go clients, as follows:
Install Oracle Lite 10g Release 3 Mobile Server in the same ORACLE_HOME directory where you installed Release 1.
Stop the Web-to-Go client.
From the Web-to-Go client machine, point your browser to http://<hostname>:<port>/webtogo/setup on the Mobile Server 10g Release 3.
Select Oracle Lite Webtogo Client from the list of Mobile clients. Download and save the setup.exe file into the WTG_CLIENT_HOME\bin directory. Overwrite the existing setup.exe file.
Copy the POLITE.INI and ODBC.INI files from the C:\Windows directory to the WTG_CLIENT_HOME\bin directory.
Open a command prompt, navigate to the WTG_CLIENT_HOME\bin directory, and execute the update.exe command to start the upgrade process. Alternatively, you can open Programs->Oracle Database Lite->Oracle Lite Update.
After upgrade is complete, log in to the Workspace and perform synchronization for the application before accessing the Web-to-go application.
When you are upgrading a Branch Office client on a Windows platform, the upgrade will not complete if Web-to-Go is running in service mode. Perform one of the following:
First terminate the Web-to-Go service and re-start it in debug mode, as follows:
webtogo -d0
Execute update.exe.
If you have Oracle Database Lite 10g Releases 1 or 2, then upgrade your Branch Office to 10g Release 3, as follows:
|
Note: These steps assume that you have a 10g Release 1 or 2 Branch Office environment already configured and synchronized. If you do not have this environment currently configured, you do not need to upgrade. |
Install Oracle Lite 10g Release 3 Mobile Server in the same ORACLE_HOME directory where you installed Release 1 or 2.
Stop the Branch Office client executing as a Windows Service.
From the Branch Office client machine, which is being migrated to 10g Release 3, point your browser to http://<hostname>:<port>/webtogo/setup on the Mobile Server 10g Release 3.
Click on "Oracle Lite Branch Office Client" link from the list of Mobile clients. Download and save the setup.exe file into the BO_CLIENT_HOME\bin directory. Overwrite the existing setup.exe file.
Copy the polite.ini and odbc.ini files from the C:\Windows directory to the BO_CLIENT_HOME\bin directory.
Open a command prompt, navigate to the BO_CLIENT_HOME\bin directory, and execute the update.exe command to start the upgrade process. Alternatively, you can open Programs->Oracle Database Lite->Oracle Lite Update.
After upgrade is complete, log in to the Workspace and perform synchronization for the application before accessing the Branch office application.
Web-to-Go Applications that upgrade from 5.0.2 to 10g Release 3 that have no associated snapshots will not display on the Mobile Server workspace.
In this release, we provide a new client that is for the Windows Mobile 5 client platform called Oracle Lite PPC50 ARMV4I. If you currently have an existing Oracle Lite PPC Mobile client installed, you can upgrade to this new Mobile client, as detailed in this section.
You may have one of the following clients already installed on your Windows Mobile 5 device: Oracle Lite PPC2000 ARM, Oracle Lite PPC2003 ARMV4, Oracle Lite PPC2003 XScale.
If you would like to upgrade the client to Oracle Lite PPC50 ARMV4I, please do the following:
|
Note: These instructions are ONLY for those Mobile clients that exist on Windows Mobile 5 devices. |
Repackage and republish the applications that are assigned to the affected users. Associate these new applications with Oracle Lite PPC50 ARMV4I.
Execute the upgradetoppc50.bat (upgradetoppc50.sh on Linux) script that exists in the <ORACLE_HOME>\Mobile\Server\admin\ directory, as follows:
upgradetoppc50.bat INSTALL [ORACLE_HOME] [REPOSITORY USERNAME] [REPOSITORY PASSWORD] [JDBC URL]
Run msync or update executables from the intended client devices. An update to PPC50 is shown. Accept the update to be installed.
You can revert the mapping by executing the same script with UNINSTALL as the first argument, as follows:
upgradetoppc50.bat UNINSTALL [ORACLE_HOME] [REPOSITORY USERNAME] [REPOSITORY PASSWORD] [JDBC URL]
Perform the following step before installing Oracle Database Lite 10.3 to increase the quota for the 10.3 Repository Wizard:
Login to sqlplus as system or sysdba.
At the SQL prompt execute the following:
alter user mobileadmin quota unlimited on USERS;
If you do not perform this before upgrading the repository from 5.0.2 to 10.3.0, then the following error is thrown:
ORA-01536: space quota exceeded for tablespace 'USERS'
When you upgrade from 5.0.2.x to the 10.3 version, then some of the online Web applications may lose the username/password. If you try to execute them, you will get the error 'accessing data'. Modify the database username and password in the Application properties to a valid username/password.
If after the upgrade process for the 10.3 is complete, the browser continues to display a "Please wait... " message, either reboot your machine or perform the following:
Restart the Oracle Database Lite MultiUser service.
Restart the Oracle Web-to-Go service.
If you have installed the Mobile client with the sample user S11U1 on a device prior to the 10g Release 3 upgrade, and you decide to re-install the sample applications, then the user will no longer be able to synchronize. You must uninstall the client and then re-install before the sample user S11U1 will work again.
After upgrading from 5.0.2.x to 10g Release 3, if you want to run your application in on-line mode, then you need to set the username and password of the application in the Mobile Manager. In some cases, the username and password may become null after the upgrade.
If you are using Japanese as your language on a Windows 2000 operating system, then when you are creating a publication item, the buttons disable at the end of the creation wizard. You can use the tabs to complete the process and end the wizard.
The following details the process where the buttons disable at the end on step 10.
Launch MDW.
Create a new project or open an existing project file.
Select Publication Item and click Create Publication Item.
Click Next on the Welcome page.
Enter the name, click Enable automatic Synchronization, and then click Next.
Select the appropriate table and click Next.
Click Next to bring you to the Summary page, and then click Finish.
Select the Specified Users tab.
Enter your SQL statement and click Applied.
Check any button in the Select Primary Base Object for Publication Item dialog box. At this point, use the tabs to enable the windows to disable and return to the main UI.
SQLite provides a command-line management tool called sqlite3.exe that is used for accessing and modifying the SQLite database, which you can download from http://www.sqlite.org/download.html.
The following subjects detail modifications that should be in the Oracle Database Lite Administration and Deployment Guide.
Section 4.2, "Synchronization Causes Files in Wrong Location"
Section 4.3, "Offline Instantiation Does Not Work with External Authentication"
Section 4.4, "OID and External Authentication Combination Not Supported"
Section 4.7, "User Password Encryption Impacts Using Older Version Database Binaries"
Section 4.8, "Device Manager Command 'Reset Password' Update"
Section 4.10, "Changing the Language or Locale for Branch Office Client"
Section 4.11, "Problem Encountered When Synchronizing on Microsoft Windows Vista"
Section 4.12, "Using MDW, OLI and WTGDebug the Same MDK Installation"
Section 4.14, "Device Management Network Provider WOR_IAS is No Longer Configured"
When you disable a member user, it cannot login to the Web-to-Go client. However, the synchronization layer is not aware of the disable. So the member user can still use the msync utility to synchronize data from the client.
If, after synchronizing with the msync executable, you do not see the Oracle Lite database files in the desired location--for example, <ORACLE_HOME>\Mobile\Sdk\OLDB40--then check and modify the DATA_DIRECTORY parameter in the polite.ini file. The polite.ini file is located in the <ORACLE_HOME>\Mobile\Sdk\bin directory.
Offline Instantiation (OLI) does not work with a server configured with external authentication because the public key, which is required for external authentication, is not downloaded by OLI. As a result, authentication fails and then synchronization fails.
You cannot combine OID and external authentication.
The NullPointerException is thrown in StandardRequestLogger.appendIP if the Mobile Server is running in the standalone SSL mode. This is a bug in the OC4J container, which will be fixed in future releases. Usually this is a harmless exception.
Perform the following as a workaround:
Open the <ORACLE_HOME>\mobile_oc4j\j2ee\mobileserver\config\secure-web-site.xml file and add access-log="false" at the end of the web-app tag for the mobileserver application, as follows:
<web-app application="mobileserver" name="webtogo" load-on-startup="true" root="/webtogo" shared="true" access-log="false"/>
If you execute the VALIDATEDB on webtogo.odb, you will receive errors. Ignore the errors.
Oracle Database Lite encrypts the user password with a one-way encryption algorithm before storing it in the database. With the change in password encryption, any database upgraded from an older version is not accessible using the old binaries.
The purpose of the Reset Password command is to reset the client side password to match the new password on the server side. Note that this command DOES NOT change the password on the server side. In order to use the command, the Administrator must change the user's password in Mobile Server and later send the command to the device to reset its stored password. Also the device must be immediately reachable from the Server.
Webtogo Clients and Branch Offices do not support the Reset Password command in this release.
The Mobile Client for Branch Office is installed as a service for an internal user. Thus, if you are running Branch Office as a service and perform an initial synchronization, then the DSN created is not visible to the other users in the ODBC administration tool.
If the user wants to use the Oracle Lite database created by Branch Office, then they must create the DSN entries using the ODBC administration tool manually.
If the user needs to change the locale for the default user-profile on the Branch Office client, the perform the following:
If the Branch Office client is installed on Windows 2000, then perform the following:
Log on to the computer as the administrator, and then create a local user account.
Log off as the administrator, and then log on to through the local user account that you just created.
Change the locale of user to the desired locale within the Control-Panel->Regional Settings page.
Log off as the local user, and then log back on as the administrator.
Turn on the following option: Show hidden files and folders. In Windows Explorer, this option can be selected in the View tab of the Tools->Folder Options screen.
Replace the current default user profile with the customized default user profile, as follows:
Navigate to the Control-Panel->System.
On the User Profiles tab, click the user profile that you just created, and then click Copy To.
In the Copy profile to section, select the location and who is permitted to use this profile. Click Browse and select the \Documents and Settings\Default User folder for where the profile is to be copied. To set the permissions, then under the Permitted to use section, click Change for everyone. Click OK to save.
This modifies the locale for the default user-profile. At this point, you should install the Branch Office, which will reflect the new locale.
Perform the following if you receive this message when you initiate a synchronization off of a Microsoft Windows Vista: "740 The requested operation requires elevation."
Right click the msync.exe on FileExplorer.
Select Properties ->Compatibility.
Click the "Run this program as an administrator" checkbox.
This issue only occurs when the Windows Vista User Account Control is on.
The MDW, OLI and WTGDebug tools all use the same polite.ini configuration file and ODBC DSN names. Because of this, they can overwrite configuration needed for the other tools. For this release, if you want to use more than one of these tools in the same MDK, then you must re-install the MDK in between using different tools to ensure that the configuration is correct.
Also, because of the polite.ini sharing issue, installing a normal client on a machine that has an MDK installation is not supported.
Some of the Linux operating systems for Japanese, Korean and Chinese use UTF-8 as the default locale. Consequently, this effects some of the Web-to-Go Workspace pages—causing some garbled characters. This applies to the Linux server, Linux Web-to-Go client, and Linux Web-to-Go OC4J client.
If you experience this situation, perform the following:
Modify the operating system locale and encoding according to your language by setting the environment variables LC_ALL for the locale and LANG for the encoding, as follows:
Supported locale and encoding for Simplified Chinese:
locale: zh_CN.gb18030, encoding: zh_CN.gb18030
Supported locale and encoding for Korean:
locale: ko_KR.eucKR, encoding : ko_KR.eucKR
Supported locale and encoding for Japanese:
locale: ja_JP.eucJP, encoding: ja_JP.eucJP
For the Mobile Server, restart the Mobile Server to re-initialize with the new locale and encoding. For any Linux Mobile clients, the locale and encoding are only initialized when you install the client. Thus, you must re-install the Oracle Lite client after modifying the locale and encoding.
During installation, we no longer configure the Network Provider WOR_IAS to send SMS based device management commands to mobile devices. If you have a device that supports Wake On Ring functionality, then you can use the SMTP network provider instead. If you need to use the WOR_IAS provider, contact Oracle Support.
If you have a mobile phone as a Mobile device, then you would have a network protocol where the mobile phone receives incoming data. Thus, the address is a phone number for the mobile phone. The mobile phone is "woken" when incoming commands are initiated from the Mobile Manager. However, you can only use the Wake on Ring over SMTP (WOR_SMTP). The Wake on Ring over OracleAS (WOR_IAS) is no longer configured.
Due to a limitation in the Windows Mobile 6 Emulator in Korean, some of the msync and dmagent GUIs are larger than can be displayed on the screen, as a result the GUIs appear to be truncated on the right hand side. This layout problem has no impact on the actual functionality of the utilities.
The following subjects detail modifications that should be in the Oracle Database Lite Developer's Guide.
Before 10.3, how you created any long objects may have caused a leading byte to be inserted before your data.
You will have a leading byte if you created a long object with the CLOB putChars and putString methods of the old JDBC driver. However, you will not have a leading byte if you had created the CLOB using an INSERT statement with an embedded string or a marker that was initialized as a string, then the CLOB object is created correctly without the leading blank. If you used both methods, you may have an inconsistency of some rows having the leading byte and others created normally.
|
Note: You will not experience the leading byte problem when the Oracle Lite database is created during the first synchronization as it does not use JDBC/ODBC for creation. |
However if your CLOB does have a leading blank, perform one of the following:
If a column in the CLOB is consistently off by one, then fix this by writing a Java program that left shifts the CLOB bytes by one and truncates the last byte.
If a column is not consistently created, then you may have to re-create all values.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Oracle Database Lite Release Notes, Release 10.3
E12094-02
Copyright © 1997, 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
|
|
Copyright © 1997, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|