1 Finding Oracle Fusion Middleware Certification Information
If you are looking for latest certification information for supported installation types, platforms, operating systems, databases, JDKs, and third-party products, refer to Oracle Fusion Middleware Certification Document, which can be found at the following URL:
Unless otherwise noted, Table 1 lists the general minimum memory requirements for Oracle Fusion Middleware products:
Table 1 Memory Requirements
Operating System
Minimum Physical Memory Required
Minimum Available Memory 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 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
Temp Space: 150MB or more
Swap Space: 512MB or more
Please note that the memory requirements also apply to the Oracle Fusion Middleware 11g Forms and Reports development environments; not just for the production environment.
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.4 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:
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.
3 Oracle Universal Installer (OUI) Requirements
The Oracle Universal Installer installer checks for the items in Table 2 as it is being started:
Table 3 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:
Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)
127111-02
137111-04
HP-UX Itanium
HP-UX 11i v2 (11.23)
B.11.23.0703.059a Base Quality Pack Bundle for HP-UX 11i v2, March 2007
Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)
PHCO_35524
PHCO_36673
PHKL_35029
PHKL_35478
PHSS_35978
PHSS_35979
PHSS_37201
HP-UX Itanium
HP-UX 11i v3 (11.31)
B.11.31.0803.318a Base Quality Pack Bundle for HP-UX 11i v3, March 2008
Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)
PHKL_36248
PHKL_36249
PHSS_37202
PHSS_37501
PHCO_38050
PHSS_38139
HP-UX PA-RISC
HP-UX 11i v2 (11.23)
B.11.23.0703.059a Base Quality Pack Bundle for HP-UX 11i v2, March 2007
Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)
PHCO_35524
PHCO_36673
PHKL_35029
PHKL_35478
PHKL_35767
PHKL_36853
PHSS_35101
PHSS_35102
PHSS_35103
PHSS_35176
PHSS_35978
PHSS_35979
PHSS_37201
HP-UX PA-RISC
HP-UX 11i v3 (11.31)
B.11.31.0803.318a Base Quality Pack Bundle for HP-UX 11i v3, March 2008
Motif: 2.1.0 (for Oracle Portal, Forms, Reports, and Discoverer only)
PHKL_36248
PHKL_36249
PHSS_37202
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)
Footnote 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.
Footnote 2 "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).
Footnote 3 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 3, 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.
5 Certified Windows Operating Systems
Please refer to the Oracle Fusion Middleware Certification Document for the latest information on certified Windows operating systems:
6.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.
This warning will not appear in the version of RCU available in Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0).
6.2 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:
Apply patch 8897382 (see the README file in the patch for instructions).
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:
RCU is available only on Linux and Windows platforms. Either the Linux RCU or Windows RCU may be used to create schemas on any supported database platform.
8.2 Required Privileges
If you are creating schemas on an Oracle database, you must have DBA 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 DBA.
Refer to our Oracle database documentation for more information about database users and roles.
8.3 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.
8.4 RCU Component-Specific Prerequisites for Oracle Databases
Table 4 lists the component-specific prerequisite information that must be met for RCU to be able to create schemas on Oracle databases.
Table 4 RCU Prerequisites for Oracle Databases
Component
Schema Owner
Requirement
AS Common Schemas
Metadata Services
prefix_MDS
Default Tablespace: 100MB
IAS_TEMP Temporary Tablespace: 100MB
Audit Services
prefix_IAU
Default Tablespace: 50MB
Temporary Tablespace: 50MB
Identity Management Schemas
Oracle Internet Directory (OID)
prefix_ODS
processes: 500
open_cursors: 500
Oracle Identity Federation (OIF)
prefix_OIF
Default Tablespace: 50MB
Temporary Tablespace: 20MB
SOA Infrastructure Schemas
Oracle BAM
prefix_ORABAM
Default Tablespace: 50MB
Temporary Tablespace: 20MB
SOA Infrastructure
prefix_SOAINFRA
Default Tablespace: 50MB
Temporary Tablespace: 20MB
processes: 200
WebCenter Suite Schemas
WebCenter Spaces
prefix_WEBCENTER
Default Tablespace: 250MB
IAS_TEMP Temporary Tablespace: 100MB
processes: 300
Discussions
prefix_DISCUSSIONS
Default Tablespace: 100MB
IAS_TEMP Temporary Tablespace: 100MB
Discussions Crawler
prefix_DISCUSSIONS_CRAWLER
Default Tablespace: 10MB
Wiki and Blog
prefix_WIKI
Default Tablespace: 100MB
IAS_TEMP Temporary Tablespace: 100MB
Portlet Producers
prefix_PORTLET
Default Tablespace: 25MB
IAS_TEMP Temporary Tablespace: 5MB
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.
Default Tablespace: 105MB
Temporary Tablespace: 100MB
Portal and Business Intelligence Schemas
Oracle Portal
prefix_PORTAL
Portal schema name cannot be longer then 30 characters.
Oracle Discoverer (Relational)
prefix_DISCOVERER
Default Tablespace: 50MB
Additional Tablespace 1: 25MB
Additional Tablespace 2: 50MB
Additional Tablespace 3: 20MB
The NLS_LENGTH_SEMANTICS parameter must be set to BYTE.
Oracle Discoverer (OLAP)
prefix_DISCOVERER
Default Tablespace: 50MB
Additional Tablespace 1: 25MB
Additional Tablespace 2: 50MB
Additional Tablespace 3: 20MB
The NLS_LENGTH_SEMANTICS parameter must be set to BYTE.
8.5 RCU Component-Specific Prerequisites for Microsoft SQL Server Databases
Table 5 lists the component-specific prerequisite information that must be met for RCU to be able to create schemas on Microsoft SQL Server databases.
Table 5 RCU Prerequisites 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
SOA Infrastructure Schemas
SOA Infrastructure
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
User Messaging Service
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
WebCenter Suite Schemas
WebCenter Spaces
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
Discussions
prefix_DISCUSSIONS
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 discussions COLLATE SQL_Latin1_General_CP1_CS_AS
Discussions Crawler
prefix_DISCUSSIONS_CRAWLER
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 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
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.
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.
Bookmark
