My Oracle Support Banner

Berkeley DB Environment Stuck when a Major System Change Occurs in the Replication Group (Doc ID 1364632.1)

Last updated on AUGUST 23, 2021

Applies to:

Berkeley DB - Version 4.4.20 and later
Information in this document applies to any platform.

Symptoms

In a replication group, where Replication Manager (RepMgr) is used, when there is a major system change such as recovery, internal init (internal initialization) or role change (downgrade to client, upgrade to primary), the Berkeley DB environment might temporarily become stuck.

This manifests through hangs of threads that are trying to start new transactions or new cursors.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.