|
Oracle® Database Lite Administration and Deployment Guide
10g (10.2.0) Part No. B15921-01 |
|
 Previous |
 Next |
|
Oracle® Database Lite Administration and Deployment Guide
10g (10.2.0) Part No. B15921-01 |
|
|
Previous |
Next |
Tuning options for your applications are described in the following sections:
Section 13.2, "Limit Application Connection Requests to the Database"
Section 13.3, "Determine Correct Synchronization Templates to Use for Subscriptions"
Section 13.5, "Synchronization Performance Affected by WebCache"
Connection pooling enables you to eliminate the time delay in creating and destroying connections for incoming application requests. Instead, enable connection pooling, as shown in Section 4.3, "Manage Application Properties or Users", so that each incoming connection request uses an existing connection from the pool.
You can limit the number of connections that access the database from each application, as shown in Section 4.3, "Manage Application Properties or Users". Set the maximum database connection limit. Any request for a database connection beyond the limit is refused.
You can use the Consperf performance tool to evaluate if the default templates used with your publication items are the best performance option. See Section 6.7, "Monitoring and Analyzing Performance" for a full description.
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.
By default, the synchronization tablespace is SYNCSERVER, and is stored in the mobilexx.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 $OLITE_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 name, filename or file location, perform the following BEFORE you install the Mobile Server; otherwise, the default tablespace is created.
To modify the name of the tablespace, locate every instance of SYNCSERVER and change it to the name of your choice. For example, if you wanted the tablespace name to be mysynctbl, then you would modify consolidator_o8a.sql, as follows:
execute immediate 'create tablespace mysynctbl datafile '''||filename||''' size 200m autoextend on';
To modify the name of the datafile where the tablespace is stored, locate the following line in consolidator_o8a.sql:
filename := 'mobile'||filename||'.dbf';
This is included within a loop that assigns a number between 1 and 25 as an extension to mobile, so that the resulting filename is between mobile01.dbf to mobile25.dbf. You can modify the name of the file by modifying mobile to the name of your choice. For example, if you wanted the name to be syncdata01.dbf, then do the following:
filename := 'syncdata'||filename||'.dbf';
To designate an absolute or relative directory of where the tablespace datafile is located, modify the execution statement in consolidator_o8a.sql to specify the absolute or relative file location. The default places the datafile in the database instance directory in ORACLE_HOME. For example, if you are on a Windows platform and you want the datafile to be located on the e:\syncserver directory, modify the execute statement, as follows:
execute immediate 'create tablespace syncserver datafile ''e:\syncserver\'||filename||''' size 200m autoextend on';
This places the datafile into the E:\syncserver directory. If you wanted the file to be in a directory relative to the default location, provide a relative pathname. For example, to have the datafile located in a directory below the database instance in its own directory called synctbl, modify the execute statement, as follows:
execute immediate 'create tablespace syncserver datafile ''./sycntbl/'||filename||''' size 200m autoextend on';
