I. Problem Description
After the host where the master and slave databases are located is restarted, RAC (master database) is automatically started upon startup, but the slave database (Single Instance) is not started upon startup and has been manually started to mount, the standby database has been alter database recover standby database disconnect from session ;.
The archived logs of the master database cannot be synchronized to the slave database:
Rac1:
Rac2:
Slave database:
-- It is strange that V $ archive_gap is still empty.
View alarm logs:
Ii. Solution
First, check whether the standby database listening is started (when the status is 'ready', it indicates that the standby database listening has been started)
If the listener is not started, start the listener: LSNRCTL start.
If the listener has been started:
Manually copy the missing logs from the master database SCP/rcp, And then alter database register logfile.
Step 3:
For example, the following logs should be copied:
+ Data/Prod/1_29_856078807.arc 29 1
+ Data/Prod/2_14_856078807.arc 14 2
+ Data/Prod/1_30_856078807.arc 30 1
+ Data/Prod/2_15_856078807.arc 15 2
+ Data/Prod/2_16_856078807.arc 16 2
1: Use RMAN to copy the required archive files from the ASM Device
Run {
Copy archivelog '+ Data/Prod/1_29_856078807.arc' to '/home/Oracle/1_29_856078807.arc ';
Copy archivelog '+ Data/Prod/export 30_856078807.arc' to '/home/Oracle/export 30_856078807.arc ';
Copy archivelog '+ Data/Prod/2_14_856078807.arc' to '/home/Oracle/2_14_856078807.arc ';
Copy archivelog '+ Data/Prod/2_15_856078807.arc' to '/home/Oracle/2_15_856078807.arc ';
Copy archivelog '+ Data/Prod/2_16_856078807.arc' to '/home/Oracle/2_16_856078807.arc ';
}
Starting backup at 27-aug-14
Using channel ora_disk_1
Channel ora_disk_1: Starting archive copy
Input archive log thread = 1 sequence = 29 recid = 82 stamp = 856665609
Output Filename =/home/Oracle/1_29_856078807.arc recid = 89 stamp = 856669631
Channel ora_disk_1: archivelog copy complete, elapsed time: 00:00:02
Finished backup at 27-aug-14
......
2: view the archive path in the slave Database
SQL> archive log list;
Database Log mode archive Mode
Automatic Archival Enabled
Archive destination/ARCH/sdyprod
Oldest online log sequence 0
Next log sequence to archive 0
Current Log sequence 0
3: Copy unsynchronized archived logs to the slave database in the master database
[[Email protected] ~] $ SCP 2*192.168.8.225:/ARCH/sdyprod/
[Email protected]'s password:
2_14_856078807.arc 100% 1024 1.0kb/s
2_15_856078807.arc 100% 121kb 120.5kb/s
2_16_856078807.arc 100% 20kb 20.0kb/s
[[Email protected] ~] $ SCP 1*192.168.8.225:/ARCH/sdyprod/
[Email protected]'s password:
201729_856078807.arc 100% 5356kb 5.2 MB/S
201730_856078807.arc 100% 12 Mb 11.7 MB/S
[[Email protected] ~] $
4: Cancel log application in the slave Database
SQL> alter database recover managed standby database cancel;
Database altered.
5. register the log file
SQL> alter database register logfile '/ARCH/sdyprod/1_29_856078807.arc ';
......
Database altered.
SQL> alter database register logfile '/ARCH/sdyprod/2_16_856078807.arc ';
Database altered.
6: Start log application
SQL> alter database recover managed standby database disconnect from session;
Database altered.
-- This article reference: http://blog.itpub.net/14507784/viewspace-759605/
If the problem persists, see the article: http://www.xifenfei.com/1176.html
FAL [client]: failed to request gap sequence gap-thread 1 sequence 29-29