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
Configuring the database service for virtual network name
Perform the steps given below to configure the database service for the virtual network name.
To configure the database service for virtual network name
- If the file tnsnames.ora does not contain entries for Database Service and Network Name, then create these entries using the Net Configuration Assistant. You must create these entries on all the cluster nodes.
Associate the database with the listener.
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)
Example SQL queries to ensure these entries:
show parameter INSTANCE_NAME show parameter SERVICE_NAME
These parameters are created during installation or database creation.
Use one of the following ways to configure the new attribute listener_alias:
Run the following SQL command:
SQL> ALTER SYSTEM SET LOCAL_LISTENER='<listener_alias>' scope=spfile;
or
Add the following entry to the initialization parameter file (pfile/spfile):
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_name)(Port=default port)))
The listener_alias parameter gets appended by the default domain name specified in the file sqlnet.ora.
Take the listener service and the database service resources offline, and then bring them online.
- Edit the initialization parameter file. For the dispatchers parameter, replace the virtual IP address with virtual name for dispatchers.
If you use PFILE
Edit the dispatchers parameter by adding or editing the HOST parameter. The edited dispatchers parameter should look like:
dispatchers = '(ADDRESS=(Protocol=TCP) (HOST=virtual_name) (other entries))'
Here virtual_name is the name of the Lanman resource.
If you use SPFILE
Log on to the Oracle database as administrator and edit the dispatchers parameter by adding or editing the HOST parameter.
Type the following commands on the command prompt:
C:\>sqlplus "/as sysdba" C:\>alter system set dispatchers = '(ADDRESS=(Protocol=TCP)(HOST=virtual_name)(other entries))' scope=spfile;
Here virtual_name is the name of the Lanman resource.