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
 

I POLITE.INI Database Parameters

You can customize your Oracle Database Lite by changing the database parameter values defined in your POLITE.INI file. This document discusses the POLITE.INI file and its associated parameters. Topics include:

I.1 POLITE.INI File Overview

The POLITE.INI file centralizes database volume ID assignments and defines parameters for all databases on a system. When you install Oracle Database Lite, the installation creates the POLITE.INI file in your Windows 98, NT, 2000, or XP home directory.

The installation automatically sets the parameters in your POLITE.INI file, but you can modify them to customize the product's behavior. To modify the POLITE.INI file, you can use an ASCII text editor.

I.2 POLITE.INI Parameters

The following sections describe the parameters in the All Databases section of the POLITE.INI file.

I.2.1 CacheSize

Specifies the size of the object cache in kilobytes. The minimum is 128. If not set, the default is 4096 (4 megabytes).

I.2.2 Database ID

Defines the next Database Volume ID number to be assigned the CREATE DATABASE SQL command. Database Volume ID numbers must be unique for each database file on the system.

I.2.3 DBCharEncoding

Specifies the Oracle Database Lite character set. If set to NATIVE, the default is the system default character set.

Table I-1 lists the supported code pages and their corresponding values of DbCharEncoding.

Table I-1 Supported Code Pages and Values

Code Page DbCharEncoding Language
(1250) ee8mswin1250 (Croatian, Czech, Hungarian, Polish, Romanian, Slovak, and Slovenian)
(1251) c18mswin1251 (Bulgarian, Russian, and Ukranian)
(1252) we8mswin1252 (English (United States), Catalan, Danish, Dutch (Netherlands), English (United Kingdom), Finish, French (France), German (Germany), Icelandic, Italian (Italy), Malay (Malaysia), Norwegian (Bokmal), Portuguese (Brazil), Portuguese (Portugal), Spanish (Mexico), Spanish (Spain), and Swedish)
(1253) el8mswin1253 (Greek)
(1254) tr8mswin1254 (Turkish)
(1255) iw8mswin1255 (Hebrew)
(1256) ar8mswin1256 (Arabic (Egypt), and Arabic (UAE))
(1257) blt8mswin1257 (Estonian and Lithuanian)
(932) ja16sjis (Japanese)
(936) zhs16gbk (Chinese (PRC) and Chinese (Singapore))
(949) ko16mswin949 (Korean)
(950) zht16mswin950 (Chinese (Taiwan) and Chinese (Hong Kong))

I.2.4 MAXINDEXCOLUMNS

Defines the number of columns used in the index creation statement. For more information, see Index Creation Options, in the Oracle Database Lite SQL Reference.

I.2.5 NLS_DATE_FORMAT

Allows you to use a date format other than the Oracle Database Lite default. When a literal character string appears where a date value is expected, the Oracle Database Lite tests the string to see if it matches the formats of Oracle, SQL-92, or the value specified for this parameter in the POLITE.INI file. Setting this parameter also defines the default format used in the TO_CHAR or TO_DATE functions when no other format string is supplied.

For Oracle, the default is dd-mon-yy or dd-mon-yyyy. For SQL-92, the default is yy-mm-dd or yyyy-mm-dd.

Using RR in the format forces two digit years less than or equal to 49 to be interpreted as years in the 21st century (2000–2049), and years 50 and over, as years in the 20th century (1950–1999). Setting the RR format as the default for all two digit year entries allows you to become year-2000 compliant. For example,

NLS_DATE_FORMAT='RR-MM-DD'

You can also modify the date format using the ALTER SESSION command. For more information, see the Oracle Database Lite SQL Reference.

I.2.5.1 Date Format

A date format includes one or more of the elements listed in the following table. Elements that represent similar information cannot be combined, for example, you cannot use SYYYY and BC in the same format string. Table I-2 lists date formats and their corresponding description.

Table I-2 Date Formats

Format Description
AM or P.M. Meridian indicator, periods are optional.
PM or P.M. Meridian indicator, periods are optional.
CC or SCC Century, "S" prefixes BC dates with "-".
D Day of week.
DAY Name of day, padded with blanks to length of 9 characters.
DD Day of month (1-31).
DDD Day of year (1-366).
DY Abbreviate name of day.
IW Week of year (1-52 or 1-53) based on the ISO standard.
IYY, IY, or I Last 3, 2, or 1 digit(s) of the ISO year, respectively.
IYYY 4-digit year, based on the ISO standard.
HH or HH12 Hour of the day (1-12).
HH24 Hour of the day (0-23).
MI Minute (0-59).
MM Month (01-12, for example, JAN=01).
MONTH Name of the month, padded with blanks to length of 9 characters.
MON Abbreviated name of the month.
Q Quarter of the year, (1,2,3,4, for example, JAN-MAR=1).
RR Last 2 digits of the year, for years in other countries. This forces two-digit years less than or equal to 49 to be interpreted as years in the 21st century (2000-2049), and years 50 and over, as years in the 20th century (1950-1959).
WW Week of the year (1-53), where 1 starts on the first day of the year and continues to the seventh day of the year.
SS Second (0-59).
SSSSS Seconds past midnight (0-86399).
Y or YYY Year with comma in this position.
YEAR or SYEAR Year, spelled out. "S" prefixes BC dates with "-".
YYYY or SYYYY 4-digit year. "S" prefixes BC dates with "-".
YYY, YY, or Y Last 3, 2, or 1 digit(s) of the year.

I.2.5.2 Date Format Examples

Listed below are sample variations of the NLS_DATE_FORMAT parameter.

  1. YYYY-MONTH-DAY:HH24:MI:P.M.

  2. YYYY/MONTH/DD, HH24:MI A.M.

  3. YYYY-MONTH-DAY:HH24:MI:PM

  4. MM D, YYY, HH:MI A.M.

  5. MM, WW, RR, HH:MI A.M.

  6. MM, IW, RR, HH:M1 A.M.

  7. MM, DY, RR, HH:MI A.M.

  8. MM; DY; IYY, HH:MI A.M.

  9. MON WW, RR, HH:MI A.M.

  10. MONTH.DD, SYYYY, HH:MI A.M.

  11. MONTH/DD, YYYY, HH:MI A.M.

  12. MONTH|DD, YYYY, HH:MI A.M.

  13. MONTH DD, YYYY, HH:SSSSS:MI A.M.

  14. MONTH DD, HH:SS::MI CC

  15. MONTH DD, HH:SS:MI SCC

  16. MONTH W, YYYY, HH:MI A.M.

  17. MONTH WW, YYYY, HH:MI A.M.

  18. MONTH WW, RR, HH:MI A.M.

  19. MONTH WW, Q, HH:MI A.M.

  20. MONTH WW, RR, HH:MI A.M.

I.2.6 NLS_LOCALE

Defines the NLS_LOCALE parameter in the POLITE.INI file to specify the locale data of Oracle Database Lite. Oracle Database Lite locale data includes the following items.

  • Decimal character and group separator

  • Locale currency symbol and ISO currency symbol

  • Day, week, month names, and their abbreviations

For example, NLS_LOCALE=FRENCH_FRANCE specifies the locale data of french_french in Oracle Database Lite. Table I-3 describes the supported locale and corresponding values of the NLS_LOCALE setting.

Table I-3 Supported Locales and Values

Locale NLS_LOCALE
English (United States) AMERICAN_AMERICA
Arabic (Egypt) ARABIC_EGYPT
Arabic (UAE) ARABIC_UNITED ARAB EMIRATES
Bulgarian BULGARIAN_BULGARIA
Catalan CATALAN_CATALONIA
Chinese (PRC) SIMPLIFIED CHINESE_CHINA
Chinese (Singapore) SIMPLIFIED CHINESE_SINGAPORE
Chinese (Taiwan) TRADITIONAL CHINESE_TAIWAN
Chinese (Hong Kong) TRADITIONAL CHINESE_HONG KONG
Croatian CROATIAN_CROATIA
Czech CZECH_CZECH REPUBLIC
Danish DANISH_DENMARK
Dutch (Netherlands) DUTCH_THE NETHERLANDS
English (United Kingdom) ENGLISH_UNITED
Estonian ESTONIAN_ESTONIA
Finnish FINNISH_FINLAND
French (France) FRENCH_FRANCE
German (Germany) GERMAN_GERMANY
Greek GREEK_GREECE
Hebrew HEBREW_ISRAEL
Hungarian HUNGARIAN_HUNGARY
Icelandic ICELANDIC_ICELAND
Italian (Italy) ITALIAN_ITALY
Japanese JAPANESE_JAPAN
Korean KOREAN_KOREA
Lithuanian LITHUANIAN_LITHUANIA
Malay (Malaysia) MALAY_MALAYSIA
Norwegian (Bokmal) NORWEGIAN_NORWAY
Polish POLISH_POLAND
Portuguese (Brazil) BRAZILIAN PORTUGUESE_BRAZIL
Portuguese (Portugal) PORTUGUESE_PORTUGAL
Romanian ROMANIAN_ROMANIA
Russian RUSSIAN_CIS
Slovak SLOVAK_SLOVAKIA
Slovenian SLOVENIAN_SLOVENIA
Spanish (Mexico) MEXICAN SPANISH_MEXICO
Spanish (Spain) SPANISH_SPAIN
Swedish SWEDISH_SWEDEN
Turkish TURKISH_TURKEY
Ukrainian UKRANIAN_UKRAINE

I.2.7 NLS_SORT

This parameter can be used to define the collation sequence for databases created on the Oracle Database Lite instance. Collation is referred as ordering strings into a culturally acceptable sequence. A collation sequence is a sequence of all collation elements from an alphabet from the smallest collation order to the largest.

NLS_SORT=[collation sequence]

When this parameter is used, all databases created with the CREATEDB command line utility or those that are replicated from the Mobile Server are enabled for the collation sequence unless a different collation sequence is specified when using the utility. Languages currently supported are BINARY (default), FRENCH, GERMAN, CZECH, and XCZECH.


Note:

Unless you require your databases to have linguistic sort enabled for a supported collation sequence, it is recommended that you use the CREATEDB utility with the NLS_SORT <collation sequence> parameter, which overrides this POLITE.INI parameter. Setting the NLS_SORT using the POLITE.INI file means that your databases have the specified collation sequence enabled. There is currently no way to convert a database from one collation sequence to another.

For a complete description of this feature, see Section 3.3, "CREATEDB," in the Oracle Database Lite Tools and Utilities Guide.

I.2.8 ReverseJoinOrder

Specifies the order of tables joined for a query. Options are TRUE or FALSE. If set to TRUE, the tables are joined in the reverse order in which they are given in the FROM clause. If FALSE, the tables are joined in the same order as they are given in the FROM clause. If not set, the Oracle Database Lite query optimizer determines the optimal join order. This option is recommended for advanced use as it disables the JOIN optimization for all queries. To optimize a single query, it is suggested that you use HINTS instead. For more information, see the Oracle Database Lite SQL Reference.

I.2.9 SharedAddress

To manage the data needed across applications, Oracle Database Lite uses shared memory. Oracle Database Lite attaches the shared memory at a specific location of the process memory. In very few cases, this location may already be in use by other tools resulting in an error. To address this issue, Oracle Database Lite supports the following protocol to determine the memory address to attach for shared memory.

Before attaching shared memory, Oracle Database Lite examines the SharedAddress and SuggestedSharedAddress variables that specify a hexadecimal 32-bit address (for example, 18000000). Oracle Database Lite uses the first value it finds. If you do not set either variable, Oracle Database Lite first tries the address 30000000. This value is above the range used by most applications.

If an Oracle Database Lite client is already running, and the second process cannot get the same shared memory address, it fails with an error. However, it also finds an address that is available in the second process and writes it to the POLITE.ini file as the SuggestedSharedAddress. If the user exits all Oracle Database Lite clients and runs the same mix of applications, the problem does not reoccur.

If automatic conflict resolution fails, you should modify the SharedAddress variable until you resolve the issue. For example, you can try values spaced by 256 MB: 20000000, 24000000, 28000000, and so on.

I.2.10 SuggestedSharedAddress

For a detailed description, see SharedAddress.

I.2.11 SQL Compatibility

Oracle Database Lite supports both Oracle SQL and SQL-92 features. For more information on Oracle SQL and SQL-92, see the Oracle Database Lite SQL Reference.

If there is a conflict between Oracle SQL and SQL-92, the SQLCompatibility flag is referenced. If you specify ORACLE for the parameter, Oracle SQL is favored, and if you specify SQL92, SQL-92 is favored. If you do not include this parameter in the POLITE.ini, Oracle SQL is favored, by default.

I.2.12 TempDB

The temporary database is created by default in the main memory. This improves the performance of some queries that require the use of temporary tables. Unless you explicitly choose to create the temporary database in the file system, the poltempx.odb files are not created. The *.slx files that are sometimes used to store savepoint information are also not created. If you plan to create a large result set, you must either have enough swap space to hold the result, or choose the file option for the temporary database.

To include this option, use the following syntax in the POLITE.INI file.

TempDB=<path temporary_database_name>

For example,

TempDB=c:\temp\olite_

As a result of the example setting, Oracle Database Lite creates temporary databases as given below.

c:\temp\olite_0.odb, c:\temp\olite_1.odb, ...

I.2.13 TempDir

Specifies the directory where the temporary database POLTEMP.ODB is created. If not set, the default is any TEMP, TMP or WINDIR setting defined in your environment.

I.2.14 OLITE_SQL_TRACE

Generates the SQL statement text, compilation time, execution plan, and the bind value.

For example,

OLITE_SQL_TRACE= yes

SQL trace output is dumped to a trace file named oldb_trc.txt in the current working directory of the database process. For a database service on Windows, Windows NT or the Oracle Database Lite daemon for a Linux platform, the current working directory is specified by the wdir parameter during the database startup service or daemon. Applications that use an embedded connection to connect to the database contain a working directory. This working directory is the application's working directory. To implement the tracing feature, the database process must contain permissions to create the trace file in the current working directory. The trace output is always included in the trace file. If the trace file does not exist, it is created automatically.

I.2.15 FLUSH_AFTER_WRITE

Syntax

FLUSH_AFTER_WRITE={YES|TRUE|FALSE|NO}

Default Value

FALSE

By default, the parameter FLUSH_AFTER_WRITE is disabled. Hence, writes to a database are not flushed. The last write operation during a COMMIT operation always flushes file buffers, thereby eliminating the danger of losing data. For devices that are unreliable, users can enable this flag and set the parameter to TRUE or YES. When enabled, every write action flushes file buffers. However, this setting degrades the database COMMIT performance.


Note:

This parameter applies to the WinCE platform only.

I.3 Sample POLITE.INI File

The following content is displayed from a sample POLITE.INI file.

[All Databases]
DatabaseID=128
DBCharEncoding=NATIVE
SuggestedSharedAddress=10270000
CacheSize=4096
MAXINDEXCOLUMNS=5
SQLCompatibility=SQL92
NLS_Date_Format=RR/MM/DD H24,MI,SS
NLS_Locale=ENGLISH
TempDB=c:\temp\olite_
TempDir=D:\TMP

On the WinCE platform, include the parameter DATADIRECTORY=\Storage Card:\Orace:\tmp. To synchronize, run mSync.exe.