Hi
I am looking into a new customer issue where their standby database is not upto date with primary.
Now after working for long on this, resloved the space issues on db_recovery area.
The statuses now shows as below:-
select database_role,switchover_status from v$database;-PRIMARY ,UNRESOLVABLE GAP
on standby, same query yields -PHYSICAL STANDBY,NOT ALLOWED
Current_scn is significantly different on both databases -on primary,162073015 and standby-66111000
I applied an incremental backup on standby starting from the standby scn and restore worked fine.
There is no rows showing for query, select * from v$archived_gap;
Standby is on mount stage now. Its unable to open on read only status as well.
primary
---------
select max(sequence#) from v$log_history;--201691
select thread#,max(sequence#) from v$archived_log group by thread#;1,201691
select process, status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CLOSING 201690
ARCH CLOSING 201691
ARCH CONNECTED 0
ARCH CLOSING 201692
LGWR WRITING 201693
Standby
-------
select max(sequence#) from v$log_history;--110039
select thread#,max(sequence#) from v$archived_log group by thread#;1,201691
(note the second query-same result on both)
select process, status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CLOSING 201691
ARCH CLOSING 201692
ARCH CONNECTED 0
ARCH CLOSING 201690
RFS IDLE 0
RFS IDLE 201693
RFS IDLE 0
MRP0 WAIT_FOR_GAP 110040
In the primary trace LOG files, the error keeps on showing that
"No standby database destinations have been configured
as being archived by the LGWR process"
How to resolve this?what to check now?Where to configure&what are the commands ?
standby alert log
============
Wed Dec 03 13:37:35 2014
Archived Log entry 116921 added for thread 1 sequence 201681 ID 0xd63d6ae5 dest 1:
ARC3: Archive log thread 1 sequence 201681 available in 1440 minute(s)
Wed Dec 03 13:47:32 2014
WARNING: Managed Standby Recovery started with REAL TIME APPLY
DELAY 1440 minutes specified at primary ignored
Standby controlfile consistent with primary
RFS[1]: Selected log 9 for thread 1 sequence 201683 dbid -700612123 branch 829387109
Wed Dec 03 13:47:32 2014
Archived Log entry 116922 added for thread 1 sequence 201682 ID 0xd63d6ae5 dest 1:
ARC0: Archive log thread 1 sequence 201682 available in 1440 minute(s)
Wed Dec 03 13:57:33 2014
WARNING: Managed Standby Recovery started with REAL TIME APPLY
DELAY 1440 minutes specified at primary ignored
Standby controlfile consistent with primary
RFS[1]: Selected log 8 for thread 1 sequence 201684 dbid -700612123 branch 829387109
Wed Dec 03 13:57:33 2014
Archived Log entry 116923 added for thread 1 sequence 201683 ID 0xd63d6ae5 dest 1:
ARC1: Archive log thread 1 sequence 201683 available in 1440 minute(s)
Wed Dec 03 14:07:33 2014
WARNING: Managed Standby Recovery started with REAL TIME APPLY
DELAY 1440 minutes specified at primary ignored
Standby controlfile consistent with primary
RFS[1]: Selected log 9 for thread 1 sequence 201685 dbid -700612123 branch 829387109
Wed Dec 03 14:07:33 2014
Archived Log entry 116924 added for thread 1 sequence 201684 ID 0xd63d6ae5 dest 1:
ARC3: Archive log thread 1 sequence 201684 available in 1440 minute(s)
primary alert log
=============
Wed Dec 03 14:47:31 2014
Thread 1 cannot allocate new log, sequence 201689
Private strand flush not complete
Current log# 4 seq# 201688 mem# 0: E:\COREHR\REDO\REDO04A.LOG
Current log# 4 seq# 201688 mem# 1: G:\COREHR\REDO\REDO04B.LOG
WARNING: Managed Standby Recovery started with USING CURRENT LOGFILE
DELAY 1440 minutes specified at primary ignored
LGWR: Standby redo logfile selected to archive thread 1 sequence 201689
LGWR: Standby redo logfile selected for thread 1 sequence 201689 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 201689 (LGWR switch)
Current log# 1 seq# 201689 mem# 0: E:\COREHR\REDO\REDO01A.LOG
Current log# 1 seq# 201689 mem# 1: G:\COREHR\REDO\REDO01B.LOG
Wed Dec 03 14:47:35 2014
Archived Log entry 319477 added for thread 1 sequence 201688 ID 0xd63d6ae5 dest 1:
Wed Dec 03 14:57:29 2014
WARNING: Managed Standby Recovery started with USING CURRENT LOGFILE
DELAY 1440 minutes specified at primary ignored
LGWR: Standby redo logfile selected to archive thread 1 sequence 201690
LGWR: Standby redo logfile selected for thread 1 sequence 201690 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 201690 (LGWR switch)
Current log# 2 seq# 201690 mem# 0: E:\COREHR\REDO\REDO02A.LOG
Current log# 2 seq# 201690 mem# 1: G:\COREHR\REDO\REDO02B.LOG
Wed Dec 03 14:57:29 2014
Archived Log entry 319479 added for thread 1 sequence 201689 ID 0xd63d6ae5 dest 1:
Wed Dec 03 15:07:29 2014
Thread 1 cannot allocate new log, sequence 201691
Private strand flush not complete
Current log# 2 seq# 201690 mem# 0: E:\COREHR\REDO\REDO02A.LOG
Current log# 2 seq# 201690 mem# 1: G:\COREHR\REDO\REDO02B.LOG
WARNING: Managed Standby Recovery started with USING CURRENT LOGFILE
DELAY 1440 minutes specified at primary ignored
LGWR: Standby redo logfile selected to archive thread 1 sequence 201691
LGWR: Standby redo logfile selected for thread 1 sequence 201691 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 201691 (LGWR switch)
Current log# 3 seq# 201691 mem# 0: E:\COREHR\REDO\REDO03A.LOG
Current log# 3 seq# 201691 mem# 1: G:\COREHR\REDO\REDO03B.LOG
Wed Dec 03 15:07:33 2014
Archived Log entry 319481 added for thread 1 sequence 201690 ID 0xd63d6ae5 dest 1:
Wed Dec 03 15:17:31 2014
Thread 1 cannot allocate new log, sequence 201692
Private strand flush not complete
Current log# 3 seq# 201691 mem# 0: E:\COREHR\REDO\REDO03A.LOG
Current log# 3 seq# 201691 mem# 1: G:\COREHR\REDO\REDO03B.LOG
WARNING: Managed Standby Recovery started with USING CURRENT LOGFILE
DELAY 1440 minutes specified at primary ignored
LGWR: Standby redo logfile selected to archive thread 1 sequence 201692
LGWR: Standby redo logfile selected for thread 1 sequence 201692 for destination LOG_ARCHIVE_DEST_2
Thread 1 advanced to log sequence 201692 (LGWR switch)
Current log# 4 seq# 201692 mem# 0: E:\COREHR\REDO\REDO04A.LOG
Current log# 4 seq# 201692 mem# 1: G:\COREHR\REDO\REDO04B.LOG
Wed Dec 03 15:17:34 2014
Archived Log entry 319483 added for thread 1 sequence 201691 ID 0xd63d6ae5 dest 1:
VERY NEW TO PRACTICALLY MANAGING STANDBY.
PLEASE GUIDE ME WHAT STEPS TO BE TAKEN NEXT TO MAKE STANDBY IN SYNCH WITH THE PRIMARY, IT WILL BE A GREAT HELP.
Any help is appreciated.
Anything else I forget to explain, please let me know.
THANKS A TON