In this blog post, we are going to rename the Linux host name of an existing Oracle 11gR2 system. We can also use this technique to change the IP address of our host.
Host renames are a useful technique in virtualized environments, where vCenter may be used to clone entire hosts including the Oracle databases installed on them. This technique will also work with physical hosts should you wish to simply rename an existing Oracle host.
In this blog post, we are going to silently install Oracle 220.127.116.11 64-bit on RedHat 6.0 using VMWare Workstation 8.
This install demonstration is going to use the silent install mode for all components. At least within the guest VM, at no point will we use a GUI for the install. We will need to use the VMWare GUI to create the VM, install the OS and add disks.
With the increasing use of VMWare, many organizations are looking to automate the deployment of Oracle database environments for development, test or validation. And increasingly DBAs are being tasked with automating the provisioning process.
You installed the Grid Infrastructure using the silent software-only option:
./runInstaller -silent -force -responseFile $HOME/grid.rsp
When you try to create the ASM instance and a diskgroup, the asmca command fails with:
Error while detecting Oracle Grid Infrastructure.
ASMCA needs Oracle Grid Infrastructure to configure ASM.
This is because the CRS components still need to be configured, you can do this as the root user as follows:
[root@localhost ~]# $ORACLE_HOME/perl/bin/perl -I \
$ORACLE_HOME/perl/lib -I \
Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params
Creating trace directory
LOCAL ADD MODE
Creating OCR keys for user 'oracle', privgrp 'oinstall'..
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
CRS-4664: Node localhost successfully pinned.
Adding Clusterware entries to upstart
localhost 2013/01/10 15:06:48 /u01/app/11.2.0/grid/cdata/localhost/backup_20130110_150648.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server
Once this is done, the asmca command can be run successfully.
During the install of Oracle 18.104.22.168, the installer pre-requisite check fails on the NTP daemon configuration.
Network Time Protocol (NTP) – This task verifies cluster time synchronization on clusters that use Network Time Protocol (NTP).
Error: – PRVF-5507 : NTP daemon or service is not running on any node but NTP configuration file exists on the following node(s): localhost –
Cause: The configuration file was found on at least one node though no NTP daemon or service was running. –
Action: If you plan to use CTSS for time synchronization then NTP configuration must be uninstalled on all nodes of the cluster.
To address this, remove the /etc/ntp.conf file. This will allow the use of CTSS for time synchronization.
[root@localhost ~]# cd /etc
[root@localhost etc]# mv ntp.conf ntp.conf.bak
While trying to install Oracle on a Red Hat 6.0 system, running on VMWare, you might encounter the following error:
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x00007fd0b80d0d70, pid=2951, tid=140533187077904
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_30-b03 mixed mode)
# Problematic frame:
# C [ld-linux-x86-64.so.2+0x14d70]
# An error report file with more information is saved as hs_err_pid2951.log
# If you would like to submit a bug report, please visit:
To resolve this problem, execute the following before launching runInstaller
$ export LD_BIND_NOW=1
The installer will run normally.
This problem has been reported with Oracle 22.214.171.124 and Oracle 126.96.36.199