Database Administration (MOSC)

MOSC Banner

LogMiner on Primary database failing due to attempted access of Newly Added Physical Standby

edited Nov 20, 2015 10:04AM in Database Administration (MOSC) 4 commentsAnswered

We have had an IBM Q Replication Capture process running against our 11.2.0.4 RAC database for a while now.  Recently we added a physical standby database which required the establishment of the log_archive_dest_2 parameter.  The set up has been/is working correctly as a primary and standby database is concerned, however, the capture process, which is using logminer for continuous mining, has broken due to not being able to access the standby environment.

Is there a way to keep the logminer session to only mine the local archived logs on the primary database and not to attempt to mine the log_archive_dest_2 location, which is the name of the standby database?

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