InfoScale™ 9.0 Cluster Server Implementation Guide for Oracle - Windows
- Introducing the VCS agents for Oracle and NetApp
- Installing and configuring VCS
- Installing and configuring Oracle
- About installing Oracle
- Prerequisites for installing Oracle
- Installing Oracle
- About creating and configuring Oracle
- Prerequisites for configuring Oracle
- Configuring Microsoft iSCSI initiator
- Managing storage using Windows Logical Disk Manager
- Managing storage using NetApp filer
- Creating a temporary service group
- Configuring Oracle on the first node
- Dismounting a volume
- Bringing the temporary service group online
- Creating the Oracle database on shared disks
- Creating the listener service
- Configuring the listeners to use the virtual IP address
- Associating the database with the listener
- Configuring the Oracle database
- Configuring the Oracle and listener services
- Disconnecting virtual disks from the first node
- Releasing disks (if you use Windows LDM)
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Administering the Oracle service group
- Troubleshooting
- Appendix A. Resource type definitions
- Appendix B. Sample configuration
- Appendix C. Oracle Enterprise Manager 10g Grid Control with VCS
- About Oracle Enterprise Manager 10g Grid Control with VCS
- Installing the VCS agent for Oracle
- Installing Oracle Enterprise Manager server
- Installing Oracle
- Installing the Oracle Management Agent
- Creating and configuring Oracle database and listener on the first node
- Configuring Oracle on failover nodes
- Configuring the Oracle service group
- Configuring a virtual network name
- Configuring the listener for virtual network name
- Configuring the database service for virtual network name
- Configuring an additional Oracle management agent
- Adding the database to the OEM 10g Grid Control
- Making the additional agent highly available
Prerequisites to associate the databases with the listeners
Ensure that the initialization parameter file contains the following entries:
SERVICE_NAMES (the name of the database service)
INSTANCE_NAME (the name of the database instance)
These parameters are created during installation or database creation.
To associate the database with the listener
- Configure a new attribute listener_alias. The listener_alias value should be unique; it should be different from the listener name.
Run the following SQL commands.
Set the SID name.
Type the following on the command prompt:
C:\>set ORACLE_SID=<SID NAME>
Log on to the Oracle database as an administrator.
Type the following on the command prompt:
C:\>sqlplus "/nolog" C:\>sqlplus "/as sysdba"
Configure listener_alias.
Type the following on the command prompt:
SQL> ALTER SYSTEM SET LOCAL_LISTENER='<listener_alias>' scope=spfile;
If you are using a pfile, add the following entry to the initialization parameter file (pfile):
LOCAL_LISTENER = <listener_alias>
- Define the parameter listener_alias. If your Oracle configuration uses the file tnsnames.ora, edit the file as instructed below. The default location of tnsnames.ora is <ORACLE_HOME>\NETWORK\ADMIN.
Add the following to tnsnames.ora file:
<listener_alias>= (DESCRIPTION = (ADDRESS=(Protocol=TCP)(HOST=virtual_IP_address)(Port=port)) )
Here, virtual IP address is the IP address you assigned to the IP resource in the temporary service group and port is the port number you specified while creating the listener. You can check the listener.ora file to find out the port number used. The default value is 1521.
- Stop and restart the database.
The listener_alias parameter gets appended by the default domain name specified in the file sqlnet.ora.