When changing redo-logs on Primary, do I need to change my standby also?

Hi, I need to resize my redo logs on a primary db which has a physical standby attached. Do I need to modify this standby or will the change propagate. It seems unlikely to me.
thanx

Only clue that I have found is at
http://download-east.oracle.com/docs/cd/B12037_01/server.101/b10726/configbp.htm
Section "Use Multiplexed Standby Redo Logs and Configure Size Appropriately"
>>
The remote file server (RFS) process for the standby database writes only to an SRL whose size is identical to the size of an online redo log for the production database. If it cannot find an appropriately sized SRL, then RFS creates an archived redo log file directly instead and logs the following message in the alert log:
No standby redo log files of size <#> blocks available.
>>

Similar Messages

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

Delete standby redo log from primary database

Hi all,
I'm trying to drop standby logfiles on primary database (other database that I'm configuring the DG).
The members of the standby log groups don't exists on file system.
Somebody have deleted these files. Its old configuration where the files were in file system. Now they are in ASM.
When I try to drop the standby logfiles I got the following error:
SQL> alter database clear logfile group 7;
alter database clear logfile group 7
ERROR at line 1:
ORA-19528: redo logs being cleared may need access to files
SQL> select * from v$logfile order by 1;
    GROUP# STATUS TYPE    MEMBER                                                                           IS_
         1         ONLINE +REDO1/proj/onlinelog/group_1.256.340558657                                     NO
         1         ONLINE +REDO2/proj/onlinelog/group_1.256.340558659                                     NO
         2         ONLINE +REDO1/proj/onlinelog/group_2.257.340558879                                     NO
         2         ONLINE +REDO2/proj/onlinelog/group_2.259.340558879                                     NO
         3         ONLINE +REDO1/proj/onlinelog/group_3.258.340558707                                     NO
         3         ONLINE +REDO2/proj/onlinelog/group_3.257.340558709                                     NO
         4         ONLINE +REDO2/proj/onlinelog/group_4.258.340558713                                     NO
         4         ONLINE +REDO1/proj/onlinelog/group_4.259.340558711                                     NO
         5         ONLINE +REDO2/proj/onlinelog/group_5.260.340558965                                     NO
         5         ONLINE +REDO1/proj/onlinelog/group_5.260.340558963                                     NO
         6         ONLINE +REDO1/proj/onlinelog/group_6.261.340558967                                     NO
         6         ONLINE +REDO2/proj/onlinelog/group_6.261.340558967                                     NO
         7         STANDBY /oracle/proj/onlinelog2/redo_702.log                                            NO
         7         STANDBY /oracle/proj/onlinelog1/redo_701.log                                            NO
         8         STANDBY /oracle/proj/onlinelog2/redo_802.log                                            NO
         8         STANDBY /oracle/proj/onlinelog1/redo_801.log                                            NO
         9         STANDBY /oracle/proj/onlinelog2/redo_902.log                                            NO
         9         STANDBY /oracle/proj/onlinelog1/redo_901.log                                            NO
        10         STANDBY /oracle/proj/onlinelog1/redo_1001.log                                           NO
        10         STANDBY /oracle/proj/onlinelog2/redo_1002.log                                           NO
20 rows selected.
SQL> select * from v$standby_log order by 1;
    GROUP# DBID            THREAD# SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
         7 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         8 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         9 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
        10 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0What can I do to drop these reference?
Any other solution instead of edit the controlfile and stop/start tghe database?
thank you!!!!

Hello;
Well Oracle thinks the files are there, but I remember a bug on metalink where the controlfile still had them, but they were not on the file system. Can you confirm they exist?
Meanwhile I check my notes for the Oracle doc nunber.
Bug 6128242: TRYING TO DROP STANDBY LOG FAILS WITH ORA-19528
So if you are Oracle 10 this might be the issue.
workaround is to re-create the controlfile without the incorrect logfile. ( Yuk!! )
ORA-01156 When Adding Or Dropping Redo Logs [ID 452152.1]
Best Regards
mseberg
Edited by: mseberg on Oct 31, 2011 5:09 PM

Recover when Online Redo Log lost.

Hi,all.
How do I recover the db while all the online redo log files were lost.
The database is running in archive mode and all the archived redo log files were saved well.
But since last hot backup,I have done some table inserting with nologging.
Now the database can not be opened.
Who can tell me how to recover the db to the recent state.
I remember the db was shutdown immediate.
(Do it make any difference to online redo log file between shutdown immediate and abort?)
Thanks.
wy.

I find out if I shutdown immediate and remove all the redo log files,I can recover the database as below:
SQL> startup
ORACLE instance started.
Total System Global Area 109164572 bytes
Fixed Size 75804 bytes
Variable Size 59498496 bytes
Database Buffers 49512448 bytes
Redo Buffers 77824 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\ORCL\REDO03.LOG'
SQL> recover database until cancel
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
but if I shutdown abort,I can not recover the database.
SQL> startup
ORACLE instance started.
Total System Global Area 109164572 bytes
Fixed Size 75804 bytes
Variable Size 59498496 bytes
Database Buffers 49512448 bytes
Redo Buffers 77824 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\ORCL\REDO03.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) O5M3UR2;5=V86(5DND<~!#
SQL> recover database until cancel
ORA-00279: change 690879 generated at 08/09/2004 16:34:04 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\ORCL\ARCHIVE\ORCLT001S00002.ARC
ORA-00280: change 690879 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 690963 generated at 08/09/2004 16:34:08 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\ORCL\ARCHIVE\ORCLT001S00003.ARC
ORA-00280: change 690963 for thread 1 is in sequence #3
ORA-00278: log file 'D:\ORACLE\ORADATA\ORCL\ARCHIVE\ORCLT001S00002.ARC' no
longer needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\ORADATA\ORCL\ARCHIVE\ORCLT001S00003.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) O5M3UR2;5=V86(5DND<~!#
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF'
SQL> recover database until cancel
ORA-00279: change 690963 generated at 08/09/2004 16:34:08 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\ORCL\ARCHIVE\ORCLT001S00003.ARC
ORA-00280: change 690963 for thread 1 is in sequence #3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF'
ORA-01112: media recovery not started
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF'
So How to recover the database when the db shutdown abort and all the online redo log were lost?

Where are BLOB Files stored when using redo log files.

I am using Archive Log Mode for my backups. I was wondering if Blob files get stored in the redo log files or if they are archived somewhere else?
Rob.

BLOB are just columns of some tables and are stored in related tablespace table by default in their own segments. Changes to BLOB columns are also stored in redo log more or less like any other column.
See an short example for default LOB storage in Re: CLOB Datatype [About Space allocation]
Edited by: P. Forstmann on 27 avr. 2011 07:20

How to recover database when all redo logs are losted

pls help me in recovering the database when all the redo logs are losted

In both cases he has to open the database in RESETLOGS option. So try:
recover database until cancel;
Then cancel the recovery, and
alter database open resetlogs;
If you want to check where your database is at then mount your database and issue:
select group#, sequence#,first_change# from v$log;
This will tell you the sequence and SCN of all the online log files then compare it with what it prompted when you issued recovery command.
Daljit Singh

Redo log on disk - do I need to multiplex them?

Hello,
I'm running my 10gR2 EE DB on SPARC server.
Currently we are running whole DB on FC LUN mounted as /u01
My folder structure is (for example):
/u01/oracle (binaries)
/u01/oradata
/u01/oraindex
/u01/oraredo1
/u02/oraredo2
/u03/oreredo3
Well, the problem is (or there is no problem :), do I really need to multiply my redo groups on 3 locations, while all of those locations are from the same FC disk array (with RAID of example)?
I have 5 groups with 3 members.
In addition: sometimes I get log_file_sync wait event.
Regards
Edited by: zawierta on 2011-02-14 01:07

Well, Oracle recommends (minimum) 2 members per group, and to use 2 separate storage. So, one location on your shared storage, and the other on your local disks is already better than both on same location.
Concerning log file sync wait event , i have found the following :
High log file sync wait event
http://www.dba-oracle.com/t_log_file_sync_waits.htm
http://christianbilien.wordpress.com/2008/02/12/the-%E2%80%9Clog-file-sync%E2%80%9D-wait-event-is-not-always-spent-waiting-for-an-io/
HTH,
Thierry

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

Increase current redo log size in standby database in mount stage

We have oracle 10g standby database. The standby database is always running in mount stage while apply logs manually not data guard is used.
We have increase size or online redo log in primary . Now want to inrease in standby database also.
how to increase the size of current online redo log in standby database while it in mount stage .
in mount stage we cant run alter system switch logfile

user11965804 wrote:
We have oracle 10g standby database. The standby database is always running in mount stage while apply logs manually not data guard is used.
We have increase size or online redo log in primary . Now want to inrease in standby database also.
how to increase the size of current online redo log in standby database while it in mount stage .
in mount stage we cant run alter system switch logfilein 10g Standby will be always in Mount status when MRP is running.
When you increase size of online redo log files in primary, You should increase in standby also..
Standby redo log file size should be equal or higher than primary. You no need to switch log files on Standby.
You will have only standby redo log files in standby not ORL(online redo log files)
You can use this below script to add standby redo log files.
http://www.pythian.com/news/581/oracle-standby-redo-logs/

When occurs crash recovery,why use active online redo log not archived log?

If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

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

Standby redo log

In what situation, standby redo logs are mandatory.
I have the below settings and my DATA GAURD setup (10.2.0.3) is working fine without Stdby redo logs.
Just wondering when do i need standby redo logs.
SQL> show parameter log_Archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=TO_STANDBY LGWR ASYNC
AFFIRM DB_UNIQUE_NAME=stand
SQL> select protection_mode from v$database;
PROTECTION_MODE
MAXIMUM PERFORMANCE

888442 wrote:
In what situation, standby redo logs are mandatory.
I have the below settings and my DATA GAURD setup (10.2.0.3) is working fine without Stdby redo logs.
Just wondering when do i need standby redo logs.
SQL> show parameter log_Archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=TO_STANDBY LGWR ASYNC AFFIRM DB_UNIQUE_NAME=stand
SQL> select protection_mode from v$database;
PROTECTION_MODE
MAXIMUM PERFORMANCEHi,
Standby Redo Logs (SRL) require when you are using MAX AVAILABILITY and MAX PROTECTIN protection modes. So SRL using for Real Time Apply.
In your case (Max Performance) if you want real time apply on standby you must add SRLs to standby database.
Best practice we adding standby redo logs to primary and standby database same time, but when database role is standby then using SRLs.
You can ask, why also to primary? Because we can switchover to standby, then priamry role will change to standby, then will use SRLs.
Regards
Mahir M. Quluzade

Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

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

When changing redo-logs on Primary, do I need to change my standby also?

Similar Messages

Maybe you are looking for