Database Reference
In-Depth Information
Listing 3-3. Ping Results from Default Gateway
[root@oak1 ~]# ping 172.30.0.1
PING 172.30.0.1 (172.30.0.1) 56(84) bytes of data.
64 bytes from 172.30.0.1: icmp_seq=1 ttl=64 time=1.31 ms
64 bytes from 172.30.0.1: icmp_seq=2 ttl=64 time=0.245 ms
64 bytes from 172.30.0.1: icmp_seq=3 ttl=64 time=0.255 ms
--- 172.30.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.245/0.606/1.319/0.504 ms
Since the network interfaces for the first node came up, copy the End User Bundle, which was discussed and
downloaded earlier to the temp directory (/tmp ) on the first node. Depending on the network connection between
your client machine and the first node of the ODA, the copy may take several minutes (see Figure 3-3 ). Once the End
User Bundle is transferring, you can continue with configuration.
Figure 3-3. Copying the End User Bundle to the Oracle Database Appliance
Network Time Protocol (NTP) Configuration
Before deploying the database, it is very important to verify that the time between both nodes is accurate and within a
few seconds of each other. The default configuration file (/etc/ntp.conf) that is deployed with the Oracle Database
Appliance is actually valid. The appliance is initially configured to use the public RedHat NTP pool of servers; for
systems access to the Internet, this should keep the time in the Oracle Database Appliance in sync. Listing 3-4
provides the server portion of the NTP configuration file, which has the Oracle Database Appliance pointing to the
RedHat NTP pool.
Listing 3-4. RedHat NTP Pool
# 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
 
Search WWH ::




Custom Search