Install guide

# Cold Failover VIP
192.168.1.60 hacf-vip
192.168.1.160 rac5
192.168.2.160 rac5-priv
192.168.2.5 rac5-jlo
192.168.1.161 rac6
192.168.2.161 rac6-priv
192.168.2.6 rac6-jlo
5.3.2.1. listener.ora Configuration
The listener is managed by the rgm anager package, but the functionality is determined by the Oracle
configuration file, listener.ora. T he bolded LIST ENER tag in the file is the specific name of this
listener instance. T his is the default, but this can be changed, and often is, when there is more than 1
SQL*Net Listener service for this database.
LISTENER =
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=hacf-vip)(PORT=1521)) #1521 is too common
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = ed) # Needs to match DBNAME in inited.ora
(ORACLE_HOME = /ff/11g/db)
(SID_NAME = ed) # Needs to match the instance’s ORACLE_SID
)
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /ff/11g/db)
(PROGRAM = extproc)
)
)
The Listener must listen on the VIP, not on the host-specific public interfaces. T he connecting clients
use an SQL*Net tnsnames.ora configuration file that contains an alias that directs them to the virtual
IP. The location of the database instance is now transparent to clients.
rhcs11g=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = hacf-vip)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME =ed) # This is the ORACLE_SID
)
)
Most JDBC clients do not install Oracle client libraries, so must use the T hin client driver. (More
advanced JDBC connectivity does require an Oracle client install). For JDBC thin, the connection string
cannot use the SQL*Net alias, but must encode the same information:
… getConnection (“jdbc:oracle:thin:@hacf-vip:1521:ed”, “scott”, “tiger”)
Red Hat Enterprise Linux 5 Configuration Example - Oracle HA on Cluster Suite
4 0