GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

ORA-01357: LogMiner transaction queue is full

edited Jul 13, 2023 3:23PM in GoldenGate, Streams and Distributed Database (MOSC) 3 commentsAnswered ✓

Dear Oracle Community,

I am using Oracle GoldenGate Integrated Extract to capture data from Oracle DB. Once per couple of weeks the extract fails on:

ORA-01357: LogMiner transaction queue is full

After the extract is restarted, it typically resumes operation without any further issues until the LogMiner transaction queue is full again.

When the extract starts, I noticed that the "Transaction Queue Size" is set to 131072 (see alert log excerpt below). This doesn't seem to be enough (?).

Is it possible to modify this value to increase the size of the LogMiner transaction queue? I am seeking guidance on how to avoid encountering this error in the future.

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