3 Installing Oracle Database Software

Overview of Oracle Database Installation

The Oracle software is compressed into installation files that can be loaded from the product DVD's or downloaded from Oracle E-Delivery Web site at http://edelivery.oracle.com/. The installation files are included in a LMS library.

You must extract the compressed files to a temporary location on a Windows or UNIX file system, and then upload the installation files to BS2000 using File Transfer protocol (FTP). Below we describe the installation process for the /390 series of ORACLE/BS2000. The installation process for the SX series is identical, except for the name of the LMS library which is ora10202.sx.lib for the SX series instead of ora10202.390.lib.

Installing the Oracle Database Software

Oracle recommends installing Oracle Database 10g release 2 using a new user ID. Follow these steps to install the Oracle database software:

1. The BS2000 System Administrator must create the Oracle installation user ID, the user ID under which you want the Oracle Database 10g release 2 software to reside. Throughout this guide we refer to this user ID as ORAC1020. This user ID does not require any special BS2000 privileges. You will need about 1 400 000 PAM pages temporarily in the installation user ID. The extracted files will occupy about 700 000 PAM pages.

2. The software must be copied to a temporary location on a Windows or UNIX system that has FTP access to the BS2000 system where you will be installing the software.

   If you have received the installation files on a DVD, mount the DVD on this system. If you have downloaded the installation files from an Oracle Web Site, move the zip file to this system.

3. Unzip the zip file with a zip utility like WinZip into a temporary location on this system. The following files should be created:

   doc/ : contains ORACLE/BS2000 specific documentation

   welcome.htm : starting point for accessing the documentation

   ora10202.390.lib : installation files packed in one LMS library

4. Transfer the LMS library binary into the installation userid, for example, ORAC1020. Before the transfer, if you are using BS2000 ftp in the installation userid, preallocate the file by using the following ftp file command:

   file ora10202.390.lib,fcbtype=pam,blkctrl=no,blksize=(std,2)
   

   Use the following command if you are using ftp on the platform where you had unzipped the file:

   quote file ora10202.390.lib,fcbtype=pam,blkctrl=no,blksize=(std,2)
   

5. Login into the installation user ID, ORAC1020.

6. Extract all files in the installation user ID by typing the following commands:

   /START-LMSCONV
   //extr (ora10202.390.lib,*,x),*
   //end
   

   After successful extraction you can delete the ora10202.390.lib file.

7. Execute the install procedure as follows:

   /CALL-PROCEDURE INSTALL.P.ORACLE,($userid)
   

   This procedure applies the necessary changes to a number of command files.

8. Optionally, run the installation procedure for the POSIX part of Oracle.

   /CALL-PROCEDURE INSTALL.P.POSIX
   

   You will be prompted for the ORACLE_HOME in the POSIX file system. If you want to accept the default value, for example, /orac1020/oracle/product/10g, press ENTER.

   You must not use the /DO option to call this procedure.The script can be run at any time after the installation of Oracle database for BS2000/OSD. However, some prerequisites are necessary before you can run the script:

   • The BS2000 administrator must enable the POSIX subsystem:

     /START-SUBSYSTEM POSIX
     

   • The BS2000 administrator must create a POSIX directory (for example /orac1020) with at least 400000 kbytes of free space.

   You need the POSIX part of Oracle if you want to use Java in the database or if you want to use Oracle Enterprise Management Agent or the Oracle Wallet Manager for BS2000/OSD.

Installing Multiple Oracle Systems

You can also install multiple Oracle systems, based on the same or different versions of Oracle software. In this case, different versions of the software must be installed under different installation user IDs. If you are creating a database manually (not using INSTALL.P.SUPER) keep the database file names unique by prefixing them with the sid of that database.