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

Cause: source database application logic error, resulting in a large number of retry rollback, daily generation of archive 300GB, remote backup at the network speed of 10Mbps, resulting in archive gap

Resolution process:

1 find out the current scn number of the standby database

Select current_scn from vault database share 1612480746

2 generate incremental backup based on standby scn in the main database

-- primaryshow all;run {ALLOCATE CHANNEL D1 TYPE disk;set limit channel D1 kbytes=104857600;BACKUP INCREMENTAL FROM SCN 1612480746 DATABASE FORMAT'J:\% Utility for roomstb.bk'include current controlfile for standby;}

3 send the log to the standby database

-- standbycatalog start with'e:\ inc'

4 apply control file, incremental backup set

Restore standby controlfile to'e:\ control01.ctl'; shutdown immediate;copy e:\ control01.ctl E:\ ORADATA\ TCIS\ CONTROL01.CTLcopy e:\ control01.ctl E:\ ORADATA\ TCIS\ CONTROL02.CTLcopy e:\ control01.ctl E:\ ORADATA\ TCIS\ CONTROL03.CTL

Recover database noredo

Error report:

RMAN-03002: recover command (on 07 RMAN-03002 08 RMAN-03002 10:49:09 2018) failed RMAN-06094: data file 5 must be re-stored

Start the previous standby library, select name from v$datafile

Found that the file has re-rename; a bit of a stalk.

5 modify the location of the data file

Alter system set standby_file_management=manual; alter database rename file'E:\ ORADATA\ TCIS\ UBSS_INDX01.DBF' to'd:\ oradata\ tcis\ ubss_indx01.dbf';alter database rename file'E:\ ORADATA\ TCIS\ UBSS_INDX02.DBF' to'd:\ oradata\ tcis\ ubss_indx02.dbf'

6 recover database noredo again

Error again, file 16 does not exist RMAN-03002: recover command (on 07ap08Uniple 10:49:09 2018) failed RMAN-06094: data file 16 must be re-stored

Started with the old control file and found that document No. 16 was added later.

7 backup file No. 16 on the main library

Backup datafile 16 format'j:\ 16.bak'

8 restore 16 files on the repository

-- primarycatalog start with'e:\ inc';restore datafile 16; recover database noredo;RMAN-03002: recover command (on 10:44:11 on 07 / 07 / 2008) failed ORA-19693: included backup segment E:\ INC\ CDT7BHIL_1_1_FOR_STB.BKrecover failed, it is obvious that this file No. 16 was restored later, and its scn is larger than the backup album made previously

9 clean up invalid backup slices, repeat the steps after 2 again, backup, restore controlfile,rename datafile,recover database

10 check after recovery is completed

Restoration parameters

Alter system set standby_file_management=auto

Start recover

Alter database recover managed standby database disconnect

Check the log application

SQL > select status,blocks,process,sequence# from v$managed_standby STATUS BLOCKS PROCESS SEQUENCE#--CONNECTED 0 ARCH 0CONNECTED 0 ARCH 0IDLE 20480 RFS 45261IDLE 20480 RFS 45262IDLE 0 RFS 0APPLYING_LOG 81560 MRP0 45248

Check the archive and delete the applied archive

Select a. Thread, a. Sequence2, a. Order by. From v$archived_log a, v$database dwhere a.activation# = d.activation#and a.

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.