Resizing online and standby redo log in dataguard setup.

In 10gr2 dataguard i would like to increase redo logsize from 50M to 100M.
on primary
standby_file_management=manual
added online redo groups with 100M
log switched
drop old one and readded with 100m
deleted log added in step2.
same for standby redo logs.
On standby
was able to resize standby redo logs.
but cannot resize online redologs status is clearing or clearing_current.
please comment. thanks.

I assume you just had to wait until the Primary switched out of that online log so it became inactive at the standby as well? We track where the Primary is by marking the online redo log files at the standby as clearing_current so you can tell where the primary was at any given moment.
Make sure you create new standby redo log files at the Primary and Standby to match the new online redo log file size.
Larry

Similar Messages

The file structure online redo log, archived redo log and standby redo log

I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

FZheng:
Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
Edited by: 853153 on Jun 22, 2011 9:42 AM

Dataguard lost both Primary redo log and standby redo log files

Hi,
I am new to data guard, i came acorss a scenario where we loose both primary redo log file and standby redo log files.
Can someone please help me understand how to recover from this situation.
Thanks!

>loose both primary redo log file and standby redo log files
We have to be very clear.
There are (set A) online redo log files and (set B) standby redo log files at (location 1) Primary and (location 2) Standby.
The standby redo log files, depending on the configuration, aren't strictly mandatory. The standby can be applying redo without online redo log files present as well, depending on how it was setup.
So, the question is : Did you lose online redo log files at the primary ? Didn't the primary shutdown itself then ? If so, you have to do an incomplete recovery at the primary OR switch over to the standby (which may or may not have received the last transaction, depending on how it was configured and operating) OR restore from the standby (again, with possible loss of transactions) to the primary.
Hemant K Chitale

Require 9i Primary and Standby redo logs files same size?

Hi,
We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
I want to increase redo log files size, but i can't this do same time primary and standby side.
Is there a rule, primary and standby database instances have same size redo log files?
If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
, but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
Thank you for helps..

Thank you for your helps.. I found this issue answer:
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
Add or drop an online redo log file:
To add an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
To drop an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
Repeat the statement you used in Step 3 on each standby database.
Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
bye..

Online Redo logs instead of Standby Redo logs

RDBMS Version: 11.2.0.3/Platform : RHEL 6.3
To migrate a 3TB Database to a new DB server , we are going to use RMAN DUPLICATE.
Step1. Take full backup of DB + Standby Control file at primary site and transfer the Bkp files to Standby site
Step2. At standy site, we will run the RMAN duplicate target database for standby
After the above step, we don't want to create the standby redo logs because the newly restored DB in standby server is going to be the new Prod DB which application will be pointing to.
So, Can I skip the Standby Redo log creation part and create Online redo logs instead ?
As mentioned earlier, Our objective is not to create a proper Dataguard Standby DB setup. We just want to clone our DB to another server using RMAN Duplicate.

Tom wrote:
RDBMS Version: 11.2.0.3/Platform : RHEL 6.3
To migrate a 3TB Database to a new DB server , we are going to use RMAN DUPLICATE.
Step1. Take full backup of DB + Standby Control file at primary site and transfer the Bkp files to Standby site
Step2. At standy site, we will run the RMAN duplicate target database for standby
After the above step, we don't want to create the standby redo logs because the newly restored DB in standby server is going to be the new Prod DB which application will be pointing to.
So, Can I skip the Standby Redo log creation part and create Online redo logs instead ?
As mentioned earlier, Our objective is not to create a proper Dataguard Standby DB setup. We just want to clone our DB to another server using RMAN Duplicate.
Hi,
Take full backup of DB + Standby Control
We just want to clone our DB to another server using RMAN Duplicate
If you want only clone database of production, why you are take Standby controlfile?
If you don't want create standby database then, why you using DUPLICATE command with FOR STANDBY option.
You can use DUPLICATE command for clone database, without for standby option.
If you say no, we want create standby database and we will perform swithover,
then yes, you can use online redo logs for max performance mode.
and you can create standby redo logs on all database, but this redo logs will use by database when database role
is standby.
Regards
Mahir M. Quluzade

Online redo logs vs standby redo logs

Hi All,
Oracle version : 10.2.0.4
OS : SunOS 5.10 Generic_118855-36 i86pc i386 i86pc
This might be a silly question for the experts :(
We are having 2 standby databases and 1 logical database. Everything is running fine , I have one confusion : My primary server having 3 online redo log files and 3 standby redo log files (on primary local), but as per the architecture standby redo logs should be on standby server.My question is whether standby redo logs on standby are online redo logs of standby server or standby redo logs of primary server. e.g If i perform a log switch on primary then what is the role of sync and affirm, will lgwr write parallel on online redo logs ,standby redo logs (of primary) or online redo logs (of primary) and online redo logs (which is known as standby redo logs on standby ). Please help me to understand the scenerio.
Thanks in advance!

RFS receives redo information from the primary database.
RFS can write the redo into standby redo logs or directly to archived redo logs. Each LNSn and ARCn process from the primary database has its own RFS process.
A standby redo log is used only when the database is in the standby role to store redo data received from the primary database. Standby redo logs form a separate pool of log file groups.
Configuring standby redo log files is highly recommended on all standby databases in a Data Guard configuration, including the primary database to aid in role reversal.
A standby redo log is required to implement:
• The maximum protection and maximum availability levels of data protection
• Real-time apply
• Cascaded redo log destinations
Standby redo logs are recommended for maximum performance data protection mode. Unless you are using the real-time apply feature, standby redo logs must be archived before the data can be applied to the standby database. The standby archival operation occurs automatically.

Dataguard Solution for standby redo log file groups

Respected Experts,
My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.
Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
need to be created.
Thanks and Regards
Monoj Das

My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.To configure standby either you can use duplicate target database for standby
or
1) restore standby controlfile
2) mount standby database
3) restore database
and configure standby paraemter then start MRP, will do.
http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
need to be created.It depends which parameter you want to use, if you mention log_archive_dest_2='service ARCH ' then no need to create any standby redo log file groups,
If you use log_archive_dest_2='service LGWR ' here transport will be in terms of redo and you need standby redo log files on standby database. Which is realtime.
When you use LGWR, data lost will be less if in case of any online redo log file lost. which is recommended.
HTH.

Standby Redo Log Files and Directory Structure in Standby Site

Hi Guru's
I just want to confirm, i know that if the Directory structure is different i need to mention these 2 parameter in pfile
on primary site:
DB_CONVERT_DATAFILE='standby','primary'
LOG_CONVERT_DATAFILE='standby','primary'
On secondary Site:
DB_CONVERT_DATAFILE='primary','standby'
LOG_CONVERT_DATAFILE='primary','standby'
But i want to confirm this wheather i need to issue the complete path of the directory in both the above paramtere:
like:
DB_CONVERT_DATAFILE='/u01/oracle/app/oracle/oradata/standby','/u01/oracle/app/oracle/oradata/primary'
LOG_CONVERT_DATAFILE='/u01/oracle/app/oracle/oradata/standby','/u01/oracle/app/oracle/oradata/primary'
Second Confusion:-
After transferring Redo Standby log files created on primary and taken to standby on the above mentioned directory structure and after restoring the backup of primary db alongwith the standby control file will not impact the physical standby redo log placed on the above mentioned location.
Thanks in advance for your help

Hello,
Regarding your 1st question, you need to provide the complete path and not just the directory name.
On the standby:
db_file_name_convert='<Full path of the datafiles on primary server>','<full path of the datafiles to be stored on the standby server>';
log_file_name_convert='<Full path of the redo logfiles on primary server>','<full path of the redo logfiles on the standby server>';
Second Confusion:-
After transferring Redo Standby log files created on primary and taken to standby on the above mentioned directory structure and after restoring the backup of primary db alongwith the standby control file will not impact the physical standby redo log placed on the above mentioned location.
How are you creating the standby database ? Using RMAN duplicate or through the restore/recovery options ?
You can create the standby redo logs later.
Regards,
Shivananda

Why do we need standby redo log on Primary database.

Hi Gurus,
I was going through the document in OBE,
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I have two queries:
1) I noticed the statement -
"Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
Why do we have to create standby redo log on a primary database?
2) There is another statement --
"It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
Why do we need one additional standby redo log group than in Primary database.
Could anyone please explain to me in simple words.
Thanks
Cherrish Vaidiyan

Hi,
1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
Regards
Anudeep

Standby Redo log creation

DB version: 11.2
OS : AIX 6.1
We have a 2 node RAC. We have one Disk group for all datafiles, tempfiles, redo logs,..etc.
Currenly in our primary DB, Redo logs look like
SQL> SELECT a.group#, b.thread#, a.member, b.bytes
FROM v$logfile a, v$log b WHERE a.group# = b.group#
order by a.group# , b.thread# 2    3 ;
         GROUP#         THREAD# MEMBER                                BYTES
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
6 rows selected.
1 member per group
3 group per instanceWe need to create a physical standby DB for the above DB with Real Time apply. For standby Redo logs, I need one extra log file for each Instance.
So, I am going to add
     group# 7 for thread 1
     and
     group# 8 for thread 2
Finally , SRLs will look like
         GROUP#         THREAD# MEMBER                                BYTES
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
           7               1 +ORCL_DG/orcl/orcl_log07.dbf         104857600 -------> Additional
              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
           8               2 +ORCL_DG/orcl/orcl_log08.dbf         104857600 -------> AdditionalAnything wrong with my proposed SRL creation ?

JOE_humble wrote:
DB version: 11.2
OS : AIX 6.1
We have a 2 node RAC. We have one Disk group for all datafiles, tempfiles, redo logs,..etc.
Currenly in our primary DB, Redo logs look like
SQL> SELECT a.group#, b.thread#, a.member, b.bytes
FROM v$logfile a, v$log b WHERE a.group# = b.group#
order by a.group# , b.thread# 2    3 ;
GROUP#         THREAD# MEMBER                                BYTES
1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
6 rows selected.
1 member per group
3 group per instanceWe need to create a physical standby DB for the above DB with Real Time apply. For standby Redo logs, I need one extra log file for each Instance.
So, I am going to add
     group# 7 for thread 1
     and
     group# 8 for thread 2
Finally , SRLs will look like
GROUP#         THREAD# MEMBER                                BYTES
1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
           7               1 +ORCL_DG/orcl/orcl_log07.dbf         104857600 -------> Additional
4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
           8               2 +ORCL_DG/orcl/orcl_log08.dbf         104857600 -------> AdditionalAnything wrong with my proposed SRL creation ?You have to create equal numbers & equal or greater size of standby redo log files than Online redo log files.
Refer http://www.pythian.com/news/581/oracle-standby-redo-logs/ to configure standby redo log files.

Standby redo log does not exist...

Hello,
Oracle 11.2.0.2, running on Solaris
This is kind of a continuation of a previous thread, but this is a different question:
I have a DG configuration, with the primary database having 2 redo logs per redo log group.
And, it has 2 redo logs for the standby redo log groups.
But I just found out something very strange:
For the standby redo log group, even though the database shows it has two redo log files per group, the second file does not actually exist on the file system.
And, I have no idea where it is, or why the database is not complaining about it.
See below:
SQL> select * from v$logfile;
         GROUP# STATUS    TYPE    MEMBER                                        IS_
             11           STANDBY /opt/oracle/oradata2/PROD/REDO01A_STDBY.log NO
             11           STANDBY /opt/oracle/oradata3/PROD/REDO01B_STDBY.log NO    <== does not exist on file system
             12           STANDBY /opt/oracle/oradata2/PROD/REDO02A_STDBY.log NO
             12           STANDBY /opt/oracle/oradata3/PROD/REDO02B_STDBY.log NO    <== does not exist on file system
             13           STANDBY /opt/oracle/oradata2/PROD/REDO03A_STDBY.log NO
             13           STANDBY /opt/oracle/oradata3/PROD/REDO03B_STDBY.log NO    <== does not exist on file system
             14           STANDBY /opt/oracle/oradata2/PROD/REDO04A_STDBY.log NO
             14           STANDBY /opt/oracle/oradata3/PROD/REDO04B_STDBY.log NO    <== does not exist on file system
             15           STANDBY /opt/oracle/oradata2/PROD/REDO05A_STDBY.log NO
             15           STANDBY /opt/oracle/oradata3/PROD/REDO05B_STDBY.log NO    <== does not exist on file system
              5           ONLINE /opt/oracle/oradata1/PROD/REDO05A.log       NO
              5           ONLINE /opt/oracle/oradata2/PROD/REDO05B.log       NO
              6           ONLINE /opt/oracle/oradata1/PROD/REDO06A.log       NO
              6           ONLINE /opt/oracle/oradata2/PROD/REDO06B.log       NO
              7           ONLINE /opt/oracle/oradata1/PROD/REDO07A.log       NO
              7           ONLINE /opt/oracle/oradata2/PROD/REDO07B.log       NO
              8           ONLINE /opt/oracle/oradata1/PROD/REDO08A.log       NO
              8           ONLINE /opt/oracle/oradata2/PROD/REDO08B.log       NO
18 rows selected.
Notice below that the "B" redo logs do not exist.
SQL> !ls -l /opt/oracle/oradata3/PROD/REDO01B_STDBY.log
/opt/oracle/oradata3/PROD/REDO01B_STDBY.log: No such file or directory
SQL> !ls -l /opt/oracle/oradata3/PROD/REDO02B_STDBY.log
/opt/oracle/oradata3/PROD/REDO02B_STDBY.log: No such file or directory
SQL> !ls -l /opt/oracle/oradata3/PROD/REDO03B_STDBY.log
/opt/oracle/oradata3/PROD/REDO03B_STDBY.log: No such file or directory
SQL> !ls -l /opt/oracle/oradata3/PROD/REDO04B_STDBY.log
/opt/oracle/oradata3/PROD/REDO04B_STDBY.log: No such file or directory
SQL> !ls -l /opt/oracle/oradata3/PROD/REDO05B_STDBY.log
/opt/oracle/oradata3/PROD/REDO05B_STDBY.log: No such file or directory
But here, you can see that the "A" redo logs actually do exist.
SQL> !ls -l /opt/oracle/oradata2/PROD/REDO01A_STDBY.log
-rw-r-----   1 oracle   dba      536871424 Jan 7 2011 /opt/oracle/oradata2/PROD/REDO01A_STDBY.log

Hello;
I'm able to recreate
SQL> select * from v$logfile;
    GROUP# STATUS TYPE    MEMBER                                             IS_
         3         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_3_8gtxxrl6_.log
         2         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_2_8gtxxr4f_.log
         1         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_1_8gtxxqng_.log
         4         STANDBY /u01/app/oracle/oradata/RECOVER2/redo04.log        NO
         5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
         6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NOAnd then
SQL> !ls -al /u01/app/oracle/oradata/RECOVER2/redo04.log
ls: /u01/app/oracle/oradata/RECOVER2/redo04.log: No such file or directoryChecking... *Not there, but Oracle ( 11.2.0.3 ) allows clean up without barking. Had only one member so I did GROUP drop.
SQL> ALTER DATABASE DROP LOGFILE GROUP 4;
Database altered.
SQL> select * from v$logfile;
    GROUP# STATUS TYPE    MEMBER                                             IS_
         3         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_3_8gtxxrl6_.log
         2         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_2_8gtxxr4f_.log
         1         ONLINE /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                           elog/o1_mf_1_8gtxxqng_.log
         5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
         6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NO
SQL> Best Regards
mseberg

What is the purpose of standby redo log files

Hi,
What is the purpose of the standby redo log files in DR?
what if the standby redo log files are created? or else not created?
Please explain
Thanks

3.1.3 Configure a Standby Redo LogA standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.>
Reference http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
HTH
Anand

Use of standby redo log files in primary database

Hi All,
What is the exact use of setting up standby redo log files in the primary database on a data guard setup?
any good documents?

A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.
refer the link,and Perform the following steps to configure the standby redo log.:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
refer the link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1023371

Number of Standby Redo Logs on Standby Database

Hello All:
Per various docs i calculated and created the number of standby redo logs.
I created 6 standby redo logs in addition to 3 online.
However, i always see only two standby redo logs being used. Any ideas?
Thanks
San~

try:
alter system archive log current;
and get information:
select * from v$logfile;
select * from v$log;
Thanks.

Data Guard : Standby Redo Log CONFUSION

Trying to set up test Standby db on 10.2.0
I am well confused about below step 3.1.3, how is the normal redo linked with standby redo, should standby not be members of orginal redo groups?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
Original redo logs:
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
         1          1         28   52428800          1 YES INACTIVE                375136 22-NOV-07
         2          1         29   52428800          1 YES INACTIVE                375138 22-NOV-07
         3          1         30   52428800          1 NO CURRENT                 375143 22-NOV-07I added below from notes:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
('/u01/oracle/oradata/db01/redo01_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11
('/u02/oracle/oradata/db01/redo02_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 12
('/u03/oracle/oradata/db01/redo03_stb.log') SIZE 50M;After few alter system switch logfile; I still have:
    GROUP#    THREAD# SEQUENCE# ARC STATUS
        10          0          0 YES UNASSIGNED
        11          0          0 YES UNASSIGNED
        12          0          0 YES UNASSIGNEDAll are UNASSIGNED, should one standby group not be ACTIVE like the above link shows.
Many think for any help

First things first:
From the Docs.:
"Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database."
You are 1 short!

Resizing online and standby redo log in dataguard setup.

Similar Messages

Maybe you are looking for