LGWR ASYNC doest not working for redolog files, while archiving is working

Question

Hi All,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.4.0.
I have created a database named black. I then creaetd a standby database. now I want to syncronize the redo logs file as well.
SO I added log_archive_dest_2='SERVICE=standby LGWR ASYNC',
I have also added following standby log files on standby database.
ALTER DATABASE ADD STANDBY LOGFILE '/oracle/oradata/black/srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE '/oracle/oradata/black/srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE '/oracle/oradata/black/srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE '/oracle/oradata/black/srl4.f' SIZE 52428800;
Now I want to confirm that the redo log files are syncronizing same time on both Primary and Standby. I have checked thru alter system switch logfile; when i executed the redo log sync at both sides.
Archive logs are also applying successfully.
The Primary database is in MAXIMUM PERFORMANCE Mode;
Regards,
Hassan

Answer 1

Hi Khurram,
I have successfully executed the commands on Primary Database as below: (Standby database was in mount state at that time)
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 2083728 bytes
Variable Size 318768240 bytes
Database Buffers 922746880 bytes
Redo Buffers 14692352 bytes
Database mounted.
SQL> alter system set log_archive_dest_2='SERVICE=standby LGWR SYNC AFFIRM' scope=both;
System altered.
SQL> alter database set standby database to MAXIMIZE AVAILABILITY;
Database altered.
SQL> alter database open;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
After that I activated managed recovery process on standby database and all archive files were applied successfully;
Then I executed a script to insert 2000 records in Primary Database Scott Schema, and during the execution of this script I executed shutdown abort from anothe session on primary database.
at that time no new archive file generated only redo files was there.
I then executed below commands on standby database to apply current redo log file but that IS WAHT I WANT TO ACHIEVE IS UN-SUCCESSFULL.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> recover standby database;
ORA-00279: change 1065936 generated at 10/22/2009 17:02:43 needed for thread 1
ORA-00289: suggestion : /oradata/black/arch/1700844250_0000000043.arc
ORA-00280: change 1065936 for thread 1 is in sequence #43
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/oradata/black/stdb_redo01.log
ORA-00310: archived log contains sequence 42; sequence 43 required
ORA-00334: archived log: '/oracle/oradata/black/stdb_redo01.log'
SQL> recover standby database;
ORA-00279: change 1065936 generated at 10/22/2009 17:02:43 needed for thread 1
ORA-00289: suggestion : /oradata/black/arch/1700844250_0000000043.arc
ORA-00280: change 1065936 for thread 1 is in sequence #43
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/oradata/black/stdb_redo02.log
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 49141 change 1095254 time 10/22/2009
17:03:55
ORA-00334: archived log: '/oracle/oradata/black/stdb_redo02.log'
ORA-01112: media recovery not started
The standby redo log files are already generated on standby database. The database is in MAXIMUM AVAILABILITY MODE.
I have also go through your blog but did not find solution for my issue.
My scenario is that: SHUTDOWN ABORT (Primary Database) means that server goes down and we have to make our Standby Database as Primary Database, so we need to apply redo log file that niether switched nor applied yet.
Kindly advice.
Regards,
Hassan
Edited by: Hassan Raza Khan Lodhi on Oct 22, 2009 4:33 PM