GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

Register a Golden Gate extract process to prevent arch logs getting zipped

edited Jun 25, 2018 4:44PM in GoldenGate, Streams and Distributed Database (MOSC) 9 commentsAnswered
Hi

I am trying to register Golden Gate extract process with the database using 'Register extract <ext_name>, logretention. After I issue the command, I do see that the extract is registered in the DBA_CAPTURE view as expected. However, I see that the STATUS column appears DISABLED always. How do I enable it? The information in this view is not updated all. Basically, I want to use this view for a situation I have which is something like this:

We have a shell script to compress the arch logs to free up space. But the GGS extract process is sometimes slow (with a lag) still reading an old file which apparently gets zipped. Since the file gets compressed/zipped, the extract process abends after several unsuccessful attempts and then sends a mail. We want to avoid this situation by registering it with the database. So that way, we can query the DBA_CAPTURE view first to determine how far behind the extract process is and thus prevent the particular archive log from getting compressed.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center