3 Oracle Database Installation and Deinstallation

3.3.1.1 Memory Requirements

Oracle Database requires at least 2 GB main memory.

The Address Space Limit for the installation user ID should be 512 MB or higher. For the DBA user IDs, it should be at least 1024 MB.

• To determine the memory size, enter the following command:

  /SHOW-SYSTEM-INFORMATION INFORMATION=*MEMORY-SIZE
  

• To determine the user address space limit, log in to the desired user ID and enter the following command:

  /SHOW-USER-ATTRIBUTES
  

If the user address space is less than the required size, then ask your BS2000 system administrator to increase the Address Space Limit by using the command:

/MODIFY-USER-ATTRIBUTES USER-IDENTIFICATION=user-id,ADRESS-SPACE-LIMIT={512|1024}

3.3.1.2 System Architecture

Oracle Database 11g Release 2 supports all BS2000/OSD server architectures, such as S Server, SQ Server and SX Server. To determine the architecture on your system, enter the following command:

/SHOW-SYSTEM-INFORMATION INFORMATION=*HSI-ATTRIBUTES

The following is the TYPE output that shows the system architecture:

• IX: HSI of a S server (/390 architecture)

• KM: HSI of a SQ server (x86-64 architecture)

• PM: HSI of a SX server (SPARC architecture)

• UD: The HSI type is not defined

On S Servers, install the Oracle Database software for the platform Fujitsu BS2000/OSD (S Series). The name of the installation staging library is ora11202.s390.lib.

On SQ Servers, install the Oracle Database software for the platform Fujitsu BS2000/OSD (SQ Series). This software runs in native x86-64 mode. The name of the installation staging library is ora11202.sq.lib.

On SX Servers install the Oracle Database software for the platform Fujitsu BS2000/OSD (S Series). This software runs in emulated mode. The name of the installation staging library is ora11202.s390.lib.

3.3.1.3 Disk Space Requirements

Due to some new features, Oracle Database 11g Release 2 requires an installation in the BS2000 file system (DMS) and in the POSIX file system. Oracle recommends using a separate POSIX file system for the Oracle Database software installation.

http://manuals.ts.fujitsu.com/file/8521/posix_g.pdf

When the POSIX administrator or BS2000 system administrator creates a new POSIX file system by using the START-POSIX-INSTALLATION command, a new POSIX container file similar to a UNIX disk partition is allocated in the BS2000 file system. The POSIX file system is created in this container file. If the desired mount point, for example, /u01, is not yet available in the root system, then it is created and the file system is mounted.

Oracle Database 11g Release 2 software for Fujitsu BS2000/OSD (S Series) requires the following disk space:

• BS2000 file system:

  Software	1.000.000 PAM pages
  Staging library	820.000 PAM pages
  Recommended (in total)	2.000.000 PAM pages

  
  

• POSIX file system:

  Minimum	400 MB
  Recommended	1 GB

  
  

The extracted files occupy about 1.000.000 PAM pages in the BS2000 file system. The files installed in the POSIX file system occupy about 200 MB.

The staging library does not have to reside in your installation user ID.

3.3.1.4 Display Requirements

Oracle Database supports 9750 compatible terminals. In addition, Oracle Database supports X-terminals in the POSIX environment if you logged in to POSIX using rlogin or ssh.

The minimum resolution for Java based tools with a Graphical User Interface shipped with Oracle Database 11g Release 2 is 1024 x 768 or higher.

3.3.2.1 Operating System and Communication System Requirements

The following operating system and communication system versions or higher, are required for Oracle Database 11g Release 2:

• BS2000/OSD V7.0

• openNet Server V3.3

  This includes BCAM V20.0 and Sockets V2.4.

Oracle recommends that you regularly install the most current correction packages for BS2000/OSD.

Check the version of your BS2000/OSD system with the following command:

/SHOW-SYSTEM-INFORMATION INFORMATION=*BS2000-ID

/EXECUTE-POSIX-CMD CMD='uname -v'

You can check the version of your openNet Server software by checking the version of the software component BCAM with the following command:

/SHOW-INSTALLATION-PATH INSTALLATION-UNIT=BCAM

Or you can ask your BS2000 system administrator to check the BCAM version with the command:

/BCSHOW SHOW=BCAM

3.3.2.2 POSIX Parameters

The following POSIX parameters must be checked for the recommended values for Oracle Database 11g Release 2:

The POSIX administrator or BS2000 system administrator can check the values in the file $TSOS.SYSSSI.POSIX-BC.version, for example, version = 070|080|090. The values can also be checked by using the POSIX command usp:

# usp -s nproc

You can update the value with the following command:

# usp -P parameter -v value

3.3.2.3 Package Requirements

The following POSIX packages with the specified versions or higher are required for Oracle Database 11g Release 2:

• POSIX-SH V7.0

• JENV V6.0

• APACHE V2.2, including correction package 2/2012

• PERL V5.8, including correction package 2/2012

• BCAM V20.0

To check the installed packages, use the following POSIX command:

$ pkginfo package name

3.3.2.4 Additional BS2000 Software Components

The following additional software is required by Oracle Database 11g Release 2. Install the required or higher versions:

• CRTE-BASYS V1.7F or CRTE-BASYS V1.8E or CRTE-BASYS V1.9A

• SDF V4.7

• SDF-P V2.5

• SDF-A V4.1

• EDT V17.0A

• LMS V3.4

• openSM2 V7.0

• PTHREADS V1.3

• ORACLE-TOOLS V1.0

  The Oracle Database utility ADRCI requires the zip utility in the POSIX environment for creating ADR incident packages, that can be uploaded to Oracle Support.

  Currently, the zip utility is not part of the supply unit of POSIX of Fujitsu BS2000/OSD. So you must download it separately from the download area of the Fujitsu Support website:

  http://support.ts.fujitsu.com/Download
  

  Download the software package called ORACLE-TOOLS. This software package contains the utilities zip and unzip. You can find this software package by entering the package name ORACLE-TOOLS into the search box of the download area. Install the software package ORACLE-TOOLS as described in the readme file.

3.3.2.5 Compiler and CRTE Requirements for Oracle Database Applications

If high-level languages, such as C or COBOL, are used to interface with the Oracle Database, then the following versions or higher are supported:

• COBOL85 V2.3

• COBOL2000 V1.2

• CPP V3.0

• CRTE V2.7F

• CRTE V2.8E

• CRTE V2.9

3.3.2.6 Additional Software Requirements

openUTM V6.0 or higher is required if you want to use Oracle Database in configurations with the transaction monitor openUTM.

3.3.3.1 Checking Sockets subsystem

On S servers, the sockets subsystem SOC6 must be created and running. On SQ servers, the sockets subsystem SOC6-X8 must also be created and running. You can check the sockets subsystems with the following command:

/SHOW-SUBSYSTEM-STATUS SOC6*

3.3.3.2 Checking BCAM Timer

It is recommended to check the BCAM connection and letter timer. Your BS2000 system administrator can display the timer values with the following command:

/SHOW-BCAM-TIMER

The value for the connection timer, also called CONN in the output of the ISO section, should be set to a minimum of 600 seconds. It is recommended that the letter timer, also known as LETT in the STD section, should be set to a large value. The value 0 in the output indicates an infinite letter time.

3.3.3.3 Checking LWRESD

It is recommended to use the Light Weight Resolver (LWRESD) for host name resolution operations. The tasks for checking and administrating the LWRESD require the BS2000 system administrator privilege. Ask your BS2000 system administrator to check if the LWRESD is running by using the following command:

/SHOW-LWRESD-PARAMETERS

For example, the following output shows the parameter file in use:

RESOLV-FILE : :PVS1:$TSOS.SYSDAT.LWRESD.011.RESOLV.CONF

This parameter file must contain valid nameserver IP-addresses and a domain or search list of domains.

3.3.3.4 Checking Loopback Address

Check if the file $TSOS.SYSDAT.BCAM.ETC.HOSTS contains an entry for the loopback address. For example:

127.0.0.1                localhost loopback           # local address

3.3.3.5 Checking the Configuration Files in the POSIX File System

Check the network configuration files /etc/hosts and /etc/resolv.conf. These files must have the same contents as the corresponding files in the BS2000 administrator user ID TSOS. If there are any mismatches, then ask your BS2000 system administrator to synchronize the files.

3.3.4.1 Creating the BS2000 Installation User ID

The BS2000 System Administrator must create a user ID under which you want the Oracle Database 11g Release 2 software to reside. This user ID is called the Oracle installation user ID or Oracle software owner. Throughout this guide, we refer to this user ID as ORAC1120. This user ID does not require any special BS2000 privileges.

When the BS2000 system administrator creates the installation user ID with the following command, the corresponding POSIX user is also created. The POSIX user attributes, namely, user number, group number, login directory and program, are assigned default values.

/ADD-USER ORAC1120,…

3.3.4.2 Creating the POSIX System Group

For installation under POSIX, the POSIX administrator or BS2000 System Administrator must create system groups in POSIX. As distinguished from other UNIX systems, the installation user ID (Oracle software owner) and the DBA user ID of an Oracle database are not identical. Therefore, the POSIX installation uses only one group, such as oracle, for Oracle software owner and Oracle database. This group is called Oracle installation group.

• If this is not the first Oracle Database installation under POSIX, then you can determine the group name by using the following POSIX command:

  $ more /var/opt/oracle/oraInst.loc
  

  If the oraInst.loc file exists, then the output from this command is similar to the following:

  inventory_loc=/u01/app/oraInventory
  inst_group=oracle
  

  The inst_group parameter shows the group name of your former Oracle Database installation, here oracle.

• To determine if this group is defined with a unique group-id, enter the following command:

  $ grep 'oracle' /etc/group
   
  

  If the output shows the group name and a group-id greater than 100, then the group exists.

  If the group-id is 100, then you must change the id to a distinct value greater than 100, for example, 104.

  If the group cannot be found in /etc/group,then ask your POSIX administrator or BS2000 system administrator to add the group name and a unique group number to the file /etc/group. The administrator must use a text editor, such as edt or vi to add a new line with the following specifications:

  groupname::groupnumber:user-id[,user-id,...]
  

  The following example shows a line in the file /etc/group for the group oracle:

  oracle::104:ORAC1120,ORADB11G
  

  Add further installation user IDs and all DBA user IDs to the line with the Oracle group-id.

3.3.4.3 Initializing the POSIX User

Before using the installation user ID as a POSIX user, the POSIX administrator or BS2000 system administrator must initialize the POSIX user with the following command:

/ADD-POSIX-USER USER-NAME=user-id,USER-NUMBER=nnn,GROUP-NUMBER=oracle group number,HOME-DIRECTORY=path[,RLOGIN-ACCOUNT=account]

Consider the following requirements:

• The USER-NAME is the installation user ID.

• The USER-NUMBER must be unique and greater than 100.

• The GROUP-NUMBER must be the number of the Oracle installation group and greater than 100.

• The HOME-DIRECTORY must be a valid path. Do not use a path which resides in the root or var file system. It is strictly recommended to create a separate file system for the POSIX users. An example for a valid HOME-DIRECTORY is /home/orac1120 where /home is the mount point of a POSIX file system.

• The RLOGIN-ACCOUNT can be specified if you allow the remote access by using rlogin or ssh.

3.3.4.4 Creating Users and Groups for Oracle Databases

Typically Oracle databases in BS2000/OSD reside in BS2000 user IDs not equal to the Oracle database installation user ID. If you create a new DBA user ID for a new Oracle database, then you must also initialize the POSIX user in the same way as described in "Initializing the POSIX User". If you want to upgrade an existing Oracle database, then you must check if the POSIX user is initialized for the DBA user ID with the following BS2000 command:

/SHOW-POSIX-USER-ATTRIBUTES

If the output shows default values and the directory is /home/gast, then initialize the POSIX user with the following BS2000 command:

/ADD-POSIX-USER

The POSIX user attributes of an initialized POSIX user can be modified with the following BS2000 command:

/MODIFY-POSIX-USER-ATTRIBUTES

Finally, add the user to the Oracle installation group in the file /etc/group.

3.3.5.1 Oracle Base Directory

Oracle base directory is a top-level directory for Oracle software installations. Oracle recommends using a path similar to the following for the Oracle base directory:

/mount_point/app/software_owner

In this example:

• mount_point is the mount point directory for the file system that contains the Oracle software. The examples in this guide use /u01 for the mount point directory.

• software_owner is the operating system user name of the software owner installing the Oracle software.

The components /mount_point/app represent the operating system part of the path. Before you start the installation of Oracle Database 11g Release 2, you must create the operating system part of the path.

You can use the same Oracle base directory for the installation of the Oracle Management Agent. Multiple Oracle installations require separate installation user IDs in BS2000/OSD with the consequence of creating separate Oracle base directories in the POSIX file system. The following are examples of Oracle base directories that can exist on the same system:

/u01/app/orac1120
/u01/app/ora10205

See "Create or Expand a File System for the Oracle Base Directory" for more information about the POSIX file system.

3.3.5.2 Oracle Inventory Directory

The Oracle Inventory directory (oraInventory) stores the inventory of all software installed on the system. It is required and shared by all Oracle software installations on a single system. If you have an existing Oracle Inventory path, then the Oracle installation procedure uses that Oracle Inventory.

The Oracle installation procedure derives the path for the Oracle Inventory directory from the file /var/opt/oracle/oraInst.loc. If this file does not exist, then it derives the inventory path from ORACLE_BASE and creates the Oracle Inventory directory in the following path: ORACLE_BASE/../oraInventory. For example, if ORACLE_BASE is set to /u01/app/orac1120, then the Oracle Inventory directory is created in the path /u01/app/oraInventory.

The Oracle installation procedure creates the Oracle subdirectories that you specify and sets the correct owner, group, and permissions for it. The operating system part of the path, for example, /u01/app must exist and you must have read, write and execute permissions in the directory app.

3.3.5.3 Oracle Home Directory

The Oracle home directory is the directory where you install the software for a particular Oracle product. When you run the Oracle installation procedure, it prompts you to specify the path of this directory. You can accept the recommended path or enter a new path. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:

oracle_base_path/product/dbhome

The Oracle installation procedure creates the directory path that you specify. It also sets the correct owner, group, and permissions on it. You do not have to create this directory manually.

3.3.6.1 Identifying an Existing Oracle Base Directory in POSIX

Existing Oracle base directories can be identified as follows:

• Identifying an existing Oracle Inventory directory.

  Search for the string 'inventory_loc' in the file /var/opt/oracle/oraInst.loc.

  $ grep 'inventory_loc' /var/opt/oracle/oraInst.loc
  

  If oraInst.loc exists, then the output is similar to the following:

  inventory_loc=/u01/app/oraInventory
  

• Deriving an Oracle base directory from an existing Oracle home directory.

  Enter the following command to display the contents of the /var/opt/oracle/oratab file:

  $ more /var/opt/oratab
  

  If the oratab file exists, then it may contain lines similar to the following:

  *:/u01/app/orac1020/product/10g:N
  *:/oracl920/9.2.0:N
  

  The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner are existing Oracle base directories. For the installation of Oracle Database 11g Release 2, you can choose the subdirectory /u01/app as root for your Oracle base directory. If you intend to use the orac1120 user to install the software, then you can choose the following directory:

  /u01/app/orac1120
  

Ensure that the Oracle base directory for this installation meets the following conditions:

• It is not on the same file system as the operating system (root or var).

• It has sufficient free disk space.

To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:

$ df -k oracle_base_path

3.3.6.2 Create or Expand a File System for the Oracle Base Directory

If you want to install the Oracle software into an existing file system with Oracle base directories but the POSIX file system has insufficient space, then the POSIX administrator or BS2000 system administrator can expand the file system with the Oracle base directory using the POSIX installer. Complete the following steps to expand the file system using the POSIX installer:

1. Start the POSIX Installer using the following command:

   /START-POSIX-INSTALLATION
   

2. Choose Administrate POSIX filesystems.

3. Mark the desired file system and choose expand.

4. Enter the number of PAM pages by which the file system should be expanded.

If you want the Oracle base directory to reside in a new POSIX files system, then the POSIX administrator or BS2000 system administrator must create a POSIX file system using the POSIX installer. Complete the following steps to create a POSIX file system using the POSIX installer:

1. Start the POSIX installer using the following command:

   /START-POSIX-INSTALLATION
   

2. Choose Administrate POSIX filesystems and then, choose append.

The POSIX installer allocates a new POSIX container file in the BS2000 file system and creates the POSIX file system inside the container. The POSIX installer also asks for a mount point for the new file system. If the mount point does not exist, then it is created in the root system and the new file system is mounted. By default, the owner of the new file system is SYSROOT. The administrator must now create the Oracle base directory and specify the correct owner, group, and permissions for it with the following specifications:

# mkdir -p /mount_point/app/oracle_sw_owner
# chown -R oracle_sw_owner:oracle_installation_group /mount_point/app/oracle_sw_owner
# chmod -R 775 /mount_point/app/oracle_sw_owner

For example:

# mkdir -p /u01/app/orac1120
# chown -R orac1120:oracle /u01/app/orac1120
# chmod -R 775 /u01/app/orac1120