8.6 V$ACTIVE_SERVICES

V$ACTIVE_SERVICES displays information about the active services in the database.

Column Datatype Description

SERVICE_ID

NUMBER

Service ID

NAME

VARCHAR2(64)

Name of the service

NAME_HASH

NUMBER

Service name hash

NETWORK_NAME

VARCHAR2(512)

Network name

CREATION_DATE

DATE

Creation date

CREATION_DATE_HASH

NUMBER

Creation date hash

GOAL

VARCHAR2(12)

Runtime Load Balancing Goal being used to create run-time load balancing and connection load balancing advice:

  • NONE

  • SERVICE_TIME - Connections are balanced by response time

  • THROUGHPUT - Connections are balanced by throughput

DTP

VARCHAR2(1)

Indicates whether or not Distributed Transaction Processing is enabled for this service. When Distributed Transaction Processing is set to Y (YES), it means that the service is offered at exactly one instance at a time for XA affinity. Possible values:

  • Y - YES

  • N - NO

BLOCKED

CHAR(2)

Indicates whether a service on the specified instance is blocked from accepting new connections altogether (YES) or not (NO). If a service is blocked, then all connections will be directed to other instances (if any) that are hosting the desired service.

AQ_HA_NOTIFICATION

VARCHAR2(3)

Indicates whether FAN - Fast Application Notification for OCI connections is set (YES) or not (NO)

CLB_GOAL

VARCHAR2(5)

Connection load balancing goal used with statistics that are sent to the listeners to determine how new connections are distributed:

  • LONG

  • SHORT

COMMIT_OUTCOME

VARCHAR2(3)

For Transaction Guard and Database Native Transaction Guard, indicates whether the database service associated with the user session has the COMMIT_OUTCOME service attribute enabled (YES) or not (NO). This attribute applies on a per session basis and is set at connect time.

When the value of this column is YES, the commit status is managed for all supported transaction types and the outcome of a COMMIT transaction is preserved after the COMMIT has executed. Refer to the COMMIT_OUTCOME_FASTPATH column to view the preferred method for preserving the commit outcome.

See Also: Oracle AI Database Development Guide for information about preserving the commit outcome

RETENTION_TIME

NUMBER

For Transaction Guard and Database Native Transaction Guard, when COMMIT_OUTCOME = YES, this value indicates the amount of time (in seconds) that the commit outcome is retained in the database.

REPLAY_INITIATION_TIMEOUT

NUMBER

For Application Continuity, this option specifies the difference between the time (in seconds) of original execution of the first operation of a request and the time that the replay is ready to start after a successful reconnect. Application Continuity will not replay after the specified amount of time has passed. This option is intended to avoid the unintentional execution of a transaction when a system is recovered after a long period of time. The default is 5 minutes (300 seconds).

SESSION_STATE_CONSISTENCY

VARCHAR2(128)

Describes how non-transactional is changed during a request. This parameter is considered only if failover_type is set to TRANSACTION for Application Continuity. Examples of session state are NLS settings, optimizer preferences, event settings, PL/SQL global variables, temporary tables, advanced queues, LOBs, and result cache. If non-transactional values change after the request starts, the default value of DYNAMIC should be set. Almost all applications should use DYNAMIC mode. If you are unsure, use DYNAMIC mode.

GLOBAL

VARCHAR2(3)

Indicates whether the service is global. A global service is managed by Global Service Manager (GSM) and can be provided by multiple databases that contain replicated data. Possible values:

  • YES: Indicates the service is global

  • NO: Indicates the service is not global

CON_NAME

VARCHAR2(128)

Container name of the object. The value of this column is NULL in non-CDBs.

SQL_TRANSLATION_PROFILE

VARCHAR2(261)

A non-NULL value specifies the initial SQL translation profile for subsequent database connections that use the service and do not specify a SQL translation profile. A NULL value has no effect.

MAX_LAG_TIME

VARCHAR2(128)

The maximum replication lag (in seconds) that is acceptable for a data replica to be used for providing the database service. Can only be specified for global services.

STOP_OPTION

VARCHAR2(128)

Stop option for sessions of this service for planned maintenance

FAILOVER_RESTORE

VARCHAR2(128)

Indicates whether sessions recover their commonly used session state (like NLS, schema) when they are failed over with TAF

DRAIN_TIMEOUT

NUMBER

Number of seconds to wait for sessions to be drained

TABLE_FAMILY_ID

NUMBER

Sharded table family ID associated with the service

PLACEMENT_TEMPLATE

VARCHAR2(64)

Reserved for future use

COMMIT_OUTCOME_FASTPATH

VARCHAR2(3)

For Transaction Guard and Database Native Transaction Guard, when COMMIT_OUTCOME = YES, the value of this column indicates the preferred method for preserving the commit outcome. Possible values:

  • YES - Database Native Transaction Guard is used. Each transaction is assigned a unique transaction identifier (DB XID) in the database. The DB XID and status of the corresponding transaction are maintained persistently in a transaction table. Note that if COMMIT_OUTCOME = YES, then the value of COMMIT_OUTCOME_FASTPATH defaults to YES.

  • NO - Transaction Guard is used. A logical transaction ID (LTXID) is set for each user session at login and at each successful commit. LTXIDs are used only when the commit is not in the same round-trip to the database as the start of the transaction. Moreover, some transaction types, such as commit on success transactions, DDL transactions, and PL/SQL transactions, will continue to use LTXIDs in the same round-trip. When Transaction Guard is used, the outcome of a COMMIT transaction is known. If there is an outage, the application can use DBMS_APP_CONT.GET_LTXID_OUTCOME to return a reliable status for the last in-flight work.

    See Also: Oracle Real Application Clusters Administration and Deployment Guide for information about logical transaction IDs

TRUE_CACHE_SERVICE

VARCHAR2(64)

True Cache service associated with this database service

PARENT_SERVICE

VARCHAR2(64)

Name of the parent service

TEMPLATE_TIMEOUT

NUMBER

Maximum number of seconds that can pass before templates for the service expire

If the value of this column is 0, then template timeout is turned off.

FAILOVER_TYPE

VARCHAR2(128)

AUTO for Transparent Application Continuity, TRANSACTION for Application Continuity, SESSION or SELECT for TAF.

FAILOVER_METHOD

VARCHAR2(128)

TAF only for compatibility - BASIC or NONE

FAILOVER_RETRIES

NUMBER

For Application Continuity and TAF, when reconnecting after a failure, number of attempts to re-connect per incident

FAILOVER_DELAY

NUMBER

For Application Continuity and TAF, when reconnecting after a failure, delay between each connection retry (in seconds)

RESET_STATE

VARCHAR2(6)

Reset state for the service. Possible values:

  • LEVEL1

  • NONE

AUTO_CONNECTION_REBALANCE

VARCHAR2(7)

Drain setting for service load balancing. Possible values:

  • 0 - DEFAULT

  • 1 - NONE

  • 255 - AUTO

CON_ID

NUMBER

The ID of the container to which the data pertains. Possible values include:

  • 0: This value is used for rows containing data that pertain to the entire CDB. This value is also used for rows in non-CDBs.

  • 1: This value is used for rows containing data that pertain to only the root

  • n: Where n is the applicable container ID for the rows containing data