My Oracle Support Banner

OGG-06530 Berkeley Database Encountered A Critical Error On GG Startup (Doc ID 2358740.1)

Last updated on MAY 11, 2022

Applies to:

Oracle GoldenGate - Version 12.2.0.1.0 and later
Information in this document applies to any platform.

Symptoms

Datastore being corrupted every time when Goldengate is started.

The GG processes (manager, extract/replicat, jagent) then become unresponsive.
Recreating the datastore allows the processes to restart but then the datastore becomes corrupt again.

Goldengate Version : 12.2.0.1.170221 

Operating System : Linux, x64, 64bit 

Database Version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

ggserr.log

=======
See the following error:

2017-12-12 08:46:52 WARNING OGG-06530 Oracle GoldenGate Command Interpreter for Oracle: Berkeley Database encountered a critical error.
2017-12-12 08:52:32 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): create datastore.
2017-12-12 08:54:30 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): delete datastore.
2017-12-12 08:55:03 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): create datastore mmap.
2017-12-12 08:55:16 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): create datastore mmap.
...
...
2017-12-12 06:28:10 WARNING OGG-06530 Oracle GoldenGate Command Interpreter for Oracle: Berkeley Database encountered a critical error.
2017-12-12 06:29:39 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): send manager restartstatus.
2017-12-12 06:29:40 WARNING OGG-06530 Oracle GoldenGate Command Interpreter for Oracle: Berkeley Database encountered a critical error.

ggsci:
GGSCI 1> send manager restartstatus
Sending RESTARTSTATUS request to MANAGER ...
ERROR: sending message to MANAGER (Timeout waiting for message).

Changes

Problem is happening when ZFS + Cluster VIP+ CRS is used

A non-CRS installation that is not using a VIP works fine on ZFS.

This issue is nothing to do with Filesystem being used. The issue is with how Oracle Goldengate Handles the BDB calls.  

 

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
Changes
Cause
Solution
References


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