Palantir Learning Center
 Government Knowledge Base > Palantir Government Knowledge Base > Servers and Administration > Using Oracle XE for the Palantir revisioning database
Summary Oracle XE limitations
Applies To Oracle XE
Article #
8617986


Oracle Database 10g Express Edition (Oracle Database XE) is an entry-level, small-footprint database based on the Oracle Database 10g Release 2 code base that's free to develop, deploy, and distribute; fast to download; and simple to administer. Oracle Database XE is available for 32-bit Linux and Windows operating systems.

Oracle Database XE can be downloaded from the Oracle Technology Network: http://www.oracle.com/technology/software/products/database/index.html

Palantir has tested Oracle XE as the backend database for the Palantir platform.  There are, however, some limitations and restrictions when using Oracle XE that do not apply to a Oracle Standard Edition or Enterprise Edition 10g R2 installation.

Oracle XE limitations
  • The first limitation is memory---Oracle Database XE can address only 1GB of RAM. But when you consider the relative rarity of machines that offer 1GB of memory  this limitation should mainly affect how many users can access the database concurrently and, to a certain degree, how well it will perform when those limits are hit.
  • The second limitation is that XE will only use one CPU. That does not mean that it won't multi-task or that it can only perform a single function at a time. Rather, XE will run on a computer with more than one CPU, it just won't scale up to use those CPUs. For that functionality, you need to purchase Oracle Database Standard Edition or Enterprise Edition.
  • The third limitation is that only a single XE database can run on any given computer. The important point here is that you don't need a database for each application you create, as you might for some competing databases. Instead, Oracle uses the concept of schemas to separate applications. 
  • The fourth limitation is that a 4GB limit is enforced on disk space---which on its face appears to be a serious limitation. However, 4GB is a huge amount of storage for most applications.
  • The fifth limit is that Oracle XE does not support Java stored procedures.
NOTE
The SID, as specified in the dispatch.prefs file, must be "XE" (no quotes)

The Palantir platform contains one Java stored procedure that it attempts to install during the database seeding process.  When you are running the SQL scripts to seed the database, you will see this error;

CREATE OR REPLACE AND RESOLVE JAVA SOURCE NAMED "PalantirId" AS

*

ERROR at line 1:

ORA-29538: Java not installed

ALTER JAVA SOURCE "PalantirId" COMPILE

*

ERROR at line 1:

ORA-29538: Java not installed
This error can be safely ignored as the stored procedure is there only for development debugging.

The Palantir platform requires that the backend database be configured with the AL32UTF8 variable-length character encoding for Unicode. This is the default charset when using the default install for OracleXEUniv.

Warning
Do not install the database using the file, OracleXE.exe. That version of Oracle XE is a single-byte LATIN1 database for Western European language storage, and does not support the Unicode charset required by Palantir.

Copyright 2012 Palantir Technologies