System Requirements and Specifications
12c (12.2.1.0.0)
E62221-01
July 2016
This document contains system and platform-specific information for Oracle Fusion Middleware products.
The following topics are covered in this document:
This document is intended for use in conjunction with the various Oracle Fusion Middleware product installation guides and the Oracle Fusion Middleware 12c Release 1 Certifications.
Consider the following pre-installation workflow:
The Oracle Fusion Middleware 12c 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 reference My Oracle Support Certifications, which is a self-service certification application which provides a structured display of most common certification data. For more information, go the following URL, and click the Certifications tab:
http://support.oracle.com/
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.
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.
Oracle Fusion Middleware requires a minimum 1-GHz CPU.
Most Fusion Middleware products are available as platform-generic distributions in .jar file format. These distributions do not include a JDK. To run the installer in a .jar distribution, you must have a certified the JDK already installed on your system.
Some products (for example, Oracle HTTP Server) have a .bin (for UNIX operating systems) or .exe (for Windows operating systems) installer; in these cases, a platform-specific JDK is included with the distribution and you do not need to install a JDK separately. However, it may be recommended that you upgrade this JDK to a more recent version, depending on the JDK versions that are certified.
At the time this document was published, the certified JDK was <version #>. For information about the latest certified JDKs, refer to the certification document for your software version on the Oracle Fusion Middleware Supported System Configurations page for certified JDKs.
|
Setting the JAVA_HOME Environment Variable: It is generally a good practice to set the JAVA_HOME variable so it references the location of the JDK software you will be using to run the installer and other Oracle Fusion Middleware utilities, such as the Repository Creation Utility (RCU). This ensures that the Oracle Fusion Middleware software is using the proper version of the JDK software.For example, if RCU cannot locate the proper JDK software, RCU will fail with the following error: ""Cannot Find the File javaw." |
This section contains the general, minimum memory and disk space requirements for Oracle Fusion Middleware, including Oracle Fusion Middleware Infrastructure.
The following topics are covered:
The following sections provide general information about how to determine the amount of memory required to run the Oracle Fusion Middleware products you have purchased:
Section 4.1.1, "Minimum Memory Requirement for Installing Oracle Fusion Middleware"
Section 4.1.2, "Using a Formula to Determine Memory Requirements for a Specific Deployment"
Section 4.1.3, "Example: Determining Memory Requirements for a Development Environment"
Section 4.1.4, "Example: Determining Memory Requirements for a Production Environment"
Section 4.1.5, "Considering the Impact of Open File and Process Limits on Memory Requirements"
Unless otherwise noted, Table 1 lists the general minimum memory requirements for installing Oracle Fusion Middleware products.
|
Notes: For the purposes of this document, memory requirements fall into two categories: physical memory (the amount of physical RAM installed on host) and the minimum available memory, which includes swap space in addition to the physical memory.The memory requirements listed here are minimum requirements; the actual required memory will vary, depending upon the number of Managed Servers and the number of Oracle Fusion Middleware products you configure in the domains on each host. For some guidelines about determining the amount of memory required for a specific deployment, see Section 4.1.2. If you plan to install and configure a database instance on the same server, you should add at least an additional 2 GB of physical and 2 GB of available memory. for more information about memory requirements for the database, see the documentation for your database software version. |
Oracle Fusion Middleware installations vary widely in terms of how the Oracle WebLogic Server domains that support them are configured. For example, in some highly available production environments, you might have several Managed Servers running on a each host. On the other hand, a single Administration Server, configured in a supported compact domain configuration is adequate for some development purposes.
To estimate the amount of required memory required to run Oracle Fusion Middleware 12c in a particular deployment configuration, you can consider the amount of memory required by the operating system and other software, and then add a set amount of memory that will be required for each Java Virtual Machine (JVM) that you plan to configure on the host. Each Managed Server configured in a domain represents a single JVM instance.
In general, you can use the following formula as a general guideline to predict the minimum available memory requirements for Oracle Fusion Middleware:
3 GB of available memory for the operating system and other software
+ 3 GB of available memory for each Managed Server
-----------------------------------------------------
Total required available memory
It is important to note that this is a general guideline and the actual memory required for the operating system or a specific Managed Server can vary widely, depending on the resources and services targeted to the host or to the Managed Server.
When determining memory required for a development environment, consider the type of domain you are using to test your applications.
If you are using the integrated Oracle WebLogic Server domain, which you run directly from Oracle JDeveloper, see Section 5.7.
If you are configuring a compact domain for your development system, you can use the general memory formula in Section 4.1.2 as a guideline to determine the initial required memory requirements.
In the compact domain scenario, all resources are targeted to the Administration server, so you need enough memory to support the operating system and one Administration Server:
3 GB for the operating system and other software + 3 GB for the Administration Server ------------------------------------- 6 GB of available memory
In a production environment, Oracle recommends as a best practice that you target products and services to specific Managed Servers and clusters, based on the resources required by the products and services.
For example, in a typical enterprise deployment of Oracle SOA Suite, you target Oracle Web Services Manager (OWSM) to one cluster and Oracle SOA Suite to another cluster. This can result in a domain with multiple Managed Servers on each host. As you add additional managed clusters, the memory requirements increase.
For example, if you are planning to configure a Oracle WebLogic Server domain with an Administration Server and two Managed Servers, then you could use the following formula to determine the minimum required available memory:
3 GB for the operating system and other software 3 GB for the Admin Server + 6 GB for the two Managed Servers -------------------------------------- 12 GB
When determining the memory requirements for a production environment, you should also take into account other operating system settings, including the number of file descriptors (open files) allowed per process and the number of processes required for each product or service that is targeted to a Managed Server.
For information about the recommended minimum open file and process limits for Oracle Fusion Middleware, see Section 7.1.2, "Setting the Open File Limit and Number of Processes Settings on UNIX Systems".
For an example of the minimum amount of memory, file descriptors, and processes required for an enterprise deployment in a production environment, see "Typical Memory, File Descriptors, and Processes Required for an Oracle SOA Suite Enterprise Deployment" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.
For the list of recommended memory settings for Oracle WebCenter Sites (Version 7.5.4 and later), see Recommended Memory Settings for WebCenter Sites.
The installation program uses a temporary directory into which it extracts the files that are needed to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory after the installation process. The files in the temporary directory require approximately 2.5 times the space that is ultimately required for the installation.
By default, the installation program uses the following temporary directories:
Windows platforms—directory referenced by the TMP system variable
UNIX platforms—system-dependent temporary directory
|
Note: If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program. |
To make sure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose by doing one of the following (depending on your operating system:
On Windows operating systems, set the TMP system variable to a directory of your choice.
Run the installation program from the command line and include the -Djava.io.tmpdir=tmpdirpath option, replacing tmpdirpath with the full path of the directory you want to designate as a temporary storage area for the installation program.
For example, to set up the temporary directory while running the Oracle Fusion Middleware Infrastructure installer for Windows, execute the following command:
java -Djava.io.tmpdir=C:\Temp -jar fmw_infra_121200.jar
Similarly, to set up the temporary directory while running a platform-specific installer, such as the Oracle HTTP Server installer on a Linux system, execute the following command:
./ohs_linux64.bin -J-Djava.io.tmpdir=/scratch/<temp dir>
This section provides memory and disk space requirements for specific Oracle Fusion Middleware products:
Section 5.3, "Oracle WebLogic Server and Coherence Disk Space Requirements"
Section 5.4, "Oracle Fusion Middleware Infrastructure Disk Space Requirements"
Section 5.8, "Oracle SOA Suite and Business Process Management Requirements"
Section 5.10, "Oracle WebCenter Content User Interface Database Driver Requirements"
This section contains prerequisite information for the Oracle Universal Installer (OUI). The requirements in this section must be met in order for the installer to start:
The items in Table 2 are checked as the installer is being started:
Table 2 Oracle Universal Installer Startup Requirements
| Category | Accepted or Minimum Values |
|---|---|
|
Platforms |
For a complete list of supported platforms, refer to Oracle Fusion Middleware Supported System Configurations page, as described in Section 1, "Using This Document With the Certification Matrix and Product Installation Guides". |
|
CPU Speed |
At least 300MHz. |
|
Monitor |
At least 256 colors (this is a requirement for the graphical mode installer only). |
|
Swap Space |
At least 512MB. |
|
JDK |
See Section 3 for more information about JDK verification on your system. |
|
Temp Space |
At least 300MB. Note that the temporary space noted here is in addition to the temporary space required for installer extraction as mentioned in Section 4.2. |
If you are running Oracle Universal Installer on a certified Linux operating system, you must modify the value of the SHMMAX kernel parameter to avoid seeing errors generated by the Oracle Universal Installer.
|
Note: The following examples are for Linux operating systems. Consult your operating system documentation to determine the commands to be used on your system. |
To set the SHMMAX kernel parameter:
Change the value of SHMMAX to 4294967295 by including the following line in /etc/sysctl.conf:
kernel.shmmax = 4294967295
Activate the new SHMMAX setting by running the command:
/sbin/sysctl -p
Start the Oracle Universal Installer and install your software.
This section contains the following:
You can run RCU from any machine to connect to any certified local or remote database in order to create the schemas required by your Oracle Fusion Middleware product. The database can be running on any operating system platform that is supported by that particular database.
RCU checks for the following on Oracle databases:
Database version is:
Equal to or higher than 11.2.0.4 for 11g Release 2 databases
Equal to or higher than 12.1.0.1 for 12c databases
|
Note: Always refer to the appropriate certification document for your release on the Oracle Fusion Middleware Supported System Configurations page for the latest certification information.In some cases, additional database certifications may be added before RCU is updated. When you run RCU, you may receive a warning that the database on which you are installing the schemas is not supported; as long as the database version is listed in the certification document, you can safely ignore this warning. |
Database is installed with Oracle JVM enabled. Refer to your database documentation for information about how to do this.
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.
The following database parameters are set as specified:
| Parameter | Minimum Required Value |
|---|---|
SHARED_POOL_SIZE |
147,456 KB |
SGA_MAX_SIZE |
147,456 KB |
DB_BLOCK_SIZE |
8 KB |
session_cached_cursors |
100 |
processes |
500 |
open_cursors |
800 |
db_files |
600 |
Table 3 shows the disk space requirements for Oracle WebLogic Server and Coherence.
Table 4 shows the disk space requirements for Oracle Fusion Middleware Infrastructure.
Table 5 shows the disk space requirements for Oracle HTTP Server.
Table 6 shows the system requirements for Oracle Data Integrator.
Table 6 Oracle Data Integrator Requirements
| Resource | Recommended Minimum Value |
|---|---|
|
CPU |
Pentium IV 2 GHz or faster |
|
Available Memory |
3 GB of RAM for one agent. For environments with no WebLogic server, the amount of memory you want to allocate to each agent is set by the The value set by For environments with WebLogic server, set the memory allocation by modifying the For more information, refer to "Tuning Java Virtual Machines (JVMs)" in Performance and Tuning for Oracle WebLogic Server in the 12c (12.2.1.0.0) documentation library. |
|
Disk Space |
Standalone Installation: 1 GB Enterprise Installation: 2.5 GB Embedded Enterprise Installation (separate installation required for the Standalone Installation to have access to ODI Studio): 2.5GB |
|
Database Space |
The following are the recommended database storage space values:
|
This section contains the system requirements for Oracle JDeveloper on various operating systems:
Section 5.7.1, "Oracle JDeveloper Requirements on Windows Operating Systems"
Section 5.7.2, "Oracle JDeveloper Requirements on Linux Operating Systems"
Section 5.7.3, "Oracle JDeveloper Requirements on MAC OS X Operating Systems"
Table 7 lists the recommended CPU, memory, display, and hard drive requirements for Windows operating systems:
Table 7 System Requirements for Oracle JDeveloper on Windows Operating Systems
| Resource | Recommended Minimum Value |
|---|---|
|
CPU |
Intel Core 2 i5 or equivalent |
|
Memory |
3 GB of RAM on 32-bit systems 4 GB of RAM on 64-bit systems |
|
Display |
65536 colors, set to at least 1024 X 768 resolution |
|
Hard Drive Space |
3 GB for Studio Edition 90 MB for Java Edition |
Table 8 lists the recommended CPU, memory, display, and hard drive requirements for Linux operating systems:
Table 8 System Requirements for Oracle JDeveloper on Linux Operating Systems
| Resource | Recommended Minimum Value |
|---|---|
|
CPU |
Intel Core 2 i5 or equivalent |
|
Memory |
3 GB of RAM on 32-bit systems 4 GB of RAM on 64-bit systems |
|
Display |
65536 colors, set to at least 1024 X 768 resolution |
|
Hard Drive Space |
3 GB for Studio Edition 90 MB for Java Edition |
Table 9 lists the recommended CPU, memory, display, and hard drive requirements for MAC OS X operating systems:
This section contains the following:
Table 10 shows the minimum disk space requirements for Oracle SOA Suite and Business Process Management:
Task Form Editor has the operating system requirements summarized in Table 11.
Installation of the Oracle Managed File Transfer distribution requires 200 MB of disk space.
The MDS data source in WebCenter Content User Interface cannot work with XA drivers only.
However, by default, the driver Oracle's DB2 XA (Type 4XA) Versions:7.x and later is selected in the JDBC Datasources screen in the Configuration Wizard. However, multi data source is not certified with the DB2 XA driver.
You must select the non-XA Driver, Oracle's DB2 Driver (Type 4) Versions:7.x and later for WebCenter Content User Interface to work properly.
See the 12c (12.2.1) certification document on the Oracle Fusion Middleware Supported System Configurations page for the latest information on certified databases.
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 6.1, "Understanding IPv6 and Oracle Fusion Middleware"
Section 6.2, "Configuration Requirements for Installing on a DHCP Host"
Section 6.3, "Configuration Requirements for Installing on a Non-Networked Computer"
Section 6.4, "Configuration Requirements for Installing on a Multihomed Computer"
Section 6.5, "Correct Format For Entries in the /etc/hosts File"
Oracle Fusion Middleware supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6.) Among other features, IPv6 supports a larger address space (128 bits) than IPv4 (32 bits), providing an exponential increase in the number of computers that can be addressable on the Web.
An IPv6 address is expressed as 8 groups of 4 hexadecimal digits. For example:
2001:0db8:85a3:08d3:1319:8a2e:0370:7334
This section contains the following additional topics to help you understand IPv6 in Oracle Fusion Middleware:
Table 12 describes support for IPv6 by Oracle Fusion Middleware components:
The column IPv6 Only shows whether a component supports using IPv6 only for all communication.
The column Dual Stack shows whether a component supports using both IPv6 and IPv4 for communication. For example, some components do not support using IPv6 only, because some of the communication is with the Oracle Database, which supports IPv4, not IPv6. Those components support dual stack, allowing for IPv6 communication with other components.
Table 12 IPv6 Support in Oracle Fusion Middleware
| Component | IPv6 Only | Dual Stack | Comments |
|---|---|---|---|
|
Oracle Application Development Framework |
Yes |
Yes |
|
|
Oracle HTTP Server |
Yes |
Yes |
To configure Oracle HTTP Server for IPv6, see "Configuring Oracle HTTP Server for IPv6" in Oracle Fusion Middleware Administering Oracle Fusion Middleware. |
|
Oracle WebLogic Server |
Yes |
Yes |
The Oracle WebLogic Server Web Server plug-ins support IPv6, beginning with the 11g release. |
Table 13 shows the supported topologies for IPv4 and IPv6 (dual-stack means that the host is configured with both IPv4 and IPv6):
Table 13 Supported IPv6 Topologies
| Topology | Description |
|---|---|
|
Topology A |
This topology includes:
|
|
Topology B |
This topology includes:
|
|
Topology C |
This topology includes:
|
|
Topology D |
This topology includes:
|
|
Topology G |
This topology includes:
|
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 Oracle Database 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, refer to your operating system documentation for instructions on how to properly configure a loopback adapter.
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 6.2, "Configuration Requirements for Installing on a DHCP Host" to install a loopback adapter and modify the hosts file on your system.
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 (IPv4 example shown below):
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 your Oracle Fusion Middleware components. See "Changing the Network Configuration of Oracle Fusion Middleware" in Oracle Fusion Middleware Administering Oracle Fusion Middleware for more information about additional steps that need to be performed.
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.
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 certification information and would no longer be considered a "certified" platform.
For more ifnormation, see Section 1, "Using This Document With the Certification Matrix and Product Installation Guides".
All packages listed are minimum versions.
The following topics are covered in this section:
This section contains the following:
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. Table 14 describes these environment variables.
Table 14 Language Environment Variables on UNIX Operating Systems
| Variable | Description |
|---|---|
|
|
This environment variable sets the installation default locale. For example: setenv LANG en_US.UTF-8 |
|
|
This environment variable overrides the value of the setenv LC_ALL en_US.UTF-8 |
To check your current locale settings, use the locale command on your system. Below is an example:
locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES= LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL=
In a design-time environment, if you are using Oracle JDeveloper, select Tools -> Preferences -> Environment -> Encoding -> UTF-8 to enable Unicode support.
For more information, see the following topic:
Section 7.1.2.1, "Viewing the Number of Currently Open Files"
Section 7.1.2.2, "Setting the Operating System Open File and Processes Limit"
|
Note: The following examples are for Linux operating systems. Consult your operating system documentation to determine the commands to be used on your system. |
You can see how many files are open with the following command:
/usr/sbin/lsof | wc -l
To check your open file limits, use the commands below.
C shell:
limit descriptors
Bash:
ulimit -n
To change the Open File Limit:
Log in as root and edit the following file:
/etc/security/limits.conf
Add the following lines to the limits.conf file.
* soft nofile 4096 * hard nofile 65536 * soft nproc 2047 * hard nproc 16384
The nofiles values represent the open file limit; the nproc values represent the number of processes limit.
Save the changes, close the limits.conf file.
If you are running Oracle Enterprise Linux 6 or Red Hat Linux 6, locate the following operating system configuration file:
/etc/security/limits.d/90-nproc.conf
Make sure the same values are added to the 90-nproc.conf file; otherwise, the values in the 90-nproc.conf file can override the values in the limits.conf file.
Reboot the host computer.
Table 15 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 the row of your choice:
x86-64 Oracle Linux 6 (Update 6) and Red Hat Linux 6 (Update 6)
x86-64 SUSE 11 (SP3+)
x86-64 SUSE 12 (SP1+)
Table 15 Linux Operating System Requirements
| Processor | Operating System Version | Required Packages | Required Kernel Version |
|---|---|---|---|
|
X86-64 |
Oracle Linux 7 (UL0+) and Red Hat Linux 7 (UL0+) |
binutils-2.23.52.0.1 compat-libcap1-1.10 compat-libstdc++-33-3.2.3 for x86_64 compat-libstdc++-33-3.2.3 for i686 gcc-4.8.2 gcc-c++-4.8.2 glibc-2.17 for x86_64 glibc-2.17 for i686 glibc-devel-2.17 for x86_64 libaio-0.3.109 for x86_64 libaio-devel-0.3.109 for x86_64 libgcc-4.8.2 for x86_64 libgcc-4.8.2 for i686 libstdc++-4.8.2 for x86_64 libstdc++-4.8.2 for i686 libstdc++-devel-4.8.2 for x86_64 ksh make-3.82 sysstat-10.1.5 numactl-2.0.9 for x86_64Foot 1 numactl-devel-2.0.9 for x86_64Foot 2 motif-2.3.4-7 for x86_64Foot 3 motif-devel-2.3.4-7 for x86_64Foot 4 |
See How to Obtain the Required Kernel Version for Linux Operating Systems |
|
x86-64 |
Oracle Linux 6 (Update 6) Red Hat Linux 6 (Update 6) |
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 i686 libXtst for i686 openmotif-2.2.3 for x86_64 openmotif22-2.2.3 for x86_64 sysstat-9.0.4-11.el6 |
See How to Obtain the Required Kernel Version for Linux Operating Systems |
|
x86-64 |
SUSE 11 (SP3+) |
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 openmotif-devel-32bit-2.3.1-3.13 openmotif22-libs-32bit-2.2.4-138.17 openmotif-libs-2.3.1-3.13 openmotif-devel-2.3.1-3.13 openmotif-libs-32bit-2.3.1-3.13 openmotif21-libs-32bit-2.1.30MLI4-143.2 openmotif22-libs-2.2.4-138.17 sysstat-8.1.5-7.8 |
3.0.76-0.11-default |
|
x86-64 |
SUSE 12 (SP1+) |
binutils-2.24-2.165 gcc-4.8-6.189 gcc-c++-4.8-6.189 glibc-2.19-17.72 glibc-devel-2.19-17.72 mksh-50-2.13 libaio1-0.3.109-17.15 libaio-devel-0.3.109-17.15 libcap2-2.22-11.709 libstdc++6-4.8.3+r212056-6.3 libstdc++48-devel-4.8.3+r212056-6.3 libstdc++48-devel-32bit-4.8.3+r212056-6.3 libstdc++6-32bit-4.8.3+r212056-6.3 libgcc_s1-4.8.3+r212056-6.3 libgcc_s1-32bit-4.8.3+r212056-6.3 make-4.0-2.107 xorg-x11-libs-7.6-45.14 openmotif-2.3.1-3.13 openmotif-devel-32bit-2.3.1-3.13 openmotif22-libs-32bit-2.2.4-138.17 openmotif-libs-2.3.1-3.13 openmotif-devel-2.3.1-3.13 openmotif-libs-32bit-2.3.1-3.13 openmotif22-libs-2.2.4-138.17 sysstat-10.2.1-3.1.x86_64 |
3.12.28-4-default |
Footnote 1 Required for OBIEE-Essbase
Footnote 2 Required for OBIEE-Essbase
Footnote 3 Required for Oracle Forms and Reports
Footnote 4 Required for Oracle Forms and Reports
|
Note: If the processor for your Linux system is x86-64, then all packages to be installed are by default x86-84 packages. |
How to Obtain the Required Kernel Version for Linux Operating Systems
To identify the required Kernel version for each supported version of Oracle Linux, refer to the following resources:
For Oracle Linux 6 (UL5+) and Oracle Linux 7 (UL0+) Containers, refer to Table 1 on "Supported Virtualization and Partitioning Technologies for Oracle Fusion Middleware" on the Oracle Technology Network.
The openmotif package is not included by default on SUSE 11 and SUSE 12 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.
Table 16 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 16 Solaris Operating System Requirements
| Processor | Operating System Version | Required Packages |
|---|---|---|
|
SPARC64 |
Oracle Solaris 11.0 Oracle Solaris 11.1 Oracle Solaris 11.2 |
SUNWlibC developer/assembler |
|
Solaris x86-64 |
Oracle Solaris 11.0 Oracle Solaris 11.1 Oracle Solaris 11.2 |
SUNWlibC developer/assembler |
Table 17 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.
|
Note: On HP_UX systems, you can verify what Motif packages are installed on the machine using the following command:/usr/sbin/swlist -l fileset | grep -i motif |
Table 18 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 18 IBM AIX Operating System Requirements
| Processor | Operating System Version | Required Packages |
|---|---|---|
|
POWER |
7.1 (Update 1) |
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 12.1.0.1+) xlC.rte (version 12.1.0.1+) |
|
POWER |
7.2 |
bos.adt.base 7.2.0.0 bos.adt.lib 7.2.0.0 bos.adt.libm 7.2.0.0 bos.perf.libperfstat 7.2.0.0 bos.perf.perfstat 7.2.0.0 bos.perf.proctools 7.2.0.0 rsct.basic.rte 3.2.1.0 rsct.compat.clients.rte 3.2.1.0 xlC.aix61.rte 13.1.2.0 xlC.rte 13.1.2.0 |
Table 19 lists the platform, operating system, package, and patch information for IBM Linux on System z operating systems that are either currently supported or were supported in a previous release.
Table 19 IBM Linux on System z Operating System Requirements
| Processor | Operating System Version | Required Packages |
|---|---|---|
|
System Z (S/390) |
Red Hat Linux 7.1 |
binutils-2.23.52.0.1-30.el7.s390x libstdc++-4.8.3-9.el7.s390 libstdc++-4.8.3-9.el7.s390x compat-libcap1-1.10-7.el7.s390x gcc-4.8.3-9.el7.s390x gcc-c++-4.8.3-9.el7.s390x glibc-2.17-78.el7.s390 glibc-2.17-78.el7.s390x glibc-devel-2.17-78.el7.s390 glibc-devel-2.17-78.el7.s390x ksh-20120801-22.el7.s390x libaio-0.3.109-12.el7.s390 libaio-0.3.109-12.el7.s390x libaio-devel-0.3.109-12.el7.s390x libgcc-4.8.3-9.el7.s390 libgcc-4.8.3-9.el7.s390x libstdc++-4.8.3-9.el7.s390x libstdc++-devel-4.8.3-9.el7.s390x libXtst-1.2.2-2.1.el7.s390 libXtst-1.2.2-2.1.el7.s390x libXi-1.7.2-2.1.el7.s390 libXi-1.7.2-2.1.el7.s390x libXmu-1.1.1-5.1.el7.s390x libXaw-1.0.11-6.1.el7.s390x libXft-2.3.1-5.1.el7.s390x libXpm-3.5.10-5.1.el7.s390x make-3.82-21.el7.s390x |
|
Red Hat Linux 6.6+ |
binutils-2.20.51.0.2-5.42.el6.s390x compat-libstdc++-33-3.2.3-69.el6.s390 compat-libstdc++-33-3.2.3-69.el6.s390x compat-libcap1-1.10-1.s390x gcc-4.4.7-11.el6.s390x gcc-c++-4.4.7-11.el6.s390x glibc-2.12-1.149.el6.s390 glibc-2.12-1.149.el6.s390x glibc-devel-2.12-1.149.el6.s390 glibc-devel-2.12-1.149.el6.s390x ksh-20120801-21.el6.s390x libaio-0.3.107-10.el6.s390 libaio-0.3.107-10.el6.s390x libaio-devel-0.3.107-10.el6.s390x libgcc-4.4.7-11.el6.s390 libgcc-4.4.7-11.el6.s390x libstdc++-4.4.7-11.el6.s390x libstdc++-devel-4.4.7-11.el6.s390x libXtst-1.2.2-2.1.el6.s390 libXtst-1.2.2-2.1.el6.s390x libXi-1.7.2-2.2.el6.s390 libXi-1.7.2-2.2.el6.s390x libXmu-1.1.1-2.el6.s390 libXaw-1.0.11-2.el6.s390 libXft-2.3.1-2.el6.s390 libXp-1.0.2-2.1.el6.s390 make-3.81-20.el6.s390x sysstat-9.0.4-27.el6.s390x |
|
|
SUSE 11 (SP3+) |
binutils-2.21.1-0.7.25 (s390x) gcc-4.3-62.198 (s390x) gcc-c++-4.3-62.198 (s390x) glibc-2.11.3-17.31.1 (s390x) glibc-32bit-2.11.3-17.31.1 (s390x) glibc-devel-2.11.3-17.31.1 (s390x) glibc-devel-32bit-2.11.3-17.31.1 (s390x) ksh-93u-0.6.1 (s390x) make-3.81-128.20 (s390x) libaio-0.3.109-0.1.46 (s390x) libaio-32bit-0.3.109-0.1.46 (s390x) libaio-devel-0.3.109-0.1.46 (s390x) libaio-devel-32bit-0.3.109-0.1.46 (s390x) libcap1-1.10-6.10 (s390x) libgcc46-4.6.1_20110701-0.13.9 (s390x) libstdc++33-3.3.3-11.9 (s390x) libstdc++33-32bit-3.3.3-11.9 (s390x) libstdc++43-devel-32bit-4.3.4_20091019-0.22.17 (s390x) libstdc++43-devel-4.3.4_20091019-0.22.17 (s390x) libstdc++46-32bit-4.6.1_20110701-0.13.9 (s390x) libstdc++46-4.6.1_20110701-0.13.9 (s390x) sysstat-8.1.5-7.32.1 (s390x) xorg-x11-libs-32bit-7.4-8.26.32.1 (s390x) xorg-x11-libs-7.4-8.26.32.1 (s390x) xorg-x11-libX11-32bit-7.4-5.9.1 (s390x) xorg-x11-libX11-7.4-5.9.1 (s390x) xorg-x11-libXau-32bit-7.4-1.15 (s390x) xorg-x11-libXau-7.4-1.15 (s390x) xorg-x11-libxcb-7.4-1.20.34 (s390x) xorg-x11-libxcb-32bit-7.4-1.20.34 (s390x) xorg-x11-libXext-32bit-7.4-1.16.21 (s390x) xorg-x11-libXext-7.4-1.16.21 (s390x) |
This section contains the following information regarding Microsoft Windows operating systems:
Section 8.3, "Installing and Configuring Java Access Bridge"
Section 8.4, "Installing Microsoft Visual C++ for Oracle HTTP Server on Windows"
Refer to the certification document for 12c (12.2.1) on the Oracle Fusion Middleware Supported System Configurations page for the latest information on certified Windows operating systems.
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.
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:
http://docs.oracle.com/javase/accessbridge/2.0.2/toc.htm
On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system.
If these libraries are not installed on your Windows operating system, then you will receive an error during the prerequisite checks phase of the Oracle HTTP Server installation.
To meet this system requirement for Oracle HTTP Server, download the Visual C++ Redistributable for Visual Studio 2012 software from the following URL:
https://www.microsoft.com/en-us/download/details.aspx?id=30679
Every Oracle Fusion Middleware product that is certified on Linux, Windows, or Oracle Solaris as physical operating system is also certified and supported when running as virtual guest on Oracle VM as long as the respective operating system is supported by Oracle VM.
For more information, see "Supported Virtualization and Partitioning Technologies for Oracle Fusion Middleware" on the Oracle Technology Network.
This section contains the following:
Refer to the certification document for 12c (12.2.1) on the Oracle Fusion Middleware Supported System Configurations page for the latest information on certified databases.
On Oracle databases, 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.
A default database must be assigned to successfully complete the standalone agent startup with Microsoft SQL server. Execute the following MSSQL statement to make this assignment:
ALTER LOGIN sql_login WITH DEFAULT_DATABASE = default_database
Replace sql_login with the login name, and default_database with the default database name.
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 that have purchased support 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.
Oracle Fusion Middleware System Requirements and Specifications, 12c (12.2.1.0.0)
E62221-01
Copyright © 2013, 2016, 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, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.