Database Reference
In-Depth Information
For some installations this is fine, but many data centers have their own NTP infrastructure. In that case, the
“server” lines pointing to the pool should be commented out (placing a hash (“#”) symbol at the start of a line), and
lines that point to the local NTP servers should be added. Listing 3-5 shows how to add your own local NTP server.
Listing 3-5. Configure Local NTP Server
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool ( http://www.pool.ntp.org/join.html ) .
#server 0.rhel.pool.ntp.org
#server 1.rhel.pool.ntp.org
#server 2.rhel.pool.ntp.org
server 172.30.0.1
Once the /etc/ntp.conf file is changed, the NTP daemon ( ntpd ) needs to be restarted using the service ntpd
restart command. This will stop the daemon, synchronizing the clock to the NTP source, and will then restart the
daemon.
In oracle Database appliance release 2.2, there is a bug with the ntp being out of sync. refer to note
1489263.1 for solutions to resolve.
Note
Once the ntpd process has restarted, you can verify the communication with the NTP server using the ntpq -p
command. This command will show all the NTP servers the appliance is currently using, as well as the time offset
experienced by each server (see Listing 3-6).
Listing 3-6. Output from the ntpdq -p Command
remote refid st t when poll reach delay offset jitter
==============================================================================
205-196-146-72. 209.51.161.238 2 u 62 64 1 26.872 -2.682 0.001
name1.glorb.com 128.174.38.133 2 u 61 64 1 17.005 -2.099 0.001
ntp1.rescomp.be 169.229.128.214 3 u 60 64 1 77.270 3.740 0.001
LOCAL(0) .LOCL. 10 l 59 64 1 0.000 0.000 0.001
Reviewing Listing 3-6, we see that three external servers and the system clock are in use. The system clock offset
is approximately -2 to 3 seconds off. The NTP daemon ( ntpd ) will now drift the time to get the system clock within one
hundred to two hundred milliseconds of real time.
Grid Infrastructure and Database Installation
At the end of Chapter 2, you were left with an Oracle Database Appliance that was “bare metal” installed. What this
means is that you should now have a clean Oracle Database Appliance running Oracle Enterprise Linux. At this point,
you need to install the Oracle Grid Infrastructure and the Oracle Database software on an Oracle Database Appliance.
How do you do this? Well, since the Oracle Database Appliance is an engineered system, you cannot just download
and install these Oracle products. Oracle provides packages for the installation of these products.
As you begin to look around for the packages to install the Oracle products, you may want to visit My Oracle
Support and download the latest End User Bundle for the Oracle Database Appliance. The End User Bundle
provides an updated version of the Grid Infrastructure and Oracle Database for a “factory shipped” or reimaged
Oracle Database Appliance. Keep in mind, when you begin the download for the End User Bundle, it is a fairly large
download and may take a bit of time to retrieve before you can begin installation.
 
 
Search WWH ::




Custom Search