This section details how to set up Oracle media for Linux and UNIX systems.
Ensure that Oracle-specific environment parameters have been set properly.
/app/clarity/oracle_media/oracle_version_number_os_type_architecture
Note
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).
/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:Example
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
The following table lists example Oracle media location paths by OS.
OS | Path example |
---|---|
Linux | /app/clarity/oracle_media/12.1.0.1_linux_x86_64 |
HP-UX | /app/clarity/oracle_media/10.2.0.1_hp-ux_ia64 |
Solaris | /app/clarity/oracle_media/10.2.0.1_sunos_sparc |
AIX | /app/clarity/oracle_media/10.2.0.1_aix_powerpc |
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.
Note
This change is only required for version 10.2.0.1. Upgrade media does not need to be modified.
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 BMC Database Automation, 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.
Oracle for Windows media must be prepared using the BMC Database Automation Media Preparation Tool (mediaprep).
Note
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).
OPatch can be upgraded as part of a patch job. BMC Database Automation supports OPatch upgrades for both platform-specific and generic OPatch:
Note
OPatch media and a platform-specific response file (ocm.rsp) must be located in the /app/clarity/oracle_media directory on the Manager.
To prepare and apply BMC Database Automation patch packages for Oracle quarterly packages, see Managing patch packages for Oracle quarterly packages.