How to deal with the DG Archive Log for too long time off

This article mainly shows you "DG archive log break time is too long how to deal with", the content is easy to understand, clear, hope to help you solve doubts, the following let the editor lead you to study and learn "DG archive log break time is too long how to deal with" this article.

1. Prepare database operation

(1) cancel the application of log

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL

(2) stop storage

Shut immediate

(3) Boot to nomount mode

Startup nomount

2. Main library operation

(1) create a standby controlfile

Alter database create physical standby controlfile as'/ tmp/controlfile_standby'

(2) copy standby controlfile to DG backup database and overwrite the original control file

(3) copy the full database backup and archive backup of the main database to the DG backup database

3. Prepare database operation

(1) confirm that the standby controlfile of the main library has been copied and overwritten controlfile, and start to mount mode

(2) enter rman, set the directory path where the backup of the main database is stored as the recovery path, and reference the backup

Catalog start with'/ oradata/bak/'

(3) restore the database

Restore database

(4) Open the database

Alter database open

(5) the application of execution log

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION

The above is all the contents of the article "how to deal with the DG Archive log break time is too long". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!