Registering Golden Gate extract process with database
edited Jun 25, 2018 4:46PM in GoldenGate, Streams and Distributed Database (MOSC) 15 commentsAnswered
Hi
I am trying to register an extract process of Golden Gate with the database using 'Register extract <ext_name>, logretention. I also see that the extract is registered in the DBA_CAPTURE view as expected. However, I see that the STATUS column appears DISABLED. How do I enable it? The situation I have 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 is zipped. Since the file gets compressed/zipped, the extract process abends after several unsuccessful attempts and then send 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 and prevent the particular archive log from getting compressed.
I am trying to register an extract process of Golden Gate with the database using 'Register extract <ext_name>, logretention. I also see that the extract is registered in the DBA_CAPTURE view as expected. However, I see that the STATUS column appears DISABLED. How do I enable it? The situation I have 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 is zipped. Since the file gets compressed/zipped, the extract process abends after several unsuccessful attempts and then send 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 and prevent the particular archive log from getting compressed.
0