Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
oracle_services [2020/10/24 17:46] – andonovj | oracle_services [2020/10/24 18:14] (current) – andonovj | ||
---|---|---|---|
Line 26: | Line 26: | ||
| | ||
| | ||
- | | + | |
| | ||
| | ||
</ | </ | ||
- | Let us break down each parameter here, except the obvious ones (db_unique_name, | + | Let us break down each parameter here, except the obvious ones (db_unique_name, |
* cardinality - Uniform (run the server on ALL instances), Singleton (run it only on one instance at a time) | * cardinality - Uniform (run the server on ALL instances), Singleton (run it only on one instance at a time) | ||
Line 39: | Line 39: | ||
* netnum (RAC / RAC One node only) - Specifies over which network interface the service is provided | * netnum (RAC / RAC One node only) - Specifies over which network interface the service is provided | ||
- | * role (used with Data Guard) - Specifies the condition for automatic starting of the service. If set to PRIMARY and the database role is PHYSICAL_STANDBY, | + | * role (used with Data Guard) - Specifies the condition for automatic starting of the service. If set to **PRIMARY** and the database role is **PHYSICAL_STANDBY**, the service WON'T start automatically. |
* policy - Specified if the service will be authomatic started, of course depending on the " | * policy - Specified if the service will be authomatic started, of course depending on the " | ||
Line 45: | Line 45: | ||
* notification - Enables / Disables Fast Application Notifications (FAN) for OCI Connections. | * notification - Enables / Disables Fast Application Notifications (FAN) for OCI Connections. | ||
- | * failovertype - Enables Application Continuity, if set to " | + | * failovertype - Enables Application Continuity, if set to " |
- | | + | |
- | * clbgoal (Connection Load Balancing Goal) - Indicates to Oracle for what kind of connections this service will handle. Specify SHORT if you will do short transactions and LONG if you will use this service for BATCH jobs. | + | * clbgoal (Connection Load Balancing Goal) - Indicates to Oracle for what kind of connections this service will handle. Specify |
- | * rlbgoal (Runtime Load Balance Goal) - Used by the Load Balance advisor, set to SERVICE_TIME to balance connections by response time. Set THROUGHPUT to balance connections by throughput. | + | * rlbgoal (Runtime Load Balance Goal) - Used by the Load Balance advisor, set to **SERVICE_TIME** to balance connections by response time. Set **THROUGHPUT** to balance connections by throughput. |
+ | |||
+ | * dtp - Indicates whether a distributed transactio processing should be enabled for that service (either singleton in Police managed or Preferred in single instance in Admin managed) | ||
* failovermethod (Oracle RAC Only) - Specifies the TAF Failover method (backward Compatibility). | * failovermethod (Oracle RAC Only) - Specifies the TAF Failover method (backward Compatibility). | ||
+ | |||
+ | * failoverretry (Application Continuity and TAF only) - For Application Continuity and TAF, this parameter determines the number of attempts to connect after an incident. | ||
+ | |||
+ | * failoverdelay (For Application Continuity and TAF Only) - Specifies the delay(in seconds) between reconnect attempts per incident at failover. | ||
+ | |||
+ | * sql_translation_profile - Specifies the SQL Translation Profile for Application moved from Non-Oracle Database to Oracle one. | ||
+ | |||
+ | * global - Indicates whether this is a Global Data Services service. | ||
+ | |||
+ | * maxlag - Maximum replication lag time in seconds. Must be a non-negative integer. The default value is ANY. | ||
+ | |||
+ | * commit_outcome - Enable Transaction Guard; when set to TRUE, the commit outcome for a transaction is accessible after the transaction' | ||
+ | |||
+ | * retention - If **commit_outcome** is set to TRUE, then this parameter determines the amount of time (in seconds) that the commit outcome is retained in the database | ||
+ | |||
+ | * session_state - For Application Continuity, this parameter specifies whether the session state that is not transactional is changed by the application. Oracle recommends a setting of DYNAMIC for most applications. | ||
+ | |||
+ | * replay_init_time - or Application Continuity, this parameter 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. | ||
+ | |||
+ | * pqservice - A comma-delimited list of parallel query service names. | ||
+ | |||
+ | * pqpool - A comma-delimited list of parallel query server pool names | ||
+ | |||
+ | Phew, that was something. I am sure, I am missing something, for a complete list you can check: [[https:// | ||
+ | |||
+ | Now let's check the administer based. I will discuss only the missing / different parameters | ||
+ | |||
+ | =====Admin Managed===== | ||
+ | The command to add a service in admin managed database is pretty similiar: | ||
+ | |||
+ | < | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | * preferred (Oracle RAC Only) - List of preferred instances where the service to run. The list of preferred instances must be mutually exclusive with the list of available instances. | ||
+ | | ||
+ | * available (Oracle RAC Only) - List of available instances where the service CAN run in case the preferred aren't available. | ||
+ | | ||
+ | * tafpolicy - TAF policy specification. You can only use PRECONNECT when you specify the -preferred and -available parameters. | ||
+ | |||
+ | These parameters are exclusive for a service on a admin managed database. The rest of the parameters are the same as the policy managed. If it will help you understand services better. You have to answer yourself the following questions. | ||
+ | |||
+ | - Where the service will run: (Singleton/ | ||
+ | - How we define a failover: (failoverretry/ | ||
+ | - What happens when a failover occurs: (tafpolicy, failovertype and others) | ||
+ | |||
+ | There are more, but these 3 are the main ones. Good luck. | ||
+ | |||
+ | =====Conclusion===== | ||
+ | Services are instrument through which we allow access to our database. These services can behave in different ways and it is up to us as DBAs to set them correct, so the client will be able to access his data. | ||