alert日志大量DISTRIB TRAN GDDB.6d36e46c.419.26.15318211问题

现象:

oracle11.2.0.4rac+linux6.9
分布式事务问题：alert日志大量分布式事务信息
Wed Sep 16 22:24:48 2020
DISTRIB TRAN GDDB.6d36e46c.419.26.15318211
is local tran 158.31.753501 (hex=9e.1f.b7f5d)
insert pending committed tran, scn=16991552165237 (hex=f74.276e5575)
Wed Sep 16 22:28:10 2020
Thread 1 advanced to log sequence 26380 (LGWR switch)
Current log# 3 seq# 26380 mem# 0: +DATADG/gddb/onlinelog/group_3.283.986639037
Wed Sep 16 22:28:15 2020
Archived Log entry 60272 added for thread 1 sequence 26379 ID 0xc64e0bd6 dest 1:
解决办法：

SQL> alter system set "_clusterwide_global_transactions"=false scope=spfile sid='*';

Does Oracle Commerce Require DTP Or _clusterwide_global_transactions Flags To Be Set For Oracle RAC (Doc ID 1945707.1)

To Bottom

In this Document

Goal

Solution

References

APPLIES TO:

Oracle Commerce Platform - Version 11.1 and later
Information in this document applies to any platform.
**Checked for relevance on 8-June-18**

GOAL

Should Distributed Transaction Processing (DTP) or Clusterwide XA transactions management (global_txn_processes) be used for RAC configuration when using Oracle Commerce?

SOLUTION

Generally when XA is configured, either DTP or _clusterwide_global_transactions is set.

However, when XA transactions use SUSPEND/RESUME operations the Clusterwide XA transactions management (global_txn_processes) introduced with 11g cannot be used. This limitation is documented in this document:

ORA-24798 WHEN XA RESUMES JOIN AN EXISTING TRANSACTION BRANCH (Doc ID 1106793.1)

Since Oracle Commerce transactions use SUSPEND/RESUME operations, _clusterwide_global_transactions will need to be set to "FALSE".

Since Clusterwide XA transactions management cannot be used, per Oracle documentation it is recommended that DTP be used. For further details, look at Overview of XA Transactions and DTP Services section of the Real Application Clusters Administration and Deployment Guide.

An additional reason to set _clusterwide_global_transactions to "FALSE" is discussed in
High rdbms ipc reply and DFS lock handle in 11gR2 RAC With XA Enabled Application (Doc ID 1361615.1)

REFERENCES

NOTE:1361615.1 - High rdbms ipc reply and DFS lock handle in 11gR2 RAC With XA Enabled Application
NOTE:1106793.1 - ORA-24798 WHEN XA RESUMES JOIN AN EXISTING TRANSACTION BRANCH

日志显示：
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Wed Sep 16 23:54:41 2020
ALTER SYSTEM SET service_names='SYS$SYS.KUPC$S_1_20200916234503.GDDB' SCOPE=MEMORY SID='gddb1';
ALTER SYSTEM SET service_names='SYS$SYS.KUPC$S_1_20200916234503.GDDB','SYS$SYS.KUPC$C_1_20200916234503.GDDB' SCOPE=MEMORY SID='gddb1';
Wed Sep 16 23:54:58 2020
Running Distributed Transactions in RAC without DTP service.
Thu Sep 17 00:01:40 2020

======================================

Can I use Oracle RAC in a distributed transaction processing environment?

YES. Best practices is to have all tightly coupled branches of a distributed transaction running on an Oracle RAC database must run on the same instance. Between transactions and between services, transactions can be load balanced across all of the database instances.
Prior to Oracle RAC 11g, you must use services to manage DTP environments. By defining the DTP property of a service, the service is guaranteed to run on one instance at a time in an Oracle RAC database. All global distributed transactions performed through the DTP service are ensured to have their tightly-coupled branches running on a single Oracle RAC instance.
Oracle RAC 11g provides transparent support for XA global transactions in an Oracle RAC environment and you do not need to use DTP services.

====================================

Services and Distributed Transaction Processing in Oracle RAC(DTP) (Doc ID 1307751.1)

To Bottom

In this Document

Symptoms

Cause

Solution

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

SYMPTOMS

You may find the following message in alert log when application servers which perform distributed transactions connects to the database at first.

"Running Distributed Transactions in RAC without DTP service."

CAUSE

If you are running any kind of distributed transactions, the service that the application uses to connect to the RAC database should be enabled for DTP. This keeps all parts of a distributed transaction on the same instance, and allows the service to migrate to a new instance in case of instance failure.

Note: DTP services are not needed in 11.2. As long as the database initialization parameter GLOBAL_TXN_PROCESSES is greater than zero,Oracle11.2 allows different branches of the same global transaction to span multiple RAC instances.

SOLUTION

1.Check for what services do you have enabled?:

select * from v$active_services;

2. Enable all services for the application which uses DTP:

EXECUTE DBMS_SERVICE.MODIFY_SERVICE(service_name => '', DTP=>TRUE);

Or alternately you can use Oracle Enterprise Manager or SRVCTL to modify the DTP property of the singleton service. Set the DTP option (-x) for the service to TRUE
(the default value is FALSE).

The following example shows how to modify the xa_01.example.com service using SRVCTL:

srvctl modify service -d crm -s xa_01.example.com -x TRUE