Well, if they arent available you should be able to do an incremental
recovery of the standby.
On Fri, Jul 2, 2021 at 10:42 AM Scott Canaan <srcdco@xxxxxxx> wrote:
I did find a gap. There are missing logs. I’m trying to get them from
backup, but it doesn’t appear they are there.
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
*From:* Sweetser, Joe <JSweetser@xxxxxxxx>
*Sent:* Friday, July 2, 2021 11:37 AM
*To:* nassyambasha@xxxxxxxxx; Scott Canaan <srcdco@xxxxxxx>
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* RE: Data Guard Question
I have sometimes had to register ‘missing’ log files like:
alter database register logfile '/full/path/to/arch/logs/arch_1234.arc';
If there are many files, you can use the RMAN catalog command:
catalog start with ‘/full/path/to/arch/logs/’;
Hth,
-joe
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> *On
Behalf Of *Nassyam Basha
*Sent:* Friday, July 2, 2021 9:29 AM
*To:* srcdco@xxxxxxx
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Data Guard Question
Hello Scott,
Are you sure that all required archives are available at standby database?
PR00 (PID:29394): GAP - thread 1 sequence *44056-44081*
Can you verify the sequences are available or not by this query?
Standby> Select sequence#, name from v$archived_log where sequence# >
44055 and sequence# < 44082;
In short, as per the alert log info it seems few set of archive logs are
not shipped from primary to standby. The reason could be either data guard
configuration issue or archives might got deleted at primary.
Nassyam on iPhone
On 2 Jul 2021, at 6:21 PM, Scott Canaan <srcdco@xxxxxxx> wrote:
I have a data guard set up where the logs are being shipped to the
secondary, but not being applied. I’ve verified that all the needed logs
are there, but it won’t apply them. I don’t know how to get it to start.
I tried ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;, but that
did nothing. All I got was an error in the alert log. I tried bouncing
the database and got the following:
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT
NODELAY
2021-07-02T11:13:24.778232-04:00
ALTER SYSTEM SET fal_server='clawbeta' SCOPE=BOTH;
2021-07-02T11:13:48.721856-04:00
PR00 (PID:29394): FAL: Failed to request gap sequence
PR00 (PID:29394): GAP - thread 1 sequence 44056-44081
PR00 (PID:29394): DBID 2700461164 branch 1043824278
PR00 (PID:29394): FAL: All defined FAL servers have been attempted
PR00 (PID:29394):
-------------------------------------------------------------------------
PR00 (PID:29394): Check that the CONTROL_FILE_RECORD_KEEP_TIME
initialization
PR00 (PID:29394): parameter is defined to a value that's sufficiently large
PR00 (PID:29394): enough to maintain adequate log switch information to
resolve
PR00 (PID:29394): archived redo log gaps.
PR00 (PID:29394):
-------------------------------------------------------------------------
Control_file_record_keep_time is 30, which I understand is in days. The
oldest log to be applied is from June 25, so that’s within the 30 days.
How do I get the secondary to apply the needed logs?
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
This e-mail transmission and any attachments that accompany it may contain
information that is privileged, confidential or otherwise exempt from
disclosure under applicable law and is intended solely for the use of the
individual's to whom it was intended to be addressed. If you have received
this e-mail by mistake, or you are not the intended recipient, any
disclosure, dissemination, distribution, copying or other use or retention
of this communication or its substance is prohibited. If you have received
this communication in error, please immediately reply to the author via
e-mail that you received this message by mistake and also permanently
delete the original and all copies of this e-mail and any attachments from
your computer. Please note that coverage cannot be bound or altered by
sending an email. You must receive written confirmation from a
representative of our firm to put coverage in force or make changes to an
existing policy.
