Installing Oracle 10gR2 on SLES10 Linux on System z - July 10, 2007

Abstract

This Technote provides information that is necessary to complete the installation of Oracle 10.2.0.2 and 10.2.0.3 on SLES10. We assume that you are performing a new installation, and not updating a SLES9 and Oracle 10.2.0.2 database to SLES10 and Oracle 10.2.0.3.

Contents

Installing Oracle 10gR2 on SLES10 Linux on System z
As of June 2007, Oracle has certified 10.2.0.3 on SLES10. Table 1 is the entry on http://metalink.oracle.com showing the certification.
DRAFT - JULY 5 2007

Certify - Certification Matrix: Oracle Database - Enterprise Edition on IBM Linux on System z (31 and 64 bit)

Table 1: Server Certifications

OS
Product
Certified With
Version
Status
Addtl. Info.
Components
Other
Install Issue
SLES-9
10gR2 64-bit
N/A
N/A
Certified
None
None
None
SLES-10
10gR2 64-bit
N/A
N/A
Certified
None
None
None
Red Hat Enterprise AS/ES 4
10gR2 64-bit
N/A
N/A
Certified
None
None
None

Installing a single instance database
The steps for a new installation are as follows:
  1. Install SLES10. We recommend that you do an “install all“ to get all the components of SLES10 for your first test environment. If you choose to only install components, make sure that you include all the gcc components and compat libraries for 31 and 64 bit.
  2. Obtain the Oracle code and documentation.
    1. Download Oracle 10.2.0.2 for Linux on z from otn.oracle.com.
    2. Download the 10.2.0.2 Release notes and Installation Guide.
    3. Use this Redbooks publication as a guide: Experiences with Oracle® 10gR2 Solutions on Linux for IBM System z, SG24-7191.
    4. Download from metalink.oracle.com patch set 5337014 for 10.2.0.3 and the patch set notes. This patchset is found under the platform IBM zSeries Based Linux.
    5. Download from metalink.oracle.com patch 6007358 to allow 10.2.0.2 to install on SLES10. Today this patch is only found under the S390 Linux platform; it should be moved to the IBM zSeries Linux platform in July.

NOTE: The Patch set README file refers to the incorrect file name in 5.4 "Download and Extract the Installation Software". The correct name is "p5337014_10203_LINUX-zSer.zip", not "p5337014_10203_LINUX-S390.zip patch set". The same README file refers to the incorrect patch name in 10.13 - "10.2.0.2 Install on SUSE Linux Enterprise Server 10 (SLES10) fails Installing 10.2.0.2 on SUSE Linux Enterprise Server (SLES) 10 fails". The work-around for this is to install the 6017970 patch, which should read "install the 6007358 patch".

3. Run the OUI for 10.2.0.2 on SLES10 until you get the link error. Do not exit. Open a separate window to install the patch. Just leave the OUI running while you install patch 6007358 from another window. After installing the patch return to the OUI and click Retry.

The manual steps to follow to apply the one-off patch are:
1. Unzip the patch zip file into a temp directory, for instance to:
      /oracle1/shiphomes/p6007358
2. This creates an appropriate patch directory structure which has all the necessary files in it.
3. Copy the libraries to the appropriate directory under $ORACLE_HOME. For example:
      cp /oracle1/shiphomes/p6007358/6007358/files/lib/libclient10.a ORACLE_HOME/lib/libclient10.a
      cp /oracle1/shiphomes/p6007358/6007358/files/lib32/libclient10.a $ORACLE_HOME/lib32/libclient10.a
4. Click "Retry" on the error message box from OUI.

This allows completion of the 10.2.0.2 installation on SLES10, and then you can upgrade to 10.2.0.3 with patchset 5337014.

Installing Oracle RAC 10.2.0.3 on SLES10
We had several problems when we first installed RAC on SLES10. This Technote is intended to help you complete a successful installation. Oracle RAC database can be installed on:
  • Raw devices with ASM
  • Block devices with ASM
  • OCFS2

We had problems with the cluster verify utility and with running root.sh on the last node. We discuss work-arounds for these issues here.

Our CRS installation failed with two error messages. We ignored the first one and we used the work-around in the Metalink note (414163) to complete the CRS installation for the second.

Next, we installed the Oracle RAC code and then ran DBCA to create the RAC database. Problems 1 and 2, below, exemplify what we did.

Problem 1 - Cluster verify utility
If you encounter an error message, such as the one shown below, just continue the installation.
Checking peer compatibility...
No checks registered for peer comparison.

Verification of peer compatibility was unsuccessful on all the nodes.

Problem 2 – Root.sh script error with vipca
If you encounter an error message such as this:
CSS is active on all nodes.
Waiting for the Oracle CRSD and EVMD to start
Oracle CRS stack installed and running under init(1M)
Running vipca(silent) for configuring nodeapps
/oracle1/install/RAC/crs/jdk/jre//bin/java: error while loading shared libraries
: libpthread.so.0: cannot open shared object file: No such file or directory
pazxxt04:/oracle1/install/RAC/crs #

Then, follow the work-arounds in MetaLink note 414163.1 entitled 10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA Failures).

Redbooks

Experiences with Oracle 10g Database for Linux on zSeries, SG24-6482

Experiences with Oracle 10gR2 on Linux on System z, SG24-7191

For more information, contact ibmoracl@us.ibm.com

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Profile

Publish Date
20 July 2007


Rating: Not yet rated


Author(s)

IBM Form Number
TIPS0669