Hi all,
I had configured DG in my machine for practice purpose.(11.2.0.1.0) on my windows laptop
Once it was running fine (syncing) i tried switchover which also worked.
I wanted to practice upgradation (11.2.0.4.0 to 12.1.0.1) which i did & needed a few more checks so paused it for a while & started my DG setup.
DG setup
Originally
Primary => ORCL
Standby => DUPORCL
after switchover
Primary => DUPORCL
Standby => ORCL
I started DUPORCL 1st & then ORCL
when i checked the
archive log list; the sequence numbers dint match, later i found tnsping was not working so made the necessary modifications & tnsping is working fine.
still there is issue of sequence is not matching...
@ORCL / physical standby
SQL> select message from v$dataguard_status;
MESSAGE
--------------------------------------------------------------------------------
ARC0: Archival started
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC4: Becoming the heartbeat ARCH
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
MESSAGE
--------------------------------------------------------------------------------
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
MESSAGE
--------------------------------------------------------------------------------
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
MESSAGE
--------------------------------------------------------------------------------
Error 3113 received logging on to the standby
FAL[client, ARC2]: Error 3113 connecting to DUPORCL for fetching gap sequence
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 131
Error 3113 received logging on to the standby
FAL[client, USER]: Error 3113 connecting to DUPORCL for fetching gap sequence
41 rows selected.
@DUPORCL / Primary
SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), m
essage from v$dataguard_status where dest_id=2;
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 12541 06-OCT-2015 21:26:13
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541.
Error 12541 06-OCT-2015 21:26:15
FAL[server, ARC3]: Error 12541 creating remote archivelog file 'orcl'
Error 12541 06-OCT-2015 21:26:16
Error 12541 for archive log file 3 to 'orcl'
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 12541 06-OCT-2015 21:27:12
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541.
Error 12541 06-OCT-2015 21:32:45
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541.
Error 12541 06-OCT-2015 21:38:13
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 12541.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 3113 06-OCT-2015 21:44:20
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 06-OCT-2015 21:50:25
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 06-OCT-2015 21:55:31
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 3113 06-OCT-2015 22:00:36
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 06-OCT-2015 22:05:46
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 1034 06-OCT-2015 22:10:47
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 1034.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 1034 07-OCT-2015 06:48:29
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 1034.
Error 3113 07-OCT-2015 06:53:42
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 06:59:47
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 3113 07-OCT-2015 07:05:50
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:11:54
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:17:57
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 3113 07-OCT-2015 07:23:02
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:29:04
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:34:11
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D
------------- ---------- --------------------
MESSAGE
--------------------------------------------------------------------------------
Error 3113 07-OCT-2015 07:40:14
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:46:19
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
Error 3113 07-OCT-2015 07:52:23
PING[ARC1]: Heartbeat failed to connect to standby 'orcl'. Error is 3113.
24 rows selected.
Not sure why standby is not reachable...
@ORCL
SQL> show parameter fal
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
fal_client string ORCL
fal_server string DUPORCL
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2 string SERVICE=DUPORCL LGWR ASYNC VAL
ID_FOR=(ONLINE_LOGFILES,PRIMAR
Y_ROLE)
DB_UNIQUE_NAME=DUPORCL
log_archive_dest_20 string
log_archive_dest_21 string
@ DUPORCL
SQL> show parameter fal
NAME TYPE VALUE
------------------------------------ ----------- ---------------------------
fal_client string duporcl
fal_server string orcl
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2 string service=orcl ASYNC valid_for=(
ONLINE_LOGFILE,PRIMARY_ROLE) d
b_unique_name=orcl
log_archive_dest_20 string
I am suspecting is it something to do with switchover?
Please guide me on this.
Mohib