Streams Capture Performance Poor, Archivelogs From DBA_REGISTERED_ARCHIVED_LOG Are Being Registered in an Incorrect Location
(Doc ID 564825.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
At a Streams capture site that is also the primary site for a Data Guard standby database, Streams capture latency is steadily increasing, and Streams capture moves very slowly. Recently an archive_log_dest_n parameter was added to this capture site where the 'n' in log_archive_dest_n was higher than the 'n' being used by logminer for Streams capture.
A check of the DBA_REGISTERED_ARCHIVED_LOG view shows that the new logs are now being registered in the new log_archive_dest_n location that was just specified. This location is remote so it takes a very long time to access these logs.
A new log_archive_dest_n parameter was specified to a remote location. For example, if Streams capture was using log_archive_dest_1 to access the logs, and then log_archive_dest_2 is specified, logs start registering in that location instead and that is where Streams capture looks for them.
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