Oracle® Fusion Middleware

4.3.1 Oracle SOA and Oracle BAM System Requirements

Below are the recommended hardware and system configuration requirements for Oracle SOA and Oracle BAM:

• CPU: dual-core Pentium, 1.5GHz or greater

• Disk Space: 15GB or more

4.3.2 Oracle BAM Client Requirements

Table 3 shows the general requirements for the Oracle BAM client.

4.3.3 Additional Requirements for Optional Excel View in Oracle BAM Active Viewer or Oracle BAM Active Studio

The Oracle BAM Excel view type requires that Microsoft Excel version XP, 2003, or 2007 is installed on the client computer.

4.3.4 Additional Notes for Microsoft Internet Explorer and Pop-Up Blockers in Oracle BAM Web Applications

If you are using the Microsoft Windows pop-up blocker, or any other tool that blocks pop-up browser windows, you must configure it to allow pop-up windows while using the Oracle BAM Web applications. Turn off pop-up blockers in Microsoft Internet Explorer for the URL on which the Oracle BAM Web applications are hosted.

The Microsoft Internet Explorer installation on client systems must be a standard version, and it must not include customizations such as add-in tool bars or hot bars for other Web sites.

4.6.1 Installation System Requirements for Oracle Business Intelligence

Below are the recommended hardware and system configuration requirements for an Oracle Business Intelligence installation:

• Disk Space: 20GB or more

• Available Memory: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems

• Temp Space: 2GB or more

• Swap Space: 4GB or more for 32-bit operating systems, or 8GB or more for 64-bit operating systems

4.6.2 Database Requirements for Oracle Business Intelligence

Below are the recommended disk space requirements for the database containing the Oracle Business Intelligence Scheduler database tables.

• 500MB on Oracle and Microsoft SQL Server databases for standalone and Business Intelligence applications and deployments.

• 500MB on IBM DB2 databases for standalone deployments.

4.7.1 Hardware and System Configuration Requirements for Oracle Data Integrator

Below are the recommended hardware and system configuration requirements for Oracle Data Integrator Studio and Standalone Agents:

• CPU: dual-core Pentium, 1.5GHz or greater

• Disk Space: 5GB or more

  • 1050MB are required for the Developer installation

  • 700MB are required for the Standalone installation

  • 1800MB are required for the Java EE installation

• Available Memory: 2GB or more for one agent

  The amount of memory you want to allocate to each agent is set by the ODI_MAX_HEAP parameter in the ODI_HOME/oracledi/agent/bin/odiparams.sh (on UNIX operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on Windows operating systems) file. The default value is 256MB, which means you can run more than one agent on a system with 2GB of available memory (for example, two agents would take up 512MB of memory).

  The value set by ODI_MAX_HEAP multiplied by the number of agents is the minimum amount of available memory required on your system; the amount of additional memory needed beyond this number depends on the number of other application you have running on your system.

4.7.2 Application Server Requirements for Java EE Components

The Java EE components in Oracle Data Integrator require the presence of an application server on your system.

For 11g Release 1 (11.1.1.6.0) and earlier, only Oracle WebLogic Server can be used as the application server; make sure your system also meets the Oracle WebLogic Server system requirements before you install the Java EE components. IBM WebSphere is supported as an application server beginning with 11g Release 1 (11.1.1.7.0).

4.7.3 Database Requirements for Oracle Data Integrator

Below are the recommended storage space requirements for the database containing the Oracle Data Integrator Repository tables:

• Master Repository: 60MB of storage space.

• Work Repository: 80MB of storage space.

  
  

  Note: The storage space required may vary depending on the size of your models and projects, and on the volume of execution logs you keep in this repository.

  
  

4.8.1 Oracle Data Quality Client Requirements

Below are the recommended hardware and system configuration requirements for the Oracle Data Quality Client:

• CPU: dual-core Pentium, 1.5GHz or greater

• Disk Space: 500MB or more

• Available Memory: 512MB or more

4.8.2 Oracle Data Profiling and Quality Server Requirements

Below are the recommended hardware and system configuration requirements for the Oracle Data Profiling and Quality Server:

• CPU: The CPU Requirement for Oracle Data Profiling and Quality Servers are listed in Table 4.

• Disk space: 1.5GB or more.

  
  

  Note: Disk usage for the postal tables and for data processing should be taken into account in addition to this space. The amount of space used by postal table varies according to the countries and options you purchase. The amount of space used for data processing varies according to your data volume.

  
  

• Available memory: 2GB or more. 4GB is recommended (8GB for a power server).

4.8.3 Additional Requirements for Servers

The Inetd (XInetd for Linux) component is required and must be installed on UNIX servers.

5.1.1 For Linux x86 Platforms

On Linux x86 operating systems, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries:

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

After doing so, check that the hostname resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

5.1.2 For Windows x86 Platforms

On Windows operating systems, install a loopback adapter on the single DHCP host that obtains an IP address from the DHCP server. This assigns a local IP address to your computer:

• Section 5.1.2.1, "Installing a Loopback Adapter on Windows 2003, Windows 2003 R2, and Windows XP"

• Section 5.1.2.2, "Installing a Loopback Adapter on Windows Vista and Windows Server 2008"

• Section 5.1.2.3, "Installing a Loopback Adapter on Windows 7 and Windows 2008 R2"

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the localhost line:

IP_address   hostname.domainname   hostname

Replace IP_address with the local IP address of the loopback adapter. To find the IP address of your loopback adapter, use the ping command, as shown in the example below using just the host name (first example) and the fully qualified domain name (second example):

ping examplehost
Reply from 10.10.10.10: bytes=32 time<1ms TTL=128
ping examplehost.exampledomainname.com
Reply from 10.10.10.10: bytes=32 time<1ms TTL=128

Instructions for removing the loopback adapter are provided in Section 5.1.2.4, "Removing a Windows Loopback Adapter".

5.4.1 Correct Format For Entries in the /etc/hosts File

To ensure that both forward lookup (find the IP address given the hostname) and reverse lookup (finding the hostname given the IP address) return the same results, make sure your /etc/hosts file is formatted correctly using the following guidelines:

• The host name may contain only alphanumeric characters, hyphen, and period. The name must begin with an alphabetic character and end with an alphanumeric character.

• Host names should be specified as fully qualified host names (host name with the appended domain name).

• Lines cannot start with a blank space or tab character, but fields may be separated by any number of space or tab characters.

• Comments are allowed and designated by a pound sign (#) preceding the comment text.

• Trailing blank and tab characters are allowed.

• Blank line entries are allowed.

• Only one host entry per line is allowed.

5.4.2 Configuration Requirements for Installing OPMN

If you are installing Oracle Identity Management, Oracle Web Tier, or Oracle Portal, Forms, Reports and Discoverer (products that include Oracle Process Manager and Notification Server or OPMN), you must make sure the installation system has valid entries in the /etc/hosts (on UNIX operating systems) and C:\windows\system32\drivers\etc\hosts (on Microsoft Windows operating systems) file.

You can check your system's IP address and host name as follows:

On UNIX operating systems:

/sbin/ifconfig -a

On Microsoft Windows operating systems:

ipconfig /all

The IP address and corresponding host name in your hosts file must match the IP address and host name you get from the ipconfig command. Otherwise, the opmn.xml file will contain incorrect configuration information, and OPMN will not start.

If you encounter any issues, refer to "Changing Network Configurations" in the Oracle Fusion Middleware Administrator's Guide.

5.5.1 IP Considerations for Domain Extension on Remote Machines

If you want to expand or extend a domain on remote machine where one machine (machine1) is listening on one network address and other machine (machine2) is listening on dual network addresses, you must do the following in order to be able to expand or extend the domain:

1. Configure the domain on machine1.

2. On machine1, go to the DOMAIN_HOME/bin/setDomainEnv.[sh|cmd] file and set the following property:

   -Djava.net.preferIPv4Stack=true
   

3. Restart the Administration Server on machine1.

4. Expand or extend the domain on the remote machine.

5.5.2 Using Web Cache in an IPv6 Network

Oracle Web cache supports the IPv6 address family by default. However, before using IPv6, you must ensure that IPv6 support is enabled in the operating system. This issue is not applicable for IPv4-only systems and for systems that support IPv6 at the kernel level.

If the system's IPv6 network configuration issue cannot be resolved, one work around is to disable IPv6 Support for Oracle Web Cache after it fails (note that this cannot be done until after the installation or configuration fails on IPv4-only systems). This can be done by adding the <IPV6 ENABLED="NO"/> tag below the </MULTIPORT> tag in the INSTANCE_HOME/config/WebCache/webcache1/webcache.xml file. This allows Web Cache to use IPv4 on the system.

5.5.3 Using Other Oracle Fusion Middleware Products in an IP6v6 Network

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.1.1 Setting 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.2 Enabling Unicode Support

Your operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.

On UNIX operating systems, Oracle highly recommends that you enable Unicode support by setting the LANG and LC_ALL environment variables to a locale with the UTF-8 character set. This enables the operating system to process any character in Unicode. Oracle SOA Suite technologies, for example, are based on Unicode.

If the operating system is configured to use a non-UTF-8 encoding, Oracle SOA Suite components may function in an unexpected way. For example, a non-ASCII file name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.

In a design-time environment, if you are using Oracle JDeveloper, select Tools -> Preferences -> Environment -> Encoding -> UTF-8 to enable Unicode support.

6.1.3 Installing as a Non-Default User on UNIX Operating Systems

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

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

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

6.1.4 Verifying Shared Storage Configurations on UNIX Operating Systems

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.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 Installing Oracle HTTP Server on Linux Operating Systems Requires NPTL

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

getconf GNU_LIBPTHREAD_VERSION

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

6.3.1 Installing Font Packages on Solaris 11 for Forms and Reports

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

system/font/daewoo-misc
system/font/gnome-fonts
system/font/isas-misc
system/font/jis-misc
system/font/misc-ethiopic
system/font/misc-meltho
system/font/sun-ja-bitmap
system/font/sun-ja-bitmap-unicode
system/font/truetype/arphic-ukai
system/font/truetype/bh-luxi
system/font/truetype/bitstream-vera
system/font/truetype/fonts-core
system/font/truetype/gentium
system/font/truetype/google-droid
system/font/truetype/hanyang-ko
system/font/truetype/ipafont-mincho
system/font/truetype/sil
system/font/truetype/unfonts-ko-core
system/font/truetype/unfonts-ko-extra
system/font/truetype/unifont
system/font/truetype/wqy-zenhei
system/font/xorg/cyrillic
system/font/xorg/iso8859-10
system/font/xorg/iso8859-11
system/font/xorg/iso8859-13
system/font/xorg/iso8859-14
system/font/xorg/iso8859-15
system/font/xorg/iso8859-16
system/font/xorg/iso8859-2
system/font/xorg/iso8859-3
system/font/xorg/iso8859-4
system/font/xorg/iso8859-5
system/font/xorg/iso8859-7
system/font/xorg/iso8859-8
system/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:

  1. Set LC_ALL=C.

  2. Set the NLS_LANG environment variable to AMERICAN_AMERICA.WE8ISO8859P15, or set the DISPLAY variable to any 64-Bit Linux machine.

6.3.2 Applying Solaris Patches in Non-Global Zones

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

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

showrev -p | grep patch_number

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

showrev -p | grep 137111

6.5.1 Patches Required Before Installing Fusion Middleware Products on IBM AIX 7.2

Install 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/prereq
     

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

8.3.1 Starting the 32-Bit Oracle Web Tier Installer on a 64-Bit Linux Operating System

If you are installing the 32-bit version of Oracle Web Tier on a 64-bit Linux operating system, you must perform the steps described below to replace your original /usr/bin/gcc file with a new GCC file (called gcc41) that makes use of the existing 32-bit library files on your system. It is not necessary to install a new 32-bit GCC on your system.

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:

   1. Move the existing /usr/bin/gcc file to /usr/bin/gcc.orig with the mv command:

      mv /usr/bin/gcc /usr/bin/gcc.orig
      

   2. Using a text editor such as vi, create a new file called gcc41 that contains the following content (the line beginning with exec must be a single line):

      #!/bin/sh
      exec /usr/bin/gcc.orig -m32 -static-libgcc -B /usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/ $*
      

      
      

      Note: The directory usr/lib/gcc/x86_64-redhat-linux/4.1.2/32/ may differ slightly depending on the version of your Linux operating system. Search for the corresponding 32-bit directory under /usr/lib/gcc on your Linux operating system and use that directory in the gcc41 file.

      
      

   3. Change the file permission for the gcc41 file using the following command:

      chmod 755 /usr/bin/gcc41
      

   4. Create a symbolic link to /usr/bin/gcc with the following command:

      ln -s -f /usr/bin/gcc41 /usr/bin/gcc
      

   5. Exit as the root user.

3. Run the following command before starting the installer:

   linux32 bash
   

4. Obtain your 32-bit Oracle Web Tier installer.

   For information on where to obtain product installers, see the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files page:

   http://docs.oracle.com/cd/E23104_01/download_readme.htm
   

5. Install Oracle Web Tier as described in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier.

   During the installation on the Configure Components screen, make sure you do not select Oracle Web Cache and associate it with a WebLogic domain; this is not supported for 32-bit Web Tier on a 64-bit system.

6. When the installation and configuration are complete, revert the gcc file back to its original state and remove the symbolic link.

Note that this procedure must be repeated anytime you are doing a 32-bit Web Tier installation on a 64-bit system, including the installation of a patch set.

8.3.2 Starting the Generic Installer with a 32-Bit JDK on a 64-Bit Operating System

If you are installing Oracle SOA Suite, Oracle WebCenter Portal, Oracle WebCenter Content, Oracle Application Developer, Oracle Service Bus, or Oracle Identity and Access Management on any supported 64-bit operating system with a 32-bit JDK, you must specify the JRE_LOCATION using the -jreLoc parameter from the command line when you start the product installer. For example:

./runInstaller -jreLoc JRE_LOCATION

Normally, if you do not use the -jreLoc parameter you will be prompted to specify the JRE_LOCATION from the command line. However, this option is not supported in such cases, and the installer will not start.

9.2.1 Using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager

If you are using Oracle Database 11g (11.1.0.7) with Oracle Identity Manager 11g, there are certain database patches that must be applied.

See "Patch Requirements for Oracle Database 11g (11.1.0.7)" in the "Oracle Identity Manager" chapter of the 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 Vault

If you are using Oracle Database 11g (11.2.0.1) and you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:

1. Apply patch 8897382 (see the README file in the patch for instructions).

2. In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql (on UNIX operating systems) or ORACLE_HOME\ldap\datasecurity\dbv_oid_command_rules.sql (on Windows operating systems) file, find the following code:

   /declare
   .
   begin
   .
      dvsys.dbms_macadm.CREATE_COMMAND_RULE(
      command => 'CONNECT'
      ,rule_set_name => 'OID App Access'
      ,object_owner => 'ODS'
      ,object_name => '%'
      ,enabled => 'Y');
   .
   commit;
   .
   end;/
   

   Change the following line:

   ,object_owner => 'ODS'
   

   to:

   ,object_owner => '%'
   

9.3.1 Notes for Using an Oracle Database for the MDS Schema

Note that when you use an Oracle Database, the MDS database user created by Repository Creation Utility (RCU) requires EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB. When you create a metadata repository using RCU, if PUBLIC does not have EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB, the RCU user must have the privilege to grant EXECUTE privilege on DBMS_OUTPUT and DBMS_LOB to the MDS user.

To ensure that you have the correct privileges, login to RCU as a SYSDBA or as a DBA user who has EXECUTE privilege with GRANT OPTION on DBMS_OUTPUT and DBMS_LOB.

9.3.2 Notes for Using a Microsoft SQL Server Database for the MDS Schema

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

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

  ALTER DATABASE mds SET READ_COMMITTED_SNAPSHOT ON
  

• You should use case-sensitive collation to support the case-sensitive semantics in the metadata repository. For example, if Latin1_General is used, select the SQL_Latin1_General_CP1_CS_AS collation using the following SQL command:

  ALTER DATABASE mds COLLATE SQL_Latin1_General_CP1_CS_AS
  

  In the example, the substring CS denotes case sensitivity. In you ned to configure your database for case-insensitive collation, use the CI substring.

• There are some minor differences between an Oracle schema and a SQL Server schema. The length of the certain text fields are shorter for a SQL Server schema. For example, the full path name of the metadata in SQL Server is limited to 400 characters.

9.3.3 Notes for Using an IBM DB2 Database for the MDS Schema

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

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

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

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

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

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

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

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

  db2 'update database config for database_alias using locktimeout 180'
  

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

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

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

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

  Restart the database server using the using db2stop and db2start commands.

• DB2 may escalate a row lock to a table lock due to memory stress or lock usage. As the result, a user's transaction may be rolled back as a victim of deadlock or lock timeout. To reduce lock escalation, you can increase the size of the MAXLOCKS and LOCKLIST configuration parameters. Use the following commands:

  db2 'update database config for database_alias using locklist value'
  db2 'update database config for database_alias using maxlocks value'
  

  For 11g Release 1 (11.1.1.8.0) and later, the MAXLOCKS value should be set to 20, and the LOCKLIST value should be set to 70000.

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

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

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

  db2 'update database config for database_alias using CUR_COMMIT ON'
  

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

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

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

9.3.4 Notes for Using a MySQL Database for the MDS Schema

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

• MySQL 5.5.14 or later must be used for the MDS repository to work properly.

• You must select MySQL's Innodb engine as the database engine during database installation.

• Set the lock timeout parameter of the database to a low value. To query the lock timeout value for your MySQL database, use the following command under the MySQL client:

  show variables like 'innodb_lock_wait_timeout';
  

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

  set global innodb_lock_wait_timeout=600
  

  The database will not remember this setting after it is rebooted. To keep the setting, make the corresponding changes in the my.cnf file.

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

• MySQL provides several my.cnf templates under the mysql_home/support-files directory. To configure MySQL to work property with MDS, use my-large.cnf as the starting point for your my.cnf and make the following setting changes:

  # The following stack memories must be set to a large enough value:
  thread_stack=1024k
  # Increase max_allowed_packet to allow for longer lobs.
  max_allowed_packet = 64M
  # max_sp_recursion_depth should be 64
  max_sp_recursion_depth=64
   
  # Set the sql_mode to STRICT_TRANS_TABLES, so MySQL will report an error if a
  # string value is too long for the table field.  By default, MySQL will
  silently truncate a string value.
  #  Also set NO_BACKSLASH_ESCAPES so strings like '\' will be accepted.
  sql_mode=STRICT_TRANS_TABLES,NO_BACKSLASH_ESCAPES
   
  # Set collation and character set for the server. 
  character-set-server=utf8mb4
  collation-server=utf8mb4_bin
   
  # Transaction isloatoin has to be "READ-COMMITED".
  transaction-isolation=READ-COMMITTED
  
  # Uncomment the following settings for InnoDB tables
  innodb_data_home_dir = /usr/local/mysql/data
  innodb_data_file_path = ibdata1:10M:autoextend
  innodb_log_group_home_dir = /usr/local/mysql/data
  # You can set .._buffer_pool_size up to 50 - 80 %
  # of RAM but beware of setting memory usage too high
  innodb_buffer_pool_size = 256M
  innodb_additional_mem_pool_size = 20M
  # Set .._log_file_size to 25 % of buffer pool size
  innodb_log_file_size = 64M
  innodb_log_buffer_size = 8M
  innodb_flush_log_at_trx_commit = 1
  innodb_lock_wait_timeout = 50
   
  # The following three parameters will ensure that MDS repository indexes
  # can be created successfully.  
  innodb_file_per_table=true
  innodb_file_format=Barracuda
  innodb_large_prefix=true
   
  # If log-bin is turned on, the following parameter
  # must be on to ensure MDS triggers can be created successfully.
  log_bin_trust_function_creators=ON
  binlog_format=mixed
   
  # In the [client] section of the configuration file, set the character set.
  default_character_set=utf8mb4
  

• Oracle WebLogic Server 10.3.5 and earlier versions do not have MySQL JDBC driver configured. Use a later version of Oracle WebLogic Server if you want to choose a MySQL database as a data source.

• Tips for starting MySQL Server using mysqld_safe: It is suggested to use the "--defaults-file=your_my.cnf" parameter when you start mysqld_safe, which will ensure a desired copy of my.cnf is used by your mySQL server. The "--defaults-file" parameter has to be the first parameter of your mysqld_safe command. For example:

  ./mysqld_safe --defaults-file=/etc/my.cnf --user=mysql &
  

  Be sure to set the access privileges of your my.cnf file to "-rw-r--r--". MySQL will ignore your my.cnf if other users have "write" access.

10.1.1 RCU Supported Platforms

RCU is available on any 32-bit x86 Linux and 32-bit Microsoft Windows operating system used with Oracle Fusion Middleware. You can run RCU from these machines to connect to any certified local or remote Oracle, IBM DB2, MySQL, or Microsoft SQL Server database in order to create the schemas required by Fusion Middleware components. The database can be running on any operating system platform that is supported by that particular database.

Beginning with 11g Release 1 (11.1.1.4.0) and later, RCU can also be run on any 64-bit x86 Linux and 64-bit Microsoft Windows operating system used with Oracle Fusion Middleware. On 64-bit Linux operating systems, you must run the following command before starting RCU:

set linux32 bash

To view the system requirements for certified 32-bit and 64-bit Linux operating systems, see Section 6.2, "Linux Operating System Requirements". RCU can be run on your Linux operating system as long as these system requirements are met.

To view the system requirements for certified 32-bit and 64-bit Windows operating systems, see Section 7, "System Requirements for Windows Operating Systems". RCU can be run on your Windows operating system as long as these system requirements are met.

10.1.2 Using the Correct RCU Version

Make sure that the RCU version number matches the version number of the Oracle Fusion Middleware product you are installing and using. You may encounter problems if your RCU version number does not match your product version number.

For more information, refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files, which contain the correct RCU version to download for each Oracle Fusion Middleware release.

10.3.1 General Oracle Database Requirements

RCU checks for the following on Oracle databases:

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

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

• Database user has SYSDBA role.

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

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

  GRANT execute on sys.dbms_lock to user_name with grant option
  

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

  GRANT execute on sys.dbms_lock to system with grant option
  

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

• Character set is AL32UTF8.

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

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

  You can ignore this warning and continue using RCU.

  
  

  Note: If you are installing Oracle WebCenter Portal or Oracle WebCenter Content, it is strongly recommended that you configure your database to use AL32UTF8 character set encoding. If your database is not already configured to do so, refer to your database documentation for instructions. If you are installing a new database, you should configure your database to use AL32UTF8 character set encoding.

  
  

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

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

• The DB_BLOCK_SIZE is greater than or equal to 8KB

10.3.2 DBMS_SHARED_POOL and XAVIEWS Must be Created on Oracle Databases for Oracle Identity Management

The following packages must be installed as SYS user on Oracle databases prior to creating Oracle Identity Management schemas:

• DBMS_SHARED_POOL

• XAVIEWS

For more information, see the following:

• For more information on DBMS_SHARED_POOL, see "DBMS_SHARED_POOL" in Oracle Database PL/SQL Packages and Types Reference.

• For more information on XAVIEWS, see "Using JDBC XA Drivers with WebLogic Server" in Oracle Fusion Middleware Programming JTA for Oracle WebLogic Server.

10.3.3 Setting the parallel_max_servers Parameter for the ODS Schema

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

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

10.3.4 Setting the nls_length_semantics Parameter in your Oracle Database for Oracle Discoverer

Oracle Discoverer only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.

To check the values of this parameter using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"
SQL> show parameters nls_length_semantics

Replace password with the actual password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"
SQL> select name,value from v$parameter;

10.3.5 Applying Oracle Database Patch 8625762 for Oracle Business Process Management Suite

If you are installing Oracle Business Process Management Suite (part of Oracle SOA Suite) and you are using an Oracle database, you must apply patch 8625762 to avoid error ORA-03137 and OutOfMemory exception.

You can obtain the patch by specifying the patch ID in My Oracle Support (formerly MetaLink):

1. Access and log into My Oracle Support at the following location:

   http://support.oracle.com/
   

2. Click the Patches & Updates link.

3. Enter the Patch ID or Number, then click Search. A Patch Search Results table appears.

4. Using the Release and Platform columns, find the desired patch, then click the associated Patch ID.

5. In the page that now appears, click the Download button in the right-hand column.

10.3.6 Installing Oracle Text for Oracle Portal

Oracle Text must be installed on your Oracle Database in order for the Oracle Portal schema to be configured. To check if Oracle Text is available on your database, use the following SQL command:

select count(*) from dba_views where owner='CTXSYS' and view_name='CTX_VERSION';

The count should be greater than 0. Refer to your Oracle Database documentation for more information about Oracle Text.

10.3.7 Applying Patch 16266667 for Oracle Portal

Oracle Portal creation requires patch 16266667.

You can obtain the patch by specifying the patch ID in My Oracle Support (formerly MetaLink):

1. Access and log into My Oracle Support at the following location:

   http://support.oracle.com/
   

2. Click the Patches & Updates link.

3. Enter the Patch ID or Number, then click Search. A Patch Search Results table appears.

4. Using the Release and Platform columns, find the desired patch, then click the associated Patch ID.

5. In the page that now appears, click the Download button in the right-hand column.

10.3.8 Component-Specific Requirements for Oracle Databases

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

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

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

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

10.4.1 General Microsoft SQL Server Database Requirements

RCU checks for the following on Microsoft SQL Server databases:

• Database version is equal to or higher than 2005.

• Database user (db_owner) should have SYSDBA or DBA privileges.

10.4.2 Creating Oracle WebCenter Portal Schemas on Microsoft SQL Server Databases

If you are creating the schemas in a Microsoft SQL Server database, a database instance must be created prior to running RCU. The MDS schema has some specific requirements; see Section 9.3.2, "Notes for Using a Microsoft SQL Server Database for the MDS Schema" for more information.

10.4.3 Component-Specific Requirements for Microsoft SQL Server Databases

Table 12 lists all of the supported schemas for Microsoft SQL Server databases, along with any component-specific prerequisite information that must be met for RCU to be able to create schema.

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

10.5.1 Creating Database Operating System Users

IBM DB2 authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example:

• If you create a schema named DEV_SOA on an IBM DB2 database running on a Linux operating system, then you must also create the operating system user dev_soa (matching name, all lowercase letters).

• If you create a schema named DEV_SOAINFRA on an IBM DB2 database running on a Windows operating system, then you must also create the operating system user dev_soainfra (matching name, all lowercase letters).

10.5.2 Size Limit for Schema Prefixes (Linux Only)

IBM DB2 has an eight character limit for schema names. Therefore, the schema names are shortened to a maximum of three characters (plus schema prefix and underscore), making the maximum size of the user defined prefix four characters.

For example, on IBM DB2 databases running on a Windows operating system, and all supported Oracle and Microsoft SQL Server databases, the SOA Infrastructure schema you create might be called DEV_SOAINFRA. However, on an IBM DB2 database running on a Linux operating system, this schema name must be shortened to DEV_SOA.

10.5.3 Configuring Your DB2 Database

For important information about configuring your IBM DB2 database, refer to Section 9.3.3, "Notes for Using an IBM DB2 Database for the MDS Schema".

10.5.4 RCU Supported Schemas for IBM DB2 Databases

Not all of the schemas that are supported in Oracle and Microsoft SQL Server databases are supported on IBM DB2 databases. Table 13 shows the schemas that are supported in IBM DB2 databases.

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

10.6.1 RCU Supported Schemas for MySQL Databases

Not all schemas are supported on MySQL databases. Table 14 shows the schemas that are supported in MySQL databases.

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

10.6.2 MySQL Requirements for the Oracle Data Integrator Schema

In order to create the Oracle Data Integrator schema in a MySQL database, the following must be set:

innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix = 1
LOG_BIN_TRUST_FUNCTION_CREATORS = on