Database Reference
In-Depth Information
Step 4
Service definitions and failover policies defined using
SRVCTL
can also be verified using
srvctl
. For example
$GRID_HOME/bin/srvctl config service -d SCDB
■
While the connection descriptions used by FaN can contain the taF definitions, they are ignored by the default
FaN operation. however, they can be programmatically used as a backup option. When the application service does not
receive any event indicating a service failure, the application connection can use taF.
Note
Step 5
For service failover and load balancing, the client side TNS connection description has to be updated with the
appropriate entries either with or without using the TAF feature. Applications connect to an HA service using the TNS
connect descriptor. The service names used in the TNS names configuration should match the service names defined
in Step 1 previously using the
srvctl
utility.
TAPS =
(DESCRIPTION =
(ADDRESS=(PROTOCOL=TCP)(HOST=prddb-scan.summersky.biz)(PORT=1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TAPS)
)
)
Step 6
Listeners should be cross-registered using the
REMOTE_LISTENER
parameter; this is to ensure all listeners are aware
of all services. Similar to the TNS names configuration, the listener should use scan addresses instead of physical
host names.
Step 7
Based on the previous definitions, several applications are sharing instances; each application is to be configured to
run at a specific priority level. Priorities should be defined for the service to enable workload management to set up
when the scheduler should start the job and for configuration of resources.
The first step in the setting up of priorities is the creation of the various consumer groups. In our preceding
example, we would require three different consumer groups:
HIGH_PRIORITY
, which will support all applications
defined in Table
15-5
as having high priority;
STD_PRIORITY
, which will support all applications defined in Table
15-5
Search WWH ::
Custom Search