Oracle® Database Installation Guide
10g Release 1 (10.1) for IBM z/OS (OS/390)
Part No. B13525-01
100 MB of disk space in the
1.4 GB to 2.5 GB of disk space for the Oracle software, depending on the installation type
2.6 GB of temporary disk space for a temporary work area, including the disk space required for the PAX files that are copied from the product CD-ROM and their expanded contents. The PAX files and expanded installation files can be located in different file systems.
1000 cylinders (860 MB) of PDS disk space, including 300 cylinders (244 MB) for the AUTHLOAD library (only 10 cylinders are needed for client-only installations and only 80 cylinders are needed for gateway installations), 450 cylinders (365 MB) for the CMDLOAD library (only 10 cylinders are needed for gateway installations), and 125 cylinders (102 MB) for the MESG PDS. The remaining data sets are less than 5 cylinders (10 MB) each.
Your z/OS system may not have the required disk space already available as an HFS or z/FS file system. In this case, you will need to ask your system administrator to allocate the space. Oracle recommends that you install Oracle software in its own separate zFS file system.
You can use the following command in a z/OS UNIX Systems Services shell to list the file systems which have space available:
$ df -k
The installation itself requires a maximum of 60 MB of temporary disk space for extracting the files. Normally the installer will use the
/tmp directory. If there is not enough space in /tmp then ask your system administrator to increase the size of
/tmp or set the TMP and TMPDIR environment variables, as described.
|Installation Type||Temporary zFS Space||Permanent zFS Space||Permanent Data Set Space|
|Oracle Database 10g for z/OS installations||2.6 GB||2.5 GB||860 MB|
|Oracle Database 10g for z/OS Client installations||2.6 GB||1.4 GB||650 MB|
|Transparent Gateway for DB2 or Transparent Gateway for iWay||2.6 GB||650 MB||180 MB|
Depending on the products that you intend to install, verify that the required software is installed on the system, as listed and described in the following table:
|Installation Type or Product||Requirement|
|Operating System||z/OS V1.4 or z/OSe V1.4 or above
Note: Required for all installations.
|Java||IBMJava2-141 (java version "1.4.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM z/OS Persistent Reusable VM build cm141-20030930 (JIT enabled: jitc))
(Up to the latest maintenance levels.)
Note: Required for all installations.
|IBM REXX||Required for all installations|
|CICS TS||V1.3 or higher is required for Oracle Access Manager for CICS TS|
|IMS TM||V7 or higher is required for Oracle Access Manager for IMS TM|
|z/OS UNIX System Services||X windows libraries
Note: Required for all interactive installations.
|TCP/IP||Required for all installations.|
|IBM C/C++||IBM C/C++ V1R2 or higher is required for Pro*C and OCI applications|
|COBOL compiler||Any currently supported IBM COBOL compiler that uses the LE runtime environment is required for Pro*COBOL applications|
|PL/I compiler||Any currently supported IBM PL/I compiler that uses the LE runtime environment is required for PRO*PL/I applications|
|DB2||IBM DB2 version 6.1 or higher is required for Oracle Transparent Gateway for DB2 installations|
|iWay||iWay Server version 5.2.3 or higher is required for Oracle Transparent Gateway for iWay installations|
To ensure that the system meets the software requirements, perform the following steps:
To determine which version of z/OS is installed, use the following command:
$ uname -a
The operating system version should appear as follows, where
systemname is the name of the system and
nnnn is the hardware model:
OS/390 systemname 14.00 03 nnnn
To determine whether Java 1.4.1 is installed in the default PATH, enter the following command:
$ java -version
The Java version should appear as follows:
IBMJava2-141 (java version "1.4.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1) Classic VM (build 1.4.1, J2RE 1.4.1 IBM z/OS Persistent Reusable VM build cm141-20030930 (JIT enabled: jitc))
Java executable is not found, or if the version displayed is less than 1.4.1, download Java 1.4.1 from the IBM Java Web site and install it:
Note that you can install IBM Java with or without SMP/E.
To determine whether the IBM
make program is installed and in the path, enter the following command:
$ make -V
make is located in the
/bin directory. You may need to copy the file
/etc/startup.mk in order for
make to function correctly. If
make is not installed and in the path, you will get an error message.
The following are required for both server and client-only installations:
The following are required for server installations only:
Some activities that are related to installing Oracle Database 10g for z/OS can be performed independently, even before the software arrives. All of these activities are related to product security features, and one (which is optional) requires an IPL of your system before it takes effect. Depending on the organization and procedures of your installation, you may need to work with system security personnel or systems programmers to perform these activities.The descriptions that are presented here are provided in RACF (IBM z/OS Security Server) terms with the assumption that RACF is in use. Any product which fully implements z/OS System Authorization Facility (SAF) can be substituted. If your installation uses a product other than RACF, refer to the documentation for that product for information on how to perform the steps that are discussed in this chapter.
Determine the virtual region size for the user performing the installation. If it is less than the required size, you must increase the maximum allowable size of the virtual region to 512 MB. The method by which you determine the virtual region size depends on whether you entered the z/OS UNIX System Services shell environment through Telnet or rlogin or through TSO OMVS:
If you entered the z/OS UNIX System Services shell environment through Telnet or rlogin, the virtual storage is the amount set in the SYS1.PARMLIB(BPXPRMxx) field MAXASSIZE. This amount can be limited in the OMVS segment of your RACF profile.
For example, if you do not define ASSIZEMAX in your RACF OMVS segment, and you have MAXASSIZE set to 2147483647, all Telnet or rlogin sessions will get 2 GB of virtual storage.
If you entered the z/OS UNIX System Services shell environment through TSO OMVS, then the virtual storage is the region size that you set for the REGION field when you logged on to TSO. This value is in KB. This amount can be limited in the TSO segment of your RACF profile.
You will need to ask your system administrator to issue the following command, which shows the maximum allowed value:
$ tso listuser username tso
tso listuser arogers tsoUSER=AROGERS NAME=ANDREW ROGERS OWNER=RACF CREATED=96.106DEFAULT-GROUP=OEG647 PASSDATE=03.356 PASS-INTERVAL= 92...TSO INFORMATION--------------- ACCTNUM= NOACCTPROC= $AROGERSSIZE= 02048000MAXSIZE= 02048000USERDATA= 0000
This shows that you can have up to 2 GB of virtual storage.
You should be aware that the SMF exit IEFUSI can limit virtual storage in either of the previous cases. Therefore, ensure that the SMF exit IEFUSI allows for enough virtual storage to use Oracle products.
Oracle Database 10g for z/OS requires the database and network region programs to run with APF authorization, which means that the load modules must reside in an APF-authorized library. While it is possible to copy these modules into an existing authorized library, Oracle recommends that you create an authorized library specifically for Oracle Database 10g for z/OS. Because z/OS requires all modules that are loaded by an authorized program to come from authorized libraries, the library will contain a number of modules in addition to the database and network region programs, including the Oracle database kernel. The authorized library must be a PDSE type rather than a PDS type.
A load library can be authorized in either of two ways: one way is to add an entry for the data set to the PROG
xx member of SYS1.PARMLIB, the other way is to add an entry for the data set to the IEAAPFxx member of SYS1.PARMLIB. The first way (using the PROG
xx member) utilizes a newer mechanism. The second way (using the IEAAPF
xx member) utilizes an older mechanism. You may need to talk to your systems programmer to determine which method to use and the correct suffix to substitute for
xx. If you plan to name the authorized library ORACLE.V10G.AUTHLOAD, for example, then the following code shows a suitable entry in PROG
APF ADD DSNAME(ORACLE.V10G.AUTHLOAD) SMS
If your installation is using IEAAPF
xx instead of PROG
xx, a comparable entry there would be:
The comma in the above entry is included only if the entry is not the last record in the member. Omit the comma in the new entry if it is last in the member, and make sure that the preceding entry has a comma.
Changes to PROG
xx or IEAAPF
xx do not take effect until the next IPL. If your installation has enabled z/OS dynamic APF facilities, a library can be authorized without an IPL by using a SETPROG APF,ADD operator command as shown in the following example:
The authorization that is conferred by the SETPROG command is independent of the PROG
xx or IEAAPF
xx members and lasts only until the next IPL. This means that you would use this technique only if you expect to install the software and actually configure and run a database service or network service before the next IPL of your system.
Regardless of the technique used, a data set does not need to exist to be authorized. The Installer will prompt you for the location of the data set and can optionally allocate it for you. If you can choose the data set name that you will use, then this step can be performed before the data set is created and populated. However, once you create a data set, you will need to authorize it.
Oracle Database 10g for z/OS instances can be composed of multiple address spaces and can make extensive use of z/OS Cross Memory Services. When a cross-memory address space is terminated, the address space ID (ASID) that was used for this address space is made unavailable. Eventually, the pool of z/OS ASIDs can become exhausted, which prevents new address spaces from being created. In order to avoid the above condition, the RSVNONR parameter in the IEASYS
xx member of SYS1.PARMLIB should be set to a higher value. Refer to the z/OS V1R4.0 MVS Initialization and Tuning Reference (SA22-7592), for details on specifying the RSVNONR parameter.
The database and network service region programs must run nonswappable and noncancelable, and should not be subject to system time limits. In addition, the database service runs in protect key 7. These attributes are indicated by adding entries for these programs to the z/OS Program Properties Table (PPT), via a member of the SYS1.PARMLIB data set named SCHED
xx is a 2-letter or 2-digit suffix. You may need to work with your systems programmer to determine the correct member name and to add the entries. The entries that you add should be similar to those in the following example. The comments, which are included for clarity, are allowed but are not required.
/* SCHEDxx PPT entry for Oracle database region */PPT PGMNAME(ORARASC) /* Program (module) name */ NOCANCEL /* Not cancelable */ KEY(7) /* Protection key */ NOSWAP /* Not swappable */ SYST /* Not subject to timing */ /* SCHEDxx PPT entry for Oracle network region */PPT PGMNAME(MINMAIN) /* Program (module) name */ NOCANCEL /* Not cancelable */ NOSWAP /* Not swappable */ SYST /* Not subject to timing */
The entries in the SCHED
xx member are normally read at z/OS IPL. You can cause z/OS to re-read the member without an IPL by using the SET SCH operator command. The PPT entries must take effect before Oracle database and network services are started.
For details on the SCHED
xx member, the PPT, and the SET SCH command, refer to the following IBM documents: z/OS V1R4.0 MVS Initialization and Tuning Reference (SA22-7592-06) and z/OS V1R4.0 MVS System Commands (SA22-7627-07).
The authorization-checking mechanism of SAF is based on resource names, which are simply character strings that identify the data, interface, or other entity that is protected. Resource names are organized into classes. A resource class is a name for a group of resources with similar name structure and attributes. RACF has a number of predefined resource classes for items such as data sets, tape volumes, and terminals.
Oracle Database 10g for z/OS has three types of resources that are subject to authorization checking:
The client-service bind interface
The database server SYSOPER/SYSDBA connection privilege
These resources must have an associated resource class. By default, Oracle Database 10g for z/OS is set up with the assumption that the resources are in the FACILITY class, which is a predefined RACF class. FACILITY is a general-use class whose resource name structure accommodates all three of the resource types of Oracle Database 10g for z/OS. If you use the default FACILITY class, then you may need to activate the class if your installation has not previously defined resources in the class. For directions on activating the FACILITY class, refer to the IBM document z/OS V1R4.0 Security Server RACF Security Administrator's Guide (SA-7683-03). This is done with a SETROPTS CLASSACT RACF command and does not require a z/OS IPL. For a description of this command, refer to the IBM document z/OS V1R4.0 Security Server RACF Command Language Reference (SA22-7687-03).
The security standards or procedures of your installation may make it preferable to create distinct resource classes for Oracle Database 10g for z/OS resources. RACF allows security administration privileges to be granted on a resource class basis. If you create distinct classes for Oracle Database 10g for z/OS, those RACF administration privileges can be granted to users without enabling administrative privileges on other (non-Oracle Database 10g for z/OS) resources that may be associated with the FACILITY class.
If you decide to create resource classes for Oracle Database 10g for z/OS, then two classes should be created: one for OSDI commands and one that is shared by both bind and database SYSOPER/SYSDBA connect authorizations. For information on adding installation-defined resource classes, refer to the following IBM documents: z/OS V1R4.0 Security Server RACF System Programmer's Guide (SA22-7681-03) and z/OS V1R4.0 Security Server RACF Macros and Interfaces (SA22-7682-03). The procedure involves coding Assembler Language macro instructions that are assembled to create non-executable load modules that are the class table and router table, and an IPL of z/OS is required to activate the change.
Note:This is the only pre-installation activity that requires an IPL.
If you choose to add new resource classes for Oracle Database 10g for z/OS, then the ICHERCDE macro that you code for the class table entries should specify parameters as in the following example, which defines the classes $ORACMD and $ORACONN.
$ORACMD ICHERCDE CLASS=$ORACMD, GROUP=$ORACONN, ID=192, Some number between 128 & 255 MAXLNTH=19, RACLIST=ALLOWED, FIRST=ALPHANUM, OTHER=ANY, POSIT=42, Probably unique to this class OPER=NO, DFTUACC=NONE $ORACONN ICHERCDE CLASS=$ORACONN, MEMBER=$ORACMD, ID=191, Some number between 128 & 255 MAXLNTH=19, FIRST=ALPHANUM, OTHER=ANY, POSIT=42, Probably unique to this class OPER=NO, DFTUACC=NONE
Note:In this example, the continuation indicators that are required in position 72 of each continued record are omitted.
You must also add entries to the installation-supplied router table module ICHRFR01, as in the following example:
ICHRFRTB CLASS=$ORACMD,ACTION=RACF ICHRFRTB CLASS=$ORACONN,ACTION=RACF
After the class table is updated and the system is IPLed, the new classes can be activated with the SETROPTS CLASSACT command. For more information, refer to the IBM document z/OS V1R4.0 Security Server RACF Security Administrator's Guide (SA-7683-03) and the RACF CLR. You must also provide Oracle Database 10g for z/OS with the class names. This is done in the subsystem parameter file discussed in the Oracle Database System Administration Guide for IBM z/OS.
Oracle Database 10g for z/OS-managed services execute as system address spaces, similar to started tasks or STCs. Some of the z/OS system functions that are invoked by Oracle Database 10g for z/OS services perform authorization checks based on the z/OS userid that is associated with the service address space. Depending on the security configuration and standards of your installation, those system functions may fail if no userid is associated with the address space. You, or security personnel for your installation, may need to take steps to ensure that Oracle Database 10g for z/OS services have an associated userid that can be authorized for system functions that are invoked by the database and network services.
If you are already running the TNS programs of previous releases as started tasks (as opposed to submitting them as batch jobs), then your installation probably already has STARTED or USER profiles for the associated JCL procedures. You should not rely on those for Oracle Database 10g for z/OS because the Oracle Database 10g for z/OS procedures should have different names. Plan to create at least two new STARTED or USER profiles, one for the database service and one for the network service. These may be all that you need, because different instances of a type of service can generally share the same JCL procedure. You may want to create additional profiles, though, if you want different instances of a service to run with different userids. Note that this requires using distinct JCL procedures even though the procedures themselves may be otherwise identical.
For details on the STARTED and USER resource classes, refer to the IBM document RACF Security Administrator's Guide. The RDEFINE command that is used to add profiles is described in the RACF CLR.
With RACF, it is also possible to associate a userid with a started task using a started procedures table that is built with Assembler macros somewhat like the resource class table discussed in the previous section. Activating such changes requires an IPL, however, and is not the preferred method. Refer to the IBM document RACF Security Administrator's Guide for more information.
Certain database features are implemented using z/OS UNIX System Services (formerly called Open Edition). These features including Java, XML, Oracle Text, Spatial Data Option, UTL_FILE package, and external LOB(BFILE) support. In order for these features to work, the database service address space must be capable of being "dubbed" as a z/OS UNIX System Services process. This requires that the z/OS userid that is associated with the address space have a default z/OS UNIX System Services segment that is defined to the security subsystem. For additional information, refer to the Oracle Database System Administration Guide for IBM z/OS.
In addition, certain utilities run only in a z/OS UNIX System Services shell environment, such as the Installer, Enterprise Manager, and some client-side Java applications. For users requiring these applications, an OMVS RACF segment must be defined. The OMVS RACF segment can be defined to a group and then the users who are likely to require these Oracle Java applications can be associated with the group. Such users are typically Oracle DBAs and Oracle operators.
Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create several groups and users who will be responsible for the installation, maintenance and operation of the oracle database.
Installation User/Group Considerations
The Installer requires that all users performing Oracle software installation and maintenance belong to the same group. Oracle recommends that you define a user group for all users performing installation and maintenance. The user who performs the installation becomes the owner of the files created as part of the installation. You may want to define a z/OS user who will be the software owner. Any user performing an Oracle installation must have an OMVS RACF segment defined. This user must be able to create and update the Oracle PDS/PDSE data sets.For maintenance, only the software owner is granted write access to the archive libraries. You may need to change the permissions for the archive libraries to allow anyone in the group write access after the installation has completed.
Determine Whether the Oracle Inventory Group Exists
When you install Oracle software on the system for the first time, the Installer creates the
oraInst.loc file. This file is located in the /var/opt/oracle directory. Alternatively, this directory can contain a pointer to a different inventory location.
Users who are performing installation and maintenance tasks must have RACF authority to create and update the directory
/var/opt/oracle and its contents, as well as the Oracle file systems created by the installation and the PDS data sets required for the installation.
This file identifies the name of the Oracle Inventory group. To determine whether the Oracle Inventory group exists, enter the following command:
$ more /var/opt/oracle/oraInst.loc
oraInst.loc file exists, the output from this command is similar to the following:
inst_group parameter shows the name of the Oracle Inventory group.
The Oracle software is installed in different types of file systems on z/OS. These file systems are: z/OS UNIX System Services for the Oracle executable code, samples, and maintenance structure; PDSE data sets for the Oracle executable code required for the Oracle Database server and TSO / batch clients.
Subsequent sections in this chapter describe how to configure the system depending on the location you choose for the software.
You must identify or create three directories for all Oracle installations, as follows:
Oracle base directory
Oracle inventory directory
Oracle home directory
Oracle Base Directory
The Oracle base directory acts as a top-level directory for Oracle software installations. Generally, you will need to allocate a zFS file system for the Oracle installation files. Oracle recommends that you allocate a high-level directory (for example,
/oracle) as the root directory for the installation, which can be fairly small. Allocate another file system under this directory for each product being installed, (for example,
/oracle/v10.1.0.2). This corresponds to the Oracle home directory.
Oracle Inventory Directory
The Oracle inventory directory (
oraInventory) stores an inventory of all software installed on the system. It is required by, and shared by, all Oracle software installations on a single system. The inventory should be placed in a location which is Oracle-version independent, as multiple versions of Oracle Database will use this inventory. The first time you install Oracle software on a system, the Installer prompts you to specify the path to this directory. Oracle recommends that you choose the following path:
This inventory directory needs to be 20-40 MB, as it holds the installation logs and parameter files. If you do not allocate a separate file system for this directory, then the space used is taken from the
If this directory does not exist, then the Installer will try to interactively create it at installation time. The
/var/opt/oracle directory points to this inventory directory.
Oracle Home Directory
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run the Installer, it prompts you to specify the path to this directory, as well as a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you define this directory as a separate zFS file system mounted under the
/oracle directory. In addition, you should specify a path similar to the following for the Oracle home directory:
Each new release of an Oracle product typically requires a separate Oracle home directory. Oracle recommends that you keep your Oracle home to less than 50 characters. This is because the path is placed in the sample JCL and has a line length of 80.
Oracle PDS and PDSE Data Sets
During installation, a number of files are placed into PDS and PDSE data sets. The Installer can create these data sets if the user performing the installation has RACF authority to create them, or it can use pre-existing data sets under a high-level qualifier supplied at installation. The Installer requires that all Oracle installation and executable files are kept under one high-level qualifier. The required sizes for these data sets are provided in Appendix B, "Installation Reference".
You need to determine a naming convention for high-level and second-level data set name qualifiers. For more information, refer to Appendix B, "Installation Reference". In addition, you need to determine a convention for naming Oracle software data files and database data files. For example, try to use a naming convention for the Oracle executable modules in data sets which includes the version. For example, ORACLE.V10G or ORACLE.V10102.
Database files should not include the version number. This is because the database is likely to exist across multiple versions or patch sets of the Oracle software.
There are two separate environments required for an interactive installation of the Oracle software: the client X server environment and the z/OS user environment. Both need to be configured before starting the installation.
This environment is required for an interactive installation. It is a non-z/OS environment and will normally be a UNIX system running X windows or a PC or other system with X windows software installed.
Note:Unless you intend to complete a silent installation, you must install the software from an X windows workstation, an X terminal, or a PC or other system with X server software installed. For more information on non-interactive and silent installations, see Appendix A.
If you are installing the software from an X windows workstation, X terminal, or PC running an X server application, you need to enable this X server to accept X client (z/OS) applications. To do this, perform the following steps:
Start a local terminal session, for example, an X terminal (
To enable remote hosts to display X windows applications on the local X server, enter the following command:
$ xhost +
The z/OS user environment is required for an interactive or non-interactive installation. It is a z/OS UNIX System Services shell environment running under the user who will be performing the installation. You must Telnet to this z/OS UNIX System Services shell environment using a VT terminal, or you can use the command OMVS from a TSO user who is logged on to the system, as described in the following steps:
On the z/OS (X client) system, connect to z/OS UNIX System Services using Telnet. Enter a command similar to the following, using the port number for z/OS UNIX System Services:
$ telnet remote_host port
If you are using a 3270 terminal emulator, you need to enter the OMVS shell command to access z/OS UNIX System Services.
If you are not logged on to the remote system as an authorized user, enter the following commands at the prompts:
EZYTE27I logon: username EZYTE27I logon username Password: password
Before you start the Installer you must configure the environment of the user performing the installation. To configure this environment, you must perform the following tasks:
Set the default file mode creation mask (umask) to 002 in the shell startup file.
Set the JAVA_HOME, PATH, LIBPATH, CLASSPATH and DISPLAY environment variables.
To set the
user's environment, follow these steps:
In any text editor, create an environment file similar to the following, specifying the appropriate values for the environment variables:
export JAVA_HOME=/usr/lpp/java/J1.4 export PATH=/bin:/usr/local/bin export LIBPATH=$JAVA_HOME/lib:$LIBPATH export CLASSPATH=$JAVA_HOME/lib/libjitc.so:$CLASSPATH export DISPLAY=nn.nn.nn.nn:0
The PATH environment variable must include Java,
ORACLE_HOME/bin. The JAVA_HOME environment variable must point to the Java home directory, and the LIBPATH environment variable must point to the
If necessary, specify in the environment file the environment variables listed in the following table. If you must specify several values for an environment variable, for example PATH, separate the values with a colon (:).
|Environment Variable||Required By||Sample Setting and Description|
|JAVA_HOME||The Installer must point to the Java installation location (directory or directories containing the Java executables)||
|PATH||All applications running in the z/OS UNIX System Services shell environment||
Note: On most systems, the
|LIBPATH||Path for library files||This should concatenate
|CLASSPATH||Path for class files||This should concatenate
|DISPLAY||Interactive installation||This is the TCP/IP address of the X server (the UNIX system or PC) where you want the installation panels to appear. It is in the form of a TCP/IP address followed by :
user's shell startup file in any text editor:
$ vi .profile
Enter or edit the following line, specifying a value of 022 for the default file creation mask:
Save the file and exit from the editor.
To run both the shell startup script and the environment script, enter commands similar to the following:
$ . ./.profile
To verify that the environment has been set correctly, enter the following commands:
$ umask $ env | more
Verify that the
umask command displays a value of
0022 and the environment variables that you set in this section have the correct values.
For interactive installations, enter a command similar to the following to direct X applications to display on your X server system:
local_host:0.0 ; export DISPLAY
In this example,
local_host is the host name or IP address of the system you want to use to display the Installer (your workstation or PC).
If you determined that the
/tmp directory has less than 100 MB of free disk space, identify or create a file system with at least 100 MB of free space and set the TMP and TMPDIR environment variables to specify a temporary directory on this file system.
Enter commands similar to the following to set the TEMP and TMPDIR environment variables:
$ TMP=/mount_point/tmp $ TMPDIR=/mount_point/tmp $ export TMP TMPDIR
The Oracle Database 10g for z/OS software is available on the Oracle Database 10g for z/OS product CD-ROMs or you can download it from the Oracle Technology Network Web site (OTN). Before you can install the software, you must first transfer the installation archive files to your z/OS system using one of the following two methods:
z/OS does not have direct CD-ROM support. Therefore, the software must be copied to a temporary location on the system before you can install it. In order to simplify this process, the installation directories have been compressed using PAX.
Each product CD-ROM contains an installation archive file labeled
Disk2.pax. Approximately 900 MB of temporary disk space is required for the contents of the two archive files.
To load the installation archive files from the product CD-ROMs, perform the following steps:
Mount the first product CD-ROM on a system which has a CD-ROM drive and has either FTP or NFS access to the z/OS system where you will be installing the software. If you NFS-mount the CD-ROM, then it needs to be mounted in binary mode. Ask your system administrator for the mount instructions specific to your system.
FTP the installation archive files in binary mode to a temporary location on the z/OS system. Ask your system administrator for the FTP instructions specific to your system.
Repeat the previous steps for each product CD-ROM. When the installation archive files
Disk2.pax are on your z/OS system, you no longer need the CD-ROMs.
The next step is to extract the installation archive files. Refer to the section "Extract the Installation Archive Files".
To download the installation archive files, perform the following steps:
Use any browser to access the software download page on OTN at:
Choose the link for the software that you want to download.
On the Oracle Technology Network Developer License Terms page, answer all questions.
On the download page, identify the required disk space by adding the file sizes for each required file.
The file sizes are listed next to the filenames.
Select a file system with enough free space to store and expand the installation archive files.
In most cases, the available disk space must be at least twice the size of the installation archive files.
On the file system that you selected in step 5, create a parent directory, for example
oracle10g, to hold the installation archive files.
Download the installation archive files to the directory that you created in step 6. Verify that the files you downloaded are the same size as the corresponding files on OTN.
Unzip the installation archive files using the
unzip utility, as follows:
Unzip each file on a PC or UNIX system, using a command similar to the following:
$ unzip filename.zip
The preceding command creates the following files:
Disk1.pax Disk2.pax doc/ welcome.htm
FTP the unzipped files,
Disk2.pax, in binary mode to your z/OS system. Ask your system administrator for the FTP instructions specific to your system.
The result should be that there are two files,
Disk2.pax, on your z/OS system.
The next step is to extract the installation archive files. Refer to the following section "Extract the Installation Archive Files".
Disk2.pax now exist in a temporary location on your z/OS system. The files need to be extracted in preparation for installation.
To extract the installation archive files, perform the following steps:
Change the working directory to the directory where you want the installation files to reside. This can be a temporary space, but it is required until you have finished installing all the Oracle products.
Extract the installation files, using commands similar to the following:
$ pax -rvf directory_location/Disk1.pax$ pax -rvf directory_location/Disk2.pax
The preceding commands extract the contents of
Disk2.pax into the current directory.
Check the current directory to make sure the files were extracted properly, using the following command:
$ ls -l
drwxr-xr-x 3 AROGERS OEQA1 288 Mar 10 14:54 Disk1 drwxr-xr-x 3 AROGERS OEQA1 288 Mar 16 10:27 Disk2 drwxr-xr-x 3 AROGERS OEQA1 288 Mar 10 14:54 Translations drwxr-xr-x 3 AROGERS OEQA1 864 Mar 30 07:56 install -rwxr-xr-x 1 AROGERS OEQA1 772 Mar 15 11:20 runInstaller
The extraction should create five directories (
/Disk1, /Disk2, /Translations, /install, and /doc), and two files, one called
runInstaller, and one called
welcome.htm. If the extraction process did not succeed, then the files may be corrupted. Repeat the process of loading or downloading the installation archive files onto your z/OS system, and then unzip and extract the files. If the extraction is still unsuccessful, then contact Oracle Support Services to obtain a new copy of the installation archive files.
You can now delete the
When you have finished extracting the files, you are ready to install the software. Depending on the product you plan to install, refer to the following installation instructions:
To install the Oracle Database or Oracle Client, refer to the instructions in Chapter 3, "Database Installation Tasks".
To install the Oracle Transparent Gateways, refer to the Installation and User's Guide for your Gateway product.