The preinstallation requirements, postinstallation tasks, installation and deinstallation of Oracle Database 12c Release 1 on BS2000 are discussed in the following topics:
You can download Oracle Database software from Oracle Software Delivery Cloud at https://edelivery.oracle.com. The installation files are included in a Library Maintenance System (LMS) library called staging library, which is delivered in a zip file.
Download the zip file and extract it to a temporary location on a Windows or UNIX system. Then upload the staging library to the BS2000 system using File Transfer Protocol (FTP). The following sections describe the installation process for Oracle Database on the Fujitsu BS2000/OSD Servers. The name of the staging library reflects the releases of Oracle Database or Oracle Database Patch Set, and the supported hardware architecture:
oraxxxxx.arch.lib
Where xxxxx is the release number and arch is the supported hardware architecture. For example:
ora12102.s390.lib
Note:
ora12102.s390.lib is the name of the staging library for the base release of Oracle Database 12c Release 1 (12.1.0.2).
You must complete the following tasks before you install Oracle Database 12c Release 1 for Fujitsu BS2000/OSD:
The system must meet the following hardware requirements:
Oracle Database 12c Release 1 for Fujitsu BS2000/OSD (S Series) is based on the /390 instruction set and supports the following Fujitsu BS2000 server lines:
S Servers
SE Servers
SQ Servers
This release runs on all Fujitsu BS2000 processors, in particular on the S servers and /390-based system units of SE servers. It runs in the /390 compatibility mode on processors that are based on Intel x86 architecture. This applies for x86-based server units of the SE servers (SU x86).
See Also:
“Oracle Database Variants for Fujitsu BS2000/OSD” for details about which variant can run on the various Fujitsu BS2000 server lines and hardware architectures
Note:
The release of a special variant of Oracle Database 12c Release 1 based on the x86 instruction set is not planned.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}
Oracle Database 12c Release 1 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.
See Also:
Fujitsu guide for BS2000/OSD mainframes POSIX Basics for Users and System Administrators for more information about creating an additional POSIX file system:
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 available in the root system, then the mount point is created and the file system is mounted.
Oracle Database 12c Release 1 software for Fujitsu BS2000/OSD requires the following disk space:
BS2000 file system:
| Item | Free Disk Space |
|---|---|
|
Software |
1.200.000 PAM pages |
|
Staging library |
1.000.000 PAM pages |
|
Recommended (in total) |
2.500.000 PAM pages |
POSIX file system:
| Requirement | Free Disk Space |
|---|---|
|
Minimum |
4 GB |
|
Recommended |
7 GB |
Note:
The diagnostic data of the Automatic Diagnostic Repository (ADR) reside in the POSIX file system. The disk space required for the ADR depends on the number of Oracle database instances and the amount of diagnostic data created for incidents. Therefore, you may need significantly more disk space in the POSIX file system than recommended.
The extracted files occupy about 1.200.000 PAM pages in the BS2000 file system. The files installed in the POSIX file system occupy about 600 MB.
The staging library does not have to reside in your installation user ID.
Oracle Database supports 9750 compatible terminals. In addition, Oracle Database supports X-terminals in the POSIX environment when you log in to POSIX using rlogin or ssh.
The minimum resolution for Java based tools with a graphical user interface (GUI) shipped with Oracle Database 12c Release 1 is 1024 x 768 or higher.
Before installing Oracle Database, Oracle recommends that you check if your system meets the following software requirements:
Oracle Database 12c Release 1 requires the following operating system and communication system versions or higher:
BS2000/OSD-BC V9.0, BS2000 OSD/BC V10.0, and higher.
openNet Server V3.5
This includes BCAM V22.0 and Sockets V2.6.
Oracle recommends that you regularly install the most current correction packages for your BS2000 system.
Check the version of your BS2000 system with the following command:
/SHOW-SYSTEM-INFORMATION INFORMATION=*BS2000-ID
Note:
The correction level of the POSIX subsystem must be A43 or higher. You can check the POSIX correction level with the following command:
/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,LOGICAL-IDENTIFIER=*NONE
You can also ask your BS2000 system administrator to check the BCAM version with the command:
/BCSHOW SHOW=BCAM
Note:
The BCAM version must be V22 or higher.
Check the following POSIX parameters for the recommended values for Oracle Database 12c Release 1:
| Parameter Name | Description | Recommended Value |
|---|---|---|
|
|
Number of hard disk server tasks |
4 |
|
|
Number of physical I/O buffers |
20 |
|
|
Maximum number of processes |
1000 |
|
|
Number of I/O buffers |
200 |
|
|
Maximum number of processes per user |
300 |
|
|
Maximum number of ttys |
512 |
|
|
Maximum number of ptys |
512 |
|
|
Maximum number of sttys |
512 |
|
|
Initial state of POSIX loader |
1 |
|
|
Size of pool in MB for POSIX loader |
30 |
The POSIX administrator or the BS2000 system administrator can check the values in the file $TSOS.SYSSSI.POSIX-BC.version, for example, version = 090|100. The values can also be checked by using the usp POSIX command :
# usp -s nproc
The POSIX administrator or the BS2000 administrator can update the value with the following command:
# usp -P parameter -v value
Note:
If you edit the parameters in the $TSOS.SYSSSI.POSIX-BC.version file, then you must restart the POSIX subsystem.
The parameter values depend on the overall load of the BS2000 system and must be adjusted to this load. The values listed previously are minimal recommendations.
Oracle Database 12c Release 1 requires the following POSIX packages with the specified versions or higher:
POSIX-SH V8.0
JENV V6.0
APACHE V2.2, including correction package 2/2015
PERL V5.8, including correction package 2/2015
BCAM V22.0
Use the following POSIX command to check the installed packages:
$ pkginfo package name
Note:
Ensure that all the specified packages are installed before installing Oracle Database.
Oracle Database 12c Release 1 requires the following additional software with the specified versions or higher:
CRTE-BASYS V1.9A or CRTE-BASYS V10.0A
SDF V4.7
SDF-P V2.5
SDF-A V4.1
EDT V17.0A
LMS V3.4
openSM2 V9.0
PTHREADS V1.4 including correction package 1/2016
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 included in the supply unit of POSIX of Fujitsu BS2000. You must download it separately from the download section on 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 section. Install the software package ORACLE-TOOLS as described in the readme file.
Note:
The subsystem CRTEBASY must be loaded.
SDF-A is optional. SDF-A is only required to update the SDF user syntax file for Oracle. If SDF-A is not available, then the SDF user syntax file update for Oracle is skipped. If you do not update the SDF syntax file for Oracle, then you cannot start Oracle Database utilities with BS2000 SDF commands in UNIX-style.
The software component PTHREAD is required by the replay client utility, wrc.
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.5
CPP V3.2
CRTE V2.9
CRTE V10.0
Typically, the computer on which you want to install Oracle Database is connected to the network as a member of a network domain. Besides the BCAM host name, the host must have a fully qualified name (hostname.domain) that can be resolved by a DNS. You must perform the following important checks on a BS2000 computer:
The sockets subsystem SOC6 must be created and running. You can check the status of the sockets subsystems with the following command:
/SHOW-SUBSYSTEM-STATUS SOC6
Oracle recommends to check the BCAM connection and letter timer. Your BS2000 system administrator can display the timer values with the following command:
/SHOW-BCAM-TIMER[TIMER=*STD]
The value for the connection timer, also called CONN in the output of the STD section must be set to a minimum of 600 seconds. The value for the letter timer, also known as LETT in the STD section must be set to a large value. The value 0 in the output indicates an infinite letter time.
Oracle recommends to use the Light Weight Resolver (LWRESD) for host name resolution operations. You require BS2000 system administrator privilege for checking and administering LWRESD. Ask your BS2000 system administrator to check if 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.012.RESOLV.CONF
This parameter file must contain valid name server IP-addresses and a domain or a search list of domain names.
Check if the $TSOS.SYSDAT.BCAM.ETC.HOSTS file contains an entry for the loopback address. For example:
127.0.0.1 localhost loopback # local address
Check the network configuration files, /etc/hosts and /etc/resolv.conf. These files must be identical to the corresponding files in the BS2000 administrator user ID TSOS. If the files are not identical, then consult your BS2000 system administrator to synchronize the files.
If you are installing Oracle software on your computer for the first time, then you may have to create several BS2000 user IDs, POSIX users, and groups. The BS2000 user ID for the Oracle Database 12c Release 1 software is called the installation user ID. The user ID where an Oracle database is stored is called the Oracle Database Administration (DBA) user ID.
The name of the groups can be:
oracle or oinstall for the Oracle Database installation user.
dba for the Oracle Database Administration (DBA) user.
On BS2000, you can use only one group for both Oracle Database installation and administration. Oracle recommends that you use the installation user ID group, oracle, as the primary group for users who require administrative privileges for Oracle Database administration. However, if you want to use a separate group for the DBA user ID, for example, dba, then you must ensure that dba is the primary group, and the installation user ID group is assigned to the DBA user ID as a subsidiary group.
This section includes the following topics:
The BS2000 system administrator must create an user ID under which you want the Oracle Database 12c Release 1 software to reside. This user ID is called the Oracle installation user ID or Oracle software owner. Throughout this guide, ORACINST is used as a proxy name for the real installation user ID. This user ID does not require any special BS2000 privileges:
You must not use the BS2000 system administrator user ID TSOS as an Oracle Database installation user ID.
The user address space limit must be set to at least 512 MB.
During installation, all files are created with the following file attributes:
USER-ACC=ALL-USERS,ACCESS=READ
You do not need to define write access for any file after installation.
When the BS2000 system administrator creates the installation user ID with the following command, the corresponding POSIX user is also created:
/ADD-USER ORACINST,…
The POSIX user attributes, namely, user number, group number, login directory and program, are assigned default values.
For installation under POSIX, the POSIX administrator or the BS2000 system administrator must create system groups in POSIX. Oracle recommends to use the oracle group for the Oracle software owner. If you want to use the dba group for the Oracle database user, then you must add the group of the software owner, that is, oracle as a supplementary group for the DBA user.
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 of 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. In the above example, it is 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 the group ID is 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 /etc/group file. 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 /etc/group file for the oracle group:
oracle::104:ORACINST,ORACDBA
Add further installation user IDs and all DBA user IDs to the line with the Oracle group ID.
Before using the installation user ID as a POSIX user, the POSIX administrator or the BS2000 system administrator must initialize the POSIX user with the following command:
/ADD-POSIX-USER USER-NAME=installation-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. Oracle strictly recommends to create a separate file system for the POSIX users. An example for a valid HOME-DIRECTORY is /home/oracinst 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.
An Oracle database in BS2000 resides in BS2000 user IDs. This user ID is called the DBA user ID and is different from the Oracle database installation user ID. The BS2000 system administrator must ensure that the DBA user ID has the following attributes and privileges to create or modify the DBA user ID:
ADDRESS-SPACE-LIMIT=1024
Set the following parameters for ACCOUNT-ATTRIBUTES:
MAX-ALLOWED-CATEGORY=TP NO-CPU-LIMIT=YES START-IMMEDIATE=YES
Note:
You must not use the BS2000 system administrator user IDTSOS as an Oracle Database DBA user ID under any circumstances.Oracle recommends that the BS2000 system administrator defines a separate job class for the background and server tasks.
This job class must have the following characteristics:
TP-ALLOWED=YES NO-CPU-LIMIT=YES JOB-TYPE=BATCH START=IMMEDIATELY
The POSIX user for the DBA user ID must be initialized with a unique user number and group number. The group number can be the same as used for the Oracle Database software owner or can be a separate dba group number.
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 "About 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 using 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 using the following BS2000 command:
/ADD-POSIX-USER USER-NAME=dba-user-id,USER-NUMBER=nnn,GROUP-NUMBER=dba-group-number,HOME-DIRECTORY=path[,RLOGIN-ACCOUNT=account]
You can modify the POSIX user attributes of an initialized POSIX user using the following BS2000 command:
/MODIFY-POSIX-USER-ATTRIBUTES USER-ID=dba-user-id,USER-NUMBER=nnn,GROUP-NUMBER=dba-group-number,DIRECTORY=path
Add the new DBA user ID to the DBA group in the /etc/group file. If the DBA group is not present, then you must create a new entry for the DBA group in the /etc/group file as described in “About Creating the POSIX System Group”. Finally, add the DBA user ID to the group of the Oracle Database software owner.
The following example shows the entries for the oracle and dba groups in the etc/group file:
oracle::504:ORAINST,ORADATA dba::505:ORADATA
Note:
Ensure that the home directory does not reside in the root or var file system.
The USER-NUMBER must be unique and greater than 100.
The GROUP-NUMBER must be unique and greater than 100. It can be the same as the Oracle installation group.
The following sections describe about the directories that you must identify or create in the POSIX file system for Oracle Database:
Oracle base directory is a top-level directory for Oracle software installations. Oracle recommends to use only one Oracle base directory for all software installations with a path similar to the following:
/mount_point/app/oracbase
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.
oracbase is used as an example for a significant subdirectory name to show that this is the Oracle base for the software insallations.
If you want to use different Oracle base directories, then you can use the operating system user name of the Oracle software owner as the last subdirectory name.
The components /mount_point/app represent the operating system part of the path. Before you install Oracle Database 12c Release 1, you must create the operating system part of the path.
Note:
The installation user ID and the installation group must have read, write, and execute permissions to the subdirectory app.
During Oracle Database software installation, you are prompted for a valid Oracle base directory. You can accept the default value or enter a new path. The installation procedure creates the Oracle base directory if possible.
Although multiple Oracle installations require separate installation user IDs in BS2000 and separate Oracle home directories, you can always use the same Oracle base directory. For example:
/u01/app/oracbase
See Also:
"Expanding a File System for the Oracle Base Directory" for more information about the POSIX file system
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 computer. 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 /var/opt/oracle/oraInst.loc file. 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/oracbase, 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 app directory.
Note:
All Oracle software installations rely on the Oracle Inventory directory. Ensure that you back it up regularly.
Do not delete this directory unless you have completely removed all Oracle software from the system.
By default, the Oracle Inventory directory is not installed under the Oracle base directory. This is because all Oracle software installations share a common Oracle Inventory, so there is only one Oracle Inventory for all software owners.
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/12.1.0/dbhome_1
The Oracle installation procedure creates the directory path that you specify. It also sets the correct owner, group, and permissions. You do not have to create this directory manually.
Note:
During the installation, you must not specify an existing directory that has predefined permissions applied to it as the Oracle home directory. If you do, then you may experience installation failure due to file and group ownership permission errors.
Before you start the installation, you must either identify the operating system part of an existing Oracle base directory or if required, create one. This section contains information about the following topics:
Note:
You can create an Oracle base directory, even if other Oracle base directories exist on the system.
You can identify the existing Oracle base directories 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
oratab file exists, then it may contain lines similar to the following:
*:/u01/app/orac1020/product/10g:N *:/u01/app/orac1120/product/dbhome:N
The directory paths specified on each line identify Oracle home directories. In the preceding examples, Oracle base directories contain the user name of the Oracle software owner, /u01/app/orac1020 and /u01/app/orac1120 respectively. Oracle recommends to use a single base directory for all Oracle Database installations. For example:
/u01/app/oracbase
Ensure that the Oracle base directory:
Is not on the same file system as the operating system (root or var).
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
Note:
The installation procedure looks for an Oracle base directory and prompts you to accept the suggested path or to enter a new path.
If you want to install Oracle Database into an existing file system with existing Oracle software installations, but the POSIX file system has insufficient space, then the POSIX administrator or the 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:
If you want the Oracle base directory to reside in a new POSIX files system, then the POSIX administrator or the 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:
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 prompts 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 at least create the operating system part of the Oracle base directory and specify the correct owner, group, and permissions for it with the following specifications:
# /mkdir -p /mount_point/app/ # chown oracle_sw_owner:oracle_installation_group/mount_point/app/ # chmod 775 /mount_point/app/
# mkdir -p /u01/app/ # chown oracinst:oracle /u01/app/ # chmod 775 /u01/app/
Oracle Database 12c Release 1 (12.1) software is available in a zipped LMS library. Complete the following steps to install Oracle Database:
Oracle Database installation procedure performs the following actions:
Checks hardware and software requirements.
Checks the available disk space for the BS2000 files and the POSIX files.
Extracts the files from the staging library.
Installs Oracle software in the installation user ID.
Updates the SDF syntax files, if SDF-A is available.
Installs Oracle Database software in the POSIX file system.
Registers the software in the Oracle Inventory file.
The following is the complete syntax of the installation procedure:
/CALL-PROCEDURE ([staging_userid.]ORAxxxxx.S390.LIB,ORAINST.PRC)[,
([CMD={INSTALL|UNINSTALL}]
[,INSTALLATION-TYPE={DATABASE|CLIENT}]]
[,STAGING-UID={''|staging_userid}]
[,ORACLE-BASE={*PROMPT|oracle_base_path}]
[,ORACLE-HOME={*PROMPT|oracle_home_path}]
[,DEBUG={Y|N}])
The following table lists the parameters, their corresponding values, and their description that are used during Oracle Database installation:
| Parameter | Value | Description |
|---|---|---|
|
|
default: |
Install or uninstall Oracle Database. |
|
|
default: |
Types of installation. |
|
|
' '|user ID of staging library default: |
BS2000 user ID where the staging library is located. |
|
|
default: |
The Oracle base directory is required for installing Oracle Database 12c Release 1 in the POSIX file system. The default value |
|
|
default: |
The Oracle home directory is required for installing Oracle Database 12c Release 1 in the POSIX file system. The default value |
|
|
default: |
Debug the installation procedures. |
The installation procedure also provides the opportunity to run the installation as a background task. In this case, you must specify the parameters ORACLE-BASE and ORACLE-HOME, otherwise the installation is aborted. Since the installation takes about 250 CPU seconds, Oracle recommends that you set the CPU-LIMIT to at least 300 seconds. You can start the installation as follows:
/ENTER-PROCEDURE (ORAxxxxx.S390.LIB,ORAINST.PRC),(ORACLE-BASE='/u01/app/oracbase',ORACLE-HOME='/u01/app/oracbase/product/12.1.0/dbhome_1'),CPU-LIMIT=300
When you run the installation as a background task, the installation process is logged to the file INSTALL.ORAINST.LST.
Installing Oracle Database in the POSIX file system requires an ORACLE_BASE and ORACLE_HOME path. During installation you are prompted for these paths, if the installation runs in the dialog mode and if you have not specified the parameters in the procedure call. You can accept the suggested paths or enter new paths.
To complete the installation, the POSIX administrator or the BS2000 system administrator must run the oracle_home_path/root.sh script as follows:
In the BS2000 environment, use the following command:
/EXECUTE-POSIX-CMD CMD='oracle_home_path/root.sh'
For example,
/EXECUTE-POSIX-CMD CMD='/u01/app/oracbase/product/12.1.0/dbhome_1/root.sh'
In the POSIX environment (shell), use the following command:
# sh oracle_home_path/root.sh
For example:
# sh /u01/app/oracbase/product/12.1.0/dbhome_1/root.sh
If this is the first Oracle Database installation on the BS2000 server, then the root.sh script completes the following actions:
Creates the path, /var/opt/oracle
Creates the file, /var/opt/oracle/oraInst.loc
Creates an empty file, /var/opt/oracle/oratab
You can install multiple Oracle databases, based on different releases of Oracle software. In this case, different releases of the software must be installed under different installation user IDs and different Oracle home directories.
To remove Oracle Database software from your computer, log in to the Oracle installation user ID and use the installation procedure as follows:
/CALL-PROCEDURE INSTALL.P.ORAINST,(CMD=UNINSTALL)
This procedure completes the following actions:
Removes the Oracle Database software from the POSIX file system.
Updates the Oracle inventory.
Removes the Oracle Database software from the BS2000 file system.
Note:
Only the files installed by the Oracle installation procedure, namely, ORAINST.PRC are removed from the system. Files created by a user or by an Oracle instance are retained in the Oracle home directory and the installation user ID.