Bonjour,
je me permets de vous soumettre une petite aide concernant une configuration
dataGuard oracle 11gR2, sous windows 7 pro ;
voilà, j'ai une base nommé test (primaire), et une base de secours physique
nommé std (physical dataguard), mon probléme c'est que la base primaire (test)
ne communique pas avec la base de secours (std) via les archivelogs et de plus
le RFS n'est pas démarré sur la base de secours, Voici le détail des informations
sous SQLPlus :
sur la base test(primaire)
--------------
sur la base std(physical dataguard)
Code : Sélectionner tout - Visualiser dans une fenêtre à part
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 SYS@test> select dest_name, status, error from v$archive_dest where target='STANDBY' ; DEST_NAME STATUS ERROR ------------------------------ --------- ------------------------------------------------------- LOG_ARCHIVE_DEST_2 ERROR ORA-03113: fin de fichier sur canal de communication SYS@test> select sequence# from v$log where status='CURRENT' ; SEQUENCE# ---------- 35 SYS@test> SELECT MESSAGE FROM V$DATAGUARD_STATUS ; MESSAGE -------------------------------------------------------------------------------------------------- ----- ARC0: Archival started ARC1: Archival started ARC2: Archival started ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH ARC2: Becoming the heartbeat ARCH ARC3: Archival started ARC1: Beginning to archive thread 1 sequence 33 (1175190-1181114) Error 1034 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 1034. ARC1: Completed archiving thread 1 sequence 33 (1175190-1181114) ARC3: Beginning to archive thread 1 sequence 34 (1181114-1181121) Error 1034 received logging on to the standby Error 1034 for archive log file 1 to 'std' Error 1034 received logging on to the standby ARC3: Completed archiving thread 1 sequence 34 (1181114-1181121) FAL[server, ARC0]: Error 1034 creating remote archivelog file 'std' ARC4: Archival started Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. ARCH shutting down ARC4: Archival stopped Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113. Error 3113 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'std'. Error is 3113.
------------------------------
la base est monté mais pas ouvert
apres initiation de la commande suivante
alter database recover managed standby database using current logfile disconnect;
voici les autres infos :
comme vous le constatez, le MRP a bien été démarré, mais le RFS ne l'est pas ?
Code : Sélectionner tout - Visualiser dans une fenêtre à part
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44 SYS@std> 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 ARC2: Becoming the heartbeat ARCH ARC3: Archival started Error 3113 received logging on to the standby FAL[client, ARC0]: Error 3113 connecting to TEST for fetching gap sequence Attempt to start background Managed Standby Recovery process MRP0: Background Managed Standby Recovery process started Managed Standby Recovery starting Real Time Apply Media Recovery Waiting for thread 1 sequence 19 Fetching gap sequence in thread 1, gap sequence 19-31 Error 3113 received logging on to the standby FAL[client, USER]: Error 3113 connecting to TEST for fetching gap sequence Error 3113 received logging on to the standby FAL[client, USER]: Error 3113 connecting to TEST for fetching gap sequence Error 3113 received logging on to the standby FAL[client, USER]: Error 3113 connecting to TEST for fetching gap sequence Error 3113 received logging on to the standby FAL[client, USER]: Error 3113 connecting to TEST for fetching gap sequence Error 3113 received logging on to the standby FAL[client, USER]: Error 3113 connecting to TEST for fetching gap sequence FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 19-31 DBID 2178511409 branch 880364981 FAL[client]: All defined FAL servers have been attempted. SYS@std> select process, pid, status, 2 sequence# from v$managed_standby ; PROCESS PID STATUS SEQUENCE# --------- ---------- ------------ ---------- ARCH 6524 CONNECTED 0 ARCH 5800 CONNECTED 0 ARCH 9132 CONNECTED 0 ARCH 8328 CONNECTED 0 MRP0 7220 WAIT_FOR_GAP 19
Voilà, donc si quelqu'un pourrait bien m'éclaircir sur ce disfonctionnement, ça m'aiderai
beaucoup sur l'environnement data guard ??
Merci par avance !
Partager