I. Log transmission problems
1. Generally, use the following statement to check whether the sequence of the archive logs of the primary database and standby database is the same.
Run the following command in the primary database:
SQL> alter system switch logfile;
System altered.
SQL> select max (sequence #) from v $ archived_log;
MAX (SEQUENCE #)
--------------
38
If they are the same, there is no problem. If they are different, the logs are not archived.
First, check whether the log application is enabled for standby.
SQL> alter database recover managed standby database disconnect from session;
If you have enabled
Check whether the archiving location is available. I have encountered this problem because the listener has not listened to the database.
SQL> select dest_name, status, error from v $ archive_dest;
DEST_NAME
Certificate --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STATUS ERROR
-----------------------------------------------------------------------------------
LOG_ARCHIVE_DEST_1
VALID
LOG_ARCHIVE_DEST_2
VALID
If not
Log on to the Oracle user in the operating system and check whether the listener is started. lsnrctl stauts and lsnrctl start
Check whether the two databases with tnsping are normal. If there is no problem, switch the logs in the primary database once to see if standby has received the archived logs.
If there are no problems with these steps, consider the database startup parameter file configuration. The specific problem is solved.