Adding STAND BY REDO LOG in the Primary side........

Hi All,
I have set STANDBY_FILE_MANAGEMENT=AUTO in standby side and also LOG_FILE_NAME_CONVERT is pointing to an exiting location at OS level...
When i added a datafile to an existing tablespace in the primary side and performed a log switch on the same . The added datafile got
relflected in STANDBY side ...
But when I am trying to add a standby logfile (new group) is not getting added .........
Please help me on this...........
For this will I need to perform the below steps .
1-Add a standby redolog in the Primary side......
2-then Cancel the managed recovery process from the standby side...
3- Add the same standby redolog (same name and size) in the standby side
4-put the standby in recovery mode ......
Thanks

Thanks for the reply ......
I have gone thgrough it....but i donot find my answer .....
My question is "Why *STANDBY_FILE_MANAGEMENT=AUTO* functionality is not adding a standby redolog in STANDBY SIDE automatically
when i am adding a standby redolog in the PRIMARY SIDE.....
Thanks.......

Similar Messages

Standby receiving redo logs although the log_archive_dest_n were wronly...

Hi,
The Primary site has two servers, each with one instance, using RAC.
The Standby site has another two servers and two instances using also RAC.
This is a logical Standby database, the Dataguard is working fine and the data is being replicated.
This is the configuration of the second instance of the Standby site (Server1b)
SQL> show parameter arch
NAME      TYPE      VALUE
============================================================
archive_lag_target      integer      0
log_archive_config      string      dg_config=(DB_S1, DB_S2)
log_archive_dest      string
log_archive_dest_1      string      LOCATION=+DB_ARCHIVE/DB/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DB_S1
log_archive_dest_5 string      service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=DB_S2_XPT)(INSTANCE_NAME=DB1)(SERVER=dedicated)))", LGWR NOAFFIRM delay=0 OPTIONALmax_failure=0 reopen=10 async=61440 db_unique_name="DB_S2" register nonet_timeout valid_for=(online_logfile,primary_role)
log_archive_dest_state_1 string      enable
log_archive_dest_state_10 string      enable
log_archive_dest_state_2 string      ENABLE
log_archive_dest_state_3 string      enable
log_archive_dest_state_4 string      ALTERNATE
log_archive_dest_state_5 string      ENABLE
log_archive_dest_state_6 string      enable
log_archive_dest_state_7 string      enable
log_archive_dest_state_8 string      enable
log_archive_dest_state_9 string      enable
log_archive_duplex_dest      string
log_archive_format      string      %t_%s_%r.dbf
log_archive_local_first      boolean      TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start      boolean      FALSE
log_archive_trace      integer      0
remote_archive_enable string      true
standby_archive_dest string
SQL>
ID      DESTINATION                STATUS      TARGET      SCHEDULE      PROCESS      MID
=============================================================================
1      +DB_ARCHIVE/db/                                           VALID          PRIMARY      ACTIVE        ARCH           0
2                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
3                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
4                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
5 (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=DB_S2_XPT)(INSTANCE_NAME=DB1)(SERVER=dedicated)))      VALID     STANDBY      PENDING      LGWR      0
6 INACTIVE PRIMARY INACTIVE ARCH      0
7 INACTIVE PRIMARY INACTIVE ARCH 0
8 INACTIVE PRIMARY INACTIVE ARCH 0
9 INACTIVE PRIMARY INACTIVE ARCH 0
10 INACTIVE PRIMARY INACTIVE ARCH 0
11 /opt/oracle/product/10.1.0/db_1/dbs VALID      STANDBY      ACTIVE      RFS      0
/arch
Here the configuration does not make sense at all. So, how is it possible that this Server (Server1b) is receiving redo logs from the Primary site?
Thank you.
Edited by: user11281526 on 21-oct-2009 7:39
Edited by: user11281526 on 22-oct-2009 0:37
Edited by: user11281526 on 22-oct-2009 0:39
Edited by: user11281526 on 22-oct-2009 0:45

Hi,
The Primary site has two servers, each with one instance, using RAC.
The Standby site has another two servers and two instances using also RAC.
This is a logical Standby database, the Dataguard is working fine and the data is being replicated.
This is the configuration of the second instance of the Standby site (Server1b)
SQL> show parameter arch
NAME      TYPE      VALUE
============================================================
archive_lag_target      integer      0
log_archive_config      string      dg_config=(DB_S1, DB_S2)
log_archive_dest      string
log_archive_dest_1      string      LOCATION=+DB_ARCHIVE/DB/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=DB_S1
log_archive_dest_5 string      service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=DB_S2_XPT)(INSTANCE_NAME=DB1)(SERVER=dedicated)))", LGWR NOAFFIRM delay=0 OPTIONALmax_failure=0 reopen=10 async=61440 db_unique_name="DB_S2" register nonet_timeout valid_for=(online_logfile,primary_role)
log_archive_dest_state_1 string      enable
log_archive_dest_state_10 string      enable
log_archive_dest_state_2 string      ENABLE
log_archive_dest_state_3 string      enable
log_archive_dest_state_4 string      ALTERNATE
log_archive_dest_state_5 string      ENABLE
log_archive_dest_state_6 string      enable
log_archive_dest_state_7 string      enable
log_archive_dest_state_8 string      enable
log_archive_dest_state_9 string      enable
log_archive_duplex_dest      string
log_archive_format      string      %t_%s_%r.dbf
log_archive_local_first      boolean      TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start      boolean      FALSE
log_archive_trace      integer      0
remote_archive_enable string      true
standby_archive_dest string
SQL>
ID      DESTINATION                STATUS      TARGET      SCHEDULE      PROCESS      MID
=============================================================================
1      +DB_ARCHIVE/db/                                           VALID          PRIMARY      ACTIVE        ARCH           0
2                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
3                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
4                     INACTIVE      PRIMARY      INACTIVE      ARCH      0
5 (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=DB_S2_XPT)(INSTANCE_NAME=DB1)(SERVER=dedicated)))      VALID     STANDBY      PENDING      LGWR      0
6 INACTIVE PRIMARY INACTIVE ARCH      0
7 INACTIVE PRIMARY INACTIVE ARCH 0
8 INACTIVE PRIMARY INACTIVE ARCH 0
9 INACTIVE PRIMARY INACTIVE ARCH 0
10 INACTIVE PRIMARY INACTIVE ARCH 0
11 /opt/oracle/product/10.1.0/db_1/dbs VALID      STANDBY      ACTIVE      RFS      0
/arch
Here the configuration does not make sense at all. So, how is it possible that this Server (Server1b) is receiving redo logs from the Primary site?
Thank you.
Edited by: user11281526 on 21-oct-2009 7:39
Edited by: user11281526 on 22-oct-2009 0:37
Edited by: user11281526 on 22-oct-2009 0:39
Edited by: user11281526 on 22-oct-2009 0:45

Clearing Online redo logs on the target physical standby

Hi,
Version 11202.
Primary on machine A
Standby on machine B
Following note: 11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus [ID 1304939.1].
Online redo logs on the target physical standby need to be cleared before that standby database can become a primary database. And later :
On the target physical standby run the following query to determine if the online redo logs have not been cleared... 1) I did not understand where i should run the query. On machine A or on machine B ?
2)
Online redo logs on the target physical standby need to be CLEARED
What does it mean that it need to be CLEARED ? Does transaction might be lost by running the clearing command?
Thanks

I have used my note many times in production.
For example they needed to do some power work on the main server room a few months back on the weekend.
We did switchovers until the work was complete and then a switch back.
I wrote a short document called "Switchover post-mortem lessons" the main point from that was :
1.
getting ORA-01017 issues in Oracle forms ( Application ) after the switchover to standby.
The issue was caused by the Standby database having a different parameter for passwords than the Primary database.
This did not show up in testing because all the tester we used had converted passwords from Oracle 10.
Solution
When in doubt issue this on the new Primary :
SQL>ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;
Note: This command can be issued repeatedly with no negative effect on the system.2.
The query to check switch_over status was returning "LOG SWITCH GAP"
select switchover_status from v$database;
This is an issue because Oracle says the return values should be one of these :
NOT ALLOWED
SESSIONS ACTIVE
SWITCHOVER PENDING
SWITCHOVER LATENT
TO PRIMARY
TO STANDBY
RECOVERY NEEDED
LOG SWITCH GAP is not one of the expected value. In addition this phase is not search friendly either on the Oracle support site or your favorite search engine.
Given this I ran this query :
SELECT
NAME AS STANDBY,
SEQUENCE#,
APPLIED,
COMPLETION_TIME
FROM
V$ARCHIVED_LOG;
Solution
SQL>ALTER SYSTEM SWITCH LOGFILE;
And wait a few minutesMy switchover document had no issue.
Best Regards
mseberg

Differetn redo log names on primary db and standby db.

we are using oracle 10.2.0.2 to run sap. we plan to use data guard.the os is suse linux 10.3.
the archived redo log name's prefix is '1_' like '1_167109_678247864.dbf' on primary db.
if i recover standy database mannuly with cmd 'ALTER DATABASE RECOVER automatic standby database' to fix redo log gap, the required archived redo log name's prefix is 'PRDarch1_' like 'PRDarch1_167260_678247864.dbf'.
i checked the oracle parameter 'LOG_ARCHIVE_FORMAT' on both side were set to '%t_%s_%r.dbf'.
my question is the different name have any effect on datagurad? Or we just can ignore it, because it doesn't matter.
thanks in advance.

I'm not interested in a debate so much as finding the answer. Thanks for the info. And welcome to the forum by the way.
That said I would think B14239-05 would answer your question.
In section 5.7.1 it shows:
LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc
You may be correct on the default, but they only answer I can give you is I have never setup Data Guard that way. I hope this saves you some time.
Where did you find this? (log_archive_dest_1 = "LOCATION=/oracle/PRD/oraarch/PRDarch MANDATORY REOPEN",)
I would consider avoiding the use of MANDATORY. This attribute will cause you a world of trouble if your Standby is unreachable.
Also if you are using a Flash Recovery Area you do not need to setup a local archiving destination.
If you are not using Flash Recovery with Data Guard you should. Try testing a failover without it.
Best Regards
mseberg

Archiver is unable to archive a redo log because the output device is full

Dear Experts,
When I logged to EM of my DB 11g R2. I found the following:
- Database Instance Status : Down
- Details
The instance has been terminated by a database process because of a fatal internal condition, or a critical background process was killed by the user.
Archiver is unable to archive a redo log because the output device is full or unavailable.
- Agent Connection to Instance
Status: Failed
Details: ORA-01034: ORACLE not available
Thank you in advance for any help you provide
Best Regards

mahmoudrabie wrote:
Thank you 919294
I was root not oracle and when I switch to oracle (which is member of dba group), the I ran
rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Mar 7 13:27:06 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
then as friends suggested
RMAN> backup archivelog all delete input;
Starting backup at 07-MAR-12
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/07/2012 13:28:00
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directorycheck the connection
connected to target database (not started)*so first startup the databaseto mount and then perform the operation
--neeraj

Adding redo logs for dataguard primary server

Dear all:
i have physical dataguard servers
i want to add new redologs for primary server with big size ..
please advice what will be the action with stand by server.
Thanks ,,

Dear all:
i have physical dataguard servers
i want to add new redologs for primary server with
big size ..
please advice what will be the action with stand by
server.
Thanks ,,Most of these information are kept in the control file . You have to recreate your stand by control file after you added the new online redo logs. Transfer this to the standby server , with the the new online redo redo while you standby is down . Your standby system should be able to recognize it when it goes back to stand by mode.

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

How long redo logs keep the transactions?

I learn Oracle and decide to do an experiment. There was a table in the test database. I deleted the file that contained this table via OS. And then I added transactions to this table.
I did 'insert' several times, then 'commit', then 'alter system switch logfile' several times, 'alter system flush buffer_cache', 'alter system flush shared_pool' and nothing happened. I could add and take data from this table successfully. Alert log showed the error only when I shutdown the database.
SQL> shutdown immediate
ORA-01116: error in opening database file 13
ORA-01110: data file 13: '/oracle/oradata/test5/POSTEMPTEST2.dbf'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
I understand that transactions are put in the redo logs at first, and then are transferred to the datafile on disk. I thought that command 'ALTER SYSTEM CHECKPOINT' writes transactions from redo logs to datafile on disk, but I was wrong. How long redo logs keep transactions? Is there the way to push data from redo logs to datafile?
I use Oracle 10.2.0.1.0.

i believe this time you will see the error message during your SQLsWRONG!probably you did not read the complete post of mine before saying WRONG. You tell me, if data file containing a table is deleted at OS level (in *nix), and then you try to insert data in this table and want to retrieve the data from the table (If data is not in db cache or cache has been flushed), from where data will come? Or if you want to insert some data into this table for which new extent are required to be allocated, where it will be allocated? Will your SQLs succeed or will return some error? Either SQL should return you data (which is not possible as data file is no there to fetch the data), or SQL should fail with some error message.
I mimicked the situation on IBM AIX, following is the outcome.
Enter user-name: system/salman
Connected to:
Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
SQL> create table test as select * from dba_tables;
Table created.
SQL> alter table test move tablespace users;
Table altered.
SQL> insert into test select * from dba_tables;
2500 rows created.
SQL> /
2500 rows created.
SQL> /
2500 rows created.
SQL> commit;
Commit complete.Now i deleted the users01.dbf file at OS level and then execute following INSERT
SQL> insert into test select * from test;
insert into test select * from test
ERROR at line 1:
ORA-01565: error in identifying file '/oracle/oradata/test/users01.dbf'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3Salman

Adding bigger size Redo log groups In RAC , ASM

Hi Folks,
Database version - 10.1.0.4.0
OS version - AIX 5.3
RAC node 2 and ASM
We had 4 redo log groups of lesser size on both nodes.yesterday I added 4 new groups of bigger size using pl/sql developer tool and deleted 2 old redolog groups. But I m not able to delete remaining 2 old groups.
ORA-01567 dropping log2 would have less than 2 log files for instance 1.
Our redolog files are on SAN and both node points to same storage. when I fired this query from command prompt
SELECT v$logfile.member, v$logfile.group#, v$log.status, v$log.bytes
FROM v$log, v$logfile
WHERE v$log.group# = v$logfile.group#;
I got same result for both nodes.
The problem I suspect is that All the 4 new log groups are added to instance 2 and its 2 old grouips are are also deleted.
Now my ques is that :
1. shouild I have added redo log groups separately on both nodes even storage is same for both nodes ?
2. redologs groups are defined separately for each node ?
How should I assign 2 new redo log groups to instance 1 ?
Regards,

Please check:
SQL> select instance_number, instance_name, thread# from gv$instance;
Show Instance with thread ID
SQL> select group#, thread#, members ,status from v$log;
Check number groups in each of thread.
On RAC, you have to add redo log Group each of node (each of thread )
SQL> select group#, thread#, members ,status from v$log;
From your environment ,I think you have 2 nodes = 2 thread
If these're thread 1, 2
So, add redo group should:
Example:
ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 11 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 12 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 13 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 14 ( '+DATA') SIZE 500M;
You should check each thread has >= 2 groups and that group had "INACTIVE" status before drop:
SQL> select group#, thread#, members ,status from v$log;
My Idea, you should have 3 redo log groups for each node(thread)
Good Luck

When is anything written to standby redo logs on standby database?

I am on Oracle 10.2.0.4 on HP UNIX. I have read Oracle 10.2 concepts guide on technet.oracle.com, have read may article on metalink and internet, yet I am unable to verify when anything is written to standby redo logs on stand by database.
I have a simple database reconfiguration: a primary database and one standby database.
I created primary database and set up log_archive_dest_2 to use LGWR SYNC AFFIRM
I have created standby redo logs on primary.
alter database add standby logfile GROUP
I create standby control file on primary.
I copied all the primary information to create standby database. I have put standby database in managed recovery.
I did archive log switches, I created a table and inserted information in table.
I never saw standby redo logs updated on standby database by looking at timestamp of standby redo log files.
I then setup database in maximum availability mode by running following on primary:
Alter database set standby database to maximize availability
When I do insert into my tables, I do see standby redo log files on primary database being updated, but I have never seen standby redo logs on standby database updated. Why?
I am still at loss when actually standby redo logs are updated on standby database.
When I read Oracle 9i database documentation on data guard, it says that you do not need standby redo logs on primary instead you need them on standby. Only reason, you need them on primary is from primary changes role to standby database, so standby redo logs on standby database should be updated instead of standby redo logs on primary.

What is the PROTECTION_MODE ,PROTECTION_LEVEL values of your database.
As per metalink:--
Create standby redo log files, if necessary:
Standby redo logs are necessary for the higher protection levels such as
Guaranteed, Instant, and Rapid. In these protection modes LGWR from the
Primary host writes transactions directly to the standby redo logs.
This enables no data loss solutions and reduces the amount of data loss
in the event of failure. Standby redo logs are not necessary if you are using
the delayed protection mode.
If you configure standby redo on the standby then you should also configure
standby redo logs on the primary database. Even though the standby redo logs
are not used when the database is running in the primary role, configuring
the standby redo logs on the primary database is recommended in preparation
for an eventual switchover operation.
Standby redo logs must be archived before the data can be applied to the
standby database. The standby archival operation occurs automatically, even if
the standby database is not in ARCHIVELOG mode. However, the archiver process
must be started on the standby database. Note that the use of the archiver
process (ARCn) is a requirement for selection of a standby redo log.
METALINK ID:- Doc ID: Note:219344.1
Edited by: Anand... on Sep 15, 2008 2:15 AM

Physical Standby Online Redo log files,

Hi,
I'm trying to create a physical standby database (10.2.0.3). I'm a little confused about the requirement for online redo logs on the standby.
in my standby alert log I get the following when I issue:
SQL> alter database recover managed standby database disconnect from session
"ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/appl/oradata/prod/prod_1_redo_01_02.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3"
/appl/oradata/prod/prod_1_redo_01_02.log is the path to the location of the online redo logs on the production system. This file does not exist on the standby filesystem so the error is correct.
I assume that it gets this information from the standby control file I created on the production system and copied over to the standby.
Do I need to copy the online redo logs from the primary over to the standby site or do I need to create online redo logs on the standby?
Does the standby need to have redo log files?
I'm not talking about 'standby log files' of the type created using 'alter database add standby log file'. I've not got that far yet.
I just need to establish if a physical standby requires online redo log files?
Thanks in advance,
user234564

I wanted to update this thread since I've been dealing with the exact same errors. The basic question is: "does a physical standby need the online redo logs?"
Answer: Not really, until one wants to switchover or failover (and become a primary database). Furthermore, whenever the MRP process is started, Oracle prepares for a possible switchover/failover by "clearing" the online redo logs (MetaLink note# 352879.1). It is not a big deal, since Oracle will build the actual redo files when the "alter database open resetlogs" is accomplished during a "role transition."
In our situation, we have decided to use our standby for nightly exports. We stop MRP, open the database read-only, then restart MRP. We built these standby DBs with RMAN. The RMAN duplicate process will not build the online redo log files until the database is opened for read/write (with resetlogs). However, we haven't had a need for read/write (i.e. a switchover).
Thus, every morning we have been getting the same errors that "user234564" posted above. At first the errors seemed scary, then we realized they were just a nusiance. In order to clean things up, all I did was just "cp" our stanby redo logs (SRL) into our online redo directories ensuring the names matched what was in v$logfile. When I restarted MRP, the alert log clearly showed Oracle clearing these "newly found" online redo logs.

Standby Redo Log Groups

I have a problem on my standby database.
When I check the status of v$standby_log
one loggroup by one is getting active.
At the end all 15 loggroups have the status active and I get the message no logs of size #### available
What is the reason that those logs are not written to disk ?
MRP is running.
database is in archivelogmode
flashback is enabled
Recover database using backup controlfile is not working
archive log all not allowed the backup controlfile....

This issue is normally found when the 'standby redo' log on the standby is not as large as the 'redo' log on the primary.
Per oracle, all standby redo log size should be equal to or larger than the largest redo log on the primary database. Oracle recommends keeping all the redo logs and standby logs of the same size.
Would you like to confirm all logs have been set as oracle mandates?
Cheers.

Standby redo log file

Hi,
From oracle document i know in the standby side the RFS process writes to Standby redo log file -> archive log and the MRP procees applys the archive logs to the standby database.
my question is ,if we dont create standby redo log file what happens?

Hello;
When redo is received by an RFS on the standby , the RFS process writes the redo data into archived redo logs or optionally to the SRL.
Standby Redo Logs is where the RFS process at your Standby database writes incoming redo, they help performance because the RFS does not have to create the Archive log file.
Standby redo logs are a component of the Data Guard setup. They should be the same size as the redo logs on the Primary.
Standby Redo Logs do not not to be multiplexed.
I would create SRL them on both the Primary and the Standby. Think of it as one database in either Standby or Primary Mode. If you have to switchover you still need them.
If you have SRL's setup and need to do either a failover or switchover it should occur faster and safer.
Best Regards
mseberg

Oracle DataGuard - Standy Redo log on physical Standby db

Hello Guys,
A quick question on my 10.2.0.2 db with Windows 2003 x64 OSs.
I have 2 machines - One for primary & the other for physical standby
I have successfully setup DG with Real Time Apply and also tested switchover & failover scenarios and they work well and as expected...
But I have a query which popped up when I was trying to set this up at home.
I create the physical standby db by shutting the primary db and copying all the datafiles, tempfiles,online redo logs and then creating a standby control file which will be used for the physical standby db to start off with.
After mounting the standby db, I tried to create standby redo logs files starting with Group 4 but I got error that standby group 4 already exists.
Upon querying v$logfile view, I noticed that the standby redo logs that I created on primary are also showing up on the standby db which I understand is from the standby control file.
So here is my quesiton: What is correct method of creating these standby redo logs on the standby database?
I know that I could drop those 4 standby redo logs from the standby db and recreate them but all the DG docs online and the documents that I have referred say that I should create the standby redo logs on the standby as I did on the primary but how can this duplication be avoided i.e. from the standby control file?
I know that I could use another method to create a hot backup such as RMAN etc...but I wanted to follow this way of shutting down the primary and copy the relevant database files.
Any help appreciated...and thanks in advance guys!
-Bharath

so with the setup that I used, i.e. create a standby control file which contains info about the standby redo logs at the primary site, should I also copy over the standby redo logs from the primary to standby as I only copied the datafiles, tempfile(s) & online redo logs? But then the filenames of the standby redo logs will be the exact same as that of the primary. Will that cause any issue during a switchover/failover?
I don't remember exactly how I did it when I got the whole thing working but I have a vague remembrance that I drop the std. redo log files entries from the std database and then recreate new ones with different filenames (as compared to primary).
Thanks

Data Guard: standby archivelog files not the same as the primary archivelog

From reading the Data Guard doco, one gets the impression that that the standby redo archive logs are just a mirror of those from the primary, that the shipped and applied archived redo logs from the primary are what end up in the standby archive directories.
However I have noted that the files are not the same (md5sum is different), which is concerning as using Oracle's archive log naming recommendation, the files have identical names.
Does this mean that the Standbys redologs can not be used as a source of redo logs if one had to restore using a backup of the primary database?
i.e. Can you recover using an RMAN backup of the primary, and redo logs from the standby?

Hi MSK, I agree, that's exactly what I thought. I'm confused though why the logs do not match. Perhaps it is just metadata in the log that has changed, not redo data.
Anyone have any knowledge on why the archivelogs are different on the standby to those on the primary?

Adding STAND BY REDO LOG in the Primary side........

Similar Messages

Maybe you are looking for