LiveCycle Product Blog

The current release of LiveCycle ES (8.0.1) is supported on Oracle 9i and 10g, but not on 11g. Oracle RAC (Real Application Cluster) will work for LiveCycle. However, the appserver system administrator is responsible for coming up with the correct connection string with help from the Oracle RAC DBA. Here's a sample (make changes to fit your environment):

jdbc:oracle:thin:@(DESCRIPTION= (ENABLE=broken) (ADDRESS_LIST= (ADDRESS= (PROTOCOL=TCP) (HOST=yourhost1) (PORT=1521) ) (ADDRESS= (PROTOCOL=TCP) (HOST=yourhost2) (PORT=1521) ) (LOAD_BALANCE=on) (FAILOVER=on) ) (CONNECT_DATA= (SERVER=dedicated) (SERVICE_NAME=service.yourcompany.com) (FAILOVER_MODE= (TYPE=session) (METHOD=basic) (RETRIES=10) (DELAY=3) ) ))

Minimum required storage is 300 MB, 500 MB is better.

Sample scripts to create a tablespace and a login could look like this, assuming that a temporary tablespace called "LC_TEMP" has already been created:

Create Tablespace
----------------------
Two data files with 500 MB each, set to grow unlimited in 10 MB increments. Make changes as appropriate.

CREATE SMALLFILE TABLESPACE "BLADERUNNER" DATAFILE 'D:\ORACLE_DATA\bladeruuner1.dat' SIZE 500M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED , 'D:\ORACLE_DATA\bladerunner2.dat' SIZE 500M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO

Create User
--------------
Assign the roles 'CONNECT' and 'RESOURCE' plus the system privilege 'CREATE VIEW'.

CREATE USER "BLADERUNNER" PROFILE "DEFAULT" IDENTIFIED BY "*******" DEFAULT TABLESPACE "BLADERUNNER" TEMPORARY TABLESPACE "LC_TEMP" ACCOUNT UNLOCK
GRANT CREATE VIEW TO "BLADERUNNER"
GRANT "CONNECT" TO "BLADERUNNER"
GRANT "RESOURCE" TO "BLADERUNNER"

Supported character sets are AL32UTF8 or AL16UTF16. Other character sets are currently not supported.

Oracle whitepaper on Unicode support.

Bootstrapping (initializing the LiveCycle database) will fail with an UnknownLocalException if the Oracle instance parameter NLS_LENGTH_SEMANTICS is not configured as ‘BYTE’. In many non-English locales, this might be configured as 'CHAR'. If possible, re-set this to BYTE and restart Oracle. If this is not possible, LiveCycle might require its own dedicated Oracle instance.