Linux Setup: Installation

Installing Red Hat Linux 9, Red Hat Advanced Server 2.1/3.0 and UnitedLinux is very similar. They each involve eight principal areas for planning and consideration. The areas are noted below.

 Hardware Compatibility
Review of Linux hardware compatibility issues.

 Network Setup
Verify & update network settings.

 Disk Partitions
Quick course on UNIX disk partitions.

 Firewall Selection
Overview of firewall options.

 Installation Steps
Step-by-step installation guide.

 Account Management
Overview on account management.

 Boot Loader
Quick course on Linux boot loaders.

 Package Selection
Quick course on package selection.


Red Hat Linux UnitedLinux 1.0
AS 2.1 AS 3.0
 Install Step-by-step  Install Step-by-step  Install Step-by-step
 Post-install Oracle9i  Post-install Oracle9i  Post-install Oracle9i
 Post-install Apps 11i  Post-install Apps 11i  Post-install Apps 11i


  • Installation Steps: Red Hat Linux AS 3.0
There are 28 steps to install the Red Hat Linux Advanced Server from the production CDs. They are listed below.

  1. Select Installation.
Choose to install the software. Red Hat's installation program will than complete a pre-check and attempt to start the Anaconda installation tool in GUI mode. If it fails at this point, there are several things that may be wrong. A brief list of the most likely causes is below.

Issue The Video card is not supported.
Solution Anaconda will run in text mode.

Issue The Motherboard is not supported.
Solution Replace the motherboard.

Issue The plug-and-play feature of the system BIOS is disabled and Anaconda cannot probe devices.
Solution Edit the BIOS configuration and reboot the system.

Issue The Network Interface Card (NIC) may not be supported by the plug-and-play installation.
Solution Two alternatives exist. One is to continue with the installation, then attempt to install a driver for the NIC card after installing the operating system. Another is to replace the NIC card.

In Red Hat Linux AS 3.0, there is a problem with the apic.c file used in building NIC driver files. If the machine is using a on-board NIC card, disable APIC in the machine BIOS before doing the installation. The on-board NIC card will not be accessible and another card is required to use the network. This occurs because APIC dynamically manages IRQ assignments, which are not properly support in Red Hat Linux AS 3.0.

Issue The memory, while recognized in the BIOS, may not be recognized by Red Hat.
Solution Verify that the memory is supported by the motherboard. Sometimes the BIOS registers memory that it cannot address. If the motherboard supports the amount of memory, replace the memory.

  1. Welcome to Red Hat Enterprise Linux.
  1. Review the release notes.
A quick snapshot of known errors and workarounds are provided but PLEASE review the release notes.

Known Problem Areas
  • Sun JRE prior to version 1.4.1
  • IBM JRE
  • Software using errno, h_errno and _res must include the appropriate header files (errno.h, netdb.h, resolv.h respectively).
  • Multi-threaded C++ programs using thread cancellation.
  • C++ programs using the C runtime environment may need to be rewritten to manage cancellation (release notes contain suggestions).
  • A Native POSIX Thread Library (NPTL).
  • Non-compliant code will trigger the following application error to console and in the system log files when using workarounds:
> application bug: () has SIGCHLD
> set to SIG_IGN but calls wait(). (see the NOTES
> section of 'man 2 wait'). Workaround activated.

Known Workarounds
  • Workaround to Native POSIX Thread Library (NPTL) Model is to set the:

    LD_ASSUME_KERNEL=<kernel-version>

    ONLY a kernel version of 2.4.19 will work if modules are missing #include references to errno, h_errno and _res header files.

  • Non-compliant code will trigger the following application error to console and in the system log files when using workarounds:
> application bug: () has SIGCHLD
> set to SIG_IGN but calls wait(). (see the NOTES
> section of 'man 2 wait'). Workaround activated.

  1. Close the release notes.
  1. Click the Next button.
  1. Language Selection.
Choose English and then click the Next button.
  1. Keyboard Configuration.
Accept the probe results unless they look wrong. Then, click the Next button.

The values are generally these:

  • Generic 105-key (Intl) PC
  • U.S. English
  • Enable dead keys
  1. Mouse Configuration.
Accept the probed result unless it is wrong and click the Next button.

  1. Disk Partitioning Setup.
There are three choices, as noted below. It is recommended that Disk Druid be used to configure partitions. If partition strategies are new, please refer to the partition section.

  • Have the installer automatically partition for you.
  • Manually partition with Disk Druid.
  1. Partitions.
If partitions exist and this is not a recovery of a file system, delete all existing partitions. This is done by selecting a partition by clicking on it and then clicking the Delete button. Disk Druid also requires deletion of the extended partition.

The Reset button undos changes. The Make RAID should be left to expert users.

Use the New button to build a partition or Edit button to modify a newly created partition as noted below. When all partitions have been made, click the Next button.

Category Selection Criteria
Mount Point Select from the list where possible. If partition strategies are new, please refer to the partition section.
Filesystem Type ext3
Allowable Drives If using multiple disks, deselect the disks that are not the target disk.
Size (MB) Enter the desired size in megabytes.
Additional Size Options For all but the last partition, fixed size should be selected. The last partition should check the Fill to maximum allowable size radio button.

Radio Buttons Context Fields
Fixed size  
Fill all space up to (MB) Enter value if selected.
Fill to maximum allowable size  

Checkboxes Force to be a primary partition Do not check this box.
Check for bad blocks Suggested if disks are old or transferred from another system.

  1. Boot Loader Installation.
  1. Change boot loader.
Use the GRUB boot loader.
  1. Edit the boot partition.
Accept the probed results. Click Next button to continue.

If changes are required, the following should be clearly understood.

Category Selection Criteria
Boot Loader Configuration Use GRUB as the boot loader. This is the default for all Red Hat installations.
Default Partition
Category Selection Criteria
Default boot target This checkbox should be checked.
Boot label This should read "Red Hat Enterprise Linux AS".

  1. Use a boot loader password.
DO NOT USE a GRUB password. Leave the checkbox unchecked.
  1. Configure advanced boot loader options.
ONLY change the advanced boot loader options if you have specialized knowledge and needs.
  1. Network Configuration.
  1. Network Devices.
Click the Edit button. Then do the following steps.
  1. Uncheck the Configure using DCHP checkbox.
  1. Enter an IP Address and Netmask.
Name Value
IP Address Enter the IP address, which is four numbers separated by periods. The numbering sequence is called dotted quad format. Each number has a valid range between 1 and 254. When the IP address is entered, it will automatically populate the Netmask value with a default value of 255.255.0.0. This is an incorrect value that will change as qualified below.
Netmask The default netmask is used for a Class B Internet addressing schema. If installing in a contained test network, use a value of 255.255.255.0. If installing on the Oracle network use a value of 255.255.252.0, which is a four-bit network value.
  1. Click the OK button.
  1. Set the hostname manually.
Name Value
Hostname The hostname should be registered with the DNS servers.
  1. Enter the following values.
Name Value
Gateway The gateway is the bridge point for the subnet network to the wide area network.
Primary DNS The primary Domain Name Server. When the user clicks on the Hostname field, the installation automatically populates the Primary DNS value as the Network value plus 1, or the value of 144.1.154.1 based on the example above.
Secondary DNS The secondary Domain Name Server, which is accessed when the primary DNS server is unavailable.
Ternary DNS The ternary Domain Name Server, which is accessed when the primary and secondary DNS servers are unavailable.
  1. Click the Next button.
  1. Firewall Configuration.
Inexperienced users and those protected within a firewall should click the No firewall radio button. Do not attempt to configure firewall rules, they do not work when done during the installation.

The default in Red Hat Enterprise Linux AS 3.0 is to enable the firewall. Click the No firewall radio button and then the Next button to continue.

  1. Language Support Selection.
Check all languages that should be supported. English is recommended as the default language. Click the Next button to continue.

  1. Time Zone Selection.
Use the map to click a major metropolitan area. Confirm the time zone and click the Next button to continue.

  1. Set Root Password.
Enter a root password twice. Click the Next button to continue.

  1. Selecting Package Groups.
Verify selection of the following packages groups. Care should be taken at package group selection because detecting which packages belong to the installation package groups is significant.

If an error is made in selecting the correct packages during installation, the RPM command-line or GUI RPM (grorpm) tool may be used to install individual packages. Please refer here for instructions.

Select Package Description
Desktops
Yes X Windows System
Yes GNOME Desktop Environment
Yes KDE Desktop Environment
Applications
Yes Editors
Yes Engineering and Scientific
Yes Graphical Internet
Yes Text-based Internet
No Office/Productivity
Yes Sound and Video
Yes Authoring and Publishing
No Graphics
No Games and Entertainment
Servers
Yes Server Configuration Tools
Yes Web Server
Yes Mail Server
Yes Web Server
Yes Windows File Server
No DNS Name Server
Yes FTP Server
No SQL Database
No MySQL Database
No News Server
No Network Servers
Yes Legacy Network Server
Development
Yes Development Tools
No Kernel Development
Yes X Software Development
No GNOME Software Development
No KDE Software Development
Yes Legacy Software Development
System
Yes Administration Tools
Yes System Tools
Yes Printing Support
Miscellaneous
No Everything
No Minimal

  1. About to Install
Click the Next button to continue.

The system will prompt for Disk #2, Disk #3 and Disk #4 to install package groups selected above. When all packages are installed, the system will prompt for Disk #1. After inserting it, the remaining configuration of the installation will be done.

  1. Video Configuration.
Verify the video card. Red Hat often defaults to generic cards. If the specific video card is known, select it. Otherwise, accept the probed generic card selected and click the Next button.

  1. Monitor Configuration.
If not probed successfully due to a swith box, the Monitor Configuration screen will display. If an unprobed monitor is selected, please select the correct monitor.

  1. Customize Graphics Configuration.
  1. Check the Color Depth desired.
  1. Check the Screen Resolution desired.
  1. Chick the Next button.
  1. Congratulations.
Click the Exit button to complete installation.

  1. Welcome.
Click the Next button.

  1. License Agreement.
Click the Yes radio button and Next button.

  1. Date and Time.
Verify and change date if necessary. DO NOT CHECK the enable network time protocol within the Oracle firewall.

Click the Next button.

  1. User Account.
DO NOT SETUP user accounts because they will by default have their own group as opposed to the generic users group. Click the Next button.

A warning message will display, click the Continue button.

  1. Red Hat Network.
If a test server, choose to not register the system and the Next button.

  1. Additional CDs.
Skip these installs and click the Next button.

  1. Finish Setup.
Click the Next button to complete installation setup.

  1. Post-Installation.
After rebooting the system, configure the /etc/resolv.conf file and add the domain to the file. If this is not added, outgoing telnet and ftp will fail notwithstanding their configuration. If networking concepts are new, please go here to the short course. Below is an example for an Oracle internal installation.

 domain        us.oracle.com


  • Post-installation Oracle9i Steps: Red Hat Linux AS 3.0
  1. Verify required packages are installed.
The following packages must be installed before running the Oracle Applications 11i installation. The presence of these packages on the system may be done as follows:

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
compat-db-4.0.14-5.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-gcc-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-gcc-c++-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-glibc-7.x-2.2.4.32.5.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-libstdc++-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-libstdc++-devel-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
openmotif21-2.1.30-8.i386.rpm  /mnt/cdrom/RedHat/RPMS
setarch-1.3-1.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Install the Java Software Development Kit.
There are many ways to install the Java Software Development Kit (SDK) on Linux. Please refer to the Java Administration section.

  1. Verify ksh shell is installed if using Oracle Discoverer.
The Oracle Discoverer product requires ksh software. If it is not installed, install it as follows:

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
pdksh-5.2.14-13.i386.rpm pdksh-5.2.14-21.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Change default GNU c and c++ compilers.
Red Hat Linux Advanced Server 3.0 ships with the default GNU c and c++ compilers set to version 3.23. Oracle9i and Oracle Applications 11i require the GNU c and c++ compiler 2.96. The older version compilers are provided in compat- packages installed in Step #1 above. The following steps switch the default GNU c++ compilers from version 3.23 to 2.96.

  1. Rename the /usr/bin/gcc and /usr/bin/g++ executables.
 # mv /usr/bin/gcc /usr/bin/gcc323
 # mv /usr/bin/g++ /usr/bin/g++323

  1. Create symbolic links to /usr/bin/gcc296 and /usr/bin/g++296 executables.
 # ln -s /usr/bin/gcc296 /usr/bin/gcc
 # ln -s /usr/bin/g++296 /usr/bin/g++
  1. Verify hostname is fully qualified.
  1. Verify hostname contains the hostname and domain name.
 # hostname

 hostname.domainname

  1. Change the hostname to a fully qualifed hostname.domainname.
  1. Edit the /etc/sysconfig/network file.
Prior to File Edit
 HOSTNAME=hostname

After File Edit
 HOSTNAME=hostname.domainname

  1. Edit the /etc/hosts file.
Prior to File Edit
 127.0.0.1       hostname  localhost.localdomain  localhost

After File Edit
 127.0.0.1      hostname  localhost.localdomain  localhost  138.1.145.189  hostname.us.oracle.com

  1. Verify there is NOT an /etc/sysconfig/networking/profiles/default/network file.
If an /etc/sysconfig/networking/profiles/default/network file is found, delete it.

NOTE:
The file is created when the /etc/hosts file is altered in error. The error occurs when the 127.0.0.1 loopback line is changed to point to the hostname.domain name and the machine is rebooted.

After correcting the error in the /etc/hosts file, Red Hat Linux Advanced Server does not delete it automatically on reboot.

  1. Reboot the server to effect the changed hostname.
 # hostname

 hostname.domainname

  1. If the server has more than 16 GB of memory, verify required packages are installed.
Red Hat Linux Advanced Server (AS) 3.0 includes a new kernel known as the hugemem kernel. The kernel supports a 4 GB per process user space as opposed to 3 GB for the other kernels. Additionally, it provides a 4 GB direct kernel space. Using hugemem kernel allows Red Hat Linux AS 3.0 to run on systems with up to 64 GB of main memory. The hugemem kernel is required in order to use memory above 16 GB. The hugemem kernel can be used in systems with less than 16 GB when the system needs to run processes that require more than 3 GB of memory.

If using hugemem kernel, please install the following package.

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
setarch-1.3-1.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Apply Oracle patch to provide libcwait.so library file.
Apply patch number 3006854 to provide libcwait symbol. The patch will build /etc/libcwait.so and ld.so.preload files. The ld.so.preload file loads the /etc/libcwait.so on reboot of the operating system.

If desired, the location of libcwait.so library may be changed to /lib/libcwait.so. The best solution to effecting the change is to alter the script in patch #3006854 before applying the patch. However, if the patch has already been applied, the following steps should be used.

  1. Copy in the /etc/libcwait.so file to /lib directory as the superuser.
 # cp /etc/libcwait.so /lib/libcwait.so
  1. Edit the /etc/ld.so.preload file as the superuser to point to the copied file.
Prior to File Edit
 /etc/libcwait.so

After File Edit
 /lib/libcwait.so

  1. Remove the /etc/libcwait.so file as the superuser.
 # rm /etc/libcwait.so
  1. Create an Oracle Installer group account.
Help to build user and group accounts may be found here.

  1. Create an Oracle user account.
Help to build user and group accounts may be found here.

  1. Modify the Oracle user account environment.
The following instructions qualify required environment files. Expanded coverage of environment files in various shells is found here.

  1. Add a setarch command to the Oracle user's environment.
The following command needs to be run in the Oracle user environment before attempting to install Oracle9i or Oracle Applications 11i if using the hugemem kernel. The command may be included within the user environment file or issued at the command-line as follows:

 # setarch i386

  1. Set the $LD_ASSUME_KERNEL in the Oracle user's environment.
The following command needs to be run in the Oracle user environment before attempting to install Oracle9i or Oracle Applications 11i. The command may be included within the user environment file or issued at the command-line as follows in bash shell:

 # export set LD_ASSUME_KERNEL=2.4.19

  1. Install Oracle9i with the Oracle Installer.
Please refer to the release notes and documentation for running Oracle Installer utility.

  • Post-installation Applications 11i Steps: Red Hat Linux AS 3.0
  1. Verify required packages are installed.
The following packages must be installed before running the Oracle Applications 11i installation. The presence of these packages on the system may be done as follows:

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
compat-db-4.0.14-5.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-gcc-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-gcc-c++-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-glibc-7.x-2.2.4.32.5.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-libstdc++-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
compat-libstdc++-devel-7.3-2.96.122.i386.rpm  /mnt/cdrom/RedHat/RPMS
openmotif21-2.1.30-8.i386.rpm  /mnt/cdrom/RedHat/RPMS
setarch-1.3-1.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Install the Java Software Development Kit.
There are many ways to install the Java Software Development Kit (SDK) on Linux. Please refer to the Java Administration section.

  1. Verify ksh shell is installed if using Oracle Discoverer.
The Oracle Discoverer product requires ksh software. If it is not installed, install it as follows:

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
pdksh-5.2.14-21.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Change default GNU c and c++ compilers.
Red Hat Linux Advanced Server 3.0 ships with the default GNU c and c++ compilers set to version 3.23. Oracle9i and Oracle Applications 11i require the GNU c and c++ compiler 2.96. The older version compilers are provided in compat- packages installed in Step #1 above. The following steps switch the default GNU c++ compilers from version 3.23 to 2.96.

  1. Rename the /usr/bin/gcc and /usr/bin/g++ executables.
 # mv /usr/bin/gcc /usr/bin/gcc323
 # mv /usr/bin/g++ /usr/bin/g++323

  1. Create symbolic links to /usr/bin/gcc296 and /usr/bin/g++296 executables.
 # ln -s /usr/bin/gcc296 /usr/bin/gcc
 # ln -s /usr/bin/g++296 /usr/bin/g++
  1. Verify hostname is fully qualified.
  1. Verify hostname contains the hostname and domain name.
 # hostname

 hostname.domainname

  1. Change the hostname to a fully qualifed hostname.domainname.
  1. Edit the /etc/sysconfig/network file.
Prior to File Edit
 HOSTNAME=hostname

After File Edit
 HOSTNAME=hostname.domainname

  1. Edit the /etc/hosts file.
Prior to File Edit
 127.0.0.1       hostname  localhost.localdomain  localhost

After File Edit
 127.0.0.1      hostname  localhost.localdomain  localhost  138.1.145.183  hostname.us.oracle.com

  1. Verify there is NOT an /etc/sysconfig/networking/profiles/default/network file.
If an /etc/sysconfig/networking/profiles/default/network file is found, delete it.

NOTE:
The file is created when the /etc/hosts file is altered in error. The error occurs when the 127.0.0.1 loopback line is changed to point to the hostname.domain name and the machine is rebooted.

After correcting the error in the /etc/hosts file, Red Hat Linux Advanced Server does not delete it automatically on reboot.

  1. Reboot the server to effect the changed hostname.
 # hostname

 hostname.domainname

  1. If the server has more than 16 GB of memory, verify required packages are installed.
Red Hat Linux Advanced Server (AS) 3.0 includes a new kernel known as the hugemem kernel. The kernel supports a 4 GB per process user space as opposed to 3 GB for the other kernels. Additionally, it provides a 4 GB direct kernel space. Using hugemem kernel allows Red Hat Linux AS 3.0 to run on systems with up to 64 GB of main memory. The hugemem kernel is required in order to use memory above 16 GB. The hugemem kernel can be used in systems with less than 16 GB when the system needs to run processes that require more than 3 GB of memory.

If using hugemem kernel, please install the following package.

  1. Use the RPM utility to verify package installation.
 # rpm -qa | grep <value>

Package Name Media Location
Disk # Directory
setarch-1.3-1.i386.rpm  /mnt/cdrom/RedHat/RPMS

  1. Use the RPM utility to install packages.
 # rpm -ivh <Package_Name>
  1. Apply Oracle patch to provide libcwait.so library file.
Apply patch number 3006854 to provide libcwait symbol. The patch will build /etc/libcwait.so and ld.so.preload files. The ld.so.preload file loads the /etc/libcwait.so on reboot of the operating system.

If desired, the location of libcwait.so library may be changed to /lib/libcwait.so. The best solution to effecting the change is to alter the script in patch #3006854 before applying the patch. However, if the patch has already been applied, the following steps should be used.

  1. Copy in the /etc/libcwait.so file to /lib directory as the superuser.
 # cp /etc/libcwait.so /lib/libcwait.so
  1. Edit the /etc/ld.so.preload file as the superuser to point to the copied file.
Prior to File Edit
 /etc/libcwait.so

After File Edit
 /lib/libcwait.so

  1. Remove the /etc/libcwait.so file as the superuser.
 # rm /etc/libcwait.so
  1. Create an Oracle Installer group account.
Help to build user and group accounts may be found here.

  1. Create an Oracle user account.
Help to build user and group accounts may be found here.

  1. Modify the Oracle user account environment.
The following instructions qualify required environment files. Expanded coverage of environment files in various shells is found here.

  1. Add a setarch command to the Oracle user's environment.
The following command needs to be run in the Oracle user environment before attempting to install Oracle9i or Oracle Applications 11i if using the hugemem kernel. The command may be included within the user environment file or issued at the command-line as follows:

 # setarch i386

  1. Set the $LD_ASSUME_KERNEL in the Oracle user's environment.
The following command needs to be run in the Oracle user environment before attempting to install Oracle9i or Oracle Applications 11i. The command may be included within the user environment file or issued at the command-line as follows in bash shell:

 # export set LD_ASSUME_KERNEL=2.4.19

  1. Use rapidwiz to install Oracle Applications 11i.
Please refer to the release notes and documentation for running rapidwiz utility.
  1. Perform required post installation steps.
  1. Shutdown all Oracle Application processes.
The following command shell script will shutdown all processes:

 # <COMMON_TOP>/admin/scripts/<TWO_TASK>_<machine_name>/adstpall.sh apps/<apps_password>

  1. Apply patch number 3212373.
The patch fixes the stubs library and the network make file in the Oracle 8.0.6 home. The patch should be applied as the single user by sourcing <SID>ora/8.0.6/<SID>_<machine_name>.env file. If the patch is applied in a two user installation, the user should be the Application Manager account.

This patch will create a directory and put the following files in the directory.

  • libc-2.1.3-stub.so
  • patch.sh
  • README.txt
Run the patch.sh script with the properly sourced environment. It will do all required file copies and edits to the environment files.

  1. Download and position patch number 3212401.
The patch fixes the stubs for the Oracle 8.0.6 home that supports Developer/2000 6i. Before unzipping the patch, create a directory in your patches directory because the patch does not create a directory and unzips the contents into the working directory.

This patch will put the following files in the present working directory.

  • env_forms60.mk
  • env_graphics60.mk
  • env_reports60.mk
  • readme.txt
  1. Manually apply patch number 3212401.
The patch fixes the stubs library and the network make file in the Oracle 8.0.6 home. The patch should be applied as the single user by sourcing <SID>ora/8.0.6/<SID>_<machine_name>.env file. If the patch is applied in a two user installation, the user should be the Application Manager account.

This patch will put the following files in the present working directory.

  • env_forms60.mk
  • env_graphics60.mk
  • env_reports60.mk
  • readme.txt
The patch does not provide a manual shell script. There are several steps to manually apply the patch. A Bash shell script is provided for *** INTERNAL USE ONLY *** here. If you prefer to do the manual steps, they are:
  1. Archive the old files.
Source the correct environment from <SID>ora/8.0.6/<SID>_<machine_name>.env and run the following commands.
# cp $ORACLE_HOME/forms60/lib/env_forms60.mk \
> $ORACLE_HOME/reports60/lib/env_forms60.mkO

# cp $ORACLE_HOME/graphics60/lib/ env_graphics60.mk \
> $ORACLE_HOME/reports60/lib/ env_graphics60.mkO

# cp $ORACLE_HOME/reports60/lib/env_reports60.mk \
> $ORACLE_HOME/reports60/lib/env_reports60.mkO

  1. Manually copy the files.
Go to the directory where the files have been unzipped. Source the correct environment from <SID>ora/8.0.6/<SID>_<machine_name>.env and copy the files as follows.
# cp env_forms60.mk \
> $ORACLE_HOME/forms60/lib/env_forms60.mk

# cp env_graphics60.mk \
> $ORACLE_HOME/forms60/lib/env_graphics60.mk

# cp env_reports60.mk \
> $ORACLE_HOME/forms60/lib/env_reports60.mk

  1. Manually copy the files.
Go to the directory where the files have been unzipped. Source the correct environment from <SID>ora/8.0.6/<SID>_<machine_name>.env and execute the following commands.
# cd $ORACLE_HOME/forms60/lib; make -f ins_forms60w.mk install

# cd $ORACLE_HOME/graphics60/lib; make -f ins_graphics60w.mk install

# cd $ORACLE_HOME/reports60/lib; make -f ins_reports60w.mk install

# cd $ORACLE_HOME/network/lib; make -f ins_network.mk install

  1. Relink all Oracle Applications executables.
Use the adadmin tool to "Relink Applications programs" from the "Generate Appications Files menu" selection.

  1. Regenerate all .jar files.
Use the adadmin tool to "Generate product JAR files" from "Generate Applications Files menu" selection.

  1. Backdown the Korn shell version.
The Oracle Discover processes will not start with the shipped version of pdksh-5.2.14-21 due to a bug with the handling of optional arguments. The pdksh-5.2.14-13 version shipped on Red Hat Linux AS 2.1 will work with 11.5.9.

  1. Secure a copy of the pdksh-5.2.14-13 RPM package.
  2. Uninstall the pdksh-5.2.14-21 RPM package.
  3. Install the pdksh-5.2.14-13 RPM package.
  1. Restart Oracle Applications.
The following command shell script will start all processes:

 # <COMMON_TOP>/admin/scripts/<TWO_TASK>_<machine_name>/adstrtal.sh apps/<apps_password>