Oracle® Fusion Middleware · 2017. 1. 20. · Section 1, "Product Names Introduced in 11g Release...

1Beta Draft

ORACLE CONFIDENTIAL.

For authorized use only.

Do not distribute to third parties.

Oracle® Fusion MiddlewareSystem Requirements and Specifications

11g Release 1 (11.1.1)

E18558-01

January 2017

This document contains system and platform-specific information for Oracle Fusion Middleware 11g Release 1 (11.1.1.9.0) products.

The following topics are covered in this document:

■ Section 1, "Product Names Introduced in 11g Release 1 (11.1.1.7.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 Product Names Introduced in 11g Release 1 (11.1.1.7.0)Starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.7.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 GuideThis 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 CertifiedThe 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.

2Beta Draft

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 CertificationThe 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 SoftwareAfter 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 InformationThis 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 VersionsMost 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)












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.





3Beta Draft

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 JDKThe 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.

4Beta Draft

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 EnvironmentIf 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)content comes from bug 14032351 and 16239381

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

5Beta Draft

4 Oracle Fusion Middleware Memory and Space RequirementsThis section contains the minimum memory and disk space requirements for Oracle Fusion Middleware products. The following topics are covered:

■ Section 4.1, "General Minimum Memory Requirements to Install Oracle Fusion Middleware"

■ 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 Minimum Memory Requirements to Install Oracle Fusion MiddlewareUnless 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.

Updated this table, based on bug 18836688 and a rogue release notes entry that really should be removed at the next opportunity.

Table 2 General Minimum Memory Requirements to Install Oracle Fusion Middleware

Operating SystemMinimum Physical Memory Required

Minimum Available Memory Required

Linux 4 GB 4 GB

UNIX 4 GB 4 GB

Windows 4 GB 4 GB

4.2 Oracle Web Tier Disk Space RequirementsOracle Web Tier requires a minimum of 2400 MB free disk space.

4.3 Oracle SOA and Oracle BAM RequirementsThis section contains the following:

■ 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"

6Beta Draft

4.3.1 Oracle SOA and Oracle BAM System RequirementsBelow 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 RequirementsTable 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 StudioThe 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 ApplicationsIf 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 RequirementsBelow 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 Minimum Memory Requirements to Install Oracle Fusion Middleware"), 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".

THIS NOTE WAS ADDED, based on bugs 10212597 and 10229760, as well as an email thread with the subject "Updated Memory Requirements for Oracle Portal, Forms, Reports, and Discoverer".

7Beta Draft

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 RequirementsThe 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.

8Beta Draft

4.6 Oracle Business Intelligence RequirementsThis 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 IntelligenceBelow 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 IntelligenceBelow 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 RequirementsThis 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 IntegratorBelow 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

content from bug 13717333

9Beta Draft

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 ComponentsThe 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 IntegratorBelow 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 RequirementsThis 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 RequirementsBelow 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 RequirementsBelow are the recommended hardware and system configuration requirements for the Oracle Data Profiling and Quality Server:

10Beta Draft

■ 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 ServerMinimum 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 ServersThe Inetd (XInetd for Linux) component is required and must be installed on UNIX servers.

5 Oracle Fusion Middleware Network RequirementsTypically, 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 HostDynamic 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

11Beta Draft

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 PlatformsOn 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 hostname127.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 PlatformsOn 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 examplehostReply from 10.10.10.10: bytes=32 time

12Beta Draft

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.

13Beta Draft

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.

14Beta Draft

5.2 Configuration Requirements for Installing on a Non-Networked ComputerYou 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 ComputerYou 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 localhost10.1.1.1 examplehost1.example.com examplehost110.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 FileThis section contains the following:

■ 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 Filecontent from bug 14680199

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).

15Beta Draft

■ 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 OPMNIf 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 ProductsThis section contains the following:

■ Section 5.5.1, "IP Considerations for Domain Extension on Remote Machines"

■ Section 5.5.2, "Using Web Cache in an IPv6 Network"

■ Section 5.5.3, "Using Other Oracle Fusion Middleware Products in an IP6v6 Network"

5.5.1 IP Considerations for Domain Extension on Remote Machinescontent comes from bug 16430319

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

16Beta Draft

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 NetworkOracle 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 tag below the tag in the INSTANCE_HOME/config/WebCache/webcache1/webcache.xml file. This allows Web Cache to use IPv4 on the system.

5.5.3 Using Other Oracle Fusion Middleware Products in an IP6v6 NetworkBug 18141562

In addition to Oracle Web Cache, you can use other Oracle Fusion Middleware products in an IP6v6 network. For more information, see "Using IPv6" in the Oracle Fusion Middleware Administrator's Guide.

6 System Requirements for UNIX Operating SystemsThis 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 RequirementsThis section contains the following topics:

■ Section 6.1.1, "Setting the Open File Limit"

17Beta Draft

■ Section 6.1.2, "Enabling Unicode Support"

■ Section 6.1.3, "Installing as a Non-Default User on UNIX Operating Systems"

■ Section 6.1.4, "Verifying Shared Storage Configurations on UNIX Operating Systems"

6.1.1 Setting the Open File LimitOn all UNIX and Linux operating systems, verify the values that are currently set for Open File Limit. The minimum Open File Limit should be at 4096, but you should also consider the number of processes required for each host.

The following examples are for Linux operating systems. Equivalent commands should be followed for other UNIX operating systems.

To verify how many files are open, use the following command:

/usr/sbin/lsof | wc -l

To check your open file limits, use the following comands:

■ For C-shell:

limit descriptors

■ For Bash:

ulimit -n

To change the open file limits:

1. Log in as the root user.

2. Locate and open the following operating system configuration file:

/etc/security/limits.conf

3. Look for or modify the following lines in the limits.conf file:

* soft nofile 4096* hard nofile 65536* soft nproc 2047* hard nproc 16384

4. Save your changes and close the limits.conf file.

5. 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

6. 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.

7. Reboot the machine.

6.1.2 Enabling Unicode SupportYour 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

18Beta Draft

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 SystemsOn 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.1.4 Verifying Shared Storage Configurations on UNIX Operating SystemsBug 18898999

If you are using shared storage for your installation media or for your Middeware home directory, be sure that you have configured your shared storage volumes correctly. Otherwise, you might run into errors when installing and configuring the Oracle Fusion Middleware software.

For example, Most client machines and storage servers support access control lists (ACL) and extended file attributes. However, there may be a mismatch between how each device handles the extended attributes. This will often show up as warnings or errors when performing a ‘cp –p’ command. If this occurs, the best option is to disable ACL when the remote storage is being mounted. This can be done by adding the option noacl to the list of mount options in the mount command.

For more information, refer to your shared storage hardware and software documentation, or review the Oracle Maximum Availability Architecture white paper, Oracle WebLogic on Shared Storage: Best Practices.

6.2 Linux Operating System RequirementsTable 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 (SP3+)

19Beta Draft

■ 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)

■ x86-64 SUSE 12 (SP1+)

Added lsb-release-2.0-1.2.18 package for SUSE 11, per bug 18331054 - pjl

Table 5 Linux Operating System Requirements

Platform

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.1compat-libcap1-1.10compat-libstdc++-33-3.2.3 for x86_64compat-libstdc++-33-3.2.3 for i686gcc-4.8.2gcc-c++-4.8.2glibc-2.17 for x86_64glibc-2.17 for i686glibc-devel-2.17 for x86_64libaio-0.3.109 for x86_64libaio-devel-0.3.109 for x86_64libgcc-4.8.2 for x86_64libgcc-4.8.2 for i686libstdc++-4.8.2 for x86_64libstdc++-4.8.2 for i686libstdc++-devel-4.8.2 for x86_64kshmake-3.82sysstat-10.1.5numactl-2.0.9 for x86_641

numactl-devel-2.0.9 for x86_642

motif-2.3.4-7 for x86_643

motif-devel-2.3.4-7 for x86_644

How to Obtain the Required Kernel Version for Linux Operating Systems

20Beta Draft

x86-64 Oracle Linux 6 (UL1+)

Red Hat Linux 6 (UL1+)

may 3 2013 - bug 16748061 - change redhat-lsb-core-4.0-7.el6.x86_64 to redhat-lsb-4.0-3.0.1.el6.x86_64. then, on may 23 2013, bug 16844585 - change redhat-lsb-4.0.3.0.1.el6.x86_64 to redhat-lsb-4.0.3.el6.x86_64

may 23 2013 - changes to libXext, libXtst and added libXi for bug 16796319. also added these three packages to OEL/RHEL5 64-bit

binutils-2.20.51.0.2-5.28.el6compat-libcap1-1.10-1compat-libstdc++-33-3.2.3-69.el6 for x86_64compat-libstdc++-33-3.2.3-69.el6 for i686gcc-4.4.4-13.el6gcc-c++-4.4.4-13.el6glibc-2.12-1.7.el6 for x86_64glibc-2.12-1.7.el6 for i686glibc-devel-2.12-1.7.el6 for i686libaio-0.3.107-10.el6libaio-devel-0.3.107-10.el6libgcc-4.4.4-13.el6libstdc++-4.4.4-13.el6 for x86_64libstdc++-4.4.4-13.el6 for i686libstdc++-devel-4.4.4-13.el6libXext for i386libXtst for i386libXi for i386openmotif-2.2.3 for x86_647

openmotif22-2.2.3 for x86_647

redhat-lsb-4.0-3.el6 for x86_64sysstat-9.0.4-11.el6

How to Obtain the Required Kernel Version for Linux Operating Systems

Table 5 (Cont.) Linux Operating System Requirements

Platform



21Beta Draft



binutils-2.17.50.0.6compat-libstdc++-33-3.2.3 for x86-64compat-libstdc++-33-3.2.3 for i386elfutils-libelf-0.125elfutils-libelf-devel-0.125gcc-4.1.1gcc-c++-4.1.1glibc-2.5-12 for x86_64glibc-2.5-12 for i686glibc-common-2.5glibc-devel-2.5 for x86-64glibc-devel-2.5-12 for i386libaio-0.3.106 for x86_64libaio-0.3.106 for i386libaio-devel-0.3.106libgcc-4.1.1 for x86_64libgcc-4.1.1 for i386libstdc++-4.1.1 for x86_64libstdc++-4.1.1 for i386libstdc++-devel-4.1.1libXext for i386libXtst for i386libXi for i386make-3.81openmotif-2.2.38

openmotif22-2.2.38

redhat-lsb-3.1-12.3.EL.0.2sysstat-7.0.0xorg-x11-utils

2.6.185


Platform



22Beta Draft



binutils-2.15.92.0.2compat-libstdc++-33-3.2.3 for x86_64compat-libstdc++-33-3.2.3 for i386elfutils-libelf-0.97elfutils-libelf-devel-0.97gcc-3.4.5gcc-c++-3.4.5glibc-2.3.4-2.19 for x86_64glibc-2.3.4-2.19 for i686glibc-common-2.3.4glic-devel-2.3.4 for x86_64glic-devel-2.3.4 for i386libaio-0.3.105 for x86_64libaio-0.3.105 for i386libaio-devel-0.3.105libgcc-3.4.5 for x86_64libgcc-3.4.5 for i386libstdc++-3.4.5 for x86_64libstdc++-3.4.5 for i386libstdc++-devel-3.4.5 for x86_64libstdc++-devel-3.4.5 for i386make-3.80openmotif-2.2.38

openmotif21-2.1.30-11.RHEL4.46

sysstat-5.0.5

2.6.9

x86-64 SUSE 12 (SP1 +)

binutils-2.24-2.165gcc-4.8-6.189gcc-c++-4.8-6.189glibc-2.19-17.72glibc-devel-2.19-17.72mksh-50-2.13libaio1-0.3.109-17.15libaio-devel-0.3.109-17.15libcap2-2.22-11.709libstdc++6-4.8.3+r212056-6.3libstdc++48-devel-4.8.3+r212056-6.3libstdc++48-devel-32bit-4.8.3+r212056-6.3libstdc++6-32bit-4.8.3+r212056-6.3libgcc_s1-4.8.3+r212056-6.3libgcc_s1-32bit-4.8.3+r212056-6.3make-4.0-2.107xorg-x11-libs-7.6-45.14motif-2.3.4-4.15.x86_64

3.12.28-4


Platform



23Beta Draft

x86-64 SUSE 11 (all SP levels included)

binutils-2.19-11.28gcc-4.3-62.198gcc-c++-4.3-62.198gcc-32bit-4.3glibc-2.9-13.2glibc-32bit-2.9-13.2glibc-devel-2.9glibc-devel-32bit-2.9-13.2ksh-93tlibaio-0.3.104-140.22libaio-devel-0.3.104-140.22libaio-32bit-0.3.104libaio-devel-32bit-0.3.104libgcc43-4.3.3_20081022libstdc++43-4.3.3_20081022-11.18libstdc++43-devel-4.3.3_20081022-11.18libstdc++33-3.3.3libstdc++33-32bit-3.3.3libstdc++43-32bit-4.3.3_20081022libstdc++43-devel-32bit-4.3.3_20081022libstdc++-devel-4.3lsb-release-2.0-1.2.18make-3.81openmotif-2.3.1-3.138

openmotif-devel-32bit-2.3.1-3.138

openmotif22-libs-32bit-2.2.4-138.178

openmotif-libs-2.3.1-3.138

openmotif-devel-2.3.1-3.138

openmotif-libs-32bit-2.3.1-3.138

openmotif21-libs-32bit-2.1.30MLI4-143.28

openmotif22-libs-2.2.4-138.178

sysstat-8.1.5-7.8

2.6.27.19-5-default

x86-64 SUSE 10 (SP1+)

binutils-2.16.91.0.5compat-libstdc++-5.0.7-22.2gcc-4.1.0gcc-c++-4.1.0glibc-2.4-31.2glibc-32bit-2.4-31.2glibc-devel-2.4glibc-devel-32bit-2.4libaio-0.3.104libaio-devel-0.3.104libelf-0.8.5libgcc-4.1.0libstdc++-4.1.0libstdc++-devel-4.1.0make-3.80openmotif-2.2.36

openmotif21-libs-2.1.306

sysstat-6.0.2

2.6.16.21


Platform



24Beta Draft

x86 Oracle Linux 5 (UL3+)


binutils-2.16.91.0.5-23.4compat-libstdc++-296-2.96-132.7.2compat-db-4.1.25-9control-center-2.8.0-12gcc-4.1.0-28.4gcc-c++-4.1.0-28.4glibc-common-2.3.4-2.9libaio-0.3.1067

libaio-devel-0.3.1067

libstdc++-4.1.0-28.4libstdc++-devel-4.1.0-28.4make-3.80-202.2openmotif-2.2.36

openmotif22-2.2.36

setarch-1.6-1sysstat-5.0.5-1

2.6.18

x86 Oracle Linux 4 (UL7+)


binutils-2.15.92.0.2-13compat-libstdc++-296-2.96-132.7.2compat-db-4.1.25-9control-center-2.8.0-12gcc-3.4.3-22.1gcc-c++-3.4.3-22.1glibc-common-2.3.4-2.9gnome-libs-1:1.4.1.2.90-44.1libaio-0.3.1056

libaio-devel-0.3.1057

libstdc++-3.4.3-22.1libstdc++-devel-3.4.3-22.1make-1:3.80-5openmotif-2.2.37

openmotif21-2.1.30-11.RHEL4.4pdksh-5.2.14-30setarch-1.6-1sysstat-5.0.5-1xscreensaver-4.18-5.rhel4.2

2.6.9


Platform



25Beta Draft

6.2.1 How to Obtain the Required Kernel Version for Linux Operating SystemsTo identify the required Kernel version for each supported version of Oracle Linux, refer to the following resources:

■ Oracle Linux 7 Documentation Library

x86 SUSE 11 (all SP levels included)

binutils-2.19-11.28gcc-4.3-62.198gcc-c++-4.3-62.198glibc-2.9-13.2glibc-devel-2.9ksh-93tlibaio-0.3.104-140.22libaio-devel-0.3.104-140.22libgcc43-4.3.3_20081022libstdc++43-4.3.3_20081022-11.18libstdc++43-devel-4.3.3_20081022-11.18libstdc++33-3.3.3libstdc++devel-4.3make-3.81openmotif22-libs-2.2.4-138.1789

openmotif-2.3.1-3.1389

openmotif21-libs-2.1.30MLI4-143.989

openmotif-libs-2.3.1-3.1389

openmotif-devel-2.3.1-3.1389

sysstat-8.1.5-7.8

2.6.27.19-5-default

x86 SUSE 10 (SP3+)

binutils-2.16.91.0.5libstdc++33gcc-4.1.2gcc-c++-4.1.2glibc-2.4-31glibc-devel-2.4-31ksh-93r-12.9libaio-0.3.104libaio-devel-0.3.104libelf-0.8.5libgcc-4.1.2libstdc++-4.1.2libstdc++-devel-4.1.2make-3.80sysstat-8.0.4

2.6.16.21

1 Required for OBIEE-Essbase2 Required for OBIEE-Essbase3 Required for Oracle Forms and Reports4 Required for Oracle Forms and Reports5 For Oracle SOA Suite, the kernel must be upgraded to version 2.6.18-308.13.1.0.1.el5.6 Required for Oracle Identity Management, Oracle Web Tier, and Oracle Portal, Forms, Reports and

Discoverer7 Required for Oracle Portal, Forms, Reports and Discoverer8 Required for Oracle Reports9 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.


Platform



26Beta Draft

- Oracle Linux 7 (UL0) Release Notes


■ Oracle Linux 6 Documentation Library



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.

6.2.2 Obtaining the openmotif22 Package on SUSE 10 and SUSE 11 Operating Systemscontent from bug 14529109

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.3 Installing Oracle HTTP Server on Linux Operating Systems Requires NPTLcontent comes from bug 12602123

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 RequirementsTable 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.

Note: The SRU 11.3.3.6.0 or later (mandatory patch) is required for the Solaris 11 Update 3 on SPARC or x86-64.

27Beta Draft

Table 6 Solaris Operating System Requirements

PlatformOperating System Version Required Packages

Required Operating System Patches

SPARC64 Solaris 9 Update 9+ SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1csSUNWi15csSUNWxwfntSUNWsprox

Motif: 2.1.01

GCC: package 3.4.2 or higher2

118558-22112874-39112760-053

114370-054

Solaris 10 Update 4+


SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1csSUNWi15csSUNWxwfnt

Motif: 2.1.01


127111-02137111-04141444-095

Solaris 11


Solaris 11.3 (SRU 11.3.3.6.0 or higher)

SUNWlibCdeveloper/assembler

28Beta Draft

6.3.1 Installing Font Packages on Solaris 11 for Forms and Reportsbug 14741791

For Oracle Forms and Reports, the following packages must also be installed on Solaris 11 systems:

system/font/daewoo-miscsystem/font/gnome-fontssystem/font/isas-miscsystem/font/jis-miscsystem/font/misc-ethiopicsystem/font/misc-melthosystem/font/sun-ja-bitmapsystem/font/sun-ja-bitmap-unicodesystem/font/truetype/arphic-ukaisystem/font/truetype/bh-luxisystem/font/truetype/bitstream-verasystem/font/truetype/fonts-coresystem/font/truetype/gentiumsystem/font/truetype/google-droidsystem/font/truetype/hanyang-kosystem/font/truetype/ipafont-mincho

x86-64 Solaris 10 Update 6+


SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1csSUNWi15csSUNWxwfnt


127112-026

137112-04

Solaris 11


Solaris 11.3 (SRU 11.3.3.6.0 or higher)

SUNWlibCdeveloper/assembler

1 Required for Oracle Portal, Forms, Reports and Discoverer.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.

3 "C 5.5: Patch for S1S8CC C compiler" patch required only if the installed version of Studio 11 does not already include this patch (or a superseded version).

4 Symlink patch required only if the method of installing Solaris 9 Update 9 was via a Solaris Patch Cluster and that version of the Solaris Patch Cluster did not already include this patch (or a superseded version).

5 This patch is required for Solaris 10 Update 7 and lower. Solaris 10 Update 8 and higher already includes this patch.

6 For additional details about patches 127112 and 137112, see notes 1000642.1 and 1019395.1 on My Oracle Support.

Table 6 (Cont.) Solaris Operating System Requirements

PlatformOperating System Version Required Packages


29Beta Draft

system/font/truetype/silsystem/font/truetype/unfonts-ko-coresystem/font/truetype/unfonts-ko-extrasystem/font/truetype/unifontsystem/font/truetype/wqy-zenheisystem/font/xorg/cyrillicsystem/font/xorg/iso8859-10system/font/xorg/iso8859-11system/font/xorg/iso8859-13system/font/xorg/iso8859-14system/font/xorg/iso8859-15system/font/xorg/iso8859-16system/font/xorg/iso8859-2system/font/xorg/iso8859-3system/font/xorg/iso8859-4system/font/xorg/iso8859-5system/font/xorg/iso8859-7system/font/xorg/iso8859-8system/font/xorg/iso8859-9

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:

a. Set LC_ALL=C.

b. 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 Zonescontent comes from bug 12641548

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 RequirementsTable 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


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)1

1 This is the Motif Development Kit and is required for Oracle Portal, Forms, Reports and Discoverer only.

PHCO_35524PHCO_36673PHKL_35029PHKL_35478PHSS_35978PHSS_35979PHSS_37201

HP-UX 11i v3 (11.31)


B3394BA (version 2.1.0)1 PHKL_36248PHKL_36249PHSS_37202PHSS_37501PHCO_38050PHSS_38139

PA-RISC HP-UX 11i v2 (11.23)


B3394BA (version 2.1.0)1 PHCO_35524PHCO_36673PHKL_35029PHKL_35478PHKL_35767PHKL_36853PHSS_35101PHSS_35102PHSS_35103PHSS_35176PHSS_35978PHSS_35979PHSS_37201

HP-UX 11i v3 (11.31)


B3394BA (version 2.1.0)1 PHKL_36248PHKL_36249PHSS_37202PHSS_37501PHCO_38050

30Beta Draft

6.5 IBM AIX Operating System RequirementsTable 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



AIX 7200-00 bos.adt.base 7.2.0.0bos.adt.lib 7.2.0.0bos.adt.libm 7.2.0.0bos.perf.libperfstat 7.2.0.0bos.perf.perfstat 7.2.0.0bos.perf.proctools 7.2.0.0rsct.basic.rte 3.2.1.0rsct.compat.clients.rte 3.2.1.0xlC.aix61.rte 13.1.2.0xlC.rte 13.1.2.0

7100-01 bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsrsct.basic.rtersct.compat.clients.rtexlC.aix61.rte (version 10.1.0.0)xlC.rte (version 10.1.0.0)IZ891651

1 Required for Oracle Business Intelligence.

6100-02 xlC versions bumped up to 11.1.0.4 per bug 16029166

bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsrsct.basic.rtersct.compat.clients.rtexlC.aix50.rte (version 11.1.0.4)xlC.rte (version 11.1.0.4)X11.motif.lib (version 2.1.30)2

gpfs.base (version 3.2.1.8)3

5300-08 bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsrsct.basic.rtersct.compat.clients.rtebos.mp64 (version 5.3.0.56)bos.rte.libc (version 5.3.0.55)xlC.aix50.rte (version 8.0.0.7)xlC.rte (version 8.0.0.7)X11.motif.lib (version 2.1.30)2

gpfs.base (version 3.2.1.8)3

31Beta Draft

32Beta Draft

6.5.1 Patches Required Before Installing Fusion Middleware Products on IBM AIX 7.2Install the patch mentioned below before you install the fusion middleware products.

Apply patch 22757185 to handle this problem.

Use the following procedure to use the patch:

1. Download patch 22757185 from My Oracle Support.

2. Unzip the patch archive, using the following command:

unzip -d PATCH_DIR p22757185_11.1.1.9.0_generic.zip

In this example, replace PATCH_DIR with the name of a local directory. This is typically a top-level directory used for storing patches you have downloaded from My Oracle Support.

3. Change directory to the following directory where you unpacked the software archive:

cd unpacked_FMW_directory/Disk1

4. Locate and run the installer (runInstaller), as follows:

./runInstaller PREREQ_CONFIG_LOCATION=PATCH_DIR/prereqIn this example, replace PATCH_DIR with the path to the local directory where you unzipped patch 22757185 in Step 3.

7 System Requirements for Windows Operating SystemsThis 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"

■ Section 7.6, "Verifying Library Files on Windows for Oracle HTTP Server"

7.1 Certified Windows Operating SystemsRefer 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 SoftwareIf 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

2 Required for Oracle Portal, Forms, Reports and Discoverer.3 Required for Oracle RAC.

33Beta Draft

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 Reportscontent from bug 12972014 and email from Rakesh Domalapalli.

This was added the IDM install guide by Nisha Singh, and when it is archived for the PS5 refresh or PS6, whichever comes first, this section should be removed from the system requirements doc. Since the PS5 IDM install guide is already archived, this items needs to remain in the system requirements doc until it can be incorporated into the core doc set.

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.

34Beta Draft

7.5 Installing and Configuring Java Access BridgeIf 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.

7.6 Verifying Library Files on Windows for Oracle HTTP ServerIf you are installing Oracle HTTP Server on your certified Windows operating system, you should verify that the msvcr90.dll and linkinfo.dll library files exist on your system; these are required by Oracle HTTP Server.

For more information, see also "Missing Libraries Might Cause HTTPD to Exit Without Notice" in Oracle HTTP Server Release Notes.

If you are unable to the required libraries on your system, contact Microsoft support for further assistance.

7.7 Installing Microsoft Visual C++ on Windows for System ComponentsThis includes:

■ Oracle HTTP Server

■ WebCenter Content

■ Forms and Reports

■ OBIEE

On the Windows platform, these components require the 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 check phase of these components.

To meet this system requirement, download the Visual C++ Redistributable for Visual Studio 2012 software (indicated as version 11.0 in the Windows control panel and Oracle Universal Installer pre-requisite check screen). You can download this software from the following URL:

https://support.oracle.com/

Note: The OBIEE installs the required version automatically. For any future reference or maintenance, check the result in the Windows control panel.

8 System Requirements for the Oracle Universal InstallerThis 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"

35Beta Draft

■ 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 VariablesThe 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.

36Beta Draft

8.2 Startup RequirementsThe 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 SystemThis 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"

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.

Table 9 (Cont.) Oracle Universal Installer Environment Variable Requirements

Variable Description

37Beta Draft

8.3.1 Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating SystemIf 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/shexec /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.

38Beta Draft

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 SystemIf 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 SystemsIf 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 ReleaseIn 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:

39Beta Draft

Warning:Checking operating system certificationExpected result: One ofenterprise-5.4,enterprise-4,enterprise-5,redhat-5.4,redhat-4,redhat-5,SuSE-10Actual Result:SuSE-11Check complete. The overall result of this check is: FailedProblem: 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

Note: The -ignoreSysPrereqs option should be used only if ALL of the following conditions are met:

■ 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 SpecificationsThis 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 DatabaseRefer 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 ProductsThis section contains the following:

■ Section 9.2.1, "Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager"

40Beta Draft

■ 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 ManagerIf 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 Release Notes for Linux x86 or Oracle Fusion Middleware Release Notes General Information. 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 VaultIf 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 SchemaThe 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".

41Beta Draft

This section contains the following:

■ 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 SchemaNote 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 SchemaNote 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 SchemaNote 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_userdb2 "get db cfg" | grep -I commitCurently 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,

42Beta Draft

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=OFFdb2set DB2_SKIPINSERTED=OFFdb2set 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 d

Date post:	17-Feb-2021
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Oracle® Fusion Middleware · 2017. 1. 20. · Section 1, "Product Names Introduced in 11g Release...

Documents