Oracle® Fusion Middleware System Requirements and Specifications

9/12/2014 Oracle Fusion Middleware System Requirements and Specifications
file:///E:/Asad/work/Oracle%C2%AE%20Fusion%20Middleware%20System%20Requirements%20and%20Specifications.htm 1/30
Oracle Fusion Middleware System Requirements and Specifications
11g Release 1 (11.1.1)

Contents
Previous

Oracle Fusion Middleware
System Requirements and Specifications
11g Release 1 (11.1.1)
E18558-01
This document contains system and platform-specific information for Oracle Fusion Middleware products.
The following topics are covered in this document:
Section 1, "New Product Names Introduced in 11g Release 1 (11.1.1.6.0)"
Section 2, "Using This Document with the Certification Matrix and Product Installation Guide"
Section 3, "Oracle WebLogic Server and JDK Information"
Section 4, "Oracle Fusion Middleware Memory and Space Requirements"
Section 5, "Oracle Fusion Middleware Network Requirements"
Section 6, "System Requirements for UNIX Operating Systems"
Section 7, "System Requirements for Windows Operating Systems"
Section 8, "System Requirements for the Oracle Universal Installer"
Section 9, "Database Requirements and Specifications"
Section 10, "Repository Creation Utility (RCU) Requirements"
Section 11, "Documentation Accessibility"
1 New Product Names Introduced in 11g Release 1 (11.1.1.6.0)
Starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0), Oracle WebCenter and Oracle Enterprise Content Management Suite have been rebranded. Refer
to "New Product Names for Oracle WebCenter and Oracle Enterprise Content Management Suite" in Oracle Fusion Middleware Patching Guide for details.
2 Using This Document with the Certification Matrix and Product Installation Guide
This document is intended for use in conjunction with the various Oracle Fusion Middleware product installation guides and the Oracle Fusion Middleware 11g Release 1
Certifications.
Task 1 Find Out What is Certified
The Oracle Fusion Middleware 11g Release 1 Certifications can be found in the table on the Oracle Fusion Middleware Supported System Configurations page.
Find the .xls document that includes your products.
Oracle has tested and verified the performance of your product on all certified systems and environments; whenever new certifications occur, they are added to
the proper certification document right away. New certifications can occur at any time, and for this reason the certification documents are kept outside of the
documentation libraries and are available on Oracle Technology Network.
If you use My Oracle Support, you can also refer to "My Oracle Support Certification Tool for Oracle Fusion Middleware Products" (Doc ID 1368736.1) for
certification information.
Task 2 Verify the Requirements of the Certification
The Oracle Fusion Middleware System Requirements and Specifications document (this document) should be used to verify that the requirements of the
certification are met. For example, if the certification document indicates that your product is certified for installation on 32-Bit Oracle Linux 5, this document
should be used to verify that your Oracle Linux 5 system has met the required minimum specifications, like disk space, available memory, specific platform
packages and patches, and other operating system-specific items. This document is updated as needed and therefore also resides outside of the documentation
libraries and is available on Oracle Technology Network.
Task 3 Install Your Software
After you have verified that your environment meets the requirements specified in both the certification documents and system requirements, you are ready to
begin your installation.
Your product installation guides contain the step-by-step instructions to get your product physically installed and configured on your system. These guides are
available only from the documentation library (http://docs.oracle.com/) and therefore are not updated unless there is a subsequent product release. Both
the certification and system requirement documents can be updated multiple times in between product releases, depending on whether or not new information is
available.
3 Oracle WebLogic Server and JDK Information
This section contains the following:
Section 3.1, "Oracle WebLogic Server and Oracle Fusion Middleware Software Versions"
Section 3.2, "Understanding the Embedded JDK"
Section 3.3, "Upgrading the Embedded JDK in 11g Release 1 (11.1.1.7.0)"
Section 3.4, "Requirements for the 64-Bit JDK Environment"
Section 3.5, "Patches Required for Oracle WebLogic Server 11gR1 (10.3.5)"
Section 3.6, "Patches Required for Oracle WebLogic Server 11gR1 (10.3.6)"
3.1 Oracle WebLogic Server and Oracle Fusion Middleware Software Versions
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 1 for more information.
Table 1 Required Oracle WebLogic Server Versions
Oracle Fusion Middleware Version Required Oracle WebLogic Server Versions
Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) Oracle WebLogic Server 11gR1 (10.3.1)
Oracle WebLogic Server 11gR1 (10.3.6)
NOTE: If you are installing Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0) software with Oracle
WebLogic Server 11gR1 (10.3.5), make sure you read Section 3.5, "Patches Required for Oracle WebLogic
Server 11gR1 (10.3.5)" for important information.
NOTE: If you are upgrading Oracle Service Bus in an environment running Oracle WebLogic Server 11gR1
(10.3.6), make sure you read Section 3.6, "Patches Required for Oracle WebLogic Server 11gR1 (10.3.6)" for
important information.
Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document to see if there are additional versions of Oracle WebLogic
Server that can be used with your version of Oracle Fusion Middleware. This document is available in the Oracle Fusion Middleware Supported System Configurations
page, as described in Section 2, "Using This Document with the Certification Matrix and Product Installation Guide".
Oracle WebLogic Server can be obtained from the following URL:
http://www.oracle.com/technetwork/middleware/weblogic/downloads/
3.2 Understanding the Embedded JDK
The Oracle WebLogic Server requires a Java run-time environment (JRE) to run. When you install Oracle WebLogic Server, a JDK is bundled in the Windows 32-bit and
Linux x86 installation programs, as well as in some UNIX installation programs (those with file names ending in .bin).
For other platforms, the installation program does not install a JDK (file names for these installation programs end in .jar). To run the .jar installation programs, you
must:
1. Have a certified JDK installed on your system.
2. Set the JAVA_HOME environment variable to point to the location of this JDK. For example:
setenv JAVA_HOME /home/JDK/jdk_version
3. Include the JAVA_HOME (up to and including the /bin directory) at the beginning of your PATH environment variable definition. For example:
setenv PATH $JAVA_HOME/bin:$PATH
3.3 Upgrading the Embedded JDK in 11g Release 1 (11.1.1.7.0)
Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) does not include an updated version of Oracle WebLogic Server; this release is supported for use with Oracle
WebLogic Server 10.3.6, which was released with Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0).
As a result, some Oracle Fusion Middleware products may require a JDK version higher than the one that is embedded with Oracle WebLogic Server 10.3.6. In such
cases, you must manually upgrade your JDK to the supported version.
See the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System
Configurations page for supported JDK versions.
3.4 Requirements for the 64-Bit JDK Environment
If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK or is using a
supported 64-bit JDK on your system. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.
3.5 Patches Required for Oracle WebLogic Server 11gR1 (10.3.5)
If you are installing Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0) software with Oracle WebLogic Server 11gR1 (10.3.5), you must download and apply the
following patches to your 11gR1 (10.3.5) Middleware home directory:
Patch 12913145 (SNMPTRAPSENDER.SENDTRAP() NOT SENDING TRAP WITH ADMIN-CHANNEL TURNED ON)
Patch 10404224 (MDB CONFIG DOES NOT DISPLAY POOL PARAMETERS IF MDB DD DOES NOT CONTAIN IT)
Make sure to download the 10.3.5 version of this patch.
Both patches are available on My Oracle Support:
https://support.oracle.com/
3.6 Patches Required for Oracle WebLogic Server 11gR1 (10.3.6)
If you are upgrading to the latest Oracle Service Bus in an environment running Oracle WebLogic Server 10.3.6, you must install the required WebLogic Server patches
as described on the "Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack" page on Oracle Technology Network:
http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-1866030.html
4 Oracle Fusion Middleware Memory and Space Requirements
This section contains the minimum memory and disk space requirements for Oracle Fusion Middleware products. The following topics are covered:
Section 4.1, "General Memory Requirements"
Section 4.2, "Oracle Web Tier Disk Space Requirements"
Section 4.3, "Oracle SOA and Oracle BAM Requirements"
Section 4.4, "Oracle Portal, Forms, Reports and Discoverer Requirements"
Section 4.5, "Oracle Identity Management Memory and Disk Space Requirements"
Section 4.6, "Oracle Business Intelligence Requirements"
Section 4.7, "Oracle Data Integrator Requirements"
Section 4.8, "Oracle Data Profiling and Data Quality Requirements"
4.1 General Memory Requirements
Unless otherwise noted, Table 2 lists the general minimum memory requirements for Oracle Fusion Middleware products. For the purposes of this document, "minimum
available memory" is defined as the amount of physical memory (RAM) and swap memory combined.
Table 2 Memory Requirements
Operating System Minimum Physical Memory Required Minimum Available Memory Required
Linux 2 GB 4 GB
UNIX 2 GB 4 GB
Windows 2 GB 4 GB
4.2 Oracle Web Tier Disk Space Requirements
Oracle Web Tier requires a minimum of 2400 MB free disk space.
4.3 Oracle SOA and Oracle BAM Requirements
Section 4.3.1, "Oracle SOA and Oracle BAM System Requirements"
Section 4.3.2, "Oracle BAM Client Requirements"
Section 4.3.3, "Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or Oracle BAM Active Studio"
Section 4.3.4, "Additional Notes for Microsoft Internet Explorer and Pop-Up Blockers in Oracle BAM Web Applications"
4.3.1 Oracle SOA and Oracle BAM System 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
4.3.2 Oracle BAM Client Requirements
Table 3 shows the general requirements for the Oracle BAM client.
Table 3 Oracle BAM Client Requirements
Category Requirements
Platforms (Microsoft Windows Intel x86-32) Microsoft Windows XP Professional, Service Pack 2 or higher
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
4.3.3 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.
4.3.4 Additional Notes for Microsoft Internet Explorer and Pop-Up Blockers in Oracle BAM Web Applications
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.
4.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):
Temp Space: 150MB or more
Swap Space: 512MB or more
Note:
Although the general Oracle Fusion Middleware product memory requirement is 4GB (Section 4.1, "General Memory Requirements"), 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 2, "Using This Document with the Certification Matrix and Product
Installation Guide".
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:
Available Memory: 6GB or more
Temp Space: 950MB or more
Swap Space: 3GB or more
4.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:
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.
4.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. The
following topics are covered:
Section 4.6.1, "Installation System Requirements for Oracle Business Intelligence"
Section 4.6.2, "Database Requirements for Oracle Business Intelligence"
4.6.1 Installation System Requirements for Oracle Business Intelligence
Below are the recommended hardware and system configuration requirements for an Oracle Business Intelligence installation:
Available Memory: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems
Temp Space: 2GB or more
Swap Space: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems
4.6.2 Database Requirements for Oracle Business Intelligence
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.
4.7 Oracle Data Integrator Requirements
This section contains the following topics:
Section 4.7.1, "Hardware and System Configuration Requirements for Oracle Data Integrator"
Section 4.7.2, "Application Server Requirements for Java EE Components"
Section 4.7.3, "Database Requirements for Oracle Data Integrator"
4.7.1 Hardware and System Configuration Requirements for Oracle Data Integrator
Below are the recommended hardware and system configuration requirements for Oracle Data Integrator Studio and Standalone Agents:
1050MB are required for the Developer installation
700MB are required for the Standalone installation
1800MB are required for the Java EE installation
Available Memory: 2GB or more for one agent
The amount of memory you want to allocate to each agent is set by the ODI_MAX_HEAP parameter in the ODI_HOME/oracledi/agent/bin/odiparams.sh (on
UNIX operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on Windows operating systems) file. The default value is 256MB, which means
you can run more than one agent on a system with 2GB of available memory (for example, two agents would take up 512MB of memory).
The value set by ODI_MAX_HEAP multiplied by the number of agents is the minimum amount of available memory required on your system; the amount of
additional memory needed beyond this number depends on the number of other application you have running on your system.
4.7.2 Application Server Requirements for Java EE Components
The Java EE components in Oracle Data Integrator require the presence of an application server on your system.
For 11g Release 1 (11.1.1.6.0) and earlier, only Oracle WebLogic Server can be used as the application server; make sure your system also meets the Oracle
WebLogic Server system requirements before you install the Java EE components. IBM WebSphere is supported as an application server beginning with 11g Release 1
(11.1.1.7.0).
4.7.3 Database Requirements for Oracle Data Integrator
Below are the recommended storage space requirements for the database containing the Oracle Data Integrator Repository tables:
Master Repository: 60MB of storage space.
Work Repository: 80MB 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.
4.8 Oracle Data Profiling and Data Quality Requirements
This section contains the requirements for Oracle Data Profiling and Oracle Data Quality for Data Integrator. The following topics are covered:
Section 4.8.1, "Oracle Data Quality Client Requirements"
Section 4.8.2, "Oracle Data Profiling and Quality Server Requirements"
Section 4.8.3, "Additional Requirements for Servers"
4.8.1 Oracle Data Quality Client Requirements
Below are the recommended hardware and system configuration requirements for the Oracle Data Quality Client:
Disk Space: 500MB or more
Available Memory: 512MB or more
4.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 4.
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 4 CPU Requirements for Oracle Data Profiling and Quality Server
Platform Server Minimum CPU Processor
IBM AIX RS/6000 900 MHz eServerP5 and pSeries Platform Power 5
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
4.8.3 Additional Requirements for Servers
The Inetd (XInetd for Linux) component is required and must be installed on UNIX servers.
5 Oracle Fusion Middleware Network Requirements
Typically, the computer on which you want to install Oracle Fusion Middleware is connected to the network. The computer has local storage to store the Oracle Fusion
Middleware installation and also contains a display monitor and DVD drive.
This section describes how to install Oracle Database on computers that do not meet the typical scenario. It describes the following cases:
Section 5.1, "Configuration Requirements for Installing on a DHCP Host"
Section 5.2, "Configuration Requirements for Installing on a Non-Networked Computer"
Section 5.3, "Configuration Requirements for Installing on a Multihomed Computer"
Section 5.4, "Configuring Your /etc/hosts File"
Section 5.5, "Configuring IPv4 and IPv6 for Fusion Middleware Products"
5.1 Configuration Requirements for Installing on a DHCP Host
Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing allows a computer to have a different IP address each
time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP
addressing in a DHCP system.
In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to
manually assign that computer a unique IP address. However, before installing this software onto a computer that uses the DHCP protocol, you must install a loopback
adapter to assign a static, non-routable IP address to that computer.
If you are installing your Oracle Fusion Middleware products on a DHCP host, you must follow the configuration steps in this section for your platform.
5.1.1 For Linux x86 Platforms
On Linux x86 operating systems, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following
entries:
127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost
After doing so, check that the hostname resolves to the loopback IP address by entering the following command:
/bin/ping hostname.domainname
5.1.2 For Windows x86 Platforms
On Windows operating systems, install a loopback adapter on the single DHCP host that obtains an IP address from the DHCP server. This assigns a local IP address
to your computer:
Section 5.1.2.1, "Installing a Loopback Adapter on Windows 2003, Windows 2003 R2, and Windows XP"
Section 5.1.2.2, "Installing a Loopback Adapter on Windows Vista and Windows Server 2008"
Section 5.1.2.3, "Installing a Loopback Adapter on Windows 7 and Windows 2008 R2"
After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the localhost line:
IP_address hostname.domainname hostname
Replace IP_address with the local IP address of the loopback adapter. To find the IP address of your loopback adapter, use the ping command, as shown in the
example below using just the host name (first example) and the fully qualified domain name (second example):
ping examplehost
Reply from 10.10.10.10: bytes=32 time<1ms TTL=128
ping examplehost.exampledomainname.com
Reply from 10.10.10.10: bytes=32 time<1ms TTL=128
Note:
When you ping a computer from itself, the ping command should return the local IP address (the IP address of the loopback adapter).
Instructions for removing the loopback adapter are provided in Section 5.1.2.4, "Removing a Windows Loopback Adapter".
5.1.2.1 Installing a Loopback Adapter on Windows 2003, Windows 2003 R2, and Windows XP
To install a loopback adapter on Windows 2003, Windows 2003 R2, and Windows XP:
1. Open the Windows Control Panel.
2. Double-click Add Hardware to start the Add Hardware wizard.
3. In the "Welcome" window, click Next.
4. In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.
5. In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click
Next.
6. In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.
7. From the list of common hardware types, select Network adapters, and click Next.
8. In the "Select Network Adapter" window, make the following selections:
Manufacturer: Microsoft
Network Adapter: Microsoft Loopback Adapter
9. Click Next.
10. In the "The wizard is ready to install your hardware" window, click Next.
11. In the "Completing the Add Hardware Wizard" window, click Finish.
12. If you are using Windows 2003, restart your computer.
13. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.
14. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.
15. On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.
16. In the "Properties" dialog box, click Use the following IP address and do the following:
a. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:
192.168.x.x (x is any value between 1 and 255)
10.10.10.10
b. Subnet mask: Enter 255.255.255.0.
c. Record the values you entered, which you will need later in this procedure.
d. Leave all other fields empty.
e. Click OK.
17. In the "Local Area Connection 2 Properties" dialog, click OK.
18. Close Network Connections.
19. Restart the computer.
5.1.2.2 Installing a Loopback Adapter on Windows Vista and Windows Server 2008
To install a loopback adapter on Windows Vista and Windows Server 2008:
1. Open the Windows Control Panel.
2. Double-click Add Hardware to start the Add Hardware wizard.
3. In the "Welcome" window, click Next.
4. In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, and click Next.
5. In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.
6. In the "Select Network Adapter" window, make the following selections:
Manufacturer: Microsoft
Network Adapter: Microsoft Loopback Adapter
7. Click Next.
8. In the "The wizard is ready to install your hardware" window, click Next.
9. In the "Completing the Add Hardware Wizard" window, click Finish.
10. Go to Step 13 in Section 5.1.2.1, "Installing a Loopback Adapter on Windows 2003, Windows 2003 R2, and Windows XP". The remaining steps are the same as
the ones given for Windows 2003, Windows 2003 R2, and Windows XP.
5.1.2.3 Installing a Loopback Adapter on Windows 7 and Windows 2008 R2
To install a loopback adapter on Windows 7 and Windows 2008 R2:
1. Click Start and enter hdwwiz in the Search box.
2. Click hdwwiz to start the Add Hardware wizard.
3. Go to Step 3 in Section 5.1.2.2, "Installing a Loopback Adapter on Windows Vista and Windows Server 2008". The remaining steps are the same as the ones
given for Windows Vista and Windows Server 2008.
5.1.2.4 Removing a Windows Loopback Adapter
To remove a loopback adapter:
1. Display System in the Windows Control Panel.
2. In the "Hardware" tab, click Device Manager. This tab is not available with Windows Vista and Windows Server 2008. Click Device Manager instead.
3. In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.
4. Right-click Microsoft Loopback Adapter and select Uninstall.
5. Click OK.
6. Restart the computer.
7. Remove the line from the %SYSTEMROOT%\system32\drivers\etc\hosts file, added immediately after the localhost line while installing the loopback adapter
on your Windows operating system.
5.2 Configuration Requirements for Installing on a Non-Networked Computer
You can install your Oracle Fusion Middleware product on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other
computers, you have to install all the components that you need on the computer.
In addition, you must follow the instructions in Section 5.1, "Configuration Requirements for Installing on a DHCP Host" to install a loopback adapter and modify the
hosts file on your system.
5.3 Configuration Requirements for Installing on a Multihomed Computer
You can install your Oracle Fusion Middleware product on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically
achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.
The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX operating systems) or
%SYSTEMROOT%\system32\drivers\etc\hosts (on Windows operating systems) file. So if your file looks like the following:
127.0.0.1 localhost.localdomain localhost
10.1.1.1 examplehost1.example.com examplehost1
10.2.2.2 examplehost2.example.com examplehost2
examplehost1.example.com would be picked for configuration.
For specific network configuration of a system component, refer to the individual component's configuration documentation.
In any situation where you change any combination of the host name, domain name, or IP address of a host, you also change the information for Java components
and system components. See "Changing the Network Configuration of Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide for more
information about additional steps that need to be performed.
5.4 Configuring Your /etc/hosts File
Section 5.4.1, "Correct Format For Entries in the /etc/hosts File"
Section 5.4.2, "Configuration Requirements for Installing OPMN"
5.4.1 Correct Format For Entries in the /etc/hosts File
To ensure that both forward lookup (find the IP address given the hostname) and reverse lookup (finding the hostname given the IP address) return the same
results, make sure your /etc/hosts file is formatted correctly using the following guidelines:
The host name may contain only alphanumeric characters, hyphen, and period. The name must begin with an alphabetic character and end with an
alphanumeric character.
Host names should be specified as fully qualified host names (host name with the appended domain name).
Lines cannot start with a blank space or tab character, but fields may be separated by any number of space or tab characters.
Comments are allowed and designated by a pound sign (#) preceding the comment text.
Trailing blank and tab characters are allowed.
Blank line entries are allowed.
Only one host entry per line is allowed.
5.4.2 Configuration Requirements for Installing OPMN
If you are installing Oracle Identity Management, Oracle Web Tier, or Oracle Portal, Forms, Reports and Discoverer (products that include Oracle Process Manager and
Notification Server or OPMN), you must make sure the installation system has valid entries in the /etc/hosts (on UNIX operating systems) and
C:\windows\system32\drivers\etc\hosts (on Microsoft Windows operating systems) file.
You can check your system's IP address and host name as follows:
On UNIX operating systems:
/sbin/ifconfig -a
On Microsoft Windows operating systems:
ipconfig /all
The IP address and corresponding host name in your hosts file must match the IP address and host name you get from the ipconfig command. Otherwise, the
opmn.xml file will contain incorrect configuration information, and OPMN will not start.
If you encounter any issues, refer to "Changing Network Configurations" in the Oracle Fusion Middleware Administrator's Guide.
5.5 Configuring IPv4 and IPv6 for Fusion Middleware Products
Section 5.5.1, "IP Considerations for Domain Extension on Remote Machines"
Section 5.5.2, "Using Web Cache in an IPv6 Network"
5.5.1 IP Considerations for Domain Extension on Remote Machines
If you want to expand or extend a domain on remote machine where one machine (machine1) is listening on one network address and other machine (machine2) is
listening on dual network addresses, you must do the following in order to be able to expand or extend the domain:
1. Configure the domain on machine1.
2. On machine1, go to the DOMAIN_HOME/bin/setDomainEnv.[sh|cmd] file and set the following property:
-Djava.net.preferIPv4Stack=true
3. Restart the Administration Server on machine1.
4. Expand or extend the domain on the remote machine.
5.5.2 Using Web Cache in an IPv6 Network
Oracle Web cache supports the IPv6 address family by default. However, before using IPv6, you must ensure that IPv6 support is enabled in the operating system.
This issue is not applicable for IPv4-only systems and for systems that support IPv6 at the kernel level.
If the system's IPv6 network configuration issue cannot be resolved, one work around is to disable IPv6 Support for Oracle Web Cache after it fails (note that this
cannot be done until after the installation or configuration fails on IPv4-only systems). This can be done by adding the <IPV6 ENABLED="NO"/> tag below the
</MULTIPORT> tag in the INSTANCE_HOME/config/WebCache/webcache1/webcache.xml file. This allows Web Cache to use IPv4 on the system.
6 System Requirements for UNIX Operating Systems
This section contains system requirement information for UNIX operating systems.
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 System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document
and would no longer be considered a "certified" platform.
The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document is located on the Oracle Fusion Middleware Supported System
Configurations page, as described in Section 2, "Using This Document with the Certification Matrix and Product Installation Guide".
All packages listed are minimum versions.
The following topics are covered in this section:
Section 6.1, "General UNIX Operating System Requirements"
Section 6.2, "Linux Operating System Requirements"
Section 6.3, "Solaris Operating System Requirements"
Section 6.4, "HP-UX Operating System Requirements"
Section 6.5, "IBM AIX Operating System Requirements"
6.1 General UNIX Operating System Requirements
Section 6.1.1, "Setting the Open File Limit"
Section 6.1.2, "Enabling Unicode Support"
Section 6.1.3, "Installing as a Non-Default User on UNIX Operating Systems"
6.1.1 Setting the Open File Limit
On all UNIX operating systems, the minimum Open File Limit should be 4096. You can see how many files are open with the following command:
Note:
The following examples are for Linux operating systems. Equivalent commands should be followed for other operating systems.
/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.
6.1.2 Enabling Unicode Support
Your operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.
On UNIX operating systems, Oracle highly recommends that you enable Unicode support by setting the LANG and LC_ALL environment variables to a locale with the
UTF-8 character set. This enables the operating system to process any character in Unicode. Oracle SOA Suite technologies, for example, are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, Oracle SOA Suite components may function in an unexpected way. For example, a non-ASCII file
name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.
In a design-time environment, if you are using Oracle JDeveloper, select Tools -> Preferences -> Environment -> Encoding -> UTF-8 to enable Unicode
support.
6.1.3 Installing as a Non-Default User on UNIX Operating Systems
On UNIX operating systems, the installation of Fusion Middleware products is owned and controlled as a known user (for example, "oracle"). The file permissions
associated with this installation are configured to ensure the highest level of security possible, which by default are 700 (meaning all files are owned and accessible by
the owner only).
Changing the default permissions settings will reduce the security of the installation and possibly your system. Therefore, making such a change is not recommended.
If access to particular files or executables is required by other users, the UNIX sudo command (or other similar command) should be considered in lieu of changing file
permissions.
Refer to your UNIX operating system Administrator's Guide or contact your operating system vendor if you need further assistance.
6.2 Linux Operating System Requirements
Table 5 lists the platform, operating system, package, and patch information for Linux operating systems that are either currently supported or were supported in a
previous release.
Use the following links to go directly to your specific Linux operating system:
x86 Oracle Linux 4 (UL7+) and Red Hat Linux 4 (UL7+)
x86 Oracle Linux 5 (UL3+) and Red Hat Linux 5 (UL3+)
x86 SUSE 10 (SP1+)
x86 SUSE 11 (all SP levels included)
x86-64 Oracle Linux 4 (UL7+) and Red Hat Linux 4 (UL7+)
x86-64 SUSE 10 (SP1+)
x86-64 SUSE 11 (all SP levels included)
Table 5 Linux Operating System Requirements
Platform
Operating System
Version Required Packages
Required Kernel
Version
x86 Oracle Linux 4 (UL7+)
Red Hat Linux 4 (UL7+)
binutils-2.15.92.0.2-13
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
glibc-common-2.3.4-2.9
gnome-libs-1:1.4.1.2.90-44.1
libaio-0.3.105
Foot 1
libaio-devel-0.3.105
Footref 2
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
make-1:3.80-5
openmotif-2.2.3
Foot 2
openmotif21-2.1.30-11.RHEL4.4
pdksh-5.2.14-30
setarch-1.6-1
sysstat-5.0.5-1
xscreensaver-4.18-5.rhel4.2
2.6.9
x86 Oracle Linux 5 (UL3+)
binutils-2.16.91.0.5-23.4
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-4.1.0-28.4
2.6.18
gcc-c++-4.1.0-28.4
glibc-common-2.3.4-2.9
libaio-0.3.106
Footref 2
Footref 2
libstdc++-4.1.0-28.4
libstdc++-devel-4.1.0-28.4
make-3.80-202.2
openmotif-2.2.3
Footref 1
openmotif22-2.2.3
Footref 1
setarch-1.6-1
sysstat-5.0.5-1
x86 SUSE 10 (SP1+) binutils (version 2.16.91.0.5-23)
compat-libstdc++ (version 5.0.7-22.2)
compat (version 2006.1.25-11.2)
gcc (version 4.1.0-28.4)
glibc-devel (version 2.4-31.2)
gcc-c++ (version 4.1.0-28.4)
libaio (version 0.3.104)
Footref 2
libaio-devel (0.3.104)
Footref 2
libgcc (version 4.1.0-28.4)
libstdc++ (version 4.1.0-28.4)
libstdc++-devel (version 4.1.0-28.4)
make (version 3.80-202.2)
openmotif (version 2.2.3)
Footref 1
openmotif21-libs (version 2.1.30)
Footref 1
2.6.16.21
x86 SUSE 11 (all SP levels
included)
binutils-2.19-11.28
gcc-4.3-62.198
gcc-c++-4.3-62.198
glibc-2.9-13.2
glibc-devel-2.9
ksh-93t
libaio-0.3.104-140.22
libaio-devel-0.3.104-140.22
libgcc43-4.3.3_20081022
libstdc++43-4.3.3_20081022-11.18
libstdc++43-devel-4.3.3_20081022-11.18
libstdc++33-3.3.3
libstdc++devel-4.3
make-3.81
openmotif22-libs-2.2.4-138.17
Foot 3 Foot 4
openmotif-2.3.1-3.13
Footref 3Footref 4
openmotif21-libs-2.1.30MLI4-143.9
Footref 3Footref 4
openmotif-libs-2.3.1-3.13
Footref 3Footref 4
openmotif-devel-2.3.1-3.13
Footref 3Footref 4
sysstat-8.1.5-7.8
2.6.27.19-5-default
x86-64 Oracle Linux 4 (UL7+)
binutils-2.15.92.0.2
compat-libstdc++-33-3.2.3 for x86_64
compat-libstdc++-33-3.2.3 for i386
elfutils-libelf-0.97
elfutils-libelf-devel-0.97
gcc-3.4.5
gcc-c++-3.4.5
glibc-2.3.4-2.19 for x86_64
glibc-2.3.4-2.19 for i686
glibc-common-2.3.4
glic-devel-2.3.4 for x86_64
glic-devel-2.3.4 for i386
libaio-0.3.105 for x86_64
libaio-0.3.105 for i386
libgcc-3.4.5 for x86_64
libgcc-3.4.5 for i386
libstdc++-3.4.5 for x86_64
libstdc++-3.4.5 for i386
libstdc++-devel-3.4.5 for x86_64
libstdc++-devel-3.4.5 for i386
make-3.80
openmotif-2.2.3
Footref 3
openmotif21-2.1.30-11.RHEL4.4
Footref 1
sysstat-5.0.5
2.6.9
binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3 for x86-64
compat-libstdc++-33-3.2.3 for i386
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12 for x86_64
glibc-2.5-12 for i686
glibc-common-2.5
glibc-devel-2.5 for x86-64
glibc-devel-2.5-12 for i386
libaio-0.3.106 for x86_64
libaio-0.3.106 for i386
libgcc-4.1.1 for x86_64
2.6.18
Foot 5
libgcc-4.1.1 for i386
libstdc++-4.1.1 for x86_64
libstdc++-4.1.1 for i386
libstdc++-devel-4.1.1
libXext for i386
libXtst for i386
libXi for i386
make-3.81
openmotif-2.2.3
Footref 3
openmotif22-2.2.3
Footref 3
redhat-lsb-3.1-12.3.EL.0.2
sysstat-7.0.0
xorg-x11-utils
binutils-2.20.51.0.2-5.28.el6
compat-libcap1-1.10-1
compat-libstdc++-33-3.2.3-69.el6 for x86_64
compat-libstdc++-33-3.2.3-69.el6 for i686
gcc-4.4.4-13.el6
gcc-c++-4.4.4-13.el6
glibc-2.12-1.7.el6 for x86_64
glibc-2.12-1.7.el6 for i686
glibc-devel-2.12-1.7.el6 for i686
libaio-0.3.107-10.el6
libaio-devel-0.3.107-10.el6
libgcc-4.4.4-13.el6
libstdc++-4.4.4-13.el6 for x86_64
libstdc++-4.4.4-13.el6 for i686
libstdc++-devel-4.4.4-13.el6
libXext for i386
libXtst for i386
libXi for i386
openmotif-2.2.3 for x86_64
Footref 2
openmotif22-2.2.3 for x86_64
Footref 2
redhat-lsb-4.0-3.el6 for x86_64
sysstat-9.0.4-11.el6
2.6.32-100.28.5.el6
x86-64 SUSE 10 (SP1+) binutils-2.16.91.0.5
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
glibc-devel-2.4
glibc-devel-32bit-2.4
libaio-0.3.104
libelf-0.8.5
libgcc-4.1.0
libstdc++-4.1.0
libstdc++-devel-4.1.0
make-3.80
openmotif-2.2.3
Footref 1
openmotif21-libs-2.1.30
Footref 1
sysstat-6.0.2
2.6.16.21
x86-64 SUSE 11 (all SP levels
included)
binutils-2.19-11.28
gcc-4.3-62.198
gcc-c++-4.3-62.198
gcc-32bit-4.3
glibc-2.9-13.2
glibc-32bit-2.9-13.2
glibc-devel-2.9
glibc-devel-32bit-2.9-13.2
ksh-93t
libaio-0.3.104-140.22
libaio-devel-0.3.104-140.22
libaio-32bit-0.3.104
libaio-devel-32bit-0.3.104
libgcc43-4.3.3_20081022
libstdc++43-4.3.3_20081022-11.18
libstdc++43-devel-4.3.3_20081022-11.18
libstdc++33-3.3.3
libstdc++33-32bit-3.3.3
libstdc++43-32bit-4.3.3_20081022
libstdc++43-devel-32bit-4.3.3_20081022
libstdc++-devel-4.3
make-3.81
openmotif-2.3.1-3.13
Footref 3
openmotif-devel-32bit-2.3.1-3.13
Footref 3
openmotif22-libs-32bit-2.2.4-138.17
Footref 3
openmotif-libs-2.3.1-3.13
Footref 3
openmotif-devel-2.3.1-3.13
Footref 3
openmotif-libs-32bit-2.3.1-3.13
Footref 3
openmotif21-libs-32bit-2.1.30MLI4-143.2
Footref 3
openmotif22-libs-2.2.4-138.17
Footref 3
sysstat-8.1.5-7.8
2.6.27.19-5-default
Footnote 1
Required for Oracle Identity Management, Oracle Web Tier, and Oracle Portal, Forms, Reports and Discoverer
Footnote 2
Required for Oracle Portal, Forms, Reports and Discoverer
Footnote 3
Required for Oracle Reports
Footnote 4
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.
Footnote 5
For Oracle SOA Suite, the kernel must be upgraded to version 2.6.18-308.13.1.0.1.el5.
6.2.1 Obtaining the openmotif22 Package on SUSE 10 and SUSE 11 Operating Systems
The openmotif22 package is not included by default on SUSE 10 and SUSE 11 operating systems. If you need to obtain this package, you must go to the Novell
website to obtain the package and then perform the installation using the instructions provided by Novell.
6.2.2 Installing Oracle HTTP Server on Linux Operating Systems Requires NPTL
If you are installing Oracle HTTP Server on a Linux operating system, the operating system needs to set Native POSIX Threads Library (NPTL) as the default threads-
implementation. To check for this, run the following command:
getconf GNU_LIBPTHREAD_VERSION
The expected results should be "NPTL 2.3.4". Failing to have NPTL can result in unexpected behavior for the Oracle HTTP Server, especially if the Multi-Processing
Module (MPM) is the Worker MPM.
6.3 Solaris Operating System Requirements
Table 6 lists the platform, operating system, package, and patch information for Solaris operating systems that are either currently supported or were supported in a
previous release.
Table 6 Solaris Operating System Requirements
Platform Operating System Version Required Packages
Required Operating
System Patches
SPARC64 Solaris 9 Update 9+ SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
SUNWsprox
Motif: 2.1.0
Foot 1
GCC: package 3.4.2 or higher
Foot 2
118558-22
112874-39
112760-05
Foot 3
114370-05
Foot 4
Solaris 10 Update 4+
SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
Motif: 2.1.0
Footref 1
Footref 2
127111-02
137111-04
141444-09
Foot 5
Solaris 11 SUNWlibC
developer/assembler
x86-64 Solaris 10 Update 6+
SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
Footref 2
127112-02
Foot 6
137112-04
Solaris 11 SUNWlibC
developer/assembler
Footnote 1
Required for Oracle Portal, Forms, Reports and Discoverer.
Footnote 2
Required for Oracle WebCenter Content: Imaging. This package must be available in /usr/local/packages. In order to start the Managed Server, make
sure the LD_LIBRARY_PATH environment variable is set to the /usr/local/packages/gcc-version/lib directory.
Footnote 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).
Footnote 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).
Footnote 5
This patch is required for Solaris 10 Update 7 and lower. Solaris 10 Update 8 and higher already includes this patch.
Footnote 6
For additional details about patches 127112 and 137112, see notes 1000642.1 and 1019395.1 on My Oracle Support.
6.3.1 Installing Font Packages on Solaris 11 for Forms and Reports
For Oracle Forms and Reports, the following packages must also be installed on Solaris 11 systems:
system/font/daewoo-misc
system/font/gnome-fonts
system/font/isas-misc
system/font/jis-misc
system/font/misc-ethiopic
system/font/misc-meltho
system/font/sun-ja-bitmap
system/font/sun-ja-bitmap-unicode
system/font/truetype/arphic-ukai
system/font/truetype/bh-luxi
system/font/truetype/bitstream-vera
system/font/truetype/fonts-core
system/font/truetype/gentium
system/font/truetype/google-droid
system/font/truetype/hanyang-ko
system/font/truetype/ipafont-mincho
system/font/truetype/sil
system/font/truetype/unfonts-ko-core
system/font/truetype/unfonts-ko-extra
system/font/truetype/unifont
system/font/truetype/wqy-zenhei
system/font/xorg/cyrillic
system/font/xorg/iso8859-10
After these packages are installed, you must also set the following environment variables:
On Solaris x86-64 operating systems, set the NLS_LANG environment variable to AMERICAN_AMERICA.WE8ISO8859P15, or set the DISPLAY variable to any 64-Bit
Linux machine.
On Solaris SPARC64 operating systems:
1. Set LC_ALL=C.
2. Set the NLS_LANG environment variable to AMERICAN_AMERICA.WE8ISO8859P15, or set the DISPLAY variable to any 64-Bit Linux machine.
6.3.2 Applying Solaris Patches in Non-Global Zones
On Solaris operating systems, the prerequisite patches that are applied in the global zone can be considered applied in the non-global zones. There is only one kernel
running on the system, and all zones must be at the same patch level with respect to the kernel and other Solaris system components. Kernel patches can only be
applied from the global zone, and they affect the global and all non-global zones equally.
To check if a kernel patch is applied in the global zone, use the following command:
showrev -p | grep patch_number
For example, to check if patch 137111-04 is applied:
showrev -p | grep 137111
6.4 HP-UX Operating System Requirements
Table 7 lists the platform, operating system, package, and patch information for HP-UX operating systems that are either currently supported or were supported in a
previous release.
Table 7 HP-UX Operating System Requirements
Platform Operating System Version Required Packages
Required Operating
System Patches
Itanium HP-UX 11i v2 (11.23)
B.11.23.0703.059a Base Quality Pack Bundle for HP-UX 11i v2, March 2007
B3394BA (version 2.1.0)
Foot 1 PHCO_35524
PHCO_36673
PHKL_35029
PHKL_35478
PHSS_35978
PHSS_35979
PHSS_37201
HP-UX 11i v3 (11.31)
Footref 1 PHKL_36248
PHKL_36249
PHSS_37202
PHSS_37501
PHCO_38050
PHSS_38139
PA-RISC HP-UX 11i v2 (11.23)
Footref 1 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 11i v3 (11.31)
Footref 1 PHKL_36248
PHKL_36249
PHSS_37202
PHSS_37501
PHCO_38050
Footnote 1
This is the Motif Development Kit and is required for Oracle Portal, Forms, Reports and Discoverer only.
6.5 IBM AIX Operating System Requirements
Table 8 lists the platform, operating system, package, and patch information for IBM AIX operating systems that are either currently supported or were supported in a
previous release.
Table 8 IBM AIX Operating System Requirements
Platform
Operating System
Version Required Packages
Required Operating
System Patches
AIX 7100-01 bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
rsct.basic.rte
rsct.compat.clients.rte
xlC.aix61.rte (version 10.1.0.0)
xlC.rte (version 10.1.0.0)
IZ89165
Foot 1
6100-02 bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.perfstat
bos.perf.proctools
rsct.basic.rte
X11.motif.lib (version 2.1.30)
Foot 2
gpfs.base (version 3.2.1.8)
Foot 3
5300-08 bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.perfstat
bos.perf.proctools
rsct.basic.rte
bos.mp64 (version 5.3.0.56)
bos.rte.libc (version 5.3.0.55)
X11.motif.lib (version 2.1.30)
Footref 2
gpfs.base (version 3.2.1.8)
Footref 3
Footnote 1
Required for Oracle Business Intelligence.
Footnote 2
Required for Oracle Portal, Forms, Reports and Discoverer.
Footnote 3
Required for Oracle RAC.
7 System Requirements for Windows Operating Systems
This section contains the following information regarding Microsoft Windows operating systems:
Section 7.1, "Certified Windows Operating Systems"
Section 7.2, "Disabling Anti-Virus Software"
Section 7.3, "Enabling User Account Control (UAC)"
Section 7.4, "Understanding the Required Installation Privileges for Oracle Identity Management and Oracle Forms and Reports"
Section 7.5, "Installing and Configuring Java Access Bridge"
7.1 Certified Windows Operating Systems
Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document for the latest information on certified Windows operating
systems. This document is available in the Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Using This Document with the
Certification Matrix and Product Installation Guide".
7.2 Disabling Anti-Virus Software
If you encounter issues related to anti-virus software during your Fusion Middleware product installation, disable your anti-virus software for the entire duration of the
installation. If the system is restarted before the installation is complete, ensure the anti-virus software was not restarted before continuing with the installation.
Anti-virus software can be re-enabled when the installation is complete.
7.3 Enabling User Account Control (UAC)
On Microsoft Windows Vista, Windows Server 2008, or Windows 7 operating systems, you must enable User Account Control (UAC) so that the correct permissions
are applied to the cwallet.sso file.
To enable UAC:
1. Run secpol.msc from the command prompt.
2. Select Security Settings > Local Policies > Security Options.
3. Set the User Account Control:Run all Administrator in Admin Approval Mode option to enabled.
4. Restart the host.
5. Restart the servers.
7.4 Understanding the Required Installation Privileges for Oracle Identity Management and Oracle Forms
and Reports
In order to install Oracle Identity Management, Oracle Forms and Reports, or use the Oracle Forms and Reports Builders after installation on a Microsoft Windows Vista
or newer operating system, the operating system user must have Windows "Administrator" privileges.
Even when a user with "Administrator" privileges logs in to the machine, the administrative role is not granted for default tasks. In order to access the Oracle home files
and folders, the user must launch the command prompt or Windows Explorer as "Administrator" explicitly, even if the user is logged in as the administrator.
To do so, you can do either one of the following:
Find the Command Prompt icon (for example, from the Start menu or from the Desktop), right-click on the icon, and select Run as Administrator. Then you
can run the executables (for example, the WebLogic Server installer) from the command line.
Start Windows Explorer, find the executable you want to run (for example, rcu.bat for RCU, config.bat for the Configuration Wizard, or setup.exe for the
installer), right-click on the executable, and select Run as Administrator.
7.5 Installing and Configuring Java Access Bridge
If you are installing on a Windows machine, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. This is only necessary if
you require Section 508 Accessibility features.
Installation instructions are available in the Oracle Java Access Bridge Installation and Application Developer's Guide.
8 System Requirements for the Oracle Universal Installer
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 8.1, "Environment Variables"
Section 8.2, "Startup Requirements"
Section 8.3, "Running the 32-Bit Installer on a 64-Bit Operating System"
Section 8.4, "Special Startup Requirements for Linux x86 or Linux x86-64 Operating Systems"
Section 8.5, "Installing on Operating Systems Not Certified at the Time of Product Release"
8.1 Environment Variables
The environment variables on your system must be set as described in Table 9:
Table 9 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 all platforms.
If you are installing on a Windows operating system, see "Resolving PATH and Directory Issues on Windows" in the Oracle Fusion
Middleware Release Notes for Microsoft Windows (32-Bit) or Oracle Fusion Middleware Release Notes for Microsoft Windows x64 for
important additional information.
This variable is automatically set by the installer and prepended with ORACLE_HOME\bin. In addition, you must have the appropriate
version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition.
Make sure this variable does not contain a reference to any other Oracle home directory.
NOTE: If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, you must have the appropriate version of
the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition.
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.
LIBPATH Applies to: all installers for products with system components only on AIX operating systems.
LD_LIBRARY_PATH Applies to: all installers for products with system components only on Linux and Solaris operating systems.
NOTE: make sure this variable does not contain a reference to any other Oracle home directory.
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.
Refer to your operating system documentation for specific instructions on how to do this, as procedures vary depending on your exact
operating system.
TMP
TMPDIR
Applies to: all installers for all products on all platforms.
Optional variable. If not set, then the default value is /tmp.
TNS_ADMIN
ORA_NLS
LD_BIND_NOW
Applies to: all installers for all products on all platforms.
For the Oracle Portal, Forms, Reports and Discoverer installer, these variables must not be set.
For all other installers, there are no restrictions as to whether these variables are set or not set.
8.2 Startup Requirements
The items in Table 10 are checked as the installer is being started:
Table 10 Oracle Universal Installer Startup Requirements
Category Accepted or Minimum Values
Platforms For a complete list of certified platforms, refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the
Oracle Fusion Middleware Supported System Configurations page, as described in Section 2, "Using This Document with the Certification Matrix and Product
Installation Guide".
CPU Speed At least 300MHz
Temp Space Varies by installer:
The generic installers (for example, Oracle SOA Suite, Oracle WebCenter Portal, Oracle Application Developer) require 150MB.
Oracle Data Integrator (ODI), while it is a generic installer, requires 500MB.
The platform-specific installers (for example, Oracle Web Tier, Oracle Identity Management, Oracle Portal, Forms, Reports and Discoverer, Oracle
Business Intelligence) require 400MB.
Swap Space At least 500MB
Monitor At least 256 colors (this is a requirement for the graphical user interface mode only)
8.3 Running the 32-Bit Installer on a 64-Bit Operating System
This section contains important information for those products that support installing the 32-bit version on a 64-bit operating system:
Section 8.3.1, "Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating System"
Section 8.3.2, "Starting the Generic Installer with a 32-Bit JDK on a 64-Bit Operating System"
8.3.1 Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating System
If you are installing the 32-bit version of Oracle Web Tier on a 64-bit Linux operating system, you must perform the steps described below to replace your original
/usr/bin/gcc file with a new GCC file (called gcc41) that makes use of the existing 32-bit library files on your system. It is not necessary to install a new 32-bit GCC
on your system.
Note:
Installing the 32-bit version of Oracle Web Tier on a 64-bit Linux operating system is only supported on certain Linux operating systems; refer to the
Oracle Fusion Middleware 11g Release 1 Certifications document on the Oracle Fusion Middleware Supported System Configurations page for details.
Installing a 32-bit version of Oracle Web Tier on a 64-bit Windows operating system is not supported.
1. Verify that you are installing your 32-bit Web Tier on a certified 64-bit Linux system.
2. Log in to the system as root, and do the following:
a. Move the existing /usr/bin/gcc file to /usr/bin/gcc.orig with the mv command:
mv /usr/bin/gcc /usr/bin/gcc.orig
b. Using a text editor such as vi, create a new file called gcc41 that contains the following content (the line beginning with exec must be a single line):
#!/bin/sh
exec /usr/bin/gcc.orig -m32 -static-libgcc -B /usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/ $*
Note:
The directory usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/ may differ slightly depending on the version of your Linux operating
system. Search for the corresponding 32-bit directory under /usr/lib/gcc on your Linux operating system and use that directory in the
gcc41 file.
c. Change the file permission for the gcc41 file using the following command:
chmod 755 /usr/bin/gcc41
d. Create a symbolic link to /usr/bin/gcc with the following command:
ln -s -f /usr/bin/gcc41 /usr/bin/gcc
e. Exit as the root user.
3. Run the following command before starting the installer:
linux32 bash
4. Obtain your 32-bit Oracle Web Tier installer.
For information on where to obtain product installers, see the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files page:
http://docs.oracle.com/cd/E23104_01/download_readme.htm
5. Install Oracle Web Tier as described in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier.
During the installation on the Configure Components screen, make sure you do not select Oracle Web Cache and associate it with a WebLogic domain; this is not
supported for 32-bit Web Tier on a 64-bit system.
6. When the installation and configuration are complete, revert the gcc file back to its original state and remove the symbolic link.
Note that this procedure must be repeated anytime you are doing a 32-bit Web Tier installation on a 64-bit system, including the installation of a patch set.
8.3.2 Starting the Generic Installer with a 32-Bit JDK on a 64-Bit Operating System
If you are installing Oracle SOA Suite, Oracle WebCenter Portal, Oracle WebCenter Content, Oracle Application Developer, Oracle Service Bus, or Oracle Identity and
Access Management on any supported 64-bit operating system with a 32-bit JDK, you must specify the JRE_LOCATION using the -jreLoc parameter from the
command line when you start the product installer. For example:
./runInstaller -jreLoc JRE_LOCATION
Normally, if you do not use the -jreLoc parameter you will be prompted to specify the JRE_LOCATION from the command line. However, this option is not supported
in such cases, and the installer will not start.
8.4 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, you must modify the value of the SHMMAX kernel parameter to avoid
seeing errors generated by the Oracle Universal Installer. To do so:
1. Change the value of SHMMAX to 4294967295 by including the following line in /etc/sysctl.conf:
kernel.shmmax = 4294967295
2. Activate the new SHMMAX setting by running the command:
/sbin/sysctl -p
3. Start the Oracle Universal Installer and install your software.
8.5 Installing on Operating Systems Not Certified at the Time of Product Release
In some cases, an operating system will become certified for use with Oracle Fusion Middleware products after a particular release has been made available. If you try
to install your Oracle Fusion Middleware product on one of these newly-certified operating systems, the product installer will give you a warning message during startup,
indicating that the operating system on which you are installing is not valid. For example:
Warning:
Checking operating system certification
Expected result: One of
enterprise-5.4,enterprise-4,enterprise-5,redhat-5.4,redhat-4,redhat-5,SuSE-10
Actual Result:SuSE-11
Check complete. The overall result of this check is: Failed
Problem: This Oracle software is not certified on the current operating system.
To work around this issue, you can click the Continue button to ignore this warning message, or you can start the installer with the -ignoreSysPrereqs option. For
example:
./runInstaller -ignoreSysPrereqs
This issue is currently seen in the platform, product, and release combinations described in Table 11:
Table 11 When is -ignoreSysPrereqs Needed?
Release Platform To Install This Product: Perform These Steps: Use -ignoreSysPrereqs?
11g Release 1 (11.1.1.3.0)
11g Release 1 (11.1.1.4.0)
SUSE 11
IBM AIX 7.1
Oracle Portal, Forms,
Reports and Discoverer
Run the 11g Release 1 (11.1.1.2.0) installer as
described in Oracle Fusion Middleware Installation
Guide for Oracle Portal, Forms, Reports and
Discoverer, then use the Patch Set Installer to
update your software to 11g Release 1
(11.1.1.3.0) or 11g Release 1 (11.1.1.4.0) as
described in Oracle Fusion Middleware Patching
Guide.
Yes when running the 11g Release 1
(11.1.1.2.0) product installer.
No when running the Patch Set Installer.
11g Release 1 (11.1.1.5.0) SUSE 11
IBM AIX 7.1
All certified Oracle Fusion
Middleware products.
For all products that require an 11g Release 1
(11.1.1.2.0) installer, run the 11g Release 1
(11.1.1.2.0) installer as described in that product's
installation guide, then use the Patch Set Installer
to update your software to 11g Release 1
(11.1.1.5.0) as described in Oracle Fusion
Middleware Patching Guide.
For all other products, run the installer as
described in that product's installation guide.
No.
Solaris 11
Oracle Linux 6
Red Hat Linux 6
z/Linux
All certified Oracle Fusion
Middleware products.
For all products that require an 11g Release 1
(11.1.1.2.0) installer, run the 11g Release 1
(11.1.1.2.0) installer as described in that product's
installation guide, then use the Patch Set Installer
to update your software to 11g Release 1
For all other products, run the installer as
described in that product's installation guide.
Yes.
11g Release 1 (11.1.1.6.0) SUSE 11
IBM AIX 7.1
Solaris 11
Oracle Linux 6
Red Hat Linux 6
All other certified Oracle
Fusion Middleware products,
except Oracle Service Bus on
Red Hat Linux 6 (see next
row)
Run the installer as described in the product's
installation guide.
No.
Red Hat Linux 6 Oracle Service Bus Run the installer as described in the product's
installation guide.
Yes.
z/Linux All certified Oracle Fusion
Middleware products
installation guide.
Yes.
11g Release 1 (11.1.1.7.0) SUSE 11
IBM AIX 7.1
Solaris 11
Oracle Linux 6
Red Hat Linux 6
z/Linux
All other certified Oracle
Fusion Middleware products
installation guide.
No.
Note:
The -ignoreSysPrereqs option should only be used if ALL of the following conditions are met:
It should only be used with the specific combination of products, releases, and operating systems listed in Table 11.
Your operating system is certified for use with Oracle Fusion Middleware, as described in the System Requirements and Supported Platforms for
Oracle Fusion Middleware 11gR1 document (see Section 2, "Using This Document with the Certification Matrix and Product Installation Guide").
Your operating system adheres to all the requirements and specifications as described in Section 6, "System Requirements for UNIX Operating
Systems" and Section 7, "System Requirements for Windows Operating Systems".
9 Database Requirements and Specifications
This section contains important information about database configuration for Fusion Middleware and RCU.
The following topics are covered:
Section 9.1, "Finding a Certified Database"
Section 9.2, "Preparing Oracle Database for use with Oracle Identity Management Products"
Section 9.3, "Notes for Databases and the MDS Schema"
9.1 Finding a Certified Database
Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System
Configurations page for the latest information on certified databases.
See the Current System Certification tab for Oracle databases, or the Non Oracle DBs Certification tab for third-party databases.
9.2 Preparing Oracle Database for use with Oracle Identity Management Products
Section 9.2.1, "Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager"
Section 9.2.2, "Using Oracle Database 11g (11.2.0.1) with OID and Oracle Data Vault"
9.2.1 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 Manager 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 (32-Bit). Patches for all operating systems (Linux, 32-bit Windows and 64-bit Windows) are identified.
9.2.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:
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 => '%'
9.3 Notes for Databases and the MDS Schema
The Oracle Metadata Services (MDS) Repository contains metadata for certain types of deployed applications. This includes custom Java EE applications developed by
your organization and some Oracle Fusion Middleware component applications, such as Oracle B2B.
The MDS Repository supports Oracle databases, as well as non-Oracle databases, including SQL Server, DB2, and MySQL. For more information about the supported
versions of these databases, see the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware
Supported System Configurations page, as described in Section 2, "Using This Document with the Certification Matrix and Product Installation Guide".
Section 9.3.1, "Notes for Using an Oracle Database for the MDS Schema"
Section 9.3.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema"
Section 9.3.3, "Notes for Using an IBM DB2 Database for the MDS Schema"
Section 9.3.4, "Notes for Using a MySQL Database for the MDS Schema"
9.3.1 Notes for Using an Oracle Database for the MDS Schema
Note that when you use an Oracle Database, the MDS database user created by Repository Creation Utility (RCU) requires EXECUTE privilege on DBMS_OUTPUT and
DBMS_LOB. When you create a metadata repository using RCU, if PUBLIC does not have EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB, the RCU user must have
the privilege to grant EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB to the MDS user.
To ensure that you have the correct privileges, login to RCU as a SYSDBA or as a DBA user who has EXECUTE privilege with GRANT OPTION on DBMS_OUTPUT and
DBMS_LOB.
9.3.2 Notes for Using a Microsoft SQL Server Database for the MDS Schema
Note the following about using SQL Server as the database for MDS:
To create a metadata repository in SQL Server, set READ_COMMITTED_SNAPSHOT to ON for the hosting database. This enables the needed row versioning
support. This feature can be enabled using the SQL command ALTER DATABASE, as in the following example:
ALTER DATABASE mds SET READ_COMMITTED_SNAPSHOT ON
You should use case-sensitive collation to support the case-sensitive semantics in the metadata repository. For example, if Latin1_General is used, select the
SQL_Latin1_General_CP1_CS_AS collation using the following SQL command:
ALTER DATABASE mds COLLATE SQL_Latin1_General_CP1_CS_AS
In the example, the substring CS denotes case sensitivity. In you ned to configure your database for case-insensitive collation, use the CI substring.
There are some minor differences between an Oracle schema and a SQL Server schema. The length of the certain text fields are shorter for a SQL Server
schema. For example, the full path name of the metadata in SQL Server is limited to 400 characters.
9.3.3 Notes for Using an IBM DB2 Database for the MDS Schema
Note the following about using DB2 as the database for MDS:
DB2 9.7 or later must be used for MDS repository to work properly.
Make sure that CUR_COMMIT is set to "ON", which is the default value for a newly installed DB2 9.7 database. This setting can be verified using following DB2
command:
db2 connect to your_database user admin_user
db2 "get db cfg" | grep -I commit
Curently Committed (CUR_COMMIT) = ON
Set the lock timeout parameter of the database to a low value. Unlike Oracle databases, with DB2, if one user is updating a row, under some conditions, another
user may be blocked when updating a different row and must wait until the 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.
To query the lock timeout value for your DB2 database, use the following command:
db2 'get database config for database_alias' | grep -i timeout
If the value is too high, change it. For example, to change the lock timeout value to 180 seconds, use the following command:
db2 'update database config for database_alias using locktimeout 180'
Choose a proper value for the locktimeout parameter. If a large value is used, it will affect system throughput, since the transaction has to wait a very long time
before giving up. If the value is set too small, users will see many timeout exceptions if the database is processing many long running transactions.
Set the DB2 registry variables DB2_EVALUNCOMMITTED, DB2_SKIPINSERTED, and DB2_SJIPDELETED to OFF to avoid deadlock and locking issues. By default, they
are set to OFF. To view the current registry variables setting, use the db2set -all command.
If they are not set to OFF, use the following commands:
db2set DB2_EVALUNCOMMITTED=OFF
db2set DB2_SKIPINSERTED=OFF
db2set DB2_SKIPDELETED=OFF
Restart the database server using the using db2stop and db2start commands.
DB2 may escalate a row lock to a table lock due to memory stress or lock usage. As the result, a user's transaction may be rolled back as a victim of deadlock
or lock timeout. To reduce lock escalation, you can increase the size of the MAXLOCKS and LOCKLIST configuration parameters. Use the following commands:
db2 'update database config for database_alias using locklist value'
db2 'update database config for database_alias using maxlocks value'
For 11g Release 1 (11.1.1.8.0) and later, the MAXLOCKS value should be set to 20, and the LOCKLIST value should be set to 70000.
The isolation level must be set to Currently Committed. To verify the setting, use the following command:
db2 'get database config for database_alias' | grep -i commit
To set the isolation level to Currently Committed, use the following command:
db2 'update database config for database_alias using CUR_COMMIT ON'
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:
db2 'update database config for database_alias using LOGFILSIZ 10000'
db2 'update database config for database_alias using LOGPRIMARY 50'
If an MDS DB2 data source is created under an IBM WebSphere application server and the IBM DB2 JCC driver is chosen for the data source, the
progressiveStreaming=2 property must be added to the property list of the data source. In effect, progressive streaming will be disabled. Without this
property setting, MDS may run into issues in accessing document contents saved in a large object (LOB) column in the MDS repository.
9.3.4 Notes for Using a MySQL Database for the MDS Schema
Note the following about using MySQL as the database for MDS:
MySQL 5.5.14 or later must be used for the MDS repository to work properly.
You must select MySQL's Innodb engine as the database engine during database installation.
Set the lock timeout parameter of the database to a low value. To query the lock timeout value for your MySQL database, use the following command under
the MySQL client:
show variables like 'innodb_lock_wait_timeout';
If the value is too high, change it. For example, to change the lock timeout value to 600 seconds at database level, use the following command:
set global innodb_lock_wait_timeout=600
The database will not remember this setting after it is rebooted. To keep the setting, make the corresponding changes in the my.cnf file.
Choose a proper value for the innodb_lock_wait_timeout parameter. If a large value is used, it will affect system throughput, since the transaction has to
wait a very long time before giving up. If the value is set too small, users will see many timeout exceptions if database is processing many long running
transactions.
MySQL provides several my.cnf templates under the mysql_home/support-files directory. To configure MySQL to work property with MDS, use my-
large.cnf as the starting point for your my.cnf and make the following setting changes:
# The following stack memories must be set to a large enough value:
thread_stack=1024k
# Increase max_allowed_packet to allow for longer lobs.
max_allowed_packet = 64M
# max_sp_recursion_depth should be 64
max_sp_recursion_depth=64

# Set the sql_mode to STRICT_TRANS_TABLES, so MySQL will report an error if a
# string value is too long for the table field. By default, MySQL will
silently truncate a string value.
# Also set NO_BACKSLASH_ESCAPES so strings like '\' will be accepted.
sql_mode=STRICT_TRANS_TABLES,NO_BACKSLASH_ESCAPES

# Set collation and character set for the server.
character-set-server=utf8mb4
collation-server=utf8mb4_bin

# Transaction isloatoin has to be "READ-COMMITED".
transaction-isolation=READ-COMMITTED
# Uncomment the following settings for InnoDB tables
innodb_data_home_dir = /usr/local/mysql/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /usr/local/mysql/data
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 256M
innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 64M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

# The following three parameters will ensure that MDS repository indexes
# can be created successfully.
innodb_file_per_table=true
innodb_file_format=Barracuda
innodb_large_prefix=true

# If log-bin is turned on, the following parameter
# must be on to ensure MDS triggers can be created successfully.
log_bin_trust_function_creators=ON
binlog_format=mixed

# In the [client] section of the configuration file, set the character set.
default_character_set=utf8mb4
Oracle WebLogic Server 10.3.5 and earlier versions do not have MySQL JDBC driver configured. Use a later version of Oracle WebLogic Server if you want to
choose a MySQL database as a data source.
Tips for starting MySQL Server using mysqld_safe: It is suggested to use the "--defaults-file=your_my.cnf" parameter when you start mysqld_safe, which will
ensure a desired copy of my.cnf is used by your mySQL server. The "--defaults-file" parameter has to be the first parameter of your mysqld_safe command.
For example:
./mysqld_safe --defaults-file=/etc/my.cnf --user=mysql &
Be sure to set the access privileges of your my.cnf file to "-rw-r--r--". MySQL will ignore your my.cnf if other users have "write" access.
10 Repository Creation Utility (RCU) Requirements
Section 10.1, "RCU Supported Platforms and Versions"
Section 10.2, "RCU Privileges for System Packages"
Section 10.3, "RCU Requirements for Oracle Databases"
Section 10.4, "RCU Requirements for Microsoft SQL Server Databases"
Section 10.5, "RCU Requirements for IBM DB2 Databases"
Section 10.6, "RCU Requirements for MySQL Databases"
10.1 RCU Supported Platforms and Versions
Section 10.1.1, "RCU Supported Platforms"
Section 10.1.2, "Using the Correct RCU Version"
10.1.1 RCU Supported Platforms
RCU is available on any 32-bit x86 Linux and 32-bit Microsoft Windows operating system used with Oracle Fusion Middleware. You can run RCU from these machines to
connect to any certified local or remote Oracle, IBM DB2, MySQL, or Microsoft SQL Server database in order to create the schemas required by Fusion Middleware
components. The database can be running on any operating system platform that is supported by that particular database.
Beginning with 11g Release 1 (11.1.1.4.0) and later, RCU can also be run on any 64-bit x86 Linux and 64-bit Microsoft Windows operating system used with Oracle
Fusion Middleware. On 64-bit Linux operating systems, you must run the following command before starting RCU:
set linux32 bash
To view the system requirements for certified 32-bit and 64-bit Linux operating systems, see Section 6.2, "Linux Operating System Requirements". RCU can be run on
your Linux operating system as long as these system requirements are met.
To view the system requirements for certified 32-bit and 64-bit Windows operating systems, see Section 7, "System Requirements for Windows Operating Systems".
RCU can be run on your Windows operating system as long as these system requirements are met.
10.1.2 Using the Correct RCU Version
Make sure that the RCU version number matches the version number of the Oracle Fusion Middleware product you are installing and using. You may encounter
problems if your RCU version number does not match your product version number.
For more information, refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files, which contain the correct RCU version to download
for each Oracle Fusion Middleware release.
10.2 RCU Privileges for System Packages
Unless explicitly stated otherwise, RCU expects system packages to be configured with the default privileges granted by the Database Configuration Assistant.
Modifying System packages to introduce more restrictive privileges may cause RCU to fail for some Oracle Fusion Middleware 11g components.
10.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 10.3.1, "General Oracle Database Requirements"
Section 10.3.2, "DBMS_SHARED_POOL and XAVIEWS Must be Created on Oracle Databases for Oracle Identity Management"
Section 10.3.3, "Setting the parallel_max_servers Parameter for the ODS Schema"
Section 10.3.4, "Setting the nls_length_semantics Parameter in your Oracle Database for Oracle Discoverer"
Section 10.3.5, "Applying Oracle Database Patch 8625762 for Oracle Business Process Management Suite"
Section 10.3.6, "Installing Oracle Text for Oracle Portal"
Section 10.3.7, "Applying Patch 16266667 for Oracle Portal"
Section 10.3.8, "Component-Specific Requirements for Oracle Databases"
10.3.1 General Oracle Database Requirements
RCU checks for the following on Oracle databases:
Database version is equal to or higher than 10.2.0.4.0 in 10g or equal to or higher than 11.1.0.7.0 in 11g.
Database is installed with Oracle JVM enabled. Refer to your database documentation for information about how to do this.
Database user has SYSDBA role.
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
Refer to your Oracle database documentation for more information about database users and roles.
Character set is AL32UTF8.
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. Oraclestrongly recommends using AL32UTF8 as the database character set.
You can ignore this warning and continue using RCU.
Note:
If you are installing Oracle WebCenter Portal or Oracle WebCenter Content, it is strongly recommended that you 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, you should configure your database to use AL32UTF8 character set encoding.
The SHARED_POOL_SIZE is greater than or equal to 147456KB.
The SGA_MAX_SIZE is greater than or equal to 147456KB.
The DB_BLOCK_SIZE is greater than or equal to 8KB
10.3.2 DBMS_SHARED_POOL and XAVIEWS Must be Created on Oracle Databases for Oracle Identity Management
The following packages must be installed as SYS user on Oracle databases prior to creating Oracle Identity Management schemas:
DBMS_SHARED_POOL
XAVIEWS
For more information, see the following:
For more information on DBMS_SHARED_POOL, see "DBMS_SHARED_POOL" in Oracle Database PL/SQL Packages and Types Reference.
For more information on XAVIEWS, see "Using JDBC XA Drivers with WebLogic Server" in Oracle Fusion Middleware Programming JTA for Oracle WebLogic Server.
10.3.3 Setting the parallel_max_servers Parameter for the ODS Schema
For the Oracle Internet Directory (ODS) schema, set parallel_max_servers=1. This setting should be used for 11gR2 Oracle RAC systems with more than 32 CPUs.
After Oracle Internet Directory is up and running, you should set the parallel_max_servers parameter to a higher value. For more information, see
"PARALLEL_MAX_SERVERS" in the Oracle Database VLDB and Partitioning Guide.
10.3.4 Setting the nls_length_semantics Parameter in your Oracle Database for Oracle Discoverer
Oracle Discoverer 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.
To check the values of this parameter using SQL*Plus, you can use the show parameters command:
prompt> sqlplus "sys/password as sysdba"
SQL> show parameters nls_length_semantics
Replace password with the actual password for the SYS user.
Alternatively, you can check the values by querying the V$PARAMETER view:
prompt> sqlplus "sys/password as sysdba"
SQL> select name,value from v$parameter;
10.3.5 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 8625762 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.
10.3.6 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.
10.3.7 Applying Patch 16266667 for Oracle Portal
Oracle Portal creation requires patch 16266667.
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.
10.3.8 Component-Specific Requirements for Oracle Databases
Table 12 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. Refer to the Oracle Database Administrator's Guide to find instructions on how to modify database parameters.
When the tablespaces are created, RCU will automatically create them with the necessary tablespace sizes.
The "Oracle EBR?" column indicates whether or not the schema is also supported on Oracle Databases with Edition-Based Redefinition (EBR).
All requirements listed are the minimum requirements; please read them carefully as some components within the same product have different requirements. For
example, if you are performing a full Oracle Identity Management installation including Oracle Identity Manager, then the open_cursors parameter must be set to
800. However, if you are installing Oracle Identity Management without Oracle Identity Manager, then open_cursors can be set to 500, which is required for Oracle
Internet Directory.
Table 12 RCU Component-Specific Requirements for Oracle Databases
Component Schema Owner Requirement Oracle EBR?
AS Common Schemas
Metadata Services prefix_MDS None. Yes
Audit Services prefix_IAU None. Yes
Audit Services for OES prefix_IAUOES None. Yes
prefix_IAUOES
Enterprise Scheduler Services prefix_ESS None. Yes
Oracle Platform Security Services prefix_OPSS None. Yes
Identity Management Schemas
Oracle Internet Directory prefix_ODS processes: 500
open_cursors: 500
No
Oracle Identity Federation prefix_OIF None. Yes
Oracle Identity Manager prefix_OIM open_cursors: 800 Yes
Oracle Access Manager prefix_OAM None. Yes
Oracle Adaptive Access Manager prefix_OAAM processes: 250
sessions: 250
Oracle Database must be Enterprise Edition.
Yes
Oracle Adaptive Access Manager (Partition
Support)
prefix_OAAM_PARTN processes: 500
sessions: 500
Oracle Database must be Enterprise Edition.
Yes
Authorization Policy Manager prefix_APM None. Yes
Oracle Data Integrator Schemas
Master and Work Repository prefix_ODI_REPO None. Yes
Oracle Business Intelligence Schemas
Business Intelligence Platform prefix_BIPLATFORM None. Yes
WebCenter Content Schemas
Oracle Information Rights Management prefix_ORAIRM None. No
Oracle WebCenter Content Server - Complete prefix_OCS None. Yes
Oracle WebCenter Content Server - Search Only prefix_OCSSEARCH None. No
Oracle WebCenter Content: Records prefix_URMSERVER None. No
Oracle WebCenter Content: Imaging prefix_IPM None. Yes
WebLogic Communication Services Schemas
Presence prefix_ORASDPXDMS None. No
SIP Infrastructure Subscriber Data Service prefix_ORASDPSDS None. No
SIP Infrastructure Location Service prefix_ORASDPLS None. No
SOA and BPM Infrastructure Schemas
Oracle BAM prefix_ORABAM None. No
SOA Infrastructure prefix_SOAINFRA processes: 200 Yes
User Messaging Server (ORASDPM) prefix_ORASDPM None. Yes
WebCenter Portal Schemas
Spaces and Services prefix_WEBCENTER processes: 300 Yes
Discussions prefix_DISCUSSIONS None. Yes
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
Yes
Activity Graph and Analytics prefix_ACTIVITIES None. Yes
Portal and Business Intelligence Schemas
Oracle Portal prefix_PORTAL Portal schema name cannot be longer then 30 characters. No
Oracle Discoverer prefix_DISCOVERER None. No
Enterprise Performance Management Schemas
Registry prefix_EPM None.
10.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 10.4.1, "General Microsoft SQL Server Database Requirements"
Section 10.4.2, "Creating Oracle WebCenter Portal Schemas on Microsoft SQL Server Databases"
Section 10.4.3, "Component-Specific Requirements for Microsoft SQL Server Databases"
10.4.1 General Microsoft SQL Server Database Requirements
RCU checks for the following on Microsoft SQL Server databases:
Database version is equal to or higher than 2005.
Database user (db_owner) should have SYSDBA or DBA privileges.
10.4.2 Creating Oracle WebCenter Portal 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 Section 9.3.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema" for more information.
10.4.3 Component-Specific Requirements for Microsoft SQL Server Databases
Table 13 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.
Table 13 RCU Component-Specific Requirements for Microsoft SQL Server Databases
Component Schema Owner Requirement
AS Common Schemas
Metadata Services prefix_MDS See Section 9.3.2, "Notes for Using a Microsoft SQL Server Database for the MDS
Schema".
Master and Work Repository prefix_ODI_REPO Database must be configured to use case insensitive collation.
Business Intelligence Schemas
Business Intelligence Platform prefix_BIPLATFORM None.
Oracle Information Rights Management prefix_ORAIRM None.
Oracle WebCenter Content Server - Complete prefix_OCS None.
Oracle WebCenter Content: Records prefix_URMSERVER None.
Oracle WebCenter Content: Imaging prefix_IPM None.
SOA Infrastructure Schemas
SOA Infrastructure prefix_SOAINFRA The read_committed_snapshot option must be turned on, and the database
must be configured to use case sensitive collation.
User Messaging Service prefix_ORASDPM The read_committed_snapshot option must be turned on, and the database
WebCenter Portal Schemas
Spaces and Services prefix_WEBCENTER The read_committed_snapshot option must be turned on, and the database
Discussions prefix_DISCUSSIONS The read_committed_snapshot option must be turned on, and the database
Portlet Producers prefix_PORTLET The read_committed_snapshot option must be turned on, and the database
Activity Graph and Analytics prefix_ACTIVITIES Database must be configured to use case insensitive collation.
10.5 RCU Requirements 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 10.5.1, "Creating Database Operating System Users"
Section 10.5.2, "Size Limit for Schema Prefixes (Linux Only)"
Section 10.5.3, "Configuring Your DB2 Database"
Section 10.5.4, "RCU Supported Schemas for IBM DB2 Databases"
10.5.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).
10.5.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.
10.5.3 Configuring Your DB2 Database
For important information about configuring your IBM DB2 database, refer to Section 9.3.3, "Notes for Using an IBM DB2 Database for the MDS Schema".
10.5.4 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 14 shows the schemas that are
supported in IBM DB2 databases.
Note:
Table 14 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 10.5.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 10.5.1, "Creating Database Operating System Users" for important information about creating the operating system users.
Table 14 Supported Schemas for IBM DB2 Databases
Component IBM DB2 Schema Name Operating System User Name
AS Common Schemas
Metadata Services prefix_MDS prefix_mds
SOA and BPM Infrastructure Schemas
SOA Infrastructure prefix_SOA prefix_soa
User Messaging Service prefix_UMS prefix_ums
Oracle WebCenter Portal Schemas
Spaces and Services prefix_WC prefix_wc
Portlet Producers prefix_PT prefix_pt
Discussions prefix_DS prefix_ds
Activity Graph and Analytics prefix_AG prefix_ag
Oracle Business Intelligence Schemas
Business Intelligence Platform prefix_BI prefix_bi
Master and Work Repository prefix_ODI prefix_odi
Oracle Information Rights Management prefix_IRM prefix_irm
Oracle WebCenter Content Server prefix_OCS prefix_ocs
Oracle WebCenter Content: Records prefix_URM prefix_urm
Oracle WebCenter Content: Imaging prefix_IPM prefix_ipm
10.6 RCU Requirements for MySQL Databases
Section 10.6.1, "RCU Supported Schemas for MySQL Databases"
Section 10.6.2, "MySQL Requirements for the Oracle Data Integrator Schema"
10.6.1 RCU Supported Schemas for MySQL Databases
Not all schemas are supported on MySQL databases. Table 15 shows the schemas that are supported in MySQL databases.
Table 15 RCU Component-Specific Requirements for MySQL Databases
Component Schema Owner Requirement
AS Common Schemas
Metadata Services prefix_MDS See Section 9.3.4, "Notes for Using a MySQL Database for the MDS
Schema".
Master and Work Repository prefix_ODI_REPO Database must be configured to use case insensitive collation.
10.6.2 MySQL Requirements for the Oracle Data Integrator Schema
In order to create the Oracle Data Integrator schema in a MySQL database, the following must be set:
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix = 1
LOG_BIN_TRUST_FUNCTION_CREATORS = on
11 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Copyright 2013, 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 is software or related documentation that 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for
any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware 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.

Previous
Copy right 2013, Oracle and/or its affiliates. All rights reserv ed.
Legal Notices

Contents

Oracle® Fusion Middleware System Requirements and Specifications

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle® Fusion Middleware System Requirements and Specifications

Uploaded by

Copyright:

Available Formats

9/12/2014 Oracle Fusion Middleware System Requirements and Specifications

You might also like