You also have to perform some post-installation tasks on your new software. This includes tasks such as editing the initialization and oratab files (under UNIX) and tuning your new instance as needed for your particular environment. You have to set up your user accounts to access the Oracle software (setting environmental variables and placing the Oracle executable directory in the search path). Finally, there is a script that has to be run by the operating system administrator to set some final permissions and turn control over to the Oracle user.

The next chapters that are interesting to DBAs performing new software installations are those that contain additional information on the use of Oracle with this operating system (you get to skip the chapters on upgrades until later in this book). The restrictions chapter is designed to show limits for parameters that are operating system-specific, such as the number of files. These chapters provide the details of how Oracle is implemented under your specific operating system. Contents normally include such items as performance tuning and disk configuration.

Finally, there are a number of appendixes that are contained in this book that provide more detailed information about the installer software, troubleshooting, and multilingual options. I tend to read these sections only when I run into a problem. However, these sections may be of interest to you, especially if you are not using American English, which is the default that I have always used.

The installation manuals are not fancy, glossy, and bound like most of the Oracle documentation (they are often printed and bound with binding tape), and they go to press well before the software is actually ready for shipping. I have found a number of important changes that are referenced only in the README file. So always read the README file after it has been off-loaded from tape. Of course, if you have a CD-ROM drive, you can read the README file before you do the installation—which is even better.

The Installation Manual is essential reading both for planning and performing the installation. I have to warn you that this discussion is based on the installation processes that I have seen using versions of Oracle up through 8.0. There is always the chance that Oracle will completely revise its installation processes and documentation just to put experienced DBAs on a level playing field with beginners. Figure 5.1 depicts the installation process.

Figure 5.1.  Oracle new installation process overview.

The README File

The stated purpose of the README file is to show the differences between the actual release of the Oracle RDBMS and related products (SQL*Plus, Server Manager, Import, Export, SQL*Loader, and PL/SQL) and the documentation. This documentation has been prepared well in advance of the product release to provide time for the printers and editors to review the material. Although the main features of a given release are fixed early in the development cycle (for example, table partitioning in Oracle8), many of the other features wait until fairly late in the product cycle. Many bugs are fixed after the main coding is done on the software. The README file is the only way you know what has been done since the installation manuals were sent to press.

The README file is also the best reference for the list of bugs fixed in the product and any final restrictions that were placed on this product since the manuals were published. The table of contents for this README file usually looks something like the following:

•  A list of documentation available

•  Forward- and backward-compatibility notes

•  Changes made to the Oracle server

•  Upgrading and downgrading notes

•  A list of bug fixes and enhancements in this release

•  Known server restrictions

•  Additional detail on topics that are pertinent to this release and platform