Database Reference
In-Depth Information
Installing the RPM
With the RPM in place it is time to put the procedure to a test. Transfer GridInfrastructure-12.1.0.1-0.el6.x86_64.rpm
to the test yum repository server and install it using YUM as shown in this example:
[root@server1 ~]# yum install GridInfrastructure-12.1.0.1-0.el6.x86_64.rpm
It will download and install the dependent packages from your repository and install Grid Infrastructure using
the silent response file. If anything goes wrong at any phase, warnings are printed on the screen pointing you to the
correct log file to check. It is recommended to try the procedure in a (virtual?) test environment first before
running live builds.
Installing the Oracle database
After the installation of Oracle Restart has been completed, it is time to focus on the installation of the database
binaries. After all, we want to run a database on our server! The installation process will again be divided into the
same parts as the Oracle Restart installation.
If you just skipped the Oracle Restart part of the chapter, don't worry there will be references to a filesystem-only
database installation in the next chapter. If you have the time please revisit chapter 2 and the first half of this chapter
for an explanation of why I like ASM and recommend it to you.
If you followed the advice laid out earlier in this chapter to use a central staging server, ensure that the installation
binaries are mounted and accessible to the installation. If not, pick a suitable staging area with enough free space and
deploy the downloaded zip files.
Interactive installation of the RDBMS binaries
The same principle already applied to the Oracle Restart installation holds true for the RDBMS installation: the
interactive installer is the best way to get a feel for what's new in a release. Even if you plan to use silent installations
only, it is still recommended to step through the assistants once to generate the response file.
The installation of the RDBMS binaries is usually owned by the oracle account. You need to log out of the grid
account if you still happen to be connected and start the X11 session as explained previously in this chapter. Begin the
installation by starting Oracle Universal Installer similar to the call shown here:
[oracle@server1 ~]$ /mnt/12.1.0.1/database/runInstaller
This command will initiate the bootstrap process and start the graphical user interface.
Security updates
Figure
6-16
shows the security updates screen, which is very similar to the wizard shown with Oracle Restart. The
database installer prompts you to enter your My Oracle Support credentials. For some time now you are prompted to
provide your email address for Oracle to receive security updates and other information from Oracle. Do this at your
own discretion. If you decline the option by unchecking the “I wish to receive security updates via My Oracle Support”
you will be prompted once more to confirm you really want to stay uniformed of advisories. You can normally safely
ignore the warning. Your enterprise monitoring solution should prompt you for security updates anyway (OEM 12
does this for example).
Search WWH ::
Custom Search