Oracle® Fusion Middleware

3.2.1 Calculating Additional Memory Requirements for 11g Release 2 (11.1.2.3) Components

The following components were added in 11g Release 2 (11.1.2.3):

• Oracle Mobile Security Suite

• Oracle Mobile Security Access Server

• Oracle Business Intelligence (BI)

• Oracle Adaptive Access Manager (OAAM)

• Oracle Privileged Account Manager

If you install any combination of the components listed above, your memory requirements will be larger than the default Oracle Identity and Access Management installation.

6.1.1 Configuring Kernel Parameters

The kernel parameter and shell limit values shown in this section are recommended values only. For production systems, Oracle recommends that you tune these values to optimize the performance of the system. See your operating system documentation for more information about tuning kernel parameters.

Kernel parameters must be set to a minimum of those below on all nodes in the topology.

If you are deploying a database onto the host, you might need to modify additional kernel parameters. Refer to the 11g Release 2 Oracle Grid Infrastructure Installation Guide for your platform.

To set these parameters:

1. Log in as root and add or amend the entries in the /etc/sysctl.conf file.

2. Save the file.

3. Activate the changes by issuing the following command:

   /sbin/sysctl -p
   

6.1.2 Checking and Changing the Open File Limit

On 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.3 Installing as a Non-Default User on UNIX Operating Systems

On UNIX operating systems, the installation of Fusion Middleware products is owned and controlled as a known user (for example, "oracle"). The file permissions associated with this installation are configured to ensure the highest level of security possible, which by default are 700 (meaning all files are owned and accessible by the owner only).

Changing the default permissions settings will reduce the security of the installation and possibly your system. Therefore, making such a change is not recommended. If access to particular files or executables is required by other users, the UNIX sudo command (or other similar command) should be considered in lieu of changing file permissions.

Refer to your UNIX operating system Administrator's Guide or contact your operating system vendor if you need further assistance.

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

6.2.2 Obtaining the openmotif22 Package on SUSE 10 and SUSE 11 Operating Systems

The openmotif22 package is not included by default on SUSE 10 and SUSE 11 operating systems. If you need to obtain this package, you must go to the Novell website to obtain the package and then perform the installation using the instructions provided by Novell.

6.2.3 Patches Required Before Installing Oracle Identity and Access Management Products on SUSE 12 (SP1+)

Install the patch mentioned below before you install the Oracle Identity and Access Management 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_IDM_directory/Disk1
     

  4. Locate and run the following command:

     On Linux installer (runInstaller):

     ./runInstaller PREREQ_CONFIG_LOCATION=PATCH_DIR/prereq
     

     In this example, replace PATCH_DIR with the path to the local directory where you unzipped patch 22757185 in Step 3.

6.2.4 Installing Oracle HTTP Server on Linux Operating Systems Requires NPTL

If you are installing Oracle HTTP Server on a Linux operating system, the operating system needs to set Native POSIX Threads Library (NPTL) as the default threads-implementation. To check for this, run the following command:

getconf GNU_LIBPTHREAD_VERSION

The expected results should be "NPTL 2.3.4". Failing to have NPTL can result in unexpected behavior for the Oracle HTTP Server, especially if the Multi-Processing Module (MPM) is the Worker MPM.

6.2.5 Installing Oracle Identity and Access Management on Red Hat Linux 6 Requires Patch 18231786

Before installing Oracle Identity and Access Management 11g Release 2 (11.1.2.2) on Red Hat Linux 6 (UL1+) (RHEL6), apply Patch 18231786. If you do not install this patch before installation, you may encounter an error during package validation.

6.2.6 Installing Oracle Mobile Security Access Server on Linux Requires compat-libtermcap-2.0.8

Before installing Oracle Mobile Security Access Server, ensure that you have installed the operating system-supported package compat-libtermcap-2.0.8* for Linux x86_64.

6.3.1 Applying Solaris Patches in Non-Global Zones

On Solaris operating systems, the prerequisite patches that are applied in the global zone can be considered applied in the non-global zones. There is only one kernel running on the system, and all zones must be at the same patch level with respect to the kernel and other Solaris system components. Kernel patches can only be applied from the global zone, and they affect the global and all non-global zones equally.

To check if a kernel patch is applied in the global zone, use the following command:

showrev -p | grep patch_number

For example, to check if patch 137111-04 is applied:

showrev -p | grep 137111

6.3.2 Checking for the SUNWxcu4 Package to Avoid Erroneous Disk Space Errors

On Solaris operating systems, the SUNWcxu4 package is required before you can install Oracle Identity and Access Management successfully. The SUNWcxu4 package is installed on most Solaris systems by default, but there are situations where the package is not installed automatically.

If the SUNWcxu4 package is not found, it can result in the following error, when you attempt to start the Oracle Identity and Access Management installer:

ERROR:
Extracting
0%.......................................................................................100%
Insufficient disk space! The installer requires:
190MB for the MW_HOME_LOCATION
450MB for the product at PRODUCT_LOCATION
and 1139MB temporary work space at TMP_LOCATION.There is only 1MB available at MW_HOME_LOCATION.

To check for the availability of this package on your Solaris system:

$ pkginfo -l SUNWxcu4

6.5.1 Patches Required Before Installing Oracle Identity and Access Management Products on AIX 7.2

Install the patch mentioned below before you install the Oracle Identity and Access Management 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_IDM_directory/Disk1
     

  4. Locate and run the following command:

     ./runInstaller PREREQ_CONFIG_LOCATION=PATCH_DIR/prereq
     

     In this example, replace PATCH_DIR with the path to the local directory where you unzipped patch 22757185 in Step 3.

7.1.1 Patches Required Before Installing Oracle Identity and Access Management Products on Windows 10

Install the patch mentioned below before you install the Oracle Identity and Access Management products on Windows 10.

The operating system prerequisite check might fail while installing the Oracle Identity and Access Management Products on Windows 10.

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_IDM_directory/Disk1
     

  4. Locate and run the following command:

     setup.exe PREREQ_CONFIG_LOCATION=<Full path to PATCH_DIR>\prereq
     

     In this example, replace PATCH_DIR with the path to the local directory where you unzipped patch 22757185 in Step 3.

10.1.1 Running RCU on 64-Bit Platforms

RCU for Oracle Identity and Access Management 11g Release 2 (11.1.2.x) can be run on any 64-bit x86 Linux and 64-bit Microsoft Windows operating system that runs Oracle Fusion Middleware.

However, on 64-bit Linux operating systems, you must run the following command before starting RCU:

set linux32 bash

In addition, on Oracle Enterprise Linux 6, 64bit, you must ensure that 32-bit versions of the following packages are installed each 64-bit Linux machine. Without these 32-bit packages, RCU will fail. Some installations of the Oracle Enterprise Linux operating system include only the 64-bit versions of these files:

glibc.i686
libXext.i686
libXtst.i686
libaio.i686

If these requirements are met, then you can run RCU from a supported machine and connect to any certified local or remote database to create the schemas required by Oracle Identity and Access Management. The database can be running on any operating system platform that is supported by that particular database

10.2.1 General Oracle Database Requirements

RCU checks for the following on Oracle databases:

• Database version is equal to or higher than 10.2.0.4.0 in 10g or equal to or higher than 11.1.0.7.0 in 11g.

• Database is installed with Oracle JVM enabled. Refer to your database documentation for information about how to do this.

• Database user has SYSDBA role.

  If you are creating schemas on an Oracle database, you must have SYSDBA privileges. For example, you can use the default database user SYS with SYSDBA privileges, or you must use a database user that has been granted the role of SYSDBA.

  If you using a user other than SYS with SYSDBA privileges, you must grant the user permissions as follows:

  GRANT execute on sys.dbms_lock to user_name with grant option
  

  For example, if you have created and are using the user named system, you would use the following command to grant the necessary privileges to system:

  GRANT execute on sys.dbms_lock to system with grant option
  

  Refer to your Oracle database documentation for more information about database users and roles.

• Character set is AL32UTF8.

  If your database does not use the AL32UTF8 character set, you will see the following warning when running RCU:

  The database you are connecting is with non-AL32UTF8 character set. Oraclestrongly recommends using AL32UTF8 as the database character set.
  

  You can ignore this warning and continue using RCU.

• The SGA_MAX_SIZE is greater than or equal to 147456KB.

• The DB_BLOCK_SIZE is greater than or equal to 8KB

10.2.2 Setting the parallel_max_servers Parameter for the ODS Schema

For the Oracle Internet Directory (ODS) schema, set parallel_max_servers=1. This setting should be used for 11gR2 Oracle RAC systems with more than 32 CPUs.

After Oracle Internet Directory is up and running, you should set the parallel_max_servers parameter to a higher value. For more information, see "PARALLEL_MAX_SERVERS" in the Oracle Database VLDB and Partitioning Guide.

10.2.3 Component-Specific Requirements for Oracle Databases

Table 11 lists all of the related Oracle Identity and Access Management schemas for Oracle databases, along with any component-specific prerequisite information that must be met for RCU to be able to create the schema. Refer to the Oracle Database Administrator's Guide to find instructions on how to modify database parameters.

Some of the AS Common Schemas and SOA and BPM Infrastructure Schemas are required for certain Identity Management products so they are included in this table. The schema dependencies can be found in the Oracle Fusion Middleware Repository Creation Utility User's Guide.

When the tablespaces are created, RCU will automatically create them with the necessary tablespace sizes.

The "Oracle EBR?" column indicates whether or not the schema is also supported on Oracle Databases with Edition-Based Redefinition (EBR).

All requirements listed are the minimum requirements; please read them carefully as some components within the same product have different requirements. For example, if you are performing a full Oracle Identity Management installation including Oracle Identity Manager, then the open_cursors parameter must be set to 800. However, if you are installing Oracle Identity Management without Oracle Identity Manager, then open_cursors can be set to 500, which is required for Oracle Internet Directory.