High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Data Guard - How to identify incoming DDL causing Barrier Synchronisation (ORA-44604)

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered

Oracle Enterprise RDBMS 19.18 with Data Guard (protection mode: Maximum Performance)

I'm trying to diagnose a slowdown in replication. It appears that there is frequent DDL causing a DDL barrier. Summarising data in v$logstdby_process, it appears there are frequent long stalls resulting from DDL Barriers, followed by quick progress applying transactions.

Can any one please advise how to proceed with identification of the DDL causing the barrier? I think that understanding what is this DDL will help understand the next steps to resolution.

Here's an example message taken from v$logstdby_process:

ORA-4604: Barrier Syncronistaion on DDL with XID 43.28.2062572 (waiting on 9070 transactions)

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center