2 Pre-Installation Tasks

2.1.1 Completing a Default Linux Installation

If your operating sytem choice is to use a Linux operating system, then Oracle recommends that you install your Linux operating system with the default software packages (RPMs). This installation includes most of the required packages and helps you limit manual checks of package dependencies. Oracle recommends that you do not customize the RPMs during installation.

After installation, add all of the Legacy Software Development packages. Review system requirements for your distribution to ensure that you have all required kernel packages installed, and complete all other configuration tasks required for your distribution, and for your system configuration.

2.1.2 About the Oracle Validated Configuration RPM and Linux

If your Linux distribution is Oracle Enterprise Linux, or Red Hat Enterprise Linux, and you are an Unbreakable Linux customer, then you can complete most preinstallation configuration tasks by using the Oracle Validated Configurations Setup RPM, available from the Unbreakable Linux Network (ULN).

When it is installed, the Oracle Validated Configuration RPM sets and verifies system parameters based on recommendations from the Oracle Validated Configurations program, and installs any additional packages needed for installing Oracle Clusterware and Oracle Database. It also updates sysctl.conf settings, system startup parameters, user limits, and driver parameters to values extensive testing shows will provide better performance.

To become an Oracle Unbreakable Linux customer, contact your sales representative, or purchase a license from the Unbreakable Linux store:

http://oraclestore.oracle.com/linux

To register your server on the Unbreakable Linux Network, or to find out more information, refer to the following URL:

https://linux.oracle.com

2.1.3 Installing the Oracle Validated Configuration RPM for Linux

Use the following procedure to subscribe to Oracle Unbreakable Linux channels, and to add the Oracle Software for Enterprise Linux channel that distributes the Oracle Validated Configurations Setup RPM:

1. Complete a default Oracle Enterprise Linux workstation installation, or a default Red Hat Enterprise Linux installation.

2. Register your server with Unbreakable Linux Network (ULN). By default, you are registered for the Enterprise Linux Latest channel for your operating system and hardware.

3. Log in to ULN at the following URL:

   https://linux.oracle.com

4. Click the Systems tab, and in the System Profiles list, select a registered server. The System Details window opens, and displays the subscriptions for the server.

5. From the Available Channels list, select the Oracle Software for Enterprise Linux channel that is appropriate for your installation of Linux (for example: "Oracle Software for Enterprise Linux 4 (x86_64)."

6. Click Subscribe.

7. From a terminal session, as root, enter the following command:

   # up2date --nox --show-channels
   

   You should see output indicating that you have subscribed to the Oracle Software for Enterprise Linux channel. For example:

   el4_i386_latest
   el4_i386_oracle
   

8. Open a terminal session as root, and install the Oracle Validated Configurations Setup RPM with up2date, using the following command:

   # up2date --install oracle-validated
   

9. Repeat steps 1 through 8 on all other servers in your cluster.

   Note:

   Check the Oracle Validated Configuration RPM log file to review system configuration changes:

   /etc/sysconfig/oracle-validated/results/orakernel.log
   

2.2.1 Entering Cluster Verification Utility Commands

Before the database is installed, to enter a CVU command, change directory and use the following syntax to start CVU:

$ /mountpoint/crs/Disk1/cluvfy/
$ ./runcluvfy.sh options

In the preceding example, the variable mountpoint represents the mountpoint path for the installation media, and the variable options represents the CVU command options that you select. For example:

$ /dev/dvdrom/crs/Disk1/cluvfy/
$ ./runcluvfy.sh comp nodereach -n node1,node2 -verbose

By default, when you enter a CVU command, CVU provides a summary of the test. During pre-installation, Oracle recommends that you obtain detailed output by using the -verbose argument with the CVU command. The -verbose argument produces detailed output of individual checks. Where applicable, it shows results for each node in a tabular layout.

2.2.2 Using CVU to Determine if Installation Prerequisites are Complete

You can use CVU to determine which system prerequisites for installation are already completed. Use this option if you are installing Oracle 10g Release 2 (10.2) on a system with a pre-existing Oracle software installation. In using this option, note the following:

• You must complete the prerequisites for using CVU

• CVU can assist you by finding pre-installation steps that need to be completed, but it cannot perform pre-installation tasks

Use the following syntax to determine what pre-installation steps are completed, and what pre-installation steps must be performed

/$ ./runcluvfy.sh stage -pre crsinst -n node_list 

In the preceding syntax example, replace the variable node_list with the names of the nodes in your cluster, separated by commas.

For example, for a cluster with mountpoint /dev/dvdrom/, and with nodes node1, node2, and node3, enter the following command:

$ cd /dev/dvdrom/crs/Disk1/cluvfy/
$ ./runcluvfy.sh stage -pre crsinst -n node1,node2,node3

Review the CVU report, and proceed to the sections of the pre-installation chapter to complete additional steps as needed.

2.2.3 Using the Cluster Verification Utility Help

The cluvfy commands have context-sensitive help that shows correct syntax usage based on the command line arguments that you enter.

If you enter an invalid CVU command, then CVU shows the correct usage for that command. For example, if you type runcluvfy.sh stage -pre dbinst, then CVU shows the correct syntax for the database pre-installation checks that CVU performs with the dbinst stage option. The following is a list of context help commands.

• cluvfy: CVU displays high-level generic usage text describing the stage and component syntax.

• cluvfy -help: CVU displays detailed CVU command information.

• cluvfy comp -list: CVU displays a list of components that can be checked, and brief descriptions of how each component is checked.

• cluvfy comp -help: CVU displays detailed syntax for each of the valid component checks.

• cluvfy stage -list: CVU displays a list of valid stages.

• cluvfy stage -help: CVU displays detailed syntax for each of the valid stage checks.

2.2.4 Using Cluster Verification Utility with Oracle 10g Release 1

You can use CVU on the Oracle 10g Release 2 (10.2) media to check system requirements for Oracle 10g Release 1 (10.1) installations. To use CVU to check 10. 1 installations, append the command flag -r 10gR1 to the standard CVU system check commands.

For example, to perform a verification check for a Cluster Ready Services 10. 1 installation, on a system where the media mountpoint is /dev/dvdrom/, and the cluster nodes are node1, node2, and node3, enter the following command:

$ ./runcluvfy.sh stage -pre crsinst -n node1,node2,node3 -r 10gR1

2.2.5 Verbose Mode and "Unknown" Output

If you run CVU using the -verbose argument, and a CVU command responds with UNKNOWN for a particular node, then this is because the CVU cannot determine whether a check passed or failed. The following is a list of possible causes for an "Unknown" response:

• The node is down

• Executables required by CVU are missing in the CRS_home /bin or Oracle home directory

• The user account starting CVU does not have privileges to run common operating system executables on the node

• The node is missing an operating system patch, or a required package

• The node has exceeded the maximum number of processes or maximum number of open files, or there is a problem with IPC segments, such as shared memory or semaphores

2.4.1 Creating the Oracle Inventory Group

Oracle Universal Installer (OUI) helps you to choose a group to use as the Oracle Inventory group. If you have an existing Oracle Inventory group, then provide this group name and path when prompted.

The following subsections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary.

Determining If the Oracle Inventory Exists

When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group (typically, oinstall), and the path of the Oracle Inventory directory.

If you have an existing Oracle Inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations.

If you do not have an existing Oracle Inventory, then you should create an Oracle Inventory group.

To determine whether you have an Oracle Inventory on your system:

On x86 or Itanium systems, enter the following command:

# more /etc/oraInst.loc

On IBM zSeries based systems, enter the following command:

# more /var/opt/oracle/oraInst.loc

If the oraInst.loc file exists, then the output from this command is similar to the following:

inventory_loc=/u01/app/oracle/oraInventory
inst_group=oinstall

In the previous output example:

• The inventory_loc group shows the location of the Oracle Inventory

• The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall).

Creating the Oracle Inventory Group If an Oracle Inventory Does Not Exist

If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering a command similar to the following:

# /usr/sbin/groupadd oinstall

2.4.2 Creating the OSDBA Group

You must create an OSDBA group in the following circumstances:

• An OSDBA group does not exist, for example, if this is the first installation of Oracle Database software on the system

• An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges for a new Oracle Database installation

If the OSDBA group does not exist or if you require a new OSDBA group, then create it as follows. In the following procedure, use the group name dba unless a group with that name already exists:

# /usr/sbin/groupadd dba

2.4.3 Creating an OSOPER Group (Optional)

Create an OSOPER group only if you want to identify a group of operating system users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, then you must create it in the following circumstances:

• If an OSOPER group does not exist; for example, if this is the first installation of Oracle Database software on the system

• If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation

If you require a new OSOPER group, then create it as follows. In the following, use the group name oper unless a group with that name already exists.

# /usr/sbin/groupadd oper

2.4.4 Creating the Oracle Software Owner User

You must create an Oracle software owner user in the following circumstances:

• If an Oracle software owner user does not exist; for example, if this is the first installation of Oracle software on the system

• If an Oracle software owner user exists, but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation

Determining if an Oracle Software Owner User Exists

To determine whether an Oracle software owner user named oracle exists, enter the following command:

# id oracle

If the oracle user exists, then the output from this command is similar to the following:

uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)

If the user exists, then determine whether you want to use the existing user, or create another oracle user. If you want to use the existing user, then ensure that the user's primary group is the Oracle Inventory group and that it is a member of the appropriate OSDBA and OSOPER groups. Refer to one of the following sections for more information:

• To modify an existing user, refer to the "Modifying an Existing Oracle Software Owner User" section.

• To create a user, refer to the following section.

Creating an Oracle Software Owner User

If the Oracle software owner user does not exist, or if you require a new Oracle software owner user, then create it as follows. In the following procedure, use the user name oracle unless a user with that name already exists.

1. To create the oracle user, enter a command similar to the following:

   # /usr/sbin/useradd -u 200 -g oinstall -G dba[,oper] oracle
   

   In the preceding command:

   • The -u option specifies the user ID. Using this command flag is optional, as you can allow the system to provide you with an automatically generated user ID number. However, you must make note of the oracle user ID number, as you require it later during pre-installation.

   • The -g option specifies the primary group, which must be the Oracle Inventory group--for example, oinstall

   • The -G option specifies the secondary groups, which must include the OSDBA group, and, if required, the OSOPER group. For example: dba, or dba,oper

2. Set the password of the oracle user:

   # passwd oracle
   

   Refer to the section "Verifying That the User nobody Exists".

Modifying an Existing Oracle Software Owner User

If the oracle user exists, but its primary group is not oinstall, or it is not a member of the appropriate OSDBA or OSOPER groups, then enter a command similar to the following to modify it. Specify the primary group using the -g option and any required secondary group using the -G option:

# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle

Repeat this procedure on all of the other nodes in the cluster.

2.4.5 Verifying That the User nobody Exists

Before installing the software, complete the following procedure to verify that the user nobody exists on the system:

1. To determine if the user exists, enter the following command:

   # id nobody
   

   If this command displays information about the nobody user, then you do not have to create that user.

2. If the nobody user does not exist, then enter the following command to create it:

   # /usr/sbin/useradd nobody
   

3. Repeat this procedure on all the other nodes in the cluster.

2.4.6 Creating Identical Users and Groups on Other Cluster Nodes

The Oracle software owner user and the Oracle Inventory, OSDBA, and OSOPER groups must exist and be identical on all cluster nodes. To create these identical users and groups, you must identify the user ID and group IDs assigned them on the node where you created them, then create the user and groups with the same name and ID on the other cluster nodes.

Identifying the User and Group IDs

To determine the user ID (UID) of the Oracle software owner user and the group IDs (GID) of the Oracle Inventory, OSDBA, and OSOPER groups, follow these steps:

1. Enter following command:

   # id oracle
   

   The output from this command is similar to the following:

   uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
   

2. From the output, identify the user ID (UID) for the oracle user and the group identities (GIDs) for the groups to which it belongs.

Creating the User and Groups on the Other Cluster Nodes

To create the user and groups on the other cluster nodes, repeat the following procedure on each node:

1. Log in to the next cluster node as root.

2. Enter commands similar to the following to create the oinstall and dba groups, and if required, the oper group. Use the -g option to specify the correct GID for each group.

   # /usr/sbin/groupadd -g 200 oinstall
   # /usr/sbin/groupadd -g 201 dba
   # /usr/sbin/groupadd -g 202 oper
   

   Note:

   If the group already exists, then use the groupmod command to modify it if necessary. If you cannot use the same group ID for a particular group on this node, then view the /etc/group file on all nodes to identify a group ID that is available on every node. You must then specify that ID for the group on all of the nodes.

3. To create the oracle user, enter a command similar to the following:

   # /usr/sbin/useradd -u 200 -g oinstall -G dba[,oper] oracle
   

   In the preceding command:

   • The -u option specifies the user ID, which must be the user ID that you identified in the previous subsection

   • The -g option specifies the primary group, which must be the Oracle Inventory group, for example oinstall

   • The -G option specifies the secondary groups, which must include the OSDBA group and if required, the OSOPER group. For example: dba or dba,oper

     Note:

     If the oracle user already exists, then use the usermod command to modify it if necessary. If you cannot use the same user ID for the oracle user on this node, then view the /etc/passwd file on all nodes to identify a user ID that is available on every node. You must then specify that ID for the user on all of the nodes.

4. Set the password of the oracle user:

   # passwd oracle
   

2.4.7 Configuring SSH on All Cluster Nodes

Before you install and use Oracle Real Application clusters, you must configure secure shell (SSH) for the oracle user on all cluster nodes. Oracle Universal Installer uses the ssh and scp commands during installation to run remote commands on and copy files to the other cluster nodes. You must configure SSH so that these commands do not prompt for a password.

$ pgrep sshd

$ man ssh

2.5.1 Installing the cvuqdisk Package for Linux

If you are using Red Hat or SUSE Linux, then you must download and install the operating system package cvuqdisk. Without cvuqdisk, CVU is unable to discover shared disks, and you receive the error message "Package cvuqdisk not installed" when you run CVU. Use the cvuqdisk rpm for your hardware (i386, or for Itanium, ia64).

To install the cvuqdisk RPM, complete the following procedure:

CV_RAW_CHECK_ENABLED=FALSE 

1. Locate the cvuqdisk RPM package, which is in the directory clusterware/rpm on the installation media. If you have already installed Oracle Clusterware, then it is located in the directory CRS_home/rpm.

2. Copy the cvuqdisk package to each node on the cluster. You should ensure that each node is running the same version of Linux.

3. Log in as root.

4. Using the following command, check to see if you have an existing version of the cvuqdisk package:

   # rpm -qi cvuqdisk
   

   If you have an existing version, then enter the following command to de-install the existing version:

   rpm -e cvuqdisk
   

5. Set the environment variable CVUQDISK_GRP to point to the group that will own cvuqdisk, typically oinstall.

6. Use the following command to install the cvuqdisk package:

   rpm -iv cvuqdisk-1.0.1-1.rpm
   

2.7.1 IP Address Requirements

Before starting the installation, you must have the following IP addresses available for each node:

• An IP address with an associated network name registered in the domain name service (DNS) for the public interface. If you do not have an available DNS, then record the network name and IP address in the system hosts file, /etc/hosts.

• One virtual IP (VIP) address with an associated network name registered in DNS. If you do not have an available DNS, then record the network name and VIP address in the system hosts file, /etc/hosts. Select an address for your VIP that meets the following requirements:

  • The IP address and network name are currently unused

  • The VIP is on the same subnet as your public interface

  Before installation, check that the default gateway can be accessed by a ping command. During installation, OUI uses the ping command to ensure that the VIP is reachable. To find the default gateway, use the route command, as described in your operating system's help utility. After installation, configure clients to use either the VIP address, or the network name associated with the VIP. If a node fails, then the node's virtual IP address fails over to another node.

• A private IP address with a host name for each private interface

  Oracle recommends that you use private network IP addresses for these interfaces (for example: 10.*.*.* or 192.168.*.*). Use the /etc/hosts file on each node to associate private network names with private IP addresses.

For example, with a two node cluster where each node has one public and one private interface, you might have the configuration shown in the following table for your network interfaces, where the hosts file is /etc/hosts:

To enable VIP failover, the configuration shown in the preceding table defines the public and VIP addresses of both nodes on the same subnet, 143.46.43. When a node or interconnect fails, then the associated VIP is relocated to the surviving instance, enabling fast notification of the failure to the clients connecting through that VIP. If the application and client are configured with transparent application failover options, then the client is reconnected to the surviving instance.

2.7.2 Node Time Requirements

Before starting the installation, ensure that each member node of the cluster is set as closely as possible to the same date and time. Oracle strongly recommends using the Network Time Protocol feature of most operating systems for this purpose, with all nodes using the same reference Network Time Protocol server.

2.7.3 Configuring the Network Requirements

To verify that each node meets the requirements, follow these steps:

1. If necessary, install the network adapters for the public and private networks and configure them with either public or private IP addresses.

2. Register the host names and IP addresses for the public network interfaces in DNS.

3. For each node, register one virtual host name and IP address in DNS.

4. For each private interface on every node, add a line similar to the following to the /etc/hosts file on all nodes, specifying the private IP address and associated private host name:

   10.0.0.1     rac1-priv1
   

5. To identify the interface name and associated IP address for every network adapter, enter the following command:

   # /sbin/ifconfig
   

   From the output, identify the interface name and IP address for all network adapters that you want to specify as public or private network interfaces.

   Note:

   When you install Oracle Clusterware and RAC, you will require this information.

6. To prevent network hangs with failovers from public to virtual IP addresses with RAC databases using NAS devices or NFS mounts, enter the following command as root to enable the Name Service Cache Daemon (nscd):

   # /sbin/service  nscd start
   

2.9.1 Software Requirements List for x86 (32-bit) Platforms

binutils-2.14
compat-db-4.0.14-5
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gcc-3.2
glibc-2.3.2-95.27
make-3.79
openmotif-2.2.3
setarch-1.3-1

binutils-2.15.92.0.2-10.EL4
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-9.EL4
gcc-c++-3.4.3-9.EL4
glibc-2.3.4-2
glibc-common-2.3.4-2
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.3-9.EL4
libstdc++-devel-3.4.3-9.EL4
make-3.80-5

gcc-3.3
gcc-c++-3.3.3-43
glibc-2.3.3-98.28
libaio-0.3.98-18
libaio-devel-0.3.98-18
make-3.80
openmotif-libs-2.2.2-519.1

ocfs-support
ocfs-tools
ocfs-kernel_version

http://oss.oracle.com/projects/ocfs/

http://oss.oracle.com/projects/ocfs2/

2.9.2 Software Requirements List for x86 (64-bit) Platforms

make-3.79.1-17
compat-db 4.0.14-5.1
control-center-2.2.0.1-13
gcc-3.2.3-47
gcc-c++-3.2.3-47
gdb-6.1post-1.20040607.52
glibc-2.3.2-95.30
glibc-common-2.3.2-95.30
glibc-devel-2.3.2-95.30
glibc-devel-2.3.2-95.20 (32 bit)
glibc-devel-2.3.4-2.13.i386 (32-bit)
compat-db-4.0.14-5
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gnome-libs-1.4.1.2.90-34.2 (32 bit)
libstdc++-3.2.3-47
libstdc++-devel-3.2.3-47
openmotif-2.2.3-3.RHEL3
sysstat-5.0.5-5.rhel3
setarch-1.3-1
libaio-0.3.96-3
libaio-devel-0.3.96-3

binutils-2.15.92.0.2-10.EL4
binutils-2.15.92.0.2-13.0.0.0.2.x86_64
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-9.EL4
gcc-c++-3.4.3-9.EL4
glibc-2.3.4-2
glibc-common-2.3.4-2
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.3-9.EL4
libstdc++-devel-3.4.3-9.EL4
make-3.80-5

binutils-2.15.90.0.1.1-32.5
gcc-3.3.3-43.24
gcc-c++-3.3.3-43.24
glibc-2.3.3-98.28
gnome-libs-1.4.1.7-671.1
libstdc++-3.3.3-43.24
libstdc++-devel-3.3.3-43.24
make-3.80-184.1

ocfs-support
ocfs-tools
ocfs-kernel_version

http://oss.oracle.com/projects/ocfs/

http://oss.oracle.com/projects/ocfs2/

2.9.3 Software Requirements List for Linux on Itanium

make-3.79.1-17
control-center-2.2.0.1-13
gcc-3.2.3-47
gcc-c++-3.2.3-47
gdb-6.1post-1.20040607.52
glibc-2.3.2-95.30
glibc-common-2.3.2-95.30
glibc-devel-2.3.2-95.30
glibc-devel-2.3.2-95.20 (32 bit)
glibc-devel-2.3.4-2.13.i386 (32-bit)
compat-db-4.0.14-5.1
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
gnome-libs-1.4.1.2.90-34.2 (32 bit)
libstdc++-3.2.3-47
libstdc++-devel-3.2.3-47
openmotif-2.2.3-3.RHEL3
sysstat-5.0.5-5.rhel3
setarch-1.3-1
libaio-0.3.96-3
libaio-devel-0.3.96-3

binutils-2.15.92.0.2-10.EL4
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-9.EL4
gcc-c++-3.4.3-9.EL4
glibc-2.3.4-2
glibc-common-2.3.4-2
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.3-9.EL4
libstdc++-devel-3.4.3-9.EL4
make-3.80-5

gcc-3.3.3
gcc-c++-3.3.3
glibc-2.3.3
libaio-0.3.102-1.2ia64
libaio-devel-0.3.102-1.2ia64
make-3.80

ocfs-support
ocfs-tools
ocfs-kernel_version

http://oss.oracle.com/projects/ocfs/

http://oss.oracle.com/projects/ocfs2/

oracleasm 2.4.21-27.EL-1.0.4-2.ia64.rpm

oracleasm 2.6.9-11.EL-2.0.0-1.ia64.rpm

http://oss.oracle.com/projects/oracleasm/

2.9.4 Software Requirements List for Linux on POWER

Gmake-3.80-5
gcc-3.4.3-22.1
gcc-ppc32-3.4.3-22.1
gcc-c++-3.4.3-22.1
gcc-c++-ppc32-3.4.3-22.1
glibc-2.3.4-2.9
glibc-2.3.4-29 (64-Bit)
libgcc-3.4.3-9.EL4
libgcc-3.4.3-9.EL4.ppc64.rp
libstdc++-3.4.3-9.EL4
libstdc++-devel-3.4.3-9.EL4
libaio-0.3.103-3
libaio-0.3.103-3 (64-Bit)
libaio-devel-0.3.103-3 (64-Bit)
compat-libstdc++-33-3.2.3-47.3
binutils-2.15.92.0.2-13

gcc-3.3.3-43.34
gcc-64bit-9-200505240008
gcc-c++-3.3.3-43.34
glibc-2.3.3-98.47
glibc-64bit-9-200506062240
libgcc-3.3.3-43.34
libgcc (64-bit) 9-200505240008
libstdc++-3.3.3-43.34
libstdc++-devel-3.3.3-43.34
libaio-0.3.102-1.2
libaio-64bit-9-200502241152
libaio-devel-0.3.102-1.2
libaio-devel-0.3.102-1.2 (64-bit)
Gmake-3.80-184.1
binutils-2.15.90.0.1.1-32.10
binutils-64bit-9-200505240008

2.9.5 Software Requirements list for IBM zSeries Based Linux

gcc-3.4.4-2
gcc-c++-3.4.4-2
libgcc-3.4.4-2
libstdc++-devel-3.4.4-2
compat-libgcc-295-2.95.3-81
compat-libstdc++-33-3.2.3-47.3
glibc-2.3.4-2.13
libaio-0.3.103-3
libaio-devel-0.3.103-3
libstdc++-devel 3.4.4-2

gcc-3.3.3-43.34
gcc-c++-3.3.3-43.34
glibc-2.3.3-98.47
glibc-2.3.3-98.28 (64-bit)
libgcc-3.3.3-43.34
libgcc (64 bit) unknown
libstdc++-3.3.3-43.34
libstdc++-devel-3.3.3-43.34
libaio-0.3.102-1.2
libaio-0.3.98-18.3 (64-bit)
libaio-devel-0.3.102-1.2
libaio-devel-0.3.98-18.3 (64-bit)
Gmake-3.80-184.1