We used DBA_LOGMNR_PURGED_LOG views to purge obsolete archivelog but why this view is not updated i
edited Apr 19, 2013 4:53AM in GoldenGate, Streams and Distributed Database (MOSC) 2 commentsAnswered
Hi,
We have a downstream configured.
We used DBA_LOGMNR_PURGED_LOG view to know wich archivelog must be purge, but this one is not updated in real time.
It's a problem for us because disk space is exausted.
The only way to be sure the view is fresh is to stop and start capture/apply.
Is there an other way to be sure the view is fresh? Why this view is not updated in real time?
Regards
William
We have a downstream configured.
We used DBA_LOGMNR_PURGED_LOG view to know wich archivelog must be purge, but this one is not updated in real time.
It's a problem for us because disk space is exausted.
The only way to be sure the view is fresh is to stop and start capture/apply.
Is there an other way to be sure the view is fresh? Why this view is not updated in real time?
Regards
William
0