Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Send Us Your Comments

1 Improving Performance

• 1.1 Improving Connection Performance
  • 1.1.1 Using Connection Pooling for Applications
  • 1.1.2 Limit Application Connection Requests to the Database
• 1.2 Increasing Synchronization Performance
  • 1.2.1 Analyzing Performance of Publications With the Consperf Utility
    • 1.2.1.1 Deciphering the Performance Evaluation Files
  • 1.2.2 Monitoring Synchronization Using SQL Scripts
    • 1.2.2.1 Synchronization Times for All Clients
    • 1.2.2.2 Failed Transactions for all Clients
    • 1.2.2.3 Completely Refreshed Publication Items for all Clients
    • 1.2.2.4 Publications Flagged for Complete Refresh for All Clients
    • 1.2.2.5 Clients and Publication where Subscription Parameters are Not Set
    • 1.2.2.6 Record Counts for Map-based Publication Item by Client
    • 1.2.2.7 Record Count for Map-based Publication Items by Store
    • 1.2.2.8 All Client Sequence Partitions and Sequence Values
    • 1.2.2.9 All Publication Item Indexes
  • 1.2.3 Create SQL Scripts With All Dependencies
  • 1.2.4 Configuration Parameters in the WEBTOGO.ORA that Affect Synchronization Performance
  • 1.2.5 Tuning Queries to Manage Synchronization Performance
    • 1.2.5.1 Avoid Using Non-Mergable Views
    • 1.2.5.2 Tune Queries With Consperf Utility
    • 1.2.5.3 Manage the Query Optimizer
  • 1.2.6 Synchronization Tablespace Layout
  • 1.2.7 Shared Maps
    • 1.2.7.1 Performance Attributes
    • 1.2.7.2 Shared Map Usage
    • 1.2.7.3 Compatibility and Migration for Shared Maps
  • 1.2.8 Use Map Table Partitions to Streamline Users Who Subscribe to a Large Amount of Data
    • 1.2.8.1 Create a Map Table Partition
    • 1.2.8.2 Add Map Table Partitions
    • 1.2.8.3 Drop a Map Table Partition
    • 1.2.8.4 Drop All Map Table Partitions
    • 1.2.8.5 Merge Map Table Partitions
  • 1.2.9 Configuring Back-End Oracle Database to Enhance Synchronization Performance
    • 1.2.9.1 Physically Separate Map Tables and Map Indexes
    • 1.2.9.2 Database Parameter Tuning
  • 1.2.10 Priority-Based Replication
    • 1.2.10.1 Create Restricting Predicate in Publication Item
    • 1.2.10.2 Set Priority Flag in Mobile Sync API Before Initiating Synchronization
  • 1.2.11 Caching Publication Item Queries
    • 1.2.11.1 Enabling Publication Item Query Caching
    • 1.2.11.2 Disabling Publication Item Query Caching
  • 1.2.12 Architecture Design of Mobile Server and Oracle Database for Synchronization Performance
  • 1.2.13 Designing Application Tables and Indexes for Synchronization Performance
• 1.3 Optimizing SQL Queries on the Client
  • 1.3.1 Enabling Tracing on the Client
  • 1.3.2 Optimizing SQL Queries for the Oracle Lite Database
• 1.4 Integrating Oracle Database Lite With the Oracle Real Application Clusters
• 1.5 Maximizing JVM Performance By Managing Java Memory
• 1.6 Maximizing Mobile Client Performance
  • 1.6.1 Synchronization Disk Needs May Impose on WinCE Platform Available Space

2 Troubleshooting

• 2.1 Troubleshooting Synchronization
  • 2.1.1 Synchronization Errors and Conflicts
    • 2.1.1.1 General Synchronization Errors and Conflicts
    • 2.1.1.2 Synchronization Error if Client Device Clock is Inaccurate
    • 2.1.1.3 Synchronization Error After Modifying Client Password
  • 2.1.2 Problems When Synchronizing Large Number of Rows
  • 2.1.3 First Synchronization Causes Browser to Timeout
  • 2.1.4 Situations Where the Client is Out of Sync that Triggers a Complete Refresh
  • 2.1.5 The "Inconsistent Datatypes" SQLException Received If Order is Not Correct in Query
  • 2.1.6 MGP Compose Postponed Due to Transaction in the In-Queue
  • 2.1.7 Avoiding the Server Busy Warning
  • 2.1.8 Enabling Online Web-to-Go Applications on the Mobile Server Host
• 2.2 Troubleshooting the Mobile Server
  • 2.2.1 Running the Mobile Server With Tracing Enabled
  • 2.2.2 Troubleshooting an Address Already In Use Error
  • 2.2.3 Overwriting OracleAS WEB.XML Causes Connection Failure
• 2.3 Troubleshooting the Mobile Server Repository
  • 2.3.1 Troubleshooting the Mobile Server Repository with the Mobile Server Repository Diagnostic Tool
    • 2.3.1.1 Use the Mobile Server Repository Diagnostic Tool to Validate Your Environment and the Repository
    • 2.3.1.2 Execute the Repository Diagnostics Tool
  • 2.3.2 Inspecting Files in the Mobile Repository With the WSH Tool
  • 2.3.3 Modifying IP Address of Machine Where Mobile Repository Exists
  • 2.3.4 Receiving SecurityException When Using OID With Mobile Server
• 2.4 Troubleshooting the Oracle Lite Databases
  • 2.4.1 Accessing the Client Database Offline
  • 2.4.2 Determining Source of Checksum Error Against Database
• 2.5 Troubleshooting JVM Errors
  • 2.5.1 Troubleshooting An Out of Memory Error
    • 2.5.1.1 JVM Memory Settings
    • 2.5.1.2 Why is Memory Not Released?
    • 2.5.1.3 Thread Memory Consumption and Concurrency
  • 2.5.2 Troubleshooting an IllegalArgumentException
• 2.6 Troubleshooting Security
  • 2.6.1 SSL Certificate Rejection for Client Authentication

3 Tracing and Logging

• 3.1 Enable Tracing on the Mobile Server
  • 3.1.1 General Tracing for the Mobile Server
  • 3.1.2 Data Synchronization Tracing
    • 3.1.2.1 Description of the Five Data Synchronization Components
• 3.2 Enable Tracing on Mobile Clients
  • 3.2.1 Enable Sync Agent Logging with SYNC_LOG Parameter
  • 3.2.2 Turn on Tracing for the Mobile Client WEBTOGO.ORA File
  • 3.2.3 Turn on Tracing using the -d0 Option for Web-to-Go Clients With the WEBTOGO Executable
  • 3.2.4 View Device Logs
• 3.3 Enabling Tracing in the Client-Side Oracle Lite Database
• 3.4 Viewing the Log Files From the Application Server

4 Backup and Recovery

• 4.1 How Does Oracle Database Lite Store its Information?
• 4.2 Backing Up Oracle Database Lite
• 4.3 Oracle Database Lite Backup Coordination Between Client and Server
• 4.4 Oracle Database Lite Recovery Issues

Index