Since the DBA in charge couldn’t resolve the problem, I was called in. In this post, I will describe the issue and how it was resolved. SQL> Film tinkerbell secret of the wings sub indo homecoming. alter database mount standby database; 11.[Standby] RMAN does not know about these files yet; so you must let it know – by a process called cataloging. Archive log thread 1 sequence 8012 is. Standby is out of Sync or GAP is not getting resolved on standby It can happen due to several reasons like 1. Archived log has been deleted 2. Nipsey hussle slauson boy vol 1 zip file. Moved log file has corrupted 3. Any network issues If it’s because of either 1 or 2 incremental backup from SCN is the best option to recover it. Suppose if we have proper archive logs exist on the primary database then FAL_SERVER, FAL_CLIENT will take care of the gap issue. SQL> select name,database_role,switchover_status,protection_mode,force_logging from v$database; NAME DATABASE_ROLE SWITCHOVER_STATUS PROTECTION_MODE FOR ——— —————- ——————– ——————– — PRD6A PHYSICAL STANDBY NOT ALLOWED MAXIMUM PERFORMANCE YES SQL> Make sure all the logs upto the gap is applied using v$archived_log and applied=YES. APPLIED=NO means MRP process is not applying logs on the standby database even though all the logs are available in standby database except the gaps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |