HS_TRANSACTION_MODEL
HS_FDS_TRANSACTION_MODEL initialization parameter for Oracle Database Gateway for DRDA.
| Property | Description |
|---|---|
|
Default Value |
|
|
Range of Values |
|
Specifies the type of transaction model that is used when the non-Oracle database is updated by a transaction.
The following values are possible:
COMMIT_CONFIRMprovides read and write access to the non-Oracle database and allows the gateway to be part of a distributed update. To use the commit-confirm model, the following items must be created in the non-Oracle database:- Transaction log table. The default table name is
HS_TRANSACTION_LOG. A different name can be set using theHS_FDS_TRANSACTION_LOGparameter. The transaction log table must be grantedSELECT,DELETE, andINSERTprivileges set to public. - Recovery account. The account name is assigned with the
HS_FDS_RECOVERY_ACCOUNTparameter. - Recovery account password. The password is assigned with the
HS_FDS_RECOVERY_PWDparameter.COMMIT_CONFIRMdoes not apply to Oracle Database Gateway for ODBC. The default value for Oracle Database Gateway for ODBC isSINGLE_SITE.
- Transaction log table. The default table name is
READ_ONLYprovides read access to the non-Oracle database.READ_ONLY_AUTOCOMMITprovides read access to the non-Oracle database that do not have logging.SINGLE_SITEprovides read and write access to the non-Oracle database. However, the gateway cannot participate in distributed updates.SINGLE_SITE_AUTOCOMMITprovides read and write access to the non-Oracle database that do not have logging. Any update is committed immediately, and the gateway cannot participate in distributed updates.