Setting up Oracle media

This topic describes how to set up Oracle media to prepare for provisioning.

Setting up Oracle media for Linux and UNIX

This section explains how to set up Oracle media for Linux and UNIX systems.

Before you begin

Ensure that Oracle specific environment parameters have been set properly.

Click here to view the Oracle specific environment prerequisites.
  • The Oracle home environment variable (ORACLE_HOME) must point to a valid Oracle home directory and match the value used during installation of the Oracle home directory.
  • JRE version 1.4 or later must be installed (Java commands for Windows, and ar, cp, fuser, and make commands for UNIX must also be available).
  • The LD_LIBRARY_PATH must be set correctly for Oracle Real Application Clusters environments. OPatch uses some APIs to detect if the system is a Real Application Clusters system.

To set up Oracle media for Linux and UNIX

  1. Download Oracle media files from the Oracle website.

    Notes

    • For Oracle version 18c and later, the media files to download are LINUX.X64_180000_db_home.zip and LINUX.X64_180000_examples.zip.
  2. Place the Oracle media in the following location and format on the BMC Database Automation (BDA) Agent:
    • (Oracle versions earlier than 12.2)
      /app/clarity/oracle_media/oracleVersionNumber_osType_architecture
    • (Oracle version 12.2)
      /app/clarity/oracle_media/oracleVersionNumber_osType_architecture/grid
    • (Oracle version 18c and later) Move the Oracle media .zip file without extracting, to the specified location: 
      • Use the following location for a single-instance installation:
         /app/clarity/oracle_media/oracleVersionNumber_osType_architecture
      • Use the following location for a grid installation:
        /app/clarity/oracle_media/oracleVersionNumber_osType_architecture/grid

  3. (Oracle versions earlier than 12.2.0.1 only) As the oinstall user, unzip the .zip files one at a time in order, which extracts them automatically into the corresponding media folder. 
    For example, the following commands populate the /app/clarity/oracle_media/12.1.0.1_linux_x86_64/database directory for Oracle 12.1.0.1 x86 64-bit for Linux media:

    cd /app/clarity/oracle_media/12.1.0.1_linux_x86_64
    unzip -q /tmp/linuxamd64_12c_database_1of2.zip
    unzip -q /tmp/linuxamd64_12c_database_2of2.zip    This directory is created with the following subdirectories:
    client
    database
    deinstall
    examples
    gateways
    grid

  4. (Oracle version 12.2 only)  Copy the 12201_grid_home.zip file to the following location: /app/clarity/oracle_media/oracleVersionNumber_osType_architecture/grid.
    For example, the /app/clarity/oracle_media/12.2.0.1_linux_x86_64/grid directory for Oracle 12.2 x86 64-bit for Linux media should contain the linuxx64_12201_grid_home.zip.

    For all other 12.2 zip files, unzip the .zip files one at a time in the 12.2 media location.
    For example, the following commands populate the /app/clarity/oracle_media/12.2.0.1_linux_x86_64/database directory for Oracle 12.2. x86 64-bit for Linux media:

    # cd /app/clarity/oracle_media/12.2.0.1_linux_x86_64/database
    # unzip -q /tmp/linuxx64_12201_database.zip

    This directory is created with the following subdirectories:
    client
    database
    deinstall
    examples
    gateways
    grid

The following table lists example Oracle media location paths by OS.


Tip

Instead of using the pre-defined location for installer directories on of your agent node hosts, use sym-links to take advantage of NFS partitions or partitions that have the available space.

For example:

rhdb2# cd /app/clarity
rhdb2# mkdir -p oracle_media/12.1.0.1_linux_x86_64
rhdb2# cd oracle_media/12.1.0.1_linux_x86_64
rhdb2# ln -s /local/oraclesys/oradata/database-installer-12.1 database

In this example, temporary disk space was available under /local/oraclesys/oradata, so the installation files were extracted into that directory. Before using BDA, rename the top-level extracted directory from database to database-installer-12.1, to make it distinctive. (Regardless of platform and version, Oracle's database installation distribution files extract to the generic top-level directory database.) Then, create a final sym link with the database (named with the Oracle version and platform) in the oracle_media subdirectory.

Setting up Oracle media for Windows

For Oracle versions earlier than 18c, Oracle media for Microsoft Windows must be prepared using the BDA Media Preparation Tool (mediaprep).

Note

For provisioning activities on Windows, BDA will push media from the Manager to the target Windows node or nodes.

Before you begin

  • Download the mediaprep utility from the Additional Utilities folder from the BMC Electronic Product Distribution (EPD) site. For more information, see Downloading-the-installation-files.
  • If your installation media consists of multiple disks, run mediaprep for each disk and then upload all of the files generated.
  • After the media is prepared, it must be copied to the Manager. If you do not have the root password of the Manager, mediaprep enables you to save the prepared media files locally on your workstation, so that someone with root access can copy the files to /app/clarity/var/media (for Multi-Manager environments, you must upload prepared media to each Satellite Manager).

To prepare Oracle media for Windows using mediaprep (Oracle versions earlier than 18c)

  1. From the command prompt, run mediaprep.exe.
  2. When prompted Do you want to prepare Microsoft SQL Server media? [y]: type n and press Enter.
  3. When prompted type y and press Enter.Do you want to prepare Oracle media? [y]:
  4. When prompted for the path to your Oracle media, enter the path (such as the CD-ROM drive) and press Enter.
    If your media resides on a network share, map the share to a drive letter and specify the drive letter and location. Mediaprep does not accept network locations as a path to the media.
    The tool searches the media for versions of Oracle and reports what it found.
  5. To prepare the media for uploading to the Manager, press Enter.
  6. When prompted to copy files up to the Manager, type y and press Enter.
  7. When prompted for the host name or IP address of the Manager, type the IP address and press Enter.
  8. When prompted to use SSL version 1, type y and press Enter.
    If n is entered, SSL version 2 is used. (Version 1 is faster but less secure than version 2).
  9. When prompted to enter the root password of the Manager, type the password and press Enter.

To prepare Oracle media for Windows (Oracle version 18c and later)

Use the following procedure to prepare media for a single-instance installation.

  1. Download the Oracle media files to the BDA Manager.

    Oracle version

    File name

    18c and later

    WINDOWS.X64_180000_db_home.zip

    WINDOWS.X64_180000_examples.zip

  2. Go to /app/clarity/var/media on the BDA Manager.

  3. Create a softlink for the downloaded media files as shown:

    For Oracle version 18c and later
    [root@rh7-ma-000 media]# ll oracle_18.0.0.0_windows_x64_database.zip oracle_18.0.0.0_windows_x64_examples.zip
    lrwxrwxrwx 1 root root 64 Feb  4 03:22 oracle_18.0.0.0_windows_x64_database.zip -> /mnt/media/oracle/18.0.0.0_win_64/WINDOWS.X64_180000_db_home.zip
    lrwxrwxrwx 1 root root 65 Feb  4 03:22 oracle_18.0.0.0_windows_x64_examples.zip -> /mnt/media/oracle/18.0.0.0_win_64/WINDOWS.X64_180000_examples.zip
    [root@rh7-ma-000 media]#

Tip

Alternatively, download the media for Oracle version 18c and later to /app/clarity/var/media and rename the files as follows:

  • For Oracle version 18c and later
    • mv WINDOWS.X64_180000_db_home.zip oracle_18.0.0.0_windows_x64_database.zip
    • mv WINDOWS.X64_180000_examples.zip oracle_18.0.0.0_windows_x64_examples.zip

Setting up OPatch media and response file

OPatch can be upgraded as part of a patch job. BDA supports OPatch upgrades for both platform-specific and generic OPatch:

  • Platform-specific OPatch files have the following format:
    p6880880_     oracle_version_platform-architecture .zip
  • Generic OPatch files have the following format:
    Oracle 10gR2: opatch-10.2.zip
    Oracle 11g: opatch-11.1.zip

Note

The file name format for platform-specific OPatch files is the same as the file name of the OPatch file downloaded from MetaLink. 6880880 is the MetaLink placeholder patch id for the latest OPatch.

OPatch media and a platform-specific response file (ocm.rsp) must be located in the /app/clarity/oracle_media directory on the Manager.

Click here to view the Oracle supported procedure for generating a response file.
  1. Install the platform-specific OPatch file in an Oracle Home.
  2. Set the ORACLE_HOME environment variables.
  3. Run the following command as the user who owns the Oracle Home:
    $ORACLE_HOME/OPatch/ocm/bin/emocmrsp
  4. Follow the prompts in the utility to generate the response file.
Example

Oracle media directory on the Manager:

[root@suprh5x64dbavm01 oracle_media]# ls 
ocm.rsp
p6880880_112000_AIX64-5L.zip
p6880880_112000_Linux-x86-64.zip
p6880880_112000_MSWIN-x86-64.zip
p6880880_112000_SOLARIS64.zip
p6880880_121010_AIX64-5L.zip
p6880880_121010_Linux-x86-64.zip
p6880880_121010_SOLARIS64.zip

Where to go from here

To prepare and apply BDA patch packages for Oracle quarterly packages, see Managing-patch-packages-for-Oracle-quarterly-packages.

Related topic

Loading-database-media

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*