To be clear, I was referring to attributes such as MAX_FAILURE, NET_TIMEOUT etc.
From: Ram Cheruvattath
Sent: Monday, July 11, 2016 1:53 PM
To: iamabhinav.akg@xxxxxxxxx ; oracle-l@xxxxxxxxxxxxx
Subject: Re: log shipping in 12c - log_archive_dest_state_2
What parameters, if any, are you using for log_archive_dest_state_2?
Ram
From: Abhinav Gupta
Sent: Monday, July 11, 2016 2:07 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: log shipping in 12c - log_archive_dest_state_2
Hi All,
I have couple of primary database (all 2 node RAC on same CRS) along with
physical standby counterparts(all single instance on same server). The RDBMS
versions are 12.1.0.2 and are on RHEL5.
Quite frequently one or more standby goes out of sync due to "WAIT_FOR_LOG" on
mrp. This is resolved by altering log_archive_dest_state_2 on primary to DEFER
and then back to ENABLE. This immediately starts the stopped log shipping and
standby is back sync soon.
Mostly, one of the database is erratic, however, at times, two or more throws
the same issue at same point of time. Hence, it could be something outside
database as well. Never seen this issue in any of our pre-12c database, so far
with similar set of configurations.
Anyone?
Regards,
Abhinav
