How To Resolve Stranded DBA_2PC_PENDING Entries [ID 401302.1].docx

jenk

991

18页

0次

2021-02-22

40墨值下载

How To Resolve Stranded DBA_2PC_PENDING Entries [ID

401302.1]

Applies to:

Oracle Server - Enterprise Edion - Version: 8.1.5.0 to 11.1.0.6 - Release: 8.1.5 to 11.1

Informaon in this document applies to any pla#orm.

Purpose

The purpose of this bullen is to assist support analysts in understanding and

resolving the stranded dba_2pc_entries.

Scope and Application

The intended audience are support analysts having good experience on distributed

databases.

How To Resolve Stranded DBA_2PC_PENDING Entries

Contents

1. Problem Description

2. Solutions

2.1 Dba_2pc entries without a corresponding transaction

2.2 Distributed transaction without corresponding dba_2pc entries

2.3 How to PURGE the DISTRIBUTED transaction in PREPARED state,

when COMMIT

or ROLLBACK FORCE hangs ?, where we have entries for both

Distributed

transaction and dba_2pc entries.

1. Problem Description:

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

As a result of a failed commit of a distributed transaction, some

entries can

be left in dba_2pc views, i.e. dba_2pc_pending and dba_2pc_neighbors.

The RECO

process checks these views to recover the failed txn. However, in

some cases

RECO cannot perform. the recovery. One cause is that all sites

involved in the

transaction not being accessible at the same time. Another cause is

dba_2pc

views being inconsistent with the transaction table, which is the

topic of

this article. This cause can further be classified as follows:

1. dba_2pc views have entries for a non-existent distributed

transaction

2. There is a distributed transaction for which there are no

entries in

dba_2pc views

of 18

40墨值下载

database

关注

评论