Skip to end of metadata
Go to start of metadata
This topic describes how to set up Oracle media to prepare for provisioning.
This section details how to set up Oracle media for Linux and UNIX systems.
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.
- Place the Oracle media in the following location and format on the Agent:
Provisioning Oracle 10.2.0.2 and 10.2.0.3 also requires that the 10.2.0.1 media is present in this location (for example: /app/clarity/oracle_media/10.2.0.1_linux_x86_64).
- (For Oracle versions earlier than 12.2 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/18.104.22.168_linux_x86_64/database directory for Oracle 22.214.171.124 x86 64-bit for Linux media:
unzip -q /tmp/linuxamd64_12c_database_1of2.zip
unzip -q /tmp/linuxamd64_12c_database_2of2.zip
This directory is created with the following subdirectories:
The following table lists example Oracle media location paths by OS.
The Disk1 folder that is extracted from the Oracle media for HP-UX PA-RISC systems must be renamed to database when it is placed in the Oracle media path for 10.2.0.1. For example, /app/clarity/oracle_media/10.2.0.1_hp-ux_ia64/database.
This change is only required for version 10.2.0.1. Upgrade media does not need to be modified.
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.
rhdb2# cd /app/clarity
rhdb2# mkdir -p oracle_media/126.96.36.199_linux_x86_64
rhdb2# cd oracle_media/188.8.131.52_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 BMC Database Automation, rename the top-level extracted directory from
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
Back to top
Oracle for Windows media must be prepared using the BMC Database Automation Media Preparation Tool (mediaprep).
For provisioning activities on Windows, BMC Database Automation will push media from the Manager to the target Windows node(s).
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).
- From the command prompt, run mediaprep.exe.
- When prompted to prepare Microsoft SQL server media?, type n.
- When prompted to prepare Oracle media, type y.
- 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.
- To prepare the media for uploading to the Manager, press Enter.
- When prompted to copy files up to the Manager, type y and press Enter.
- When prompted for the host name or IP address of the Manager, type the IP address and press Enter.
- 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).
- When prompted to enter the root password of the Manager, type the password and press Enter.
Back to top
OPatch can be upgraded as part of a patch job. BMC Database Automation supports OPatch upgrades for both platform-specific and generic OPatch:
- Platform-specific OPatch files have the following format:
- Generic OPatch files have the following format:
Oracle 10gR2: opatch-10.2.zip
Oracle 11g: opatch-11.1.zip
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.
- Install the platform-specific OPatch file in an Oracle Home.
- Set the ORACLE_HOME environment variables.
- Run the following command as the user who owns the Oracle Home:
- Follow the prompts in the utility to generate the response file.
Back to top
To prepare and apply BMC Database Automation patch packages for Oracle quarterly packages, see Managing patch packages for Oracle quarterly packages.