Database Reference
In-Depth Information
DB_DOMAIN
is appended to the network name, unless it is already present. Instance service names
specified with the parameter
NETWORK_NAME
are not case sensitive. The service name as well as
the network name must be unique. Otherwise the error “ORA-44303: service name exists” or
“ORA-44314: network name already exists” is raised. The following sample code creates and
starts a service with the TAF settings used in the previous examples:
SQL> BEGIN
dbms_service.create_service(
service_name=>'TAF_INST_SVC',
network_name=>'taf_inst_svc_net_name',
failover_method=>dbms_service.failover_method_basic,
failover_type=>dbms_service.failover_type_select,
failover_retries=>36,
failover_delay=>12
);
dbms_service.start_service('TAF_INST_SVC', DBMS_SERVICE.ALL_INSTANCES);
END;
/
PL/SQL procedure successfully completed.
The new service is now present in
DBA_SERVICES
.
SQL> SELECT name, network_name, failover_method method, failover_type type,
failover_retries retries, failover_delay delay
FROM sys.dba_services;
NAME NETWORK_NAME METHOD TYPE RETRIES DELAY
------------------ ----------------------- ------ ------ ------- -----
SYS$BACKGROUND
SYS$USERS
TEN.oradbpro.com TEN.oradbpro.com
TAF_INST_SVC taf_inst_svc_net_name BASIC SELECT 36 12
Since the service was started, it's also registered as an active service in
GV$ACTIVE_SERVICES
. This view lists active services for all instances:
SQL> SELECT inst_id, name, network_name, blocked
FROM gv$active_services
WHERE name NOT LIKE 'SYS$%';
INST_ID NAME NETWORK_NAME BLOCKED
------- ---------------- --------------------- -------
1 TAF_INST_SVC taf_inst_svc_net_name NO
1 TEN.oradbpro.com TEN.oradbpro.com NO
2 TAF_INST_SVC taf_inst_svc_net_name NO
2 TEN.oradbpro.com TEN.oradbpro.com NO
The database domain name (
DB_DOMAIN)
“oradbpro.com” was appended to the network
name, since it lacked a domain suffix. The network name was also added to the list of instance
service names in the parameter
SERVICE_NAMES
.
