mkdir /tmp/cdrom /tmp/RPM_LISTS
mount /dev/cdrom /tmp/cdrom
ls /tmp/cdrom/Enterprise/RPMS> /tmp/RPM_LISTS/rpmsdisk1.txt
umount /tmp/cdrom


grep MemTotal /proc/meminfo multiplied by 512

1. Add the missing RPMs.  For each of your CDs, make a list of the enclosed RPMs.
   mkdir /tmp/cdrom /tmp/RPM_LISTS
mount /dev/cdrom /tmp/cdrom
ls /tmp/cdrom/Enterprise/RPMS> /tmp/RPM_LISTS/rpmsdisk1.txt
umount /tmp/cdrom

   When you are done with this, you will have 4 files labeled

   rpmsdisk1.txt, rpmsdisk2.txt, rpmsdisk3.txt and rpmsdisk4.txt

   that you will be able to grep inorder to find the RPMs that you need that were omitted from the original install.  Alternatively, you could download all the RPMs into one place where you could retrieve them without having to shuffle through CDs.
   
   If you cleverly took notes while reading several of the Install Guides, you probably already have a nice long list of the additional RPMs you will need.  Check first to find out if they are already installed on your server.
   
   I created a LONG script that checked for all my missing RPMs the first time I ran it; and verified the installation the last time I ran it.  Maybe you can create a better one.  Here are a few sample lines from that script:
   
   # rpm_chech.sh
# Oracle required RPMs for RedHat Enterprise 4
echo "RPM List: find RPMs, version listed or later">rpmlist
echo "">>rpmlist
echo "Checking first for x86_64 RPMs">>rpmlist
echo " CHECKING FOR binutils-2.15.92.0.2-10 ">>rpmlist
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' binutils >>rpmlist
rpm -V binutils>>rpmlist
echo " CHECKING FOR xscreensaver-4.18-5.rhel4.2 ">>rpmlist
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' xscreensaver >>rpmlist
rpm -V xscreensaver >>rpmlist
echo "">>rpmlist

echo "The following RPMs need to be installed as both i386 and x86_64">>rpmlist
echo " CHECKING FOR libaio-0.3.96 ">>rpmlist
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' libaio >>rpmlist
rpm -V libaio >>rpmlist
echo " CHECKING FOR xorg-x11-Mesa-libGL-6.8.2.1.EL.13.20.i386.rpm ">>rpmlist
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' xorg-x11-Mesa-libGL >>rpmlist
rpm -V xorg-x11-Mesa-libGL >>rpmlist
echo "">>rpmlist

echo "The following RPMs require i386 versions installed">>rpmlist
echo " CHECKING FOR expat-1.95.7-4.i386 ">>rpmlist
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' expat >>rpmlist
rpm -V expat >>rpmlist

   BTW, I created this script by putting the list of required RPMs into a spreadsheet and sorting them by whether x86_64 or i386 was required (or both). Then I transferred the list into a plain text file and ran a quick script on that to generate the long rpm_check.sh.
   
   The benefit of doing it this way is that if I discovered that some of the RPMs in my list were wrong, or misplaced, regenerating the script with corrected values was easy.  Also, if I decided to use a different version of Unbreakable Linux, rewriting the script was just a matter of repopulating the spreadsheet with new RPM names.
   
   The weakness of this particular script is that the final verification must be done by eye in the rpmlist file.  Although it would be possible to read the file with another script, I prefer the check by eye.
   
   
2. Modify the values of several config files in /etc.  See script:  runMeFixEtc.sh
   Make sure you read the script before running it.  You might want to hand-modify /etc/pam.d/login and make sure you figure out your own value for kernel.shmmax in /etc/sysctl.conf
   
   
3. Make sure your Minimum Values have been properly set in the kernel.  See script:  kernelparam.sh
   Read this file before running it.  Check out /etc/sysctl_conf_original and make sure you aren't setting any values lower than your own system defaults.
   
   
4. Create the user whose login is oracle.  See script:  create_user.sh
   You absolutely need to read this file before running it.  Make sure you modify the script so that it points to the home directory you want to use for oracle, and the ORACLE_HOME you want to use for the database.  Also, before you run this script, be prepared to supply a password for your new user, oracle.
   
   
5. Modify oracle's login script.  The PATH is probably already set in the .bash_profile file.  It would be better to edit this file by hand.  Either verify that your paths are the same as mine or modify accordingly.
   
   cat >> /opt/oracle/.bash_profile << EOF
# mount_point = /u01

ORACLE_BASE=/u01/app/oracle
export ORACLE_BASE

# UNCOMMENT THESE AFTER INSTALL (verify them first)

# ORACLE_HOME=/u01/app/oracle/product/10.2.0
# export ORACLE_HOME
# TNS_ADMIN=$ORACLE_HOME/network/admin
# export TNS_ADMIN
# DYLD_LIBRARY_PATH=$ORACLE_HOME/lib
# export DYLD_LIBRARY_PATH
# LD_LIBRARY_PATH=$ORACLE_HOME/lib
# export LD_LIBRARY_PATH

ORACLE_SID=db_1
export ORACLE_SID

# PUT YOUR SERVER WITH FULLY QUALIFIED DOMAIN NAME HERE
ORACLE_HOSTNAME=server.fqdomain.com
export ORACLE_HOSTNAME

TEMP=/u01/tmp
TMPDIR=/u01/tmp
chmod a+wr /u01/tmp
export TEMP TMPDIR

umask 022

# Oracle requires that the user oracle's home/bin
# appear in the PATH before /usr/X11R6/bin
PATH=$HOME/bin:$PATH
# Comment the above line out AFTER INSTALL and change it to:
# PATH=$ORACLE_HOME/bin:$PATH

export PATH
unset USERNAME

EOF
   
   
6. Create directories, modify their owners and permissions.  See script:  directoryTweaks.sh
   Make sure you modify the script so that it points to your ORACLE_HOME.
   
   
7. Prepare the Oracle Install files.  Download the Oracle Install files into the directory you have prepared for that purpose.  I used /u01/tmp:

   cd /u01/tmp
   
   # make sure you can run the Oracle Install as the user oracle.
   chown oracle:oinstall oracle_install_file.cpio.gz
   # or, if you have already ungzipped the file
   chown oracle:oinstall oracle_install_file.cpio
   
   # Complete the install as the user oracle.
   su - oracle
   
   # Use one of the following methods to extract the file into the current directory
   zcat oracle_install_file.cpio.gz| cpio -idmv
   # or, if you have already ungzipped the file
   cpio -idmv < oracle_install_file.cpio

   
   
8. Use X11 Forwarding over ssh to install Oracle from a desktop with a terminal into your server.  Maybe.  The install actually runs very smoothly using X11 Forwarding over ssh, that is, provided you CAN run Xll Forwarding over ssh.  If you need an X server on Windows, I would recommmend downloading and installing one.  What Oracle is suggesting you do is sit at a desktop PC (not the server at which you are installing Oracle); open an ssh session, and then run the Oracle installer over that.
   
   If you can't run X11 Forwarding over ssh, you will have to install Oracle at the console.
   
   
   As root, on the console or from a terminal, make sure X11 forwarding is permitted by checking /etc/ssh/ssh_config
   an UNCOMMENTED line in that file should read:
   ForwardX11 yes
   
   or better
   ForwardX11Trusted yes
   
   As root at the database server console, add the fully qualified domain name (or ip address) of PC terminal to xhost
   xhost +desktopname.fqdomain.com
   If you don't know your desktop's ip address, open a DOS prompt and type
   ipconfig
   
   At PC terminal, with SSH Secure Shell Client, open an ssh session and login as the user oracle
   
   then set the DISPLAY variable, the using IP address of PC terminal
   DISPLAY=192.168.0.23:0.0 ; export DISPLAY
   
   Run Oracle installer (as user oracle) from desktop terminal
   cd /u01/tmp/database
./runInstaller
   
   
   • Pay attention to the installer preferences (particularly the ORACLE_HOME path).  If you have gotten this far, you probably already know what kind of database you want to install, etc.  I would like to make one last strong suggestion:  DO install the "sample database".  It is the best way to check after the install that your database can actually run.
     
     
   • Finishing up.  By whatever run it takes, when your database has finally installed successfully, you will want to make some changes to the user oracle's .bash_profile file, set some environmental variables, check that the database is actually running, and then shut it down if you want to install additional components.