Install RedHat 2.1 AS/ES
Oracle Application Server Tips by Burleson
Start the installation and select your
language etc. When you arrive at the Disk Partitioning screen,
manually define you disk partitions using Disk Druid. You can
implement RAID 0,1,5 at this time however you must ensure that you
meet the minimum disk space requirement on mount points that you
will use for ORACLE_HOMEs as per the table earlier in the chapter.
Also ensure sufficient /tmp and swap space are defined.
When you get to the Network Configuration
Screen, it is recommended that you assign a static IP address
instead of using DHCP. However if you require the use of DHCP
you must configure the host to resolve the host name using the local
loopback in the /etc/hosts file. We will discuss this later.
The next screen is the Firewall
configuration screen. If the server is behind a firewall then
select ?No Firewall?. If the server is not behind a firewall
and you want to use the OS firewall, I recommend that you still
select ?No Firewall? and configure the firewall after the
application server is installed. If the firewall is active you
must ensure that the ports needed by the installer are open or the
installation will have problems. Once the installation is
completed, you can get a list of used ports from the Application
Server Control website and then configure the firewall.
When you get to the root password screen do
not configure any other users. Continue with the installation
until you get to the Package Group selection screen. Ensure
that you include the following packages.
You should uncheck all other selections.
At the bottom of the screen select the ?Select Individual Packages?
and press Next. Locate the package compat-glibc-6.2-188.8.131.52
and select it. Also locate the Pdksh-5.2.14-13 package (do not
worry if it is an earlier version at this time) and select it.
Continue with the installation selecting to have the server boot to
your preferred desktop (Gnome or KDE).
Configure RedHat 2.1 AS/ES
Update Installed Packages
When the OS reboots after the install,
select the correct kernel for you system. Log on as root and
run the Red Hat update program. First run /usr/sbin/rhn_register.
Next run the Update Agent located in the system or system-settings
folder depending on if you are using Gnome or KDE. The Update
Agent will check all the installed packages against the latest
versions and update any needed packages. The Update Agent will
also update the kernel to one optimized for the server processor.
It is important that you select the kernel for update, as the
default is to exclude the kernel. The first time you run the
Update Agent it may take quite a while to complete. Once the
Update Agent has completed, reboot the server to begin using the
Verify Minimum Requirements
The next step is to verify that all packages
meet the minimum requirements to install Oracle Application Server
root]# grep MemTotal /proc/meminfo
MemTotal: 1535772 kB
[root@appsvr root]# grep SwapTotal /proc/meminfo
SwapTotal: 2097136 kB
[root@appsvr root]# df ?k
1k-blocks Used Available Use% Mounted
38362000 3449504 32963812 10% /
101089 22773 73097
767884 0% /dev/shm
35445208 2729792 30914876 9% /u01
38464340 1549752 34960684 5% /u02
As you can see from my example above, this
server has greater than the 1 GB memory and greater that 1.5 GB of
swap space. There is also plenty of disk space for the
installation of both the Infrastructure and Middle tiers. For
performance reasons you should install the Infrastructure on a
separate server but for this example both the Infrastructure and the
Middle tier will be installed on a single server. Next verify
that the kernel is greater than errata 25.
root]# uname ?r
At the time of this install the current
errata is 34. If your kernel is not greater than 25, rerun the
Update Agent and select the kernel for update.
Next we need to verify the other packages.
The easiest way to do this is to use the rpm utility. If you
pass in the ?qa parameters, rpm will list all packages installed on
the server. If you only pass in the ?q parameter you must pass
in the package name (without the version number). You can also
use the grep utility to limit the return of the ?qa parameters.
Ensure that the packages are greater than the minimum required.
If you ran the Update Agent all packages should be greater than the
root]# rpm -q gcc
[root@appsvr root]# rpm -qa |grep gcc
Check each of the required packages.
root]# rpm -qa |grep openmotif
[root@appsvr root]# rpm -qa |grep sysstat
[root@appsvr root]# rpm -qa |grep libstdc
[root@appsvr root]# rpm -qa |grep pdkah
[root@appsvr root]# rpm -qa |grep pdksh
[root@appsvr root]# rpm -qa |grep compat-glibc
The last two packages must be installed.
If rpm does not return anything for pdksh and compat-glibc, you must
install them. Neither are installed by default and both are
found on the Red Hat installation disk 2 under the /RedHat/RPMS
directory. To install a package from the cdrom use the
rpm ?i /mnt/cdrom/RedHat/RPMS/pdksh-5.2.14-13.i386.rpm
rpm ?i /mnt/cdrom/RedHat/RPMS/compat-glibc-6.2-184.108.40.206.i386.rpm
After installing pdksh you can run the
Update Agent to update the package to the latest errata. Also,
the errata number for these packages may be different in your
distribution so ensure that you use the rpm file name from you cdrom.
This is an excerpt from "Oracle
10g Application Server Administration Handbook" by Don Burleson
and John Garmany.