Go to primary content
Oracle Agile Engineering Data Management Prerequisites Guide
Release e6.2.1.0
E69108-1
  Go To Table Of Contents
Contents

Previous
Previous
 
 

4 Operating System Requirements and Configurations

The Agile e6.2.1.0 software has been certified under the following operating system configurations. The following sections describe the configurations supported on your platforms.


Note:

The EDM product only supports IPv4 addresses. Network connections with IPv6 are not supported.

4.1 Windows

The minimum service packs for the supported Windows operating systems are as follows:

Windows Version Service Pack
Windows 7 64-bit (client only) SP1
Windows 10 64-bit (client only)
Windows 2012 R2 64-bit
Windows Server 2016 R2 64-bit

4.1.1 Microsoft Visual Studio 2010 C/C++ Runtime Libraries

The Agile e6.2.1.0 software requires a specific installed runtime library (10.0.40219.325) which always has to be installed even if there is already a newer version of the runtime library installed.

Installation Type Microsoft Visual Studio 2010 C/C++ Runtime Libraries Package Names
Agile e6.2.1.0 server 32bit and 64bit vcredist_x86_vc10.exeand

vcredist_x64_vc10.exe

WebLogic server 64bit vcredist_x64_vc10.exe
Java Client 32bit vcredist_x86_vc10.exe

Execute the package, which can be found in the directory <installation_package_root>\tools\bin\Windows\, which will install the specific required Microsoft Visual Studio 2010 C/C++ runtime libraries.


Note:

The version that is bundled with the Agile e6.2.1.0 software should always be installed even if the Microsoft update is used to install updates for the runtime libraries in the future.

4.2 IBM AIX

4.2.1 Web References

  • IBM fixes: http://www.ibm.com/support/fixcentral/main/System+p/AIX

  • IBM Java Runtime Environment: http://www.ibm.com/developerworks/java/jdk/aix/service.html

4.2.2 Generic Requirements

The supported OS version for the IBM workstation is AIX 7.1 and the minimum technology level for the supported AIX operating system is as follows:

AIX Version Technology Level
7.1 1 (with SP4)

To determine the full operating system version enter the following command into a command shell:

oslevel -s
bos.perf.libperfstat bos.perf.proctools xlC.aix61.rte gpfs.base
7100-01-04-1216

The result for AIX 7.1 TL 1 SP4 should look like:

The following file sets must be installed:

  • bos.adt.base

  • bos.adt.libm

  • xlC.aix61.rte: 11.1.0.4 or later

To determine which operating system file sets are installed, enter the following command into a command shell:

lslpp -l [fileset_name]
lslpp -l

Or, enter the following command to list all the file sets:

4.2.3 Database Requirements

4.2.3.1 Operating System Packages

The following additional operating system file sets are required:

  • bos.adt.base

  • bos.adt.lib

  • bos.perf.libperfstat

  • bos.perf.perfstat

  • bos.perf.proctools

  • resct.compat.clients.rte

  • xlC.aix61.rte (version 10.1.0.0)

  • xlC.rte version 10.1.0.0)


Note:

GPFS is required only if you want to use a cluster file system for Oracle cluster ware or database files.

To determine whether the required file sets are installed and committed, enter a command into a command shell as follows:

lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \
 

If you are using the minimum operating system TL level for AIX 7.1 listed above, then install all AIX 7.1 Authorized Problem Analysis Reports (APARs) for AIX 7.1 TL 0 SP1, and the following AIX fixes:

  • IV16737

    Java won't instantiate if prot_none used for shared mmap region

  • IV21116

    System hangs or crashes when app uses shared symtab capability

  • IV21235

    System crash due to freed socket when socketpair() call used

  • IV28925

    Shlap process fails when shared symbol table feature is used

  • IV34869

    Thread_cputime() returns incorrect values

  • IV35057

    Loading 5.3 tls enabled libs by 5.2 apps caused core dump in 32b

  • IV39136

    Link fails with undocumented compiler flag and thread-local stg

  • IV41415

    Runtime linking failed to bind the bss symbol exported from main

  • IV45072

    A special-purpose linker flag works incorrectly

  • IV45073

    Add ability to reorder toc symbols in limited circumstances

To determine whether an APAR is installed, enter the command into a command shell:

/usr/sbin/instfix -i -k "IV16737"

The following compiler is required

  • IBM XL C/C++ Enterprise Edition for AIX, V9.0 April 2008 PTF

To determine the supported kernel mode, enter a command similar to the following:

/usr/bin/getconf KERNEL_BITMODE

The output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.

4.2.3.2 Configuring the Shell Limits

You do not need to configure kernel parameters on AIX systems. However, Oracle recommends that you set shell limits and system configuration parameters.

Shell Limit Recommended Value
Soft FILE size -1 (Unlimited)
Soft CPU time -1 (Unlimited) (This is the default value)
Soft DATA segment -1 (Unlimited)
Soft STACK size -1 (Unlimited)
Soft Real Memory site -1 (Unlimited)
Processes (per user) -1 (Unlimited) This limit is available only in AIX 6.1 or later

To display the current value specified for these shell limits, and to change them if necessary, you must:

  1. Enter the following command into a command shell:

    smit chuser

  2. In the User NAME field, enter the user name of the Oracle software owner, for example: oracle.

  3. Scroll down the list and verify that the value shown for the soft limits listed in the previous table is -1.

    If necessary, edit the existing value. To edit the values, you can use smit utility. However, to set the value of Soft Real Memory size, you must edit the file /etc/security/limits.


    Note:

    If you have permissions to run smit utility, then you automatically have the permissions to edit the limits file.

  4. When you have finished making changes, press F10 to exit.

4.2.3.3 Configuring the System Configuration Parameters

Verify that the kernel parameters shown below are set to values greater than or equal to the minimum value shown.

  • maxuprocs 16384

  • ncargs 128

To verify the values of both parameters, enter the following command

smit chgsys

Verify the values shown for Maximum number of PROCESSES and ARG/ENV list size in 4K byte blocks and if necessary, edit the values.

4.2.4 WebLogic Requirements

4.2.4.1 Operating System Packages

The following additional operating system file sets are required:

  • bos.adt.base

  • bos.adt.lib

  • bos.adt.libm

  • bos.perf.libperfstat

  • bos.perf.perfstat

  • bos.perf.proctools

  • rsct.basic.rte

  • rsct.compat.clients.rte

  • xlC.aix61.rte (version 12.1.0.1+)

  • xlC.rte (version 12.1.0.1+)

4.3 HP-UX

4.3.1 Web References

4.3.2 Generic Requirements

The supported OS version for the Itanium 2 architecture is 11i v3 (11.31) and the minimum quality pack for the supported HP-UX operating system is as follows:

HP-UX Version Quality Pack

Base Application
11iv3 (11.31) September 2012 September 2012

To determine the full operating system version enter the following command into a command shell:

uname -r
B11.31

The result for HP-UX 11iv3 should look like:

The installed base and application patches can be tested with the following command:

swlist -l bundle | grep QPK
QPKAPPS  B.11.31.1209.383 Applications Patches for HP-UX 11i v3, September 2012
QPKBASE  B.11.31.1209.383 Base Quality Pack Bundle for HP-UX 11i v3, September 2012

The output must be:

4.3.3 Recommended HP-UX Kernel Settings

The HP-UX 11i default value for maximum threads per process is 64. It is recommended that you use the maximum kernel setting for the max_thread_proc and maxusers parameters.


Note:

Setting maxusers to a higher value increases other machine-wide limits, such as nkthread (max number of kernel threads).

The table below lists the recommended configuration of the HP-UX kernel.

Parameter Old New Description
max_thread_proc 64 1024 Maximum threads per process
maxfiles 60 256 Soft file limit per process
maxusers 32 256 Influences other parameters
nkthread 499 3635 Number of threads total on the system
nproc 276 2068 Maximum number of processes
ncallout 292 2084 Number of pending timeouts


Note:

The values become effective after rebooting.

4.3.4 Database Requirements

4.3.4.1 Operating System Patches

  • PHCO_43503 - 11.31 diskowner (1M) cumulative patch

  • PHKL_38038 - 11.31 VM cumulative patch

  • PHKL_38938 - 11.31 SCSI cumulative I/O patch

  • PHKL_40941 - 11.31 scheduler cumulative patch

  • PHSS_36354 - 11.31 assembler patch

  • PHSS_37042 - 11.31 hppac (packed decimal)

  • PHSS_37959 - Libcl patch for alternate stack issue fix (QXCR1000818011)

  • PHSS_39094 - 11.31 linker + fdp cumulative patch

  • PHSS_39100 - 11.31 Math Library Cumulative Patch

  • PHSS_39102 Integrity Unwind Library

  • PHSS_38141 - 11.31 aC++ Runtime

4.3.4.2 Kernel Parameters

Verify that the below listed kernel parameters are set either to the formula or to values greater than, or equal to the recommended value shown:

Parameter Minimum Value
ksi_alloc_max 32768
executable_stack 0
maxfiles 1024
Maxfiles_lim 63488
max_thread_proc 1024
maxdsiz 1073741824 (1 GB)
maxdsiz_64bit 2147483648 (2 GB)
maxssiz 134217728 (128 MB)
maxssiz_64bit 1073741824 (1 GB)
maxuprc 3686
msgmap 4096
msgmni 4096
msgseg 32767
msgtql 4096
ncsize 35840
nfile 63488
nflocks 4096
ninode 34816
nkthread 7184
nproc 4096
semmni 4096
semmns 8192
semmnu 4092
semvmx 32767
shmmax The size of physical memory, or 1073741824 (0X40000000), whichever is greater.

Note: To avoid performance degradation, the value should be greater than or equal to the size of the available memory.

shmmni 4096
shmseg 512
vps_ceiling 64

To start the kcweb application, enter the following command into a command shell:

  • /usr/sbin/kcweb -F

  • Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

  • If necessary, refer to the kcweb online help for more information about completing this step.


Note:

If the current value for any parameter is higher than the value listed in this table, then do not change the value of that parameter.

If you modify the value of a parameter that is not dynamic, then you must restart the system.

MSGMAP and NCALLOUT are obsolete in HP_UX 11.31. You need not specify values for these parameters.


4.3.5 WebLogic Requirements

4.3.5.1 Operating System Packages

  • B3394BA (version 2.1.0)

4.3.5.2 Operating System Patches

  • PHKL_36248

  • PHKL_36249

  • PHSS_37202

  • PHSS_37501

  • PHCO_38050

  • PHSS_38139

4.4 Oracle Solaris (SPARC)

4.4.1 Web References

  • Oracle Solaris:

    http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html

  • Oracle Java Development Kit:

    http://www.oracle.com/technetwork/java/index.html

4.4.2 Generic Requirements

The supported OS version for Oracle servers (SPARC) is Solaris 11 and the minimum release level for the supported Solaris operating system is as follows:

Solaris Version Required Release
11 11.3

To determine the full operating system version enter the following command into a command shell:

uname -srvp

The result for Solaris 11.3 should look similar to:

SunOS 5.11 11.3 sparc

4.4.2.1 Operating System Packages

In addition, you will need the Sun Workshop Compilers Bundled libC (SUNWlibC) package to meet the C++ runtime environment requirements.

You also require the package: developer/assembler

To get the status of the above package enter the following command into a command shell:

pkg info system/library/c++-runtime

The exact version of Solaris 11 can be found in /etc/release:

cat /etc/release

The output should be:

Oracle Solaris 11.3 SPARC
Copyright (c) 1983, 2015, Oracle and/or its affiliates. All rights reserved.
Assembled 06 October 2015

Note:

No special kernel parameters, packages, or patches are required at the time of this release for Oracle Solaris 11.

4.5 Oracle Linux

4.5.1 Generic Requirements

The patch set for the supported Oracle Linux operating system is as follows:

Oracle Linux Required Update
7 2

The minimum package levels for the supported Linux operating system are:

Product Package Version
Oracle Agile EDM kernel 3.8.13-118.13.3.el7uek.x86_64 or later

glibc 2.17-105.el7 or later

libstdc++ 4.8.5-4.el7 or later

The installed versions of rpm packages can be tested with the following command:

rpm -q -a | grep <package-name>

To determine the amount of RAM memory installed on your system, enter the following command:

cat /proc/meminfo | grep MemTotal

To determine the bytes of swap space currently configured on your system, enter the following command:

/sbin/swapon --bytes

Note:

During the Oracle Linux OS installation it is recommended to use the "Server with GUI" option because this provides the required libraries to use the GUI installer.

4.5.2 Database Requirements

To determine whether the required packages are installed, enter a command into a command shell similar to the following:

rpm -q <package_name>

If a package is not installed, then install it from the Linux distribution media or download the required package version from the Linux vendor's website.

4.5.2.1 Database General

The following packages have to be installed for both the Server and Client:

Operating System Packages

  • binutils.x86_64

  • compat-libcap1.x86_64

  • compat-libstdc++-33.x86_64

  • gcc.x86_64

  • gcc-c++.x86_64

  • glibc.x86_64

  • glibc-devel.x86_64

  • ksh

  • libaio.x86_64

  • libaio-devel.x86_64

  • libgcc.x86_64

  • libstdc++.x86_64

  • libstdc++-devel.x86_64

  • libXi.x86_64

  • libXtst.x86_64

  • make.x86_64

  • psmisc.x86_64

  • sysstat.x86_64

4.5.2.2 Database Client

The following additional packages have to be installed:

Operating System Packages

  • compat-libstdc++-33.i686

  • glibc.i686

  • glibc-devel.i686

  • libgcc.i686

  • libstdc++.i686

  • libstdc++-devel.i686

  • libaio.i686

  • libaio-devel.i686

  • libXi.i686

  • libXtst.i686

4.5.2.3 Database Server

No additional packages are required.

4.5.2.4 Kernel Parameters

During the Oracle Database installation, you can generate and run the fixup script to check and set the kernel parameter values required for successful installation of the database. This script updates required kernel packages, if necessary, to minimum values.


Note:

If you cannot use the fixup script, review the following table to set the values manually.


Note:

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

The procedure following the table describes how to verify and set the values.

Parameter Minimum Value File
semmsl

semmns

semopm

semmni

250

32000

100

128

/proc/sys/kernel/sem
shmall 40 percent of the size of physical memory in pagesNote: If the server supports multiple databases, or uses a large SGA, then set this parameter to a value that is equal to the total amount of shared memory, in 4K pages, that the system can use at one time. /proc/sys/kernel/shmall
shmmax Half the size of physical memory in bytes.

See My Oracle Support Note 567506.1 for additional information about configuring shmmax.

/proc/sys/kernel/shmmax
shmmni 4096 /proc/sys/kernel/shmmni
file-max 6815744 /proc/sys/fs/file-max
aio-max-nr 1048576

Note: This value limits concurrent outstanding requests and should be set to avoid I/O subsystem failures.

/proc/sys/fs/aio-max-nr
ip_local_port_range Minimum: 9000

Maximum: 65500

Note: See message URL http://docs.oracle.com/cd/E16655_01/install.121/e17720/app_manual.htm#CIHGEGJJSetting UDP and TCP Kernel Parameters Manually

/proc/sys/net/ipv4/ip_local_port_range
rmem_default 262144 /proc/sys/net/core/rmem_default
rmem_max 4194304 /proc/sys/net/core/rmem_max
wmem_default 262144 /proc/sys/net/core/wmem_default
wmem_max 1048576 /proc/sys/net/core/wmem_max


Note:

If the current value for any parameter is higher than the value listed in this table, do not change the value of that parameter!

To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

  1. To view the current values of the kernel parameters, enter the commands similar to the following into a command shell:


    Note:

    Make a note of the current values and identify any values that you must change.

    Parameter Command Description
    semmsl, semmns, semopm and semmni # /sbin/sysctl -a | grep sem This command displays the value of the semaphore parameters in the order listed.
    shmall, shmmax and shmmni # /sbin/sysctl -a | grep shm This command displays details of the shared memory segment sizes.
    file-max # /sbin/sysctl -a | grep file-max This command displays the maximum number of file handles.
    ip_local_port_range # /sbin/sysctl -a | grep ip_local_port_range This command displays a range of port numbers.
    rmem_default # /sbin/sysctl -a | grep rmem_default -
    rmem_max # /sbin/sysctl -a | grep rmem_max -
    wmem_default # /sbin/sysctl -a | grep wmem_default -
    wmem_max # /sbin/sysctl -a | grep wmem_max -
    aio-max-nr # /sbin/sysctl -a | grep aio-max-nr -

  2. If the value of any kernel parameter is different from the recommended value, then complete the following steps:

    Use any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:


    Note:

    Include lines only for the kernel parameter values to change. For the semaphore parameters (kernel.sem), you must define all four the four values. However, if any of the current values are larger than the minimum value, then specify the larger value.

    fs.aio-max-nr = 1048576
    fs.file-max = 6815744
    kernel.shmall = 2097152
    kernel.shmmax = 536870912
    kernel.shmmni = 4096
    kernel.sem = 250 32000 100 128
    net.ipv4.ip_local_port_range = 9000 65500
    net.core.rmem_default = 262144
    net.core.rmem_max = 4194304
    net.core.wmem_default = 262144
    net.core.wmem_max = 1048586
    

    Note:

    By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.

  3. Enter the following command to change the current values of the kernel parameters:

    /sbin/sysctl -p
    
  4. Review the output from this command to verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then enter this command again.

  5. To confirm that the values are set correctly, enter the command:

    /sbin/sysctl -a
    
  6. After updating the values of the kernel parameters in the /etc/sysctl.conf file, either restart the computer, or run the command sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.

4.5.2.5 Setting UDP and TCP Kernel Parameters Manually

If you do not use a fixup script or CVU to set ephemeral ports, then set TCP/IP ephemeral port range parameters to provide enough ephemeral ports for the anticipated server workload. Ensure that the lower range is set to at least 9000 or higher, to avoid Well Known ports, and to avoid ports in the Registered Ports range commonly used by Oracle and other server ports. Set the port range high enough to avoid reserved ports for any applications you may intend to use. If the lower value of the range you have is greater than 9000, and the range is large enough for your anticipated workload, then you can ignore Oracle Universal Installer warnings regarding the ephemeral port range.

For example, with IPv4, use the following command to check your current range for ephemeral ports:

$ cat /proc/sys/net/ipv4/ip_local_port_range
32768 61000

In the preceding example, the lowest port (32768) and the highest port (61000) are set to the default range.

If necessary, update the UDP and TCP ephemeral port range to a range high enough for anticipated system workloads, and to ensure that the ephemeral port range starts at 9000 and above. For example:

# echo 9000 65500 > /proc/sys/net/ipv4/ip_local_port_range

Oracle recommends that you make these settings permanent. For example, as root, use a text editor to open /etc/sysctl.conf, and add or change to the following: net.ipv4.ip_local_port_range = 9000 65500, and then restart the network (# /etc/rc.d/init.d/network restart).

Refer to your Linux distribution system administration documentation for detailed information about how to automate this ephemeral port range alteration on system restarts

See also Setting TCP Network Protocol Buffer for Direct NFS Client if you use Direct NFS Client.

4.5.2.6 Setting the Shell Limits for the Oracle User

For each installation, the software owner must check the resource limits for installation, using the following recommended ranges:

Resource Shell Limit Resource Soft Limit (KB) Hard Limit (KB)
Open file descriptors nofile at least 1024 at least 65536
Number of processes available to a single user nproc at least 2047 at least 16384
Size of the stack segment of the process stack at least 10240 at least 10240, and at most 32768

To check resource limits:

  1. Log in as an installation owner:

  2. Check the soft and hard limits for the file descriptor setting. Ensure that the result is in the recommended range. For example:

    $ ulimit -Sn4096$ ulimit -Hn65536
    
  3. Check the soft and hard limits for the number of processes available to a user. Ensure that the result are in the recommended range. For example:

    $ ulimit -Su2047$ ulimit -Hu16384
    
  4. Check the soft limit for the stack setting. Ensure that the result is in the recommended range. For example:

    $ ulimit -Ss10240$ ulimit -Hs32768
    
  5. Repeat this procedure for each Oracle software installation owner.

    If necessary, update the resource limits in the /etc/security/limits.conf configuration file for the installation owner. However, note that the configuration file is distribution specific. Contact your system administrator for distribution specific configuration file information.


    Note:

    If Oracle users are logged in, then changes in the limits.conf file do not take effect until you log these users out and log them back in. You must do this before you use these accounts for installation.

4.5.2.7 Using MEMORY_TARGET by 12c Installation on Oracle Linux

Increase the size of /dev/shm mountpoint - to be bigger than the value of the initialization parameters MEMORY_TARGET and MEMORY_MAX_TARGET. Refer to the Hardware Sizing Guide for Agile e6.2.1.0 document for the value of the initialization parameters MEMORY_TARGET and MEMORY_MAX_TARGET.

For instance, if the value of MEMORY_MAX_TARGET is 8GB, increase the size of /dev/shm mountpoint with the following command:

mount -t tmpfs shmfs -o size=8g /dev/shm

Also, to make this change persistent for a system restarts, add an entry in the file /etc/fstab similar to the following:

shmfs /dev/shm tmpfs size=8g 0

When AMM (Automatic Memory Management) is enabled, by setting the initialization parameters MEMORY_TARGET and MEMORY_MAX_TARGET, it uses /dev/shm on Linux. If MEMORY_MAX_TARGET is set over /dev/shm size, you may get the following error message:

ORA-00845: MEMORY_TARGET not supported on this system!

A solution is to increase the /dev/shm mountpoint size.

4.5.3 WebLogic Requirements

The following need to be installed.

4.5.3.1 Operating System Packages

The following packages have to be installed:

  • binutils.x86_64

  • compat-libcap1.x86_64

  • compat-libstdc++-33.x86_64

  • compat-libstdc++-33.i686

  • gcc.x86_64

  • gcc-c++.x86_64

  • glibc.x86_64

  • glibc.i686

  • glibc-devel.i686

  • ksh

  • libaio.x86_64

  • libaio-devel.x86_64

  • libgcc.x86_64

  • libgcc.i686

  • libstdc++.x86_64

  • libstdc++.i686

  • libstdc++-devel.x86_64

  • libXext.i686

  • libXtst.i686

  • make

  • motif.x86_64

  • ocfs2-tools

  • sysstat.x86_64

4.5.4 Agile e6 Server Requirements

The following need to be available:

4.5.4.1 Operation System Packages

The following packages have to be installed:

  • redhat-lsb-core 4.1-27.0.1.el7 or later

  • llibXrender 0.9.8-2.1.el7 or later

  • libcurl 7.29.0-25.0.1.el7 or later

  • libaio 0.3.109-13.el7 or later