This content has been marked as final. Show 5 replies
Try registering the archives with the correct naming convention. Make sure that the MRP is started on the standby database.
On the standby database:
SQL>select process,status,sequence# from v$managed_standby;
SQL> select process,status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
--------- ------------ ----------
ARCH CLOSING 5370
ARCH CONNECTED 0
ARCH CLOSING 5371
ARCH CLOSING 5369
MRP0 WAIT_FOR_GAP 811
RFS IDLE 0
RFS IDLE 5372
RFS IDLE 0
RFS IDLE 4241
9 rows selected.
this is the result of the query.
so is it ok if i rename manually the from OS the archivelogs? like for example, we have archivelogs from prod named "oradb.arc" and on standby we have "orasty.arc". so i just copied the oradb.arc to standby. is it ok if i manually rename it? then register the archivelog?
Edited by: Kaye Chow on Nov 23, 2012 6:50 AM
Use below sql to find the gaps in the database.
Select * from v$archive_gap;
This will show the lowest and highest sequence need to resolve the gaps.
and then just scp the archives from primary to standby location and register the archives in standby. It will automatically start applying.
Alter database register logfile '\u01\app\oracle\standby_arch\oradb.arc';
Let me know if you have any issues.
Try to register those log files manually using
alter database register logfile 'path'
or whatever the syntax is
Or check whether MRP is started
You can do this manually by registering the archivelog files on standby
If you have broker configured on your DG you can also see the gap using "show database <standby db>" command
You can also look from errors using the query below
column message format a80
select message, timestamp
where severity in ('Error','Fatal')
order by timestamp;