You are managing a three-instance policy-managed RAC database PROD. You created a service called GL for the PROD database by using the following command:
oracle@gr7597~]$srvctl add service -d PROD -s GL -g SP1 -c singleton -y manual Examine the following output:
(oracle@gr7597~]$srvctl config database -d PROD -a
Database unique name: PROD
base name: PROD
Oracle home: /u0l/app/oracle/product/11.2.0/dbhome_l cle user: oracle Spfile: +DATA/PROD/ spfil6RACDB.ora Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: SPl Database instances:
Disk Groups: DATA, FRA
Services:
Database is enabled Database is policy managed
[oracle@gr?597~]$ crsctl stat res ora.PROD.db
NAME=ora.PROD.db
TYPE=cluster__resource
TARGET=ONLlNE
STATE^ONLINE on gr7597 ONLINE on gr7602 ONLINE on gr7633
[oracle@gr7597~]S crsctl stat serverpool ora.SPl
NAME=ora.SPl
ACTIVE_SERVERS=gr7S97 gr7 602 gr7633
[oracle@gr7597-JS crsctl NAME=ora.prod.gl.svc
TYPE=ora.service - type
TARGET=ONLINE
STATE=ONLlNE on gr7597
Which three steps are required to enable ODP.NET clients that connect to the GL services to receive FAN High Availability Events?