Database Reference
In-Depth Information
To use VNC you need to install the vnc server on the database server. In Oracle Linux 6, the VNC package to be
used is called
tigervnc-server
. Install it using
yum
as usual. Once the software is installed, start a VNC server session
on the database host. Each of these will create a new display ID, as shown in the example below:
[grid@server1 ~]$ vncserver
You will require a password to access your desktops.
Password: <not shown>
Verify: <not shown>
New 'server1.example.com:1 (grid)' desktop is server1.example.com:1
Creating default startup script /home/grid/.vnc/xstartup
Starting applications specified in /home/grid/.vnc/xstartup
Log file is /home/grid/.vnc/server1.example.com:1.log
As you can see the VNC server is started on display one. Subsequent VNC server sessions started will increment
that counter and start on the next available display. To connect to the VNC server process, start a VNC client on your
workstation and provide the connection string, such as server1.example.com:1. The RealVNC client which is probably
the most widely spread viewer has not been updated for quite some time, and the free edition is still at version 4.1.3
but works even with tigervnc used in Oracle Linux 6. The viewer does not require an installation and comes as a
binary executable of only a few hundred KiB in size.
The neat aspect about the use of VNC is that it does not require a lot of bandwidth to work properly, and a
network glitch does not ruin your installer session. Just like a Microsoft Terminal Server session you can resume where
you left off.
Installing Oracle Restart
Beginning with 11g Release 2 Oracle has rolled up the installation of Automatic Storage Management (ASM) and
Clusterware into one single Oracle home. The new installation type is called Grid Infrastructure, which can be
installed either for a standalone host in which it is called “Oracle Restart”, or it can be installed for a Real Application
Cluster. There are good reasons to install Oracle Restart, even if you are not planning to use RAC. First of all, it gives
the administrator a unified interface to his environment: the commands to administer Oracle Restart are identical
to the ones the RAC DBA uses. Also, there is no more problem with automatically starting the listener and/or the
database when the server reboots; it happens automatically. All these entities are registered in the Oracle Restart
metadata from where they can be processed during boot and shutdown. And the best is: Oracle Restart behaves
identically regardless of the platform. A server reboot is guaranteed to finish with the start of the database instances
and the listener. Oracle Restart works really well in standardizing environments, which is one of the ideas of this topic.
Interactive installation of Oracle Restart
The interactive installation is the recommended way to get a “feeling” for the new installer. Interactive installation
can also be used to create a response file which is going to be used later for the silent installation. The standard
layout of the database servers in terms of file system layout and permissions will make it very easy to perform a
silent installation.
Log on to the database server as the grid user. Follow the steps as described earlier in this chapter in section
“Configuring your graphical user interface” to create a GUI environment; using your terminal session start the Oracle
Universal Installer.
Search WWH ::
Custom Search