Shulou(Shulou.com)06/03 Report--

Check the database server, found that the disk is full, because of previous planning problems, insufficient disk space, fortunately, the library does not affect.

When deleting an archive, it is found that there are too many deletions, so that the standby archive is not successfully applied, so it is deleted.

This operation is indeed careless. When checking the archive of the preparation database, it is found that it cannot be applied. Check the log and report the following error:

Fetching gap sequence in thread 1 Gap sequence 42102-42102FAL [client]: All defined FAL servers have been attempted.---Check that the CONTROL_FILE_RECORD_KEEP_TIME initializationparameter is defined to a value that's sufficiently largeenough to maintain adequate log switch information to resolvearchivelog gaps.-

The processing method is to view the sequence of the archived SCN in the main library:

SQL > col first_change# for 999999999999999SQL > select first_change# from v$archived_log where sequence#='42102' 2; FIRST_CHANGE#- 11769444390910 main library SQL > alter system set log_archive_dest_state_2=defer; slave library SQL > alter database managed standby database recovery cancel

Make incremental and control file backups of the main library:

RMAN > backup incremental from scn 11769444390910 database format'/ u01tempUnitempUniverse archivedlogbooks% uplink transmissibility rman > backup current controlfile for standby format'/ u01tempUnitempUnitempUnitioncontrolfile.bak'

After copying the file to the standby library, restore it.

RMAN > shutdown immediateRMAN > startup nomountRMAN > restore standby controlfile from'/ u01amp temp _ control _ file.bakeries _ rman > alter database mount;RMAN > recover database noredo

In addition, if you do not use the standby log mode, you need to empty the repository redo log, and there are several groups to clean up.

SQL > alter database clear logfile group 1

Switch the main database log file to see if the log sequence of the master and backup database is consistent!

Main library: SQL > alter system switch logfile;SQL > select max (sequence#) from vs. logically correct Max (SEQUENCE#)-42141 Reserve Library: SQL > select max (sequence#) from vicious logarithmic transactions: Max (SEQUENCE#)-42141

Restore archiving application

Main library SQL > alter system set log_archive_dest_state_2=enable; slave library SQL > alter database managed standby database recovery disconnect from session

Focus on the following views:

V$managed_standbySQL > select process,status,sequence# from vastly managed management standbyscape vastly archivedestined statusSQL > col dest_name for a25SQL > select dest_name,status,recovery_mode from v$archive_dest_status

Observe the alert log at startup and find the following

Wed Sep 30 14:27:09 2015

Managed Standby Recovery not using Real Time Apply

Indicates that the archive is not synchronized in real time, and it is found that standby monitoring is not enabled.

Tnsping sss_dgTNS Ping Utility for Linux: Version 11.2.0.3.0-Production on 30-SEP-2015 14:27:42Copyright (c) 1997, 2011, Oracle. All rights reserved.Used parameter files:Used TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=x.x.x.x) (PORT=1521)) (CONNECT_DATA= (SERVER=DEDICATED) (SERVICE_NAME=sss) TNS-12541: TNS:no listene

Reference:

Http://www.xifenfei.com/2011/07/data-guard%e5%87%ba%e7%8e%b0gap-sequence%e4%bf%ae%e5%a4%8d.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.