Clearing redo in phyical standby

Hi
I know that the online redologs are not being used in physical standby database.
So why do I see "CLEARING_CURRENT" or "CLEARING" in their status? and their status changes.
and
When I perform switch logfile in production, in standby "clearing current log" also changes

No help is possible if you can not, or will not, answer the questions that were asked.
Redo log files didn't exist before version 6 of Oracle so clearly "any version" is not possible. Nor is it possible to
create a Physical Data Guard standby in "any version."
Similarly no one trying to help you can check the docs for "any version."
We don't ask this question to waste your time ... we ask it to avoid wasting ours.

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

Physical stndby doesn'1 apply redo or primary standby didn't transport redo

I setup physical standby (OEL5.0, DB 11.2), every things seem right. But when i create table on primary DB, it does not appear on standby database. The Physical standby doesn'1 apply redo or primary standby didn't transport redo to standby Datadase
Please consider mine configuration
----Standby :
SQL> select database_role, protection_mode, log_mode from v$database;
DATABASE_ROLE PROTECTION_MODE LOG_MODE
PHYSICAL STANDBY MAXIMUM PERFORMANCE ARCHIVELOG
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
Next log sequence to archive 40
Current log sequence 40
------Primary :
SQL> select database_role, protection_mode, open_mode from v$database;
DATABASE_ROLE PROTECTION_MODE OPEN_MODE
PRIMARY MAXIMUM PERFORMANCE READ WRITE
SQL> create table test_stby (
2 cot_1 number,
3 cot_2 number);
Table created.
SQL> insert into test_stby values (10,11);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
---- Standby :
SQL> SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
no rows selected
SQL> SELECT PROCESS, STATUS,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS FROM V$MANAGED_STANDBY;
PROCESS STATUS SEQUENCE# BLOCK# BLOCKS DELAY_MINS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MRP0 WAIT_FOR_LOG 40 0 0 0
- Standby cancel redo apply, open read only and query for table test_stby, it does not have this table
Please help
Ch

I did solved this problem :)

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.

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

Unable to ship Redo logs to standby DB (Oracle Data Gaurd)

Hi all,
We have configured Oracle Data Gaurd between our Production (NPP) & Standby (NPP_DR).
The configuration is complete however, the production is unable to ship redo logs to standby DB.
We keep getting the error "PING[ARC0]: Heartbeat failed to connect to standby 'NPP_DR'. Error is 12154." in Primary DB
Primary & DR are on different boxes.
Please see the logs below in the production alert log file & npp_arc0_18944.trc trace files:
npp_arc0_18944.trc :*
2011-01-19 09:17:38.007 62692 kcrr.c
Error 12154 received logging on to the standby
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'NPP_DR'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'NPP_DR'
2011-01-19 09:17:38.007 62692 kcrr.c
PING[ARC0]: Heartbeat failed to connect to standby 'NPP_DR'. Error is 12154.
2011-01-19 09:17:38.007 60970 kcrr.c
kcrrfail: dest:2 err:12154 force:0 blast:1
2011-01-19 09:22:38.863
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
alert log file on Primary*
Error 12154 received logging on to the standby
Wed Jan 19 09:02:35 2011
Error 12154 received logging on to the standby
Wed Jan 19 09:07:36 2011
Error 12154 received logging on to the standby
Wed Jan 19 09:12:37 2011
Error 12154 received logging on to the standby
Wed Jan 19 09:13:10 2011
Incremental checkpoint up to RBA [0x2cc.2fe0.0], current log tail at RBA [0x2cc.2fe9.0]
Wed Jan 19 09:17:38 2011
Error 12154 received logging on to the standby
Wed Jan 19 09:22:38 2011
Error 12154 received logging on to the standby
Wed Jan 19 09:27:39 2011
Error 12154 received logging on to the standby
However, we are able to tnsping from primary to DR
Tnsping Results
From Primary:
juemdbp1:oranpp 19> tnsping NPP_DR
TNS Ping Utility for HPUX: Version 10.2.0.4.0 - Production on 19-JAN-2011 09:32:50
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
/oracle/NPP/102_64/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = 10.80.51.101) (PORT = 49160))) (CONNECT_DATA = (SID = NPP) (SERVER = DEDICATED)))
OK (60 msec)
Tnsnames.ora in Primary:
Filename......: tnsnames.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $
NPP.WORLD=
(DESCRIPTION =
    (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = nppjorp)
          (PORT = 49160)
    (CONNECT_DATA =
       (SID = NPP)
       (GLOBAL_NAME = NPP.WORLD)
NPP_HQ.WORLD=
(DESCRIPTION =
   (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = nppjorp)
          (PORT = 49160)
   (CONNECT_DATA =
        (SID = NPP)
        (SERVER = DEDICATED)
NPP_DR.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
   (ADDRESS =
        (COMMUNITY = SAP.WORLD)
        (PROTOCOL = TCP)
        (HOST = 10.80.51.101)
        (PORT = 49160)
(CONNECT_DATA =
        (SID = NPP)
        (SERVER = DEDICATED)
NPPLISTENER.WORLD=
        (DESCRIPTION =
          (ADDRESS =
                (PROTOCOL = TCP)
                (HOST = nppjorp)
                (PORT = 49160)
Listener.ora in Primary
Filename......: listener.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $
ADMIN_RESTRICTIONS_LISTENER = on
LISTENER =
(ADDRESS_LIST =
        (ADDRESS =
          (PROTOCOL = IPC)
          (KEY = NPP.WORLD)
        (ADDRESS=
          (PROTOCOL = IPC)
          (KEY = NPP)
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = nppjorp)
          (PORT = 49160)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = NPP)
      (ORACLE_HOME = /oracle/NPP/102_64)
Thank You,
Salman Qayyum
Edited by: Salman M.A. Qayyum on Jan 19, 2011 8:12 AM

Hi,
Please find the remaining post ...
Tnsnames.ora in DR:
Filename......: tnsnames.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $
NPP.WORLD=
(DESCRIPTION =
    (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = nppjor)
          (PORT = 49160)
    (CONNECT_DATA =
       (SID = NPP)
       (GLOBAL_NAME = NPP.WORLD)
NPP_HQ.WORLD=
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS =
        (COMMUNITY = SAP.WORLD)
        (PROTOCOL = TCP)
        (HOST = hq_nppjor)
        (PORT = 49160)
    (CONNECT_DATA =
        (SID = NPP)
        (SERVER = DEDICATED)
NPP_DR.WORLD=
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS =
        (COMMUNITY = SAP.WORLD)
        (PROTOCOL = TCP)
        (HOST = nppjor)
        (PORT = 49160)
    (CONNECT_DATA =
        (SID = NPP)
        (SERVER = DEDICATED)
        (SERVICE_NAME = NPP_DR)
NPPLISTENER.WORLD=
        (DESCRIPTION =
          (ADDRESS =
                (PROTOCOL = TCP)
                (HOST = nppjor)
                (PORT = 49160)
Listener.ora in DR
Filename......: listener.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $
ADMIN_RESTRICTIONS_LISTENER = on
LISTENER =
(ADDRESS_LIST =
        (ADDRESS =
          (PROTOCOL = IPC)
          (KEY = NPP.WORLD)
        (ADDRESS=
          (PROTOCOL = IPC)
          (KEY = NPP)
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = nppjor)
          (PORT = 49160)
       (ADDRESS =
         (COMMUNITY = SAP.WORLD)
         (PROTOCOL = TCP)
         (HOST = 10.80.50.101)
         (PORT = 49160)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = NPP)
      (ORACLE_HOME = /oracle/NPP/102_64)
/etc/hosts settings in Primary
host:oranpp 25> grep nppjor /etc/hosts
10.32.243.54    nppjor.sabic.com        nppjor
10.32.50.115    nppjorp.sabic.com        nppjorp
/etc/hosts settings in DR
host:oranpp 11> grep nppjor /etc/hosts
10.32.243.54    hq_nppjor.sabic.com     hq_nppjor
10.80.243.54    nppjor.sabic.com        nppjor
10.80.50.115    nppjorp.sabic.com        nppjorp
Thank You,
Salman Qayyum

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

It is possible to apply redo while the standby is open in read only mode ?

Hi,
I am using Oracle 11g R2 (11.2.0.1.0)
Step 1: Two node RAC is Configured.
Step 2: One node Data Guard RAC is configured.( i,e Standby is one node RAC).
Primary:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ WRITE PRIMARY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
Standby:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
Question:
I have not purchased active dataguard license.
In my case In Data Guard RAC it is possible to apply redo while the database is open in read only mode?
Thanks
Solaiman

876149 wrote:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
"READ ONLY WITH APPLY" in V$DATABASE.OPEN_MODE means Active Data Guard is enabled.
Oracle code cannot check if you have the right license: it is up to you to know which license you have for your database environments.

Where RFS exactly write redo data ? ( archived redo log or standby redo log ) ?

Good Morning to all ;
I am getting bit confused from oracle official link . REF_LINK : Log Apply Services
Redo data transmitted from the primary database is received by the RFS on the standby system ,
where the RFS process writes the redo data to either archived redo log files or standby redo log files.
In standby site , does rfs write redo data in any one file or both ?
Thanks in advance ..

Hi GTS,
GTS (DBA) wrote:
Primary & standby log file size should be same - this is okay.
1) what are trying to disclose about largest & smallest here ? - You are confusing.
Read: http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_transport.htm#SBYDB4752
"Each standby redo log file must be at least as large as the largest redo log file in the redo log of the redo source database. For administrative ease, Oracle recommends that all redo log files in the redo log at the redo source database and the standby redo log at a redo transport destination be of the same size."
GTS (DBA) wrote:
2) what abt group members ? should be same as primary or need to add some members additionally. ?
Data Guard best practice for performance, is to create one member per each group in standby DB. on standby DB, one member per group is reasonable enough. why? to avoid write penalty; writing to more than one log files at the standby DB.
SCENARIO 1: if in your source primary DB you have 2 log member per group, in standby DB you can have 1 member per group, additionally create an extra group.
primary
standby
Member per group
2
1
Number of log group
4
5
SCENARIO 2: you can also have this scenario 2 but i will not encourage it
primary
standby
Member per group
2
2
Number of log group
4
5
GTS (DBA) wrote:
All standby redo logs of the correct size have not yet been archived.
- at this situation , can we force on standby site ? any possibilities ?
you can not force it , just size your standby redo files correctly and make sure you don not have network failure that will cause redo gap.
hope there is clarity now
Tobi

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.

Adding online redo logs with standby database in place

Hi group,
I have decided to add one new member to my existing redo log groups and an additional redo log group to my primary database.
That change went ok without problems. I assumed that with standby_file_management=auto the equivalent online redo logs are created on the standby database. But this is not the case.
The documentation is unclear about this point and I did not find anything suitable on metalink. The docs suggest to cancel managed recovery on the standy, setting standby_file_management to MANUAL and then adding online logs, quote:
"To add an online redo log, use a SQL statement such as this:
SQL> ALTER DATABASE ADD STANDBY LOGFILE 'prmy3.log' SIZE 100K;"
This however - IMO - adds a new STANDBY redo log to the standby database, what I need is an ONLINE redo log.
Does anybody have some experience to share here?
Facts:
Solaris 8
Oracle 9.2.0.6
Thanks!
Martin

OK, for those who come across the same problem.
You need to create a new standby controlfile, copy it as well as any new online redo log from production to the standby environment.
Once the files are in place, start the standby as normal and open it read only to see if everything is ok:
startup nomount
alter database mount standby database;
alter database open read only
Only when there are no errors in your alert.log you are safe.
Martin

Current redo at the standby server

Hi,
Oracle 10.2.0/Windows 2003 Server
At my standby system in v$managed_standby view Process MRP0 is showing WAIT_FOR_LOG instead APPLYING_LOG. I have given statement:
Alter database recover managed standby database using current logfile disconnect from session
All the archive logs are being shipped, but I am worried of current redo?
what should I do to solve this problem.
SQL> select process,status,sequence#,block#,blocks from v$managed_standby;
PROCESS STATUS SEQUENCE# BLOCK# BLOCKS
ARCH CLOSING 1917 4097 168
ARCH CONNECTED 0 0 0
MRP0 WAIT_FOR_LOG 1918 0 0
RFS IDLE 0 0 0
thanks
satyanag

Hi Satyanag,
It isn't necessarily a problem...
The status of waiting is normal if the database has applied the latest log. It just means that it is waiting for the next log.
The only thing you need to watch out for is that the standby hasn't fallen behind for some reason (network outage for example). To check, run the following queries:
On the primary:
set numwidth 15
select     max(sequence#) current_seq
from     v$log
On the standby:
set numwidth 15
select     max(applied_seq#) last_seq
from     v$archive_dest_status
Make sure that the numbers are roughly the same. It's also worth checking the alert log of the standby for errors.
Cheers,
Andy Barry
http://www.shutdownabort.com

11g dataguard, v$ view to monitor rate of redo transfer to standby?

Hello,
Which v$ views can I query to monitor the speed/rate of archivelogs transfer from primary to standby? Thank you in advance.

V$standby_apply_snapshot - redo apply rate in KB/second
v$dataguard_stats - info about standby background process
v$recovery_progress - information about the redo.
Hopes this helps!
Thanks

Standby redo log status

Can anyone explain what the status of clearing means when viewing standby redo log status?
SQL> select status from v$log;
STATUS
CLEARING
CLEARING
CURRENT
This is a bit different to what we'd see on an open database.

Hello;
Log is being re-created as an empty log.
In a Standby database the regular redo are not used ( when not in PRIMARY MODE) only the standby redo logs are used. Sometimes as buffers for the redo coming from the primary.
You should be able to change the status by doing a ALTER SYSTEM SWITCH LOGFILE on your primary.
This note may help:
Online Redo Logs on Physical Standby [ID 740675.1]
Also
Take a look at v$standby_log too.
http://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3068.htm
Best Regards
mseberg

Resizing redo log files on a 3 node RAC with single node standby database

Hi
On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
SQL> select group#,thread#,members,status from v$log;
GROUP# THREAD# MEMBERS STATUS
1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
2 1 3 CURRENT & resized, switch logfile can change logfile group
3 1 3 INACTIVE
4 2 3 INACTIVE
5 2 3 INACTIVE
6 2 3 CURRENT
7 3 3 INACTIVE
8 3 3 INACTIVE
9 3 3 CURRENT
9 rows selected.
SQL> alter database drop logfile group 1;
Database altered.
SQL> ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (
'/PROD/redo1/redo01a.log',
'/PROD/redo2/redo01b.log',
'/PROD/redo3/redo01c.log'
) SIZE 100M reuse; 2 3 4 5 6
Database altered.
However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
SQL> select group#,member from v$logfile where type='STANDBY';
GROUP#
MEMBER
10
/PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
11
/PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
12
/PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
Please let me know.
Thanks
Sumathy

Hello;
For Redo and Standby redo this won't help :
standby_file_management is set to auto
On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
Then start recovery again.
Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
alter database add standby logfile group 4
('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
Notes worth reviewing :
Online Redo Logs on Physical Standby [ID 740675.1]
Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
Best Regards
mseberg

Clearing redo in phyical standby

Similar Messages

Maybe you are looking for