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

Similar Messages

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

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.

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

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 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.......

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

Question on redo log files at the standby

Oracle version: 10.2.0.5
Platform : AIX
We have 2 node RAC primary with 2 node RAC standby
Primary Instance1 named as cmapcp1
Primary Instance2 named as cmapcp2
Standby Instance1 named as cmapcp3
Standby Instance2 named as cmapcp4At standby side
SQL> show parameter log_file_name_convert
NAME                 TYPE                 VALUE
log_file_name_conver string               cmapcp1, cmapcp3, cmapcp2, cmapcp4
Despite the value set for log_file_name_convert, I don't see any change in names of Online and Standby redo logs at the Standby site.
-- From primary
SQL> select member,type from v$logfile;
MEMBER                                             TYPE
+CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log11.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log12.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log13.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log14.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log15.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log16.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log17.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log18.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log19.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log20.dbf             STANDBY
16 rows selected.-- From standby
SQL> select member,type from v$logfile;
MEMBER                                             TYPE
+CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log11.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log12.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log13.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log14.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log15.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log16.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log17.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log18.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log19.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log20.dbf             STANDBY
16 rows selected.--- Another thing I noticed, v$log doesn't list Standby Redo Logs. This is expected behaviour , I guess
Below is the output from Primary and Standby (it is the same)
set linesize 200
set pagesize 50
col member for a50
break on INST SKIP PAGE on GROUP# SKIP 1
select l.thread# inst, l.group#,lf.member, lf.type
    from v$log l , v$logfile lf
    where l.group# = lf.group#
    order by 1,2 ;
      INST     GROUP# MEMBER                                             TYPE
         1          1 +CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
                    2 +CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
                    3 +CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
      INST     GROUP# MEMBER                                             TYPE
         2          4 +CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
                    5 +CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
                    6 +CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE

John_75 wrote:
Thank you ckpt, mseberg.
I think log_file_name_convert is set wrongly as you've mentioned. But If I don't want to any change to name of Online or standby redo log files in standby, I don't have to set log_file_name_convert at all. Right ?From Same link
If you specify an odd number of strings (the last string has no corresponding replacement string), an error is signalled during startup. If the filename being converted matches more than one pattern in the pattern/replace string list, the first matched pattern takes effect. There is no limit on the number of pairs that you can specify in this parameter (other than the hard limit of the maximum length of multivalue parameters).

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

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

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

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

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.

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

Redo Log Apply after Standby Restarts

hi all,
To start my learning on Data Guard, I've successfully followed the manual steps to create a physical standby database. What I noticed is when I restart the standby database, the received redo log aren't automatically applied until I issued the following command:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;Is that normal? If yes, is there a way to make redo application remains automatic after standby database restarts?
Thanks in advance.

When you configure the DataGuard in an SQL environment you need to manually start the redo apply process after the Standby Database is mounted. You can script the database startup and include that when "select database_role from v$database" is Physical Standby then "ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;"
OR
Yo can configure the DataGuard under the broker control which will start the redo apply process automatically when the Standby Server starts.
Sudhir.

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

Similar Messages

Maybe you are looking for