Oracle® Fusion Middleware

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>

Table 1-3 shows the disk space requirements for Oracle WebLogic Server and Coherence.

Table 1-4 shows the disk space requirements for Oracle Fusion Middleware Infrastructure.

Table 1-5 shows the disk space requirements for Oracle HTTP Server.

Table 1-6 shows the system requirements for Oracle Data Integrator.

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.2)certification document on the Oracle Fusion Middleware Supported System Configurations page for the latest information on certified databases.

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

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.

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:

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

Table 1-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 7 (UL0+) and Red Hat Linux 7 (UL0+)

• x86-64 Oracle Linux 6 (Update 6) and Red Hat Linux 6 (Update 6)

• x86-64 SUSE 11 (SP3+)

• x86-64 SUSE 12 (SP1+)

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:

• Oracle Linux 7 Documentation Library

  • Oracle Linux 7 (UL0) Release Notes

  • Oracle Linux 7 (UL1) Release Notes

• Oracle Linux 6 Documentation Library

  • Oracle Linux 6 (UL6) Release Notes

  • Oracle Linux 6 (UL7) Release Notes

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.

Table 1-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 1-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.

/usr/sbin/swlist -l fileset | grep -i motif

Table 1-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 1-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.

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

This includes:

• Oracle HTTP Server

• Oracle Traffic Director

• 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 correct version of Visual C++ Redistributable for Visual Studio by referring to Table 1-20 below.

You can download the software from https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads.

For correct operation of WebCenter Content, Inbound Refinery, or Records on a Windows operating system, you need to have the Visual C++ libraries that are included in the Visual C++ Redistributable Package.

If these libraries are not installed on Windows operating system, then you will receive errors during server start phase.

To meet this system requirement, download the Microsoft Visual Studio 2012 (VC++ 11.0) software from the following URL:

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

While installing Fusion Middleware 12.2.1.2.0 products on Microsoft Windows Server 2016 , the installer might encounter the following warnings in the prerequisite checks like Operating System Version Check on Microsoft Windows Server 2016.

For Example:

Ignore these warnings and proceed with the installation by clicking Next.

Refer to the certification document for 12c (12.2.1.2.0) 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, DBMS_STATS, and DBMS_LOB. When you create a metadata repository using RCU, if PUBLIC does not have EXECUTE privilege on DBMS_OUTPUT and DBMS_STATS, the RCU user must have the privilege to grant EXECUTE privilege on DBMS_OUTPUT and DBMS_STAT to the MDS user. The RCU user must have the privilege to grant EXECUTE privilege on 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.

Note the following about using SQL Server as the database for MDS:

• To create a metadata repository in SQL Server, set READ_COMMITTED_SNAPSHOT to ON for the hosting database. This enables the needed row versioning support. Use the following SQL command ALTER DATABASE, as in the following example:

  ALTER DATABASE mds SET READ_COMMITTED_SNAPSHOT ON
  

• 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 many cases, this command will run successfully. However, the command might fail and generate error messages concerning functions, primary keys, constraints, or indexes. This can be caused if the database already has collation aware objects. In this case, SQL Server does not allow you to change the collation at the database level. In this case, the alternative is to create a new database with the expected collation for MDS to use.

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

Note the following about using DB2 as the database for MDS:

• DB2 9.7 or later must be used for MDS repository to work properly.

• Make sure that CUR_COMMIT is set to ON, which is the default value for a newly installed DB2 9.7 database. This setting can be verified using following DB2 command:

  db2 connect to your_database user admin_user
  db2 "get db cfg" | grep -I commit
  Curently Committed   (CUR_COMMIT) = ON
  

• Set the lock timeout parameter of the database to a low value. Unlike Oracle databases, with DB2, if one user is updating a row, under some conditions, another user may be blocked when updating a different row and must wait until the transaction is committed or rolled back by the first user. To facilitate better concurrency, do not specify -1, which sets the lock timeout to infinity.

  To query the lock timeout value for your DB2 database, use the following command:

  db2 'get database config for database_alias' | grep -i timeout
  

  If the value is too high, change it. For example, to change the lock timeout value to 180 seconds, use the following command:

  db2 'update database config for database_alias using locktimeout 180'
  

  Choose a proper value for the locktimeout parameter. If a large value is used, it will affect system throughput, since the transaction has to wait a very long time before giving up. If the value is set too small, users will see many timeout exceptions if the database is processing many long running transactions.

• Set the DB2 registry variables DB2_EVALUNCOMMITTED, DB2_SKIPINSERTED, and DB2_SJIPDELETED to OFF to avoid deadlock and locking issues. By default, they are set to OFF. To view the current registry variables setting, use the db2set -all command.

  If they are not set to OFF, use the following commands:

  db2set DB2_EVALUNCOMMITTED=OFF
  db2set DB2_SKIPINSERTED=OFF
  db2set DB2_SKIPDELETED=OFF
  

  Then, 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'
  

  The recommended value for MAXLOCKS is 20, and the recommended value for LOCKLIST is 70000. You should set appropriate values based on your environment and usage.

• The isolation level must be set to Currently Committed. To verify the setting, use the following command:

  db2 'get database config for database_alias' | grep -i commit
  

  To set the isolation level to Currently Committed, use the following command:

  db2 'update database config for database_alias using CUR_COMMIT ON'
  

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

  db2 'update database config for database_alias using LOGFILSIZ 10000'
  db2 'update database config for database_alias using LOGPRIMARY 50'
  

• If the IBM DB2 JCC driver is chosen for the data source, the progressiveStreaming=2 property must be added to the property list of the data source. In effect, progressive streaming will be disabled. Without this property setting, MDS may run into issues in accessing document contents saved in a large object (LOB) column in the MDS repository.