1.4 GB to 3.6 GB of disk space for the Oracle software, depending on the installation type
4.0 GB of temporary disk space for a temporary work area, including the disk space required for the zip files that are downloaded and their expanded contents. The zip files and expanded installation files can be located in different file systems.
1000 cylinders (860 MB) of PDS disk space, including 350 cylinders (284 MB) for the
AUTHLOAD library (only 10 cylinders are needed for client-only installations), 300 cylinders (244 MB) for the
CMDLOAD library, and 125 cylinders (102 MB) for the
MESG PDS. The remaining data sets require less than 10 cylinders (10 MB) each.
Your z/OS system may not have the required disk space available as an HFS or z/FS file system. In this case, 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.
Refer to Oracle Database Patch Set Notes 10g Release 2 (10.2.0.5) Patch Set 4 for IBM z/OS on System z for a detailed list and an accurate estimate of disk space requirements.
Depending on the features that you intend to use, 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||IBM z/OS (5694-A01) V1.10.0 or later
Required for all installations.
|Java||The installation and patching procedures for Oracle Database 10g Release 2 (10.2.0.5) no longer require Java. However, if you do not have an
Other features of Oracle Database for z/OS may require Java. Refer to Oracle Database Patch Set Notes 10g Release 2 (10.2.0.5) Patch Set 4 for IBM z/OS on System z for the specific version of Java required.
|IBM REXX||Required for all installations|
|CICS TS||V3.2 or later is required for Oracle Access Manager for CICS TS|
|IMS TM||V10.1 or later is required for Oracle Access Manager for IMS TM|
|z/OS UNIX System Services||Required for all installations.|
|TCP/IP||Required for all installations.|
|IBM C/C++||IBM z/OS XL C/C++ V1.10 or later 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|
|Unzip||The need to process
An Unzip utility for z/OS UNIX System Services is available from the IBM Ported Tools web site.
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 -aI
The operating system version should appear as follows, where
systemname is the name of the system and
nnnn is the hardware model:
z/OS systemname 10.00 01 nnnn
To determine whether Java 1.4.2 is installed in the default
PATH, enter the following command:
$ java -version
The Java version should appear as follows:
java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS Persistent Reusable VM build cm142ifx-20100705 (SR13 FP5) (JIT enabled: jitc))
Java executable is not found, or if the version displayed is less than 1.4.2, download Java 1.4.2 from the IBM Java Web site and install it:
Note: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 for the
make to function correctly. If
make is not installed and in the path, then an error message is displayed. Oracle recommends that you should not modify this file.
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 activity, which is optional, requires an initial program load (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 following descriptions 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 about 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 you use to 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
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 must ask your system administrator to issue the following command, which shows the maximum allowed value:
$ tso listuser username tso
tso listuser arogers tso USER=AROGERS NAME=ANDREW ROGERS OWNER=RACF CREATED=96.106 DEFAULT-GROUP=OEG647 PASSDATE=03.356 PASS-INTERVAL= 92 ... TSO INFORMATION --------------- ACCTNUM= NOACCT PROC= $AROGERS SIZE= 02048000 MAXSIZE= 02048000 USERDATA= 0000
This shows that you can have up to 2 GB of virtual storage.
You must 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 contains 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: add an entry for the data set to the
xx member of
SYS1.PARMLIB, or add an entry for the data set to the
xx member of
SYS1.PARMLIB. The first way (using the
xx member) utilizes a newer mechanism. The second way (using the
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
APF ADD DSNAME(ORACLE.V10G.AUTHLOAD) SMS
If your installation is using
xx instead of
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 ensure that the preceding entry has a comma.
xx do not take effect until the next IPL. If your installation has enabled z/OS dynamic APF facilities, then 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
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. Oracle Universal Installer prompts 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 want to use, then this step can be performed before the data set is created and populated. However, once you create a data set, you must 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
xx member of
SYS1.PARMLIB must be set to a higher value.
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), through a member of the
SYS1.PARMLIB data set named
xx is a 2-letter or 2-digit suffix. The entries that you add must be similar to those in the following example. The comments, which are included for clarity, are allowed but are not required.
Note:You may need to work with your systems programmer to determine the correct member name and to add the entries.
/* 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
xx member are usually read at z/OS IPL. You can cause z/OS to reread 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.
See Also:For details on the
xxmember, the PPT, and the
SET SCHcommand, refer to the following IBM documents:
MVS Initialization and Tuning Reference
MVS System Commands
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
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
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.
See Also:For directions on activating the
FACILITYclass, refer to the IBM document Security Server RACF Security Administrator's Guide
This is done with a
SETROPTS CLASSACT RACF command and does not require a z/OS IPL.
See Also:For a description of this command, refer to the IBM document Security Server RACF Command Language Reference
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 resources that may be associated with the
If you decide to create resource classes for Oracle Database 10g for z/OS, then two classes must be created: one for OSDI commands and one that is shared by both bind and database
SYSDBA connect authorizations.
See Also:For information about adding installation-defined resource classes, refer to the following IBM documents:
Security Server RACF Macros and Interfaces
Security Server RACF System Programmer's Guide
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 preinstallation 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 must specify parameters as in the following example, which defines the classes
$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.
See Also:For more information, refer to the IBM document Security Server RACF Security Administrator's Guide and the Security Server RACF Command Language Reference
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 on System z.
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 user ID 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 user ID is associated with the address space. You, or security personnel for your installation, must take steps to ensure that Oracle Database 10g for z/OS services have an associated user ID that can be authorized for system functions that are invoked by the database and network services.
If you are running the TNS programs of previous releases as started tasks (as opposed to submitting them as batch jobs), then your installation probably has
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
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 user IDs. This requires using distinct JCL procedures even though the procedures themselves may be otherwise identical. The
RDEFINE command that is used to add profiles is described in the Security Server RACF Command Language Reference.
See Also:For details on the
USERresource classes, refer to the IBM document RACF Security Administrator's Guide
With RACF, it is also possible to associate a user ID 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.
See Also: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 include 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 user ID that is associated with the address space have a default z/OS UNIX System Services segment that is defined to the security subsystem.
See Also:For additional information, refer to the Oracle Database System Administration Guide for IBM z/OS on System z
In addition, certain utilities run only in a z/OS UNIX System Services shell environment, such as Oracle Universal 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.
Oracle Universal 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.
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:
The Oracle base directory acts as a top-level directory for Oracle software installations. Generally, you must 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.2.0.5. This corresponds to the 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. 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.
During installation, a number of files are placed into PDS and PDSE data sets. The installation process creates these data sets. The user performing the installation must have the RACF authority to create them. The installation process requires that all Oracle installation and executable files are kept under one high level qualifier.
You must determine a naming convention for high-level and second-level data set name qualifiers. For more information, refer to Appendix A. In addition, you must 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,
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.
Starting with Oracle Database 10g Release 2 (10.2.0.5), installations no longer require a Client X Server environment. However, an interactive environment with the ability to edit, submit, and monitor batch jobs is required.
This section describes the required environment of the user (user ID) who is performing the 10.2.0.5 installation. The installation is performed by running z/OS batch jobs. The user must have access to an interactive environment with the ability to perform the following:
Edit the JCL files that include the jobs needed for installation using either:
A TSO/ISPF environment.
A z/OS UNIX System Services OMVS shell environment controlled by a 3270-style terminal, and use of the OEDIT editor.
A z/OS UNIX System Services shell environment controlled by a VT-style terminal, and use of the vi editor.
Submit the jobs for execution on the target z/OS system using either:
A TSO/ISPF environment.
A TSO environment with permission to use the SUBMIT command.
A z/OS UNIX System Services shell environment controlled by a VT-style terminal, and use of the SUBMIT command.
Monitor jobs for progress and successful completion by using:
An SDSF environment.
A TSO environment with permission to use the STATUS and OUTPUT commands.
A z/OS UNIX System Services shell environment controlled by a VT-style terminal, and use of the SUBMIT command.
Although it is possible to perform the installation from a VT-style terminal and the UNIX shell, Oracle recommends that you use a 3270-style terminal where you have the ability to use TSO, ISPF, and SDSF. From that environment, you can still perform the UNIX System Services operations utilizing the OMVS shell.
This environment is only used to edit, submit, and monitor batch jobs. The actual installation is performed by batch jobs. These batch jobs require the correct configuration, authority, and resources to perform the installation.
For detailed information about the composition of the installation software zip files, refer to Oracle Database Patch Set Notes 10g Release 2 (10.2.0.5) Patch Set 4 for IBM z/OS on System z. It also contains specific information on obtaining these zip files and where they should be placed on the z/OS system.
In short, you download 4 to 8 zip files from Oracle Support, then transfer them to a temporary location in an HFS or zFS file space. You may delete these zip files after the installation is complete.