Oracle login uard Error: Error 1017 caught ed logging on to the standby, login uardlogging

Oracle login uard Error: Error 1017 caught ed logging on to the standby, login uardlogging
1. Status description:
SQL> SELECT MESSAGE FROM V $ DATAGUARD_STATUS;


MESSAGE
--------------------------------------------------------------------------------
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started


MESSAGE
--------------------------------------------------------------------------------
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCi: Becoming the 'no fal' ARCH
ARC1: Becoming the heartbeat ARCH
Error 1017 removed ed logging on to the standby


MESSAGE
--------------------------------------------------------------------------------
FAL [client, ARC2]: Error 16191 connecting to PD for fetching gap sequence
ARCj: Archival started
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 28870


28 rows selected.


SQL>

2. Solution: copy the password file of the master database to the backup database, and restart the backup database.


Reference Article address: http://blog.itpub.net/26230597/viewspace-1224676/


3. Recovery Process:
Restart slave Database
Startup mount;
Apply redo again
Alter database recover managed standby database disconnect from session;
Check whether yes exists
Select name, sequence #, applied from v $ archived_log;


Switch the logs on the master database to see if the new 24178 archived logs are transmitted and whether they are applied to YES:
Alter system switch logfile;
SQL> alter system switch logfile;
System altered.
SQL>


Check the database
SQL> select sequence #, applied from v $ archived_log;
SEQUENCE # APPLIED
-------------------
24170 YES
24169 YES
24173 YES
24176 YES
24177 YES
24178 IN-MEMORY


2800 rows selected.
Check again, and the applied becomes YES.
SEQUENCE # APPLIED
-------------------
24170 YES
24169 YES
24173 YES
24176 YES
24177 YES
24178 YES
2800 rows selected.


Stop a redo Application
Alter database recover managed standby database cancel;
Open the open mode and open the slave database for you to query data.
Alter database open read only;
Start the redo application again
Alter database recover managed standby database disconnect from session;



Bytes ----------------------------------------------------------------------------------------------------------------
<All Rights Reserved. This document can be reprinted, but the source address must be indicated by link. Otherwise, we will be held legally responsible.>
Original blog address: http://blog.itpub.net/26230597/viewspace-1413077/
Original Author: Huang Shan (mchdba)
Bytes ----------------------------------------------------------------------------------------------------------------