Oracle® Fusion Middleware

System Requirements and Specifications

11g Release 1 (11.1.1)
E18558-01
November 18, 2010

This document contains system and platform-specific information for Oracle Fusion
Middleware products.
The following topics are covered in this document:
■ Section 1, "Finding Oracle Fusion Middleware Certification Information"
■ Section 2, "Oracle Fusion Middleware System Requirements"
■ Section 3, "Oracle Universal Installer (OUI) Requirements"
■ Section 4, "System Requirements for UNIX Operating Systems"
■ Section 5, "Certified Windows Operating Systems"
■ Section 6, "Oracle WebLogic Server Information"
■ Section 7, "Certified Databases"
■ Section 8, "Repository Creation Utility (RCU) Requirements"
■ Section 9, "Documentation Accessibility"

1 Finding Oracle Fusion Middleware Certification Information

If you are looking for latest certification information for current and previous releases,
go to the Oracle Fusion Middleware Supported System Configurations page:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certi
fication-100350.html

The "System Requirements and Supported Platforms for Oracle Fusion Middleware
11gR1" document contains certification information related to supported 32-bit and
64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs,
and third-party products.

2 Oracle Fusion Middleware System Requirements

This section contains the minimum memory and disk space requirements for Oracle
Fusion Middleware products. The following topics are covered:
■ Section 2.1, "General Memory Requirements"
■ Section 2.2, "Oracle SOA and Oracle BAM Requirements"
■ Section 2.3, "Oracle BAM Client Requirements"
■ Section 2.4, "Oracle Portal, Forms, Reports and Discoverer Requirements"

1
■ Section 2.5, "Oracle Identity Management Memory and Disk Space Requirements"
■ Section 2.6, "Oracle Business Intelligence Requirements"
■ Section 2.7, "Oracle Data Integrator Requirements"
■ Section 2.8, "Oracle Data Profiling and Data Quality Requirements"

2.1 General Memory Requirements

Unless otherwise noted, Table 1 lists the general minimum memory requirements for
Oracle Fusion Middleware products:

Table 1 Memory Requirements

Minimum Physical Memory Minimum Available Memory
Operating System Required Required
Linux 2 GB 1 GB
UNIX 2 GB 1 GB
Windows 2 GB 1 GB

2.2 Oracle SOA and Oracle BAM Requirements

Below are the recommended hardware and system configuration requirements for
Oracle SOA and Oracle BAM:
■ CPU: dual-core Pentium, 1.5GHz or greater
■ Disk Space: 15GB or more
■ Available Memory: 4GB or more

2.3 Oracle BAM Client Requirements

Table 2 shows the general requirements for the Oracle BAM client.

Table 2 Oracle BAM Client Requirements

Category Requirements
Platforms (Microsoft Microsoft Windows XP Professional, Service Pack 2 or higher
Windows Intel x86-32)
Microsoft Windows Vista
Web Browsers Microsoft Internet Explorer 7.x
Microsoft Internet Explorer 8.x
Hardware 1 CPU at 1.2 GHz or faster minimum (a faster processor may be
necessary to view complex dashboards)
512MB RAM minimum
5MB of free disk space
Display Oracle BAM Active Studio requires 1024 x 768 minimum resolution
Oracle BAM Active Viewer requires 800 x 600 or higher resolution

2
2.3.1 Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or
Oracle BAM Active Studio
The Oracle BAM Excel view type requires that Microsoft Excel version XP, 2003, or
2007 is installed on the client computer.

2.3.2 Additional Notes for Microsoft Internet Explorer

If you are using the Microsoft Windows pop-up blocker, or any other tool that blocks
pop-up browser windows, you must configure it to allow pop-up windows while
using the Oracle BAM Web applications. Turn off pop-up blockers in Microsoft
Internet Explorer for the URL on which the Oracle BAM Web applications are hosted.
The Microsoft Internet Explorer installation on client systems must be a standard
version, and it must not include customizations such as add-in tool bars or hot bars for
other Web sites.

2.4 Oracle Portal, Forms, Reports and Discoverer Requirements

Below are the recommended hardware and system configuration requirements for
Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1):
■ Disk Space: 15GB or more
■ Available Memory: 4GB or more

Note: On some Windows 32-bit operating systems, the available

memory is limited to 3GB. For components that are certified on such
systems, Oracle recommends using the /3GB switch, as specified in
Microsoft Knowledge Base Article #291988.
For more information, see the certification information, as described in
Section 1, "Finding Oracle Fusion Middleware Certification
Information".

■ Temp Space: 150MB or more

■ Swap Space: 512MB or more
If you are upgrading Oracle Portal, Forms, Reports and Discoverer from Oracle
Application Server Release 10g (10.1.2.0.2), below are the recommended hardware and
system configuration requirements:
■ Disk Space: 21GB or more
■ Available Memory: 6GB or more
■ Temp Space: 950MB or more
■ Swap Space: 3GB or more

2.5 Oracle Identity Management Memory and Disk Space Requirements

The specific memory requirements for your Oracle Identity Management 11g Release 1
(11.1.1) deployment depends on which components, or combination of components,
you install. The following list identifies memory requirements for various components.
Use the list as a guideline for determining the memory requirements specific to your
deployment:

3
■ WebLogic Administration Server: 750 MB
■ WebLogic Managed Server running Oracle Directory Integration Platform and
Oracle Directory Services Manager: 720 MB
■ WebLogic Managed Server running Oracle Identity Federation: 650 MB
■ Oracle Internet Directory: 75 MB
■ Oracle Virtual Directory: 105 MB
■ Oracle Enterprise Manager (EM) Agent: 25 MB
■ Oracle Process Manager and Notification Server (OPMN): 5 MB
Oracle Identity Management requires 2,200 MB of disk space if you are only installing
the software (you select the Install Software - Do Not Configure installation type). If
you configure the software, an additional 150 MB of space are required if all
components are selected for configuration; less space is required if fewer components
are selected.

2.6 Oracle Business Intelligence Requirements

This section contains important information for the system on which you are installing
Oracle Business Intelligence and the database containing the schemas.

2.6.1 Installation System Requirements

Below are the recommended hardware and system configuration requirements for an
Oracle Business Intelligence installation on Linux and 32-bit Windows operating
systems:
■ Disk Space: 20GB or more
■ Available Memory: 4GB or more
■ Temp Space: 950MB or more
■ Swap Space: 3GB or more
■ CPU: dual-core Pentium, 1.5GHz or greater

2.6.2 Database Requirements

Below are the recommended disk space requirements for the database containing the
Oracle Business Intelligence Scheduler database tables.
■ 500MB on Oracle and Microsoft SQL Server databases for standalone and Business
Intelligence applications and deployments.
■ 500MB on IBM DB2 databases for standalone deployments.

2.7 Oracle Data Integrator Requirements

Below are the recommended hardware and system configuration requirements for
Oracle Data Integrator Studio and Standalone Agents:
■ CPU: dual-core Pentium, 1.5GHz or greater
■ Disk Space: 5GB or more
■ Available Memory: 2GB or more

4
2.7.1 Additional Requirements for Oracle Data Integrator JEE Components
JEE Components require the presence of Oracle WebLogic Server on your system. The
Oracle WebLogic Server requirements apply to these components.

2.7.2 Database Requirements

Below are the recommended storage space requirements for the database containing
the Oracle Data Integrator Repository tables:
■ Master Repository: 60 Mb of storage space.
■ Work Repository: 80 Mb of storage space.

Note: The storage space required may vary depending on the size of
your models and projects, and on the volume of execution logs you
keep in this repository.

2.8 Oracle Data Profiling and Data Quality Requirements

This section contains the requirements for Oracle Data Profiling and Oracle Data
Quality for Data Integrator.

2.8.1 Oracle Data Quality Client Requirements

Below are the recommended hardware and system configuration requirements for the
Oracle Data Quality Client:
■ CPU: dual-core Pentium, 1.5GHz or greater
■ Disk Space: 500MB or more
■ Available Memory: 512MB or more

2.8.2 Oracle Data Profiling and Quality Server Requirements

Below are the recommended hardware and system configuration requirements for the
Oracle Data Profiling and Quality Server:
■ CPU: The CPU Requirement for Oracle Data Profiling and Quality Servers are
listed in Table 3.
■ Disk space: 1.5GB or more.

Note: Disk usage for the postal tables and for data processing should
be taken into account in addition to this space. The amount of space
used by postal table varies according to the countries and options you
purchase. The amount of space used for data processing varies
according to your data volume.

■ Available memory: 2GB or more. 4GB is recommended (8GB for a power server).

Table 3 CPU Requirements for Oracle Data Profiling and Quality Server
Minimum
Platform Server CPU Processor
IBM AIX RS/6000 900 MHz eServerP5 and pSeries
Platform Power 5

5
Table 3 (Cont.) CPU Requirements for Oracle Data Profiling and Quality Server
Minimum
Platform Server CPU Processor
Sun Solaris Sun Sparc 900 MHz Ultrasparc IV
HP-UX (PA Risc) HP PA RISC (PA 2.0) 750 MHz PA RISC PA 8800
HP-UX (IA64/Itanium) HP Itanium (IA 64) 1.4 GHz Intel Itanium 2
Linux and Windows Any 3 GHz Intel Xeon MP

2.8.3 Additional Requirements for Servers

The Inetd (XInetd for Linux) component is required and must be installed on UNIX
servers.

3 Oracle Universal Installer (OUI) Requirements

This section contains prerequisite information for the Oracle Universal Installer (OUI).
The requirements in this section must be met in order for the installer to start:
■ Section 3.1, "Environment Variables"
■ Section 3.2, "Startup Requirements"
■ Section 3.3, "Special Startup Requirements for Linux x86 or Linux x86-64
Operating Systems"

3.1 Environment Variables

The environment variables on your system must be set as described in Table 4:

Table 4 Oracle Universal Installer Environment Variable Requirements

Variable Description
ORACLE_HOME Applies to: all configuration tools for all products on all platforms.
This variable is automatically set by the configuration tool to the
Oracle home from where the configuration tool is started. This is true
even if the ORACLE_HOME variable is already set.
ORACLE_SID Applies to: all installers for all products on all platforms.
For the Oracle Portal, Forms, Reports and Discoverer installer, this
variable must not be set.
For all other installers, there are no restrictions as to whether this
variable is set or not set.
PATH Applies to: all installers for products with system components only
on Windows operating systems.
This variable is automatically set by the installer and prepended with
ORACLE_HOME\bin.
SHLIB_PATH Applies to: all installers for products with system components only
on HP-UX and HP-IA operating systems.
This variable is automatically set by the installer and prepended with
ORACLE_HOME/lib.

6
Table 4 (Cont.) Oracle Universal Installer Environment Variable Requirements
Variable Description
LIBPATH Applies to: all installers for products with system components only
on AIX operating systems.
This variable is automatically set by the installer and prepended with
ORACLE_HOME/lib.
LD_LIBRARY_PATH Applies to: all installers for products with system components only
on Linux and Solaris operating systems.
This variable is automatically set by the installer and prepended with
ORACLE_HOME/lib.
DISPLAY Applies to: all installers for all products on all platforms.
If you are installing with a graphical user interface (GUI), this
variable must be set to the monitor where you want the installer GUI
to appear.
TMP Applies to: all installers for all products on all platforms.
TMPDIR Optional variable. If not set, then the default value is /tmp.
TNS_ADMIN Applies to: all installers for all products on all platforms.
ORA_NLS For the Oracle Portal, Forms, Reports and Discoverer installer, these
variables must not be set.
LD_BIND_NOW
For all other installers, there are no restrictions as to whether these
variables are set or not set.

3.2 Startup Requirements

The items in Table 5 are checked as the installer is being started:

Table 5 Oracle Universal Installer Startup Requirements

Category Accepted or Minimum Values
Platforms For a complete list of supported platforms, refer to the Oracle
Fusion Middleware Certification Document:
http://www.oracle.com/technology/software/produc
ts/ias/files/fusion_certification.html
CPU Speed At least 300MHz
Temp Space At least 270MB
Swap Space At least 500MB
Monitor At least 256 colors

3.3 Special Startup Requirements for Linux x86 or Linux x86-64 Operating
Systems
If you are running Oracle Universal Installer on Linux x86 or Linux x86-64 operating
systems, refer to Note 468051.1 on My Oracle Support for special information:
1. Access and log into My Oracle Support at the following location:
https://support.oracle.com/

2. In the Search Knowledge Base field (upper right portion of the page), enter
"468051.1" into the field, then click the search icon.

7
3. Click on the article titled "OUI-15038 Occurs During The Oracle11g Product
Specific Prerequisite Checks".

4 System Requirements for UNIX Operating Systems

This section contains system requirement information for UNIX systems. The
following topics are covered:
■ Section 4.1, "System Requirements"
■ Section 4.2, "Open File Limit"

4.1 System Requirements

Table 6 lists the platform, operating system, package, and patch information for UNIX
operating systems that are either currently supported or were supported in a previous
release.
In some cases, a particular platform may be de-supported for use with Oracle Fusion
Middleware products. While this particular platform’s requirements may remain in
this document for legacy purposes, it would no longer be listed in the Oracle Fusion
Middleware Certification Document. Be sure to consult the Oracle Fusion Middleware
Certification Document for the latest certification information:
http://www.oracle.com/technology/software/products/ias/files/fusion_
certification.html

All packages listed are minimum versions.

8
Table 6 Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Linux x86 Oracle Enterprise gcc-3.4.3-22.1 Kernel 2.6.9
Linux 4
gcc-c++-3.4.3-22.1
Red Hat Linux 4
openmotif21-2.1.30-11.RHEL4.4
setarch-1.6-1
pdksh-5.2.14-30
sysstat-5.0.5-1
gnome-libs-1:1.4.1.2.90-44.1
libaio-0.3.105
libaio-devel-0.3.105
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
control-center-2.8.0-12
glibc-common-2.3.4-2.9
binutils-2.15.92.0.2-13
make-1:3.80-5
xscreensaver-4.18-5.rhel4.2
openmotif22-2.2.3 (for Oracle Reports
Server)
openmotif-2.2.3 (for Oracle Reports Server)
Linux x86 Oracle Enterprise gcc-4.1.0-28.4 Kernel 2.6.18
Linux 5
gcc-c++-4.1.0-28.4
Red Hat Linux 5
setarch-1.6-1
sysstat-5.0.5-1
libaio-0.3.106
libaio-devel-0.3.106
libstdc++-4.1.0-28.4
libstdc++-devel-4.1.0-28.4
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
control-center-2.8.0-12
glibc-common-2.3.4-2.9
binutils-2.16.91.0.5-23.4
make-3.80-202.2
openmotif22-2.2.3 (for Oracle Reports
Server)
openmotif-2.2.3 (for Oracle Reports Server)

9
Table 6 (Cont.) Supported UNIX Operating Systems
Operating System
Platform Version
Linux x86 SUSE 10
Linux x86 SUSE 11
Operating
System
Supported Packages Patches
gcc-4.1.0-28.4 Kernel
2.6.16.21
glibc-devel-2.4-31.2
gcc-c++-4.1.0-28.4
libaio-0.3.104
libaio-devel-0.3.104
libgcc-4.1.0-28.4
libstdc++-devel-4.1.0-28.4
libstdc++-4.1.0-28.4
binutils-2.16.91.0.5-23
compat-libstdc-296-2.96-132.7.21
compat-libstdc++-5.0.7-22.2
compat-2006.1.25-11.2
make-3.80-202.2
openmotif21-libs-2.1.30
openmotif-2.2.3 (for Oracle Reports Server)
binutils-2.19-11.28 Kernel
2.6.27.19-5-def
gcc-4.3-62.198
ault
gcc-c++-4.3-62.198
glibc-2.9-13.2
glibc-devel-2.9-13.2
libaio-0.3.104-140.22
libaio-devel-0.3.104-140.22
libgcc43-4.3.3_20081022-11.18
libstdc++43-4.3.3_20081022-11.18
libstdc++43-devel-4.3.3_20081022-11.18
make-3.81-128.20
sysstat-8.1.5-7.8
openmotif22-libs-2.2.4-138.17 (for Oracle
Reports)2
openmotif-2.3.1-3.132
openmotif21-libs-2.1.30MLI4-143.92
openmotif-libs-2.3.1-3.132
openmotif-devel-2.3.1-3.132
10
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Linux Oracle Enterprise binutils-2.15.92.0.2 Kernel 2.6.9
x86-64 Linux 4
compat-libstdc++-33-3.2.3
Red Hat Linux 4
compat-libstdc++-33-3.2.3 (32-bit)
elfutils-libelf-0.97
elfutils-libelf-devel-0.97
gcc-3.4.5
gcc-c++-3.4.5
glibc-2.3.4-2.19
glibc-2.3.4-2.19 (32-bit)
glibc-common-2.3.4
glibc-devel-2.3.4
glibc-devel-2.3.4 (32-bit)
libaio-0.3.105
libaio-0.3.105 (32-bit)
libaio-devel-0.3.105
libgcc-3.4.5
libgcc-3.4.5 (32-bit)
libstdc++-3.4.5
libstdc++-3.4.5 (32-bit)
libstdc++-devel 3.4.5
make-3.80 sysstat-5.0.5
openmotif21-2.1.30-11.RHEL4.4 (for Oracle
Portal, Forms, Reports and Discoverer)
openmotif-2.2.3 (for Oracle Reports Server)

11
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Linux Oracle Enterprise binutils-2.17.50.0.6 Kernel 2.6.18
x86-64 Linux 5
compat-libstdc++-33-3.2.3
Red Hat Linux 5
compat-libstdc++-33-3.2.3 (32-bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12
glibc-2.5-12 (32-bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5-12 (32-bit)
libaio-0.3.106
libaio-0.3.106 (32-bit)
libaio-devel-0.3.106
libgcc-4.1.1
libgcc-4.1.1 (32-bit)
libstdc++-4.1.1
libstdc++-4.1.1 (32-bit)
libstdc++-devel 4.1.1
make-3.81 sysstat-7.0.0
openmotif22-2.2.3 (for Oracle Reports
Server)
openmotif-2.2.3 (for Oracle Reports Server)

12
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Linux SUSE 10 binutils-2.16.91.0.5 Kernel
x86-64 2.6.16.21
compat-libstdc++-5.0.7-22.2
gcc-4.1.0 gcc-c++-4.1.0
glibc-2.4-31.2
glibc-32bit-2.4-31.2 (32-bit)
glibc-devel-2.4
glibc-devel-32bit-2.4 (32-bit)
libaio-0.3.104
libaio-0.3.106 (32 bit)
libaio-devel-0.3.104
libelf-0.8.5
libgcc-4.1.0
libstdc++-4.1.0
libstdc++-devel-4.1.0
make-3.80 sysstat-6.0.2
openmotif21-libs-2.1.30 (for Oracle Portal,
Forms, Reports and Discoverer)
openmotif-2.2.3 (for Oracle Reports Server)

13
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Linux SUSE 11 binutils-2.19-11.28 Kernel
x86-64 2.6.27.19-5-def
gcc-4.3-62.198
ault
gcc-c++-4.3-62.198
glibc-2.9-13.2
glibc-devel-32bit-2.9-13.2
libaio-0.3.104-140.22
libaio-0.3.106 (32 bit)
libaio-devel-0.3.104-140.22
libgcc43-4.3.3_20081022-11.18
libstdc++43-4.3.3_20081022-11.18
libstdc++43-devel-4.3.3_20081022-11.18
make-3.81-128.20
sysstat-8.1.5-7.8
Packages required for Oracle Reports:
openmotif-2.3.1-3.132
openmotif-devel-32bit-2.3.1-3.132
openmotif22-libs-32bit-2.2.4-138.172
openmotif-libs-2.3.1-3.132
openmotif-devel-2.3.1-3.132
openmotif-libs-32bit-2.3.1-3.132
openmotif21-libs-32bit-2.1.30MLI4-143.22
openmotif22-libs-2.2.4-138.172
Solaris Solaris 9 Update 9 SUNWarc, SUNWbtool, SUNWhea 118558-22
SPARC64
SUNWlibC, SUNWlibm, SUNWlibms 112874-39
SUNWsprot, SUNWtoo, SUNWi1of 112760-053
SUNWi1cs, SUNWi15cs, SUNWxwfnt 114370-054
SUNWsprox
Motif: 2.1.0 (for Oracle Portal, Forms,
Reports and Discoverer only)
GCC: package 3.4.2 or higher in
/usr/local/packages (for Oracle
I/PM). The LD_LIBRARY_PATH
environment variable must also be set to
/usr/local/packages/gcc-3.4.2/li
b before starting the Oracle I/PM Managed
Server.

14
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
Solaris Solaris 10 Update 4 SUNWarc, SUNWbtool, SUNWhea 127111-02
SPARC64
SUNWlibC, SUNWlibm, SUNWlibms 137111-04
SUNWsprot, SUNWtoo, SUNWi1of
SUNWi1cs, SUNWi15cs, SUNWxwfnt
Motif: 2.1.0 (for Oracle Portal, Forms,
Reports, and Discoverer only)
GCC: package 3.4.2 or higher in
/usr/local/packages (for Oracle
I/PM). The LD_LIBRARY_PATH
environment variable must also be set to
/usr/local/packages/gcc-3.4.2/li
b before starting the Oracle I/PM Managed
Server.
HP-UX HP-UX 11i v2 (11.23) Motif: 2.1.0 (for Oracle Portal, Forms, PHCO_35524
Itanium Reports, and Discoverer only)
B.11.23.0703.059a PHCO_36673
Base Quality Pack
PHKL_35029
Bundle for HP-UX
11i v2, March 2007 PHKL_35478
PHSS_35978
PHSS_35979
PHSS_37201
HP-UX HP-UX 11i v3 (11.31) Motif: 2.1.0 (for Oracle Portal, Forms, PHKL_36248
Itanium Reports, and Discoverer only)
B.11.31.0803.318a PHKL_36249
Base Quality Pack
PHSS_37202
Bundle for HP-UX
11i v3, March 2008 PHSS_37501
PHCO_38050
PHSS_38139
HP-UX HP-UX 11i v2 (11.23) Motif: 2.1.0 (for Oracle Portal, Forms, PHCO_35524
PA-RISC Reports, and Discoverer only)
B.11.23.0703.059a PHCO_36673
Base Quality Pack
PHKL_35029
Bundle for HP-UX
11i v2, March 2007 PHKL_35478
PHKL_35767
PHKL_36853
PHSS_35101
PHSS_35102
PHSS_35103
PHSS_35176
PHSS_35978
PHSS_35979
PHSS_37201

15
Table 6 (Cont.) Supported UNIX Operating Systems
Operating
Operating System System
Platform Version Supported Packages Patches
HP-UX HP-UX 11i v3 (11.31) Motif: 2.1.0 (for Oracle Portal, Forms, PHKL_36248
PA-RISC Reports, and Discoverer only)
B.11.31.0803.318a PHKL_36249
Base Quality Pack
PHSS_37202
Bundle for HP-UX
11i v3, March 2008 PHSS_37501
PHCO_38050
PHSS_38139
AIX 6100-02 Motif: 2.1.0 (for Oracle Portal, Forms,
Reports, and Discoverer only)
AIX 5300-08 Motif: 2.1.0 (for Oracle Portal, Forms,
Reports, and Discoverer only)
1
This package is required for Oracle Discoverer to work properly, but is not available for SUSE 10. To work
around this issue, you must install compat-libstdc++-296-2.96-132.7.2 or higher from any Red Hat Linux
or Oracle Enterprise Linux distribution.
2
To obtain openmotif packages for SUSE11, go to the public download location
http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz. This
is a single zip file from Novell and includes a README file with details about package names, versions,
and source.
3
"C 5.5: Patch for S1S8CC C compiler" patch required only if the installed version of Studio 11 does not
already include this patch (or a superseded version).
4
Symlink patch required only if the method of installing Solaris 9 Update 9 was via a Solaris Patch Cluster
and that version of the Solaris Patch Cluster did not already include this patch (or a superseded version).

4.2 Open File Limit

In addition to the requirements detailed in Table 6, the Open File Limit should also be
checked. The minimum Open File Limit should be 4096.
The following examples are for Linux systems. Equivalent commands should be
followed for other operating systems.
You can see how many files are open with the following command:
/usr/sbin/lsof | wc -l

To check your open file limits, use the commands below.

For C-shell:
limit descriptors

For Bash:
ulimit -n

To change the open file limits, login as root and edit the
/etc/security/limits.conf file. Look for the following two lines:
* soft nofile 2048
* hard nofile 2048

Change the values from 2048 to 4096, then reboot the machine.

16
5 Certified Windows Operating Systems
Please refer to the Oracle Fusion Middleware Certification Document for the latest
information on certified Windows operating systems:
http://www.oracle.com/technology/software/products/ias/files/fusion_
certification.html

6 Oracle WebLogic Server Information

Most Oracle Fusion Middleware products require the presence of Oracle WebLogic
Server on your system. The version of Oracle WebLogic Server that is required
depends on the version of Oracle Fusion Middleware you are installing. See Table 7 for
more information.
Oracle WebLogic Server can be obtained from the following URL:
http://www.oracle.com/technology/software/products/ias/htdocs/wls_
main.html

Table 7 Required Oracle WebLogic Server Versions

Oracle Fusion Middleware Version
Oracle Fusion Middleware 11g Release 1 (11.1.1)
Oracle Fusion Middleware 11g Release 1 (11.1.1.2)
Oracle Fusion Middleware 11g Release 1 (11.1.1.3)
Required Oracle WebLogic Server
Version
Oracle WebLogic Server 11gR1 (10.3.1)
Oracle WebLogic Server 11gR1 (10.3.2)
Oracle WebLogic Server 11gR1 (10.3.3)

7 Certified Databases
Please refer to the Oracle Fusion Middleware Certification Document for the latest
information on certified databases:
http://www.oracle.com/technology/software/products/ias/files/fusion_
certification.html

This section contains the following topics:

■ Section 7.1, "Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g
(11.2.0.1)"
■ Section 7.2, "Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager"
■ Section 7.3, "Using Oracle Database 11g (11.2.0.1) with OID and Oracle Data Vault"

7.1 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g
(11.2.0.1)
If you are using the version of RCU that is available in Oracle Fusion Middleware 11g
Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1), you will receive the following
warning message:
The database you are connecting is not a supported version. Enter Database
with version equal to or higher than 10.2.0.4.0 in 10g or version equal to
higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for
supported DB versions.

This warning can be safely ignored and you can proceed with your RCU operations.

17
This warning will not appear in the version of RCU available in Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0).

7.2 Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager
If you are using Oracle Database 11g (11.1.0.7) with Oracle Identity Management 11g,
there are certain database patches that must be applied.
See "Patch Requirements for Oracle Database 11g (11.1.0.7)" in the "Oracle Identity
Manager" chapter of the Oracle Fusion Middleware Release Notes for Linux x86 or Oracle
Fusion Middleware Release Notes for Microsoft Windows. Patches for all operating systems
(Linux, 32-bit Windows and 64-bit Windows) are identified.

7.3 Using Oracle Database 11g (11.2.0.1) with OID and Oracle Data Vault
If you are using Oracle Database 11g (11.2.0.1) and you choose to configure Oracle
Internet Directory (OID) with Oracle Data Vault:
1. Apply patch 8897382 (see the README file in the patch for instructions).
2. In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql
(on UNIX operating systems) or ORACLE_HOME\ldap\datasecurity\dbv_
oid_command_rules.sql (on Windows operating systems) file, find the
following code:
/declare
.
begin
.
dvsys.dbms_macadm.CREATE_COMMAND_RULE(
command => 'CONNECT'
,rule_set_name => 'OID App Access'
,object_owner => 'ODS'
,object_name => '%'
,enabled => 'Y');
.
commit;
.
end;/

Change the following line:

,object_owner => 'ODS'

to:
,object_owner => '%'

8 Repository Creation Utility (RCU) Requirements

This section contains the following:
■ Section 8.1, "RCU Supported Platforms"
■ Section 8.2, "Using the AL32UTF8 Character Set"
■ Section 8.3, "RCU Requirements for Oracle Databases"
■ Section 8.4, "RCU Requirements for Microsoft SQL Server Databases"
■ Section 8.5, "RCU Supported Schemas for IBM DB2 Databases"

18
■ Section 8.6, "RCU Prerequisites for IBM DB2 Databases"

8.1 RCU Supported Platforms

RCU is available only on 32-bit x86 Linux and 32-bit Microsoft Windows operating
system platforms. You can run RCU from these machines to connect to any certified
versions of Oracle, IBM DB2, or Microsoft SQL Server database in order to create the
schemas required by Fusion Middleware components. The database server can be
running on any platform that is supported by its respective database.

8.2 Using the AL32UTF8 Character Set

If your database does not use the AL32UTF8 character set, you will see the following
warning when running RCU:
The database you are connecting is with non-AL32UTF8 character set. Oracle
strongly recommends using AL32UTF8 as the database character set.

You can ignore this warning and continue using RCU.

Note: If you are installing Oracle WebCenter or Oracle Identity

Management, you must configure your database to use AL32UTF8
character set encoding. If your database is not already configured to
do so, refer to your database documentation for instructions. If you
are installing a new database, be sure to configure your database to
use AL32UTF8 character set encoding.

8.3 RCU Requirements for Oracle Databases

This section contains information pertaining to running RCU and creating schemas on
Oracle databases. The following topics are covered:
■ Section 8.3.1, "Required Privileges for Oracle Databases"
■ Section 8.3.2, "Setting the nls_length_semantics Parameter in your Oracle
Database"
■ Section 8.3.3, "Applying Oracle Database Patch 8625762 for Oracle Business
Process Management Suite"
■ Section 8.3.4, "Installing Oracle Text for Oracle Portal"
■ Section 8.3.5, "Component-Specific Requirements for Oracle Databases"

8.3.1 Required Privileges for Oracle Databases

If you are creating schemas on an Oracle database, you must have SYSDBA privileges.
For example, you can use the default database user SYS with SYSDBA privileges, or
you must use a database user that has been granted the role of SYSDBA.
If you using a user other than SYS with SYSDBA privileges, you must grant the user
permissions as follows:
GRANT execute on sys.dbms_lock to user_name with grant option

For example, if you have created and are using the user named system, you would
use the following command to grant the necessary privileges to system:
GRANT execute on sys.dbms_lock to system with grant option

19
Refer to your Oracle database documentation for more information about database
users and roles.

8.3.2 Setting the nls_length_semantics Parameter in your Oracle Database

Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_
length_semantics initialization parameter on the database where the schemas
reside must be set to BYTE; setting this parameter to CHAR is not supported.

8.3.3 Applying Oracle Database Patch 8625762 for Oracle Business Process
Management Suite
If you are installing Oracle Business Process Management Suite (part of Oracle SOA
Suite) and you are using an Oracle database, you must apply patch 862576 to avoid
error ORA-03137 and OutOfMemory exception.
You can obtain the patch by specifying the patch ID in My Oracle Support (formerly
MetaLink):
1. Access and log into My Oracle Support at the following location:
http://support.oracle.com/

2. Click the Patches & Updates link.

3. Enter the Patch ID or Number, then click Search. A Patch Search Results table
appears.
4. Using the Release and Platform columns, find the desired patch, then click the
associated Patch ID.
5. In the page that now appears, click the Download button in the right-hand
column.

8.3.4 Installing Oracle Text for Oracle Portal

Oracle Text must be installed on your Oracle Database in order for the Oracle Portal
schema to be configured. To check if Oracle Text is available on your database, use the
following SQL command:
select count(*) from dba_views where owner = 'CTXSYS' and view_name = 'CTX_
VERSION';

The count should be greater than 0. Refer to your Oracle Database documentation for
more information about Oracle Text.

8.3.5 Component-Specific Requirements for Oracle Databases

Table 8 lists all of the supported schemas for Oracle databases, along with any
component-specific prerequisite information that must be met for RCU to be able to
create the schema.
When the tablespaces are created, RCU will automatically create them with the
necessary tablespace sizes.

20
Table 8 RCU Component-Specific Requirements for Oracle Databases
Component Schema Owner Requirement
AS Common Schemas
Metadata Services prefix_MDS None.
Audit Services prefix_IAU None.
Enterprise Scheduler Services prefix_ESS None.
Identity Management Schemas
Oracle Internet Directory prefix_ODS processes: 500
open_cursors: 500
Oracle Identity Federation prefix_OIF None.
Oracle Identity Manager prefix_OIM None.
Oracle Access Manager prefix_OAM None.
Oracle Adaptive Access prefix_OAAM processes: 250
Manager
sessions: 250
Oracle Database must be Enterprise
Edition.
Oracle Adaptive Access prefix_OAAM_ processes: 500
Manager (Partition Support) PARTN
sessions: 500
Oracle Database must be Enterprise
Edition.
Authorization Policy Manager prefix_APM None.
Oracle Data Integrator Schemas
Master and Work Repository prefix_ODI_REPO None.
Business Intelligence Schemas
Oracle BI Server prefix_BISERVER None.
Oracle BI Scheduler prefix_ None.
BISCHEDULER
Oracle BI Scorecard prefix_ None.
BISCORECARD
Oracle BI Publisher prefix_ None.
BIPUBLISHER
Oracle Real Time Decisions prefix_RTD None.
Oracle BI Shiphome prefix_ None.
BISHIPHOME
Oracle Middleware Extensions prefix_FND None.
for Applications
Oracle Enterprise Content Management Suite Schemas
Oracle Information Rights prefix_ORAIRM None.
Management
Oracle Content Server 11g - prefix_OCS None.
Complete
Oracle Content Server 11g - prefix_ None.
Search Only OCSSEARCH

21
Table 8 (Cont.) RCU Component-Specific Requirements for Oracle Databases
Component Schema Owner Requirement
Oracle Universal Records prefix_ None.
Management 11g URMSERVER
Oracle Imaging and Process prefix_IPM None.
Management
WebLogic Communication Services Schemas
Presence prefix_ None.
ORASDPXDMS
SIP Infrastructure Subscriber prefix_ None.
Data Service ORASDPSDS
SIP Infrastructure Location prefix_ORASDPLS None.
Service
SOA and BPM Infrastructure Schemas
Oracle BAM prefix_ORABAM None.
SOA Infrastructure prefix_SOAINFRA processes: 200
User Messaging Server prefix_ORASDPM None.
(ORASDPM)
WebCenter Suite Schemas
WebCenter Spaces prefix_ processes: 300
WEBCENTER
Discussions prefix_ None.
DISCUSSIONS
Discussions Crawler prefix_ None.
DISCUSSIONS_
CRAWLER
Wiki and Blog prefix_WIKI None.
Portlet Producers prefix_PORTLET The database user, in connection with
the target-DB, must have
rdbms-implementation equivalent of:
■ Create/Modify User/Schema
■ Create/Modify Table
■ Create/Modify Sequence
■ Create/Modify Index
■ Grant Resource Privilege
■ Grant Connect privilege
Oracle Content Server 10g prefix_OCSERVER Database character set must be
AL32UTF8.
Portal and Business Intelligence Schemas
Oracle Portal prefix_PORTAL Portal schema name cannot be longer
then 30 characters.
Oracle Discoverer prefix_ None.
DISCOVERER

22
8.4 RCU Requirements for Microsoft SQL Server Databases
This section contains information pertaining to running RCU and creating schemas on
Oracle databases. The following topics are covered:
■ Section 8.4.1, "Creating Oracle WebCenter Schemas on Microsoft SQL Server
Databases"
■ Section 8.4.2, "Component-Specific Requirements for Microsoft SQL Server
Databases"

8.4.1 Creating Oracle WebCenter Schemas on Microsoft SQL Server Databases

If you are creating the schemas in a Microsoft SQL Server database, a database
instance must be created prior to running RCU. The MDS schema has some specific
requirements; see "Databases Supported by MDS" in Oracle Fusion Middleware
Administrator's Guide for more information.
In addition, the MDS schema requires a database with case sensitive collation, while
Oracle Content Server 10g requires a database instance with case insensitive collation.
If you wish to install Oracle Content Server 10g on a SQL Server database, you will
need to create two database instances (one with case sensitive collation and one with
case insensitive collation) and run RCU twice: once to install the Oracle Content Server
10g schemas into the database instance with case insensitive collation, and a second
time to install all of the other WebCenter schemas into the database instance with case
sensitive collation.

8.4.2 Component-Specific Requirements for Microsoft SQL Server Databases

Table 9 lists all of the supported schemas for Microsoft SQL Server databases, along
with any component-specific prerequisite information that must be met for RCU to be
able to create schema.
When the tablespaces are created, RCU will automatically create them with the
necessary tablespace sizes.

Table 9 RCU Component-Specific Requirements for Microsoft SQL Server Databases

Component Schema Owner Requirement
AS Common Schemas
Metadata Services prefix_MDS The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE mds COLLATE SQL_
Latin1_General_CP1_CS_AS
Oracle Data Integrator Schemas
Master and Work prefix_ODI_REPO None.
Repository
Business Intelligence Schemas
Oracle BI Server prefix_BISERVER None.
Oracle BI Scheduler prefix_ None.
BISCHEDULER

23
Table 9 (Cont.) RCU Component-Specific Requirements for Microsoft SQL Server
Component
Oracle BI Scorecard
Oracle BI Publisher
Oracle Real Time Decisions
Oracle BI Shiphome
Oracle Middleware
Extensions for Applications
Oracle Enterprise Content Management Suite Schemas
Oracle Information Rights
Management
Oracle Content Server 11g -
Complete
Oracle Universal Records
Management 11g
Oracle Imaging and Process
Management
SOA Infrastructure Schemas
SOA Infrastructure
User Messaging Service
WebCenter Suite Schemas
WebCenter Spaces
Schema Owner Requirement
prefix_ None.
BISCORECARD
prefix_ None.
BIPUBLISHER
prefix_RTD None.
prefix_ None.
BISHIPHOME
prefix_FND The read_committed_snapshot
option must be turned on.
prefix_ORAIRM None.
prefix_OCS Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE mds COLLATE SQL_
Latin1_General_CP1_CS_AS
prefix_URMSERVER None.
prefix_IPM None.
prefix_SOAINFRA The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE soainfra COLLATE
SQL_Latin1_General_CP1_CS_AS
prefix_ORASDPM The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE orasdpm COLLATE
SQL_Latin1_General_CP1_CS_AS
prefix_WEBCENTER The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE webcenter COLLATE
SQL_Latin1_General_CP1_CS_AS
24
Table 9 (Cont.) RCU Component-Specific Requirements for Microsoft SQL Server
Component Schema Owner Requirement
Discussions prefix_ The read_committed_snapshot
DISCUSSIONS option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE discussions COLLATE
SQL_Latin1_General_CP1_CS_AS
Discussions Crawler prefix_ The read_committed_snapshot
DISCUSSIONS_ option must be turned on.
CRAWLER
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE discussions_crawler
COLLATE SQL_Latin1_General_CP1_CS_
AS
Wiki and Blog prefix_WIKI The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE wiki COLLATE SQL_
Latin1_General_CP1_CS_AS
Portlet Producers prefix_PORTLET The read_committed_snapshot
option must be turned on.
Database must be configured to use case
sensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE portlet COLLATE
SQL_Latin1_General_CP1_CS_AS
Oracle Content Server 10g prefix_OCSERVER Database must be configured to use case
insensitive collation. The following
command can be used to set the proper
collation:
ALTER DATABASE contentserver
COLLATE SQL_Latin1_General_CP1_CI_
AS

8.5 RCU Supported Schemas for IBM DB2 Databases

Not all of the schemas that are supported in Oracle and Microsoft SQL Server
databases are supported on IBM DB2 databases. Table 10 shows the schemas that are
supported in IBM DB2 databases.

25
 Note: Table 10 lists the schema names for an IBM DB2 database
running on a Linux operating system, due to a restriction on the
number of characters (including the prefix) in the schema name. For
more information, see Section 8.6.2, "Size Limit for Schema Prefixes
(Linux Only)".
If you are creating schemas in an IBM DB2 database running on a
Windows operating system, the schema names are the same as the
ones for a Microsoft SQL Server or Oracle database.
See Section 8.6.1, "Creating Database Operating System Users" for
important information about creating the operating system users.

When the tablespaces are created, RCU will automatically create them with the
necessary tablespace sizes.

Table 10 Supported Schemas for IBM DB2 Databases

IBM DB2 Schema Operating System
Component Name User Name
AS Common Schemas
Metadata Services prefix_MDS prefix_mds
SOA Infrastructure
SOA Infrastructure prefix_SOA prefix_soa
User Messaging Service prefix_UMS prefix_ums
WebCenter Suite
WebCenter Spaces prefix_WC prefix_wc
Portlet Producers prefix_PT prefix_pt
Oracle Content Server 10g prefix_CS prefix_cs
Discussions prefix_DS prefix_ds
Discussions Crawler prefix_DC prefix_dc
Wiki and Blog prefix_WK prefix_wk
Oracle Data Integrator Schemas
Master and Work Repository prefix_ODI prefix_odi
Oracle Enterprise Content Management Suite
Information Rights Management prefix_IRM prefix_irm
Oracle Content Server 11g prefix_OCS prefix_ocs
Oracle Universal Records Management 11g prefix_URM prefix_urm
Oracle Imaging and Process Management prefix_IPM prefix_ipm

8.6 RCU Prerequisites for IBM DB2 Databases

This section contains information you need to know about configuring IBM DB2
databases for schema creation. The following topics are covered:
■ Section 8.6.1, "Creating Database Operating System Users"

26
■ Section 8.6.2, "Size Limit for Schema Prefixes (Linux Only)"
■ Section 8.6.3, "Configuring Your DB2 Database"

8.6.1 Creating Database Operating System Users

IBM DB2 authenticates its database users using equivalent operating system users.
Therefore, prior to running RCU, one operating system user must be created for each
schema. The operating system user name must match the schema owner name and
must contain only lowercase letters; no all-uppercase or mixed-case names are
allowed. For example:
■ If you create a schema named DEV_SOA on an IBM DB2 database running on a
Linux operating system, then you must also create the operating system user dev_
soa (matching name, all lowercase letters).
■ If you create a schema named DEV_SOAINFRA on an IBM DB2 database running
on a Windows operating system, then you must also create the operating system
user dev_soainfra (matching name, all lowercase letters).

8.6.2 Size Limit for Schema Prefixes (Linux Only)

IBM DB2 has an eight character limit for schema names. Therefore, the schema names
are shortened to a maximum of three characters (plus schema prefix and underscore),
making the maximum size of the user defined prefix four characters.
For example, on IBM DB2 databases running on a Windows operating system, and all
supported Oracle and Microsoft SQL Server databases, the SOA Infrastructure schema
you create might be called DEV_SOAINFRA. However, on an IBM DB2 database
running on a Linux operating system, this schema name must be shortened to DEV_
SOA.

8.6.3 Configuring Your DB2 Database

This section contains important configuration information for your IBM DB2 database.
Make sure that your database is configured properly before running RCU to create
schemas.
■ Setting the pagesize
■ Setting the Log File Size for Oracle B2B
■ Setting the Lock Timeout Parameter
■ Setting the Registry Variables for the MDS Schema
■ Reducing Lock Escalation
■ Setting the CURR_COMMIT Parameter
■ Increasing the Log File Size

8.6.3.1 Setting the pagesize If you are creating schmeas in an IBM DB2 database, a
database instance with a pagesize of 32768 must be created prior to running RCU. Use
the following commands:
db2 create database wc automatic storage yes on path using codeset UTF8 pagesize
32768

For more information, see "Creating a Database-Based Metadata Repository" in Oracle

Fusion Middleware Administrator's Guide for more information.

27
8.6.3.2 Setting the Log File Size for Oracle B2B Because documents created in Oracle B2B
are stored in the metadata repository, it is possible that the transaction log for the
database can become full. If this occurs often, increase the LOGFILSIZ database
configuration parameter to allow a larger log file. A larger log file requires more space
but reduces the need for applications to retry the operation.
To increase the LOGFILSIZ value to 8,192KB, use the following command:
db2 update database config for soainfra using LOGFILESIZ 8192

8.6.3.3 Setting the Lock Timeout Parameter IBM DB2 does not support row versioning
during updates; if one user is updating a row, another user may be blocked when
attempting to update a different row and must wait until the first transaction is
committed or rolled back by the first user. To facilitate better concurrency, do not
specify -1, which sets the lock timeout to infinity. Instead, you should set the lock
timeout to a smaller value. For example:
db2 "update db cfg for mds using locktimeout 60"

To query the current lock timeout value on your database, you can use the following
command:
db2 "get db cfg for database_name" | grep -i timeout

8.6.3.4 Setting the Registry Variables for the MDS Schema The values for registry variables
must be set to the following for the Metadata Services (MDS) component:
db2set DB2_EVALUNCOMMITTED=OFF
db2set DB2_SKIPINSERTED=OFF
db2set DB2_SKIPDELETED=OFF

8.6.3.5 Reducing Lock Escalation IBM DB2 may escalate a "row lock" to a "table lock" due
to memory stress or lock usage; as the result, you may find that a transaction is rolled
back as a victim of "deadlock" or lock "timeout". You can increase the size of the
MAXLOCKS and LOCKLIST configuration parameters to reduce lock escalation with the
following commands:
db2 "update db cfg using locklist locklist_value"
db2 "update db cfg using maxlocks maxlocks_value"

To view the current setting of these two parameters:

db2 "get db cfg" | grep -i lock

8.6.3.6 Setting the CURR_COMMIT Parameter Verify the isolation level to be set to
Currently Committed (which is the default setting for DB2 9.7 databases):
db2 "get db cfg" | grep -i commit

Currently Committed (CUR_COMMIT) = ON

You can set the Currently Committed isolation by the following command:
db2 'update database config for database_name using CUR_COMMIT ON'

8.6.3.7 Increasing the Log File Size If the database transaction log is often full, increase
the database configuration parameter to allow for a larger log file. A larger log file
requires more space, but it reduces the need for applications to retry the operation.
You should set the log file size to at least 10000 and the number of primary log files to
at least 50. Use the following commands:

28
db2 'update database config for database_name using LOGFILESIZ 10000'
db2 'update database config for database_name using LOGPRIMARY 50'

9 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible to all users, including users that are disabled. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an
otherwise empty line; however, some screen readers may not always read a line of text
that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or
organizations that Oracle does not own or control. Oracle neither evaluates nor makes
any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call
Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle
technical issues and provide customer support according to the Oracle service request
process. Information about TRS is available at
http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone
numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Copyright © 2010 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected
by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them
to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following
notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions
and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway,
Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any
inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications,
then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services.
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services.

29
30