To configure services to use Transaction Guard, set the following service parameters:
-commit_outcome: Set the -commit_outcome service parameter to TRUE. This service parameter determines whether the transaction commit outcome is accessible after the COMMIT has executed and an outage has occurred. While Oracle Database has always made COMMIT durable, Transaction Guard makes the outcome of the COMMIT durable, and is used by applications to enforce the status of the last transaction executed before an outage.
-retention: Use the -retention service parameter with -commit_outcome. This service parameter determines the amount of time, in seconds, that the COMMIT outcome is retained. Oracle recommends that most installations use the default value.
The following SRVCTL command configures a policy-managed service named sales for Transaction Guard:
$ srvctl add service -db crm -service sales -serverpool spool_1
-commit_outcome TRUE -retention 86400 -notification TRUE
The following SRVCTL command configures an administrator-managed service named sales for Transaction Guard:
$ srvctl add service -db crm -service sales -preferred crm_1,crm_2
-available crm_3,crm_4 -commit_outcome TRUE -retention 86400
-notification TRUE
You can also modify an existing service to configure it for Transaction Guard by using the srvctl modify service command.
See Also:
"srvctl add service" and "srvctl modify service" for information about these commands
"Application Continuity: Automated Replay for Masking Outages"
Oracle Database Development Guide for more information about Transaction Guard and idempotence
Oracle Database JDBC Developer's Guide for more information about Transaction Guard for Java
Oracle Call Interface Programmer's Guide for more information about developing Oracle Call Interface applications that use Transaction Guard
Note:
Do not use database services because these services are for administration purposes and cannot be manipulated. Do not use a service name that is set to db_name or db_unique_name.