Redolog in standby

Hi Chaps
I know that the 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.
Does that mean that they are used?

Setting the 'CLEARING' status is done for performance reasons (through commands like RMAN DUPLICATE ... FOR STANDBY) , the online are prepared for a faster switchover/failover. But there are not used until such a switch happens,from documentation:
Clearing Online Redo Logs
After creating the standby database, you can clear online redo logs on the standby site to optimize performance by issuing the following statement, where 2 is the number of the log group:
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
This statement optimizes failover to the standby database because it is no longer necessary for the Oracle database server to clear the logs before failover. Clearing involves writing zeros to the entire contents of the redo log and then setting a new header to make the redo log look like it was when it was created.
If you clear the logs manually, the Oracle database server realizes at activation that the logs already have zeros and skips the clearing step. This optimization is important because it can take a long time to write zeros into all of the online logs. If you prefer not to perform this operation during maintenance, the Oracle database server clears the online logs automatically during failover.
Werner

Similar Messages

At the time of copying online redologs to STANDBY site.....

hai..
At the time of configureing dataguard manually(without rman) do i need to copy the online redologs to standby site along with *.dbf files and standby controlfile after clena shutdown? bcaz some procdeures guide me to copy all files with online redolog files to the stanndby environment.but some procedures guide me to only copy the *.dbf files to the standby environment along with init.ora,standby controlfile from the primary site.whcih one is correct? and which one is better?
please guide me.

What is better is to use RMAN.
Why violate "best practice" guidelines.
RMAN knows what to copy and does it correctly.
Hint: If you don't copy the online redologs ... how will they be created? Magic rarely works.

Online redolog on standby

Hello
I know that standby redologs are used in standby database, Does oracle also uses online redologs in standby database? I notice that the status of online redologs changed in standby database
select group#, bytes, status from v$log;
1 10485760 UNUSED
3 10485760 CLEARING_CURRENT
2 10485760 UNUSED

hi..
me too just noticed this...
from my standby
SQL> /
    GROUP#      BYTES STATUS
         3 314572800 CLEARING_CURRENT
         4 314572800 CLEARING
         5 314572800 CLEARING
         6 314572800 CLEARING
         7 314572800 CLEARING
         8 314572800 CLEARING
         9 314572800 CLEARING_CURRENT
        10 314572800 CLEARING
        11 314572800 CLEARING
        12 314572800 CLEARING
10 rows selected.
from my primary
SQL> /
    GROUP#            BYTES STATUS
         3      314,572,800 CURRENT
         4      314,572,800 INACTIVE
         5      314,572,800 INACTIVE
         6      314,572,800 INACTIVE
         7      314,572,800 INACTIVE
         8      314,572,800 ACTIVE
         9      314,572,800 CURRENT
        10      314,572,800 INACTIVE
        11      314,572,800 INACTIVE
        12      314,572,800 INACTIVEGuess in standby, it uses the primary redo logs too and clears it..
thanks,
baskar.l

Standby database online redologs

1-)
I know that online redologs are not being used in physical standby database.
Suppose I created a physical standby database with standby redologs.
As far as I know online redologs are not used in standby database,(standby redologs are used)
However, when I check the status of the online redologs in standby database I see that:
"CLEARING_CURRENT" or "CLEARING".
Their status is also changing once log switch occurs in production.
Whats the reason for this and why does this status always change, if standby online redologs are not used, their status
should not change.
2-)
What would happen if I delete the online redolog of the standby database from the operating system?
Does the status again show: clearing,clearing current?

Standby online logs are not used, but they have status CLEARING in preparation for a possible switchover/failover. So they are ready to become very fast active online logs.
I would never delete any database files on OS level, although the standby online logs are not needed when the database runs in standby role, Oracle will complain about their missing. At least when you restart the standby.
Werner

Error in starting MRP process in Standby database.

Hi All,
OS:Windows server 03
DB:11g
I am creating a Standby database, everything is fine until i fire the below command to start the MRP process to start the recovery of the database.
alter database recover managed standby database disconnect from session;MRP0 started with pid=27, OS id=6640
2013-02-07 17:59:48.515000 +05:30
started logmerger process
Managed Standby Recovery not using Real Time Apply
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSAUX01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\APP\ORACLE\ORADATA\TEST\TEST\UNDOTBS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\APP\ORACLE\ORADATA\TEST\TEST\USERS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
MRP0: Background Media Recovery terminated with error 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_pr00_7984.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Recovery Slave PR00 previously exited with exception 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_mrp0_6640.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Completed: alter database recover managed standby database disconnect from session
Can anyone tell me why is this comming?
Regards,
Sphinx

Hi ,
Yes, it is on the same server.
I have used the below mentioned parameters to rename the files
At Primary Pfile:
*.db_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\datafiles\')
*.log_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\redologs\')
At Standby:
*.db_file_name_convert=('D:\app\oracle\testdr\oradata\datafiles\','D:\app\oracle\oradata\test\test\')
*.log_file_name_convert=('D:\app\oracle\testdr\oradata\redologs\','D:\app\oracle\oradata\test\test\')
But the output of v$datafile at standby is showing the path of Primary datafiles
I manually tried recovering them but it is prompting me the same error.
Regards
Edited by: $phinx19 on Feb 7, 2013 6:23 AM

Real time apply dataguard

Hello
I have some doubts about real time apply.
If a transaction occurs in production, lgwr will automatically write this transaction to standby redologs in standby database.
Is this transaction applied to standby database immediately or wait for standby redolog switch and applied as soon as standby log is archived ?

Thanks Uwe.
Eventhough you mentioned this before, I just want to ask last time to confirm:
Regarding real time apply;
When a transaction occurs in production, this transaction is not applied directly to standby database.
It is first transferred to standby redolog( by the log writer of primary) and from there to standby database immediately. (I dont know which background proces is responsible for this)
Is this right?By default, the archives are transferred(on completion) to standby database server using ARCH process and received by Remote File Server process (RFS) on standby database server. Optionally, you may choose to do the same using standby redo logs instead of archive log files (LGWR and LNS processes comes into picture). The standby redo logs are compulsory for real time apply regardless of protection mode.
If you're using SRL, then redo data is transferred to SRL and once the SRL is archived the changes are written to the database using Managed Recovery Process (MRP) and hence minimizes the data loss in case of failover and minimizes the time in case of switchover and failover.
If you're using Real Time Apply, then the standby redo log data is directly written to the database using LSP or MRP without waiting for SRL to be archived.
Regards,
S.K.
Edited by: Santosh Kumar on Sep 22, 2009 3:53 PM

Problem with activating DR server.

Hello experts,
We are having a standby database which is a replica of our production
system and we are applying redologs (recover standby database) to keep
it in sync with production. Now we are not able to activate the standby
database. We have followed the below steps.
SQL> alter database activate standby database;
SQL> shutdown immediate
SQL> startup
ORACLE instance started.
Total System Global Area 1191182336 bytes
Fixed Size                  2020424 bytes
Variable Size             603982776 bytes
Database Buffers          570425344 bytes
Redo Buffers               14753792 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
The database is getting mounted but not opening. I am attaching the
last 200 lines of the alert_BPS.log file. Kindly suggest.
Successful mount of redo thread 1, with mount id 3298849371
Wed May 21 12:52:48 2008
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Wed May 21 12:52:48 2008
ALTER DATABASE OPEN
Wed May 21 12:52:48 2008
Assigning activation ID 3298849371 (0xc4a0725b)
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=721072
Wed May 21 12:52:48 2008
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=15, OS id=536658
Wed May 21 12:52:48 2008
Thread 1 opened at log sequence 1
Current log# 2 seq# 1 mem# 0: /oracle/BPS/origlogB/log_g12m1.dbf
Current log# 2 seq# 1 mem# 1: /oracle/BPS/mirrlogB/log_g12m2.dbf
Successful open of redo thread 1
Wed May 21 12:52:48 2008
ARC0: STARTING ARCH PROCESSES
Wed May 21 12:52:48 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Wed May 21 12:52:48 2008
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed May 21 12:52:48 2008
SMON: enabling cache recovery
Wed May 21 12:52:48 2008
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=16, OS id=647326
Wed May 21 12:52:48 2008
Incremental checkpoint up to RBA [0x1.3.0], current log tail at RBA [0x1.3.0]
Wed May 21 12:52:50 2008
Errors in file /oracle/BPS/saptrace/usertrace/bps_ora_1843232.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Wed May 21 12:52:50 2008
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 1843232
ORA-1092 signalled during: ALTER DATABASE OPEN...
Wed May 21 12:53:25 2008
Starting ORACLE instance (normal)
Wed May 21 12:53:25 2008
Specified value of sga_max_size is too small, bumping to 1191182336
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
event                    = 10191 trace name context forever, level 1
sga_max_size             = 1191182336
shared_pool_size         = 570425344
shared_pool_reserved_size= 55490641
filesystemio_options     = setall
control_files            = /oracle/BPS/origlogA/cntrl/cntrlBPS.dbf, /oracle/B
S/origlogB/cntrl/cntrlBPS.dbf, /oracle/BPS/sapdata1/cntrl/cntrlBPS.dbf
control_file_record_keep_time= 30
db_block_size            = 8192
db_cache_size            = 570425344
compatible               = 10.2.0
log_archive_dest         = /oracle/BPS/oraarch/BPSarch
log_buffer               = 14306304
log_checkpoint_interval = 0
db_files                 = 254
standby_file_management = AUTO
log_checkpoints_to_alert = TRUE
dml_locks                = 4000
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
recyclebin               = off
remote_os_authent        = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes      = 1
background_dump_dest     = /oracle/BPS/saptrace/background
user_dump_dest           = /oracle/BPS/saptrace/usertrace
core_dump_dest           = /oracle/BPS/saptrace/background
optimizer_features_enable= 10.2.0.1
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = BPS
open_cursors             = 800
optimpeek_user_binds   = FALSE
pga_aggregate_target     = 739875225
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2, OS id=1777774
PSP0 started with pid=3, OS id=1745118
MMAN started with pid=4, OS id=1867912
DBW0 started with pid=5, OS id=1523752
LGWR started with pid=6, OS id=1470538
CKPT started with pid=7, OS id=1466614
SMON started with pid=8, OS id=1659030
RECO started with pid=9, OS id=721074
CJQ0 started with pid=10, OS id=684214
MMON started with pid=11, OS id=675992
MMNL started with pid=12, OS id=659512
Wed May 21 12:53:40 2008
alter database open read only
Wed May 21 12:53:40 2008
ORA-1507 signalled during: alter database open read only...
Wed May 21 12:53:53 2008
alter database mount
Wed May 21 12:53:58 2008
Setting recovery target incarnation to 3
Wed May 21 12:53:58 2008
Successful mount of redo thread 1, with mount id 3298876065
Wed May 21 12:53:58 2008
Database mounted in Exclusive Mode
Completed: alter database mount
Wed May 21 12:54:03 2008
alter database open read only
ORA-16005 signalled during: alter database open read only...
Wed May 21 12:55:06 2008
ALTER DATABASE RECOVER database
Wed May 21 12:55:06 2008
Media Recovery Start
parallel recovery started with 3 processes
Wed May 21 12:55:07 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 1 Reading mem 0
Mem# 0 errs 0: /oracle/BPS/origlogB/log_g12m1.dbf
Mem# 1 errs 0: /oracle/BPS/mirrlogB/log_g12m2.dbf
Wed May 21 12:55:07 2008
Media Recovery Complete (BPS)
Completed: ALTER DATABASE RECOVER database
Wed May 21 12:55:13 2008
alter database open read only
ORA-16005 signalled during: alter database open read only...
Wed May 21 12:55:28 2008
alter database open
Wed May 21 12:55:28 2008
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Wed May 21 12:55:28 2008
Started redo scan
Wed May 21 12:55:28 2008
Completed redo scan
0 redo blocks read, 0 data blocks need recovery
Wed May 21 12:55:28 2008
Started redo application at
Thread 1: logseq 1, block 3, scn 652226614
Wed May 21 12:55:28 2008
Recovery of Online Redo Log: Thread 1 Group 2 Seq 1 Reading mem 0
Mem# 0 errs 0: /oracle/BPS/origlogB/log_g12m1.dbf
Mem# 1 errs 0: /oracle/BPS/mirrlogB/log_g12m2.dbf
Wed May 21 12:55:28 2008
Completed redo application
Wed May 21 12:55:28 2008
Completed crash recovery at
Thread 1: logseq 1, block 3, scn 652246615
0 data blocks read, 0 data blocks written, 0 redo blocks read
Wed May 21 12:55:28 2008
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=17, OS id=1827040
Wed May 21 12:55:28 2008
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=18, OS id=1830936
Wed May 21 12:55:28 2008
Thread 1 advanced to log sequence 2
Thread 1 opened at log sequence 2
Current log# 1 seq# 2 mem# 0: /oracle/BPS/origlogA/log_g11m1.dbf
Current log# 1 seq# 2 mem# 1: /oracle/BPS/mirrlogA/log_g11m2.dbf
Successful open of redo thread 1
Wed May 21 12:55:29 2008
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed May 21 12:55:29 2008
ARC0: STARTING ARCH PROCESSES
Wed May 21 12:55:29 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Wed May 21 12:55:29 2008
SMON: enabling cache recovery
ARC2 started with pid=19, OS id=1871876
Wed May 21 12:55:29 2008
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
Wed May 21 12:55:29 2008
Errors in file /oracle/BPS/saptrace/usertrace/bps_ora_647328.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Wed May 21 12:55:29 2008
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 647328
ORA-1092 signalled during: alter database open...

Hi Amit
Could you please verify the versions on both systems. Try something like this:
SQL> select * from v$version;
The ORA-39700: database must be opened with UPGRADE option might indicate some inconsistency regarding versions. Please also check the file /oracle/BPS/saptrace/usertrace/bps_ora_647328.trc.
Regards, Michael

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

Dataguard archivelog transmission

Hello
When primary redo is generated, it is written to standby redologs on standby server and when the standby redolog is filled, it has been archived hence archivelogs are generated on standby server.
How about in dataguard configurations which there are no standby redologs?
How does the redo transmitted to standby side?
Does oracle transfer archivelog from primary to standby as soon as it is generated ?
or
Does the arc process simultaously generate two archivelogs one in primary, one in standby side ?

A standby redo log is used only when the database is in the standby role to store redo data
received from the primary database.
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
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.
the managed recovery process (MRP) applies the redo from the standby redo log files after the remote file server (RFS) process finishes writing.
refer the below link , you will understand.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#i1033862
Good Luck.

Configuration doubt

Could somebody, please, explain me ?
I know tha when I set up redo shipping, the number of standby redolog (at standby database) must be at less, one more than the number of online redolog present in the source database. That is why when the standby database is a single instance I execute the following, at the standby database, if the number of online redolog in the source is 2:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('+BD2')SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('+BD2') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('+BD2') SIZE 50M;
After, I set the LOG_ARCHIVE_DEST_2 parameter like
alter system set LOG_ARCHIVE_DEST_2='LOCATION=+BD3/ VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)';
BUT when I have a Real Application Clusters with two instances as standby database, I need create the standby redolog in both instances or just in one ? :
INSTANCE1
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('+BD2')SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('+BD2') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('+BD2') SIZE 50M;
INSTANCE2
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('+BD2')SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('+BD2') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('+BD2') SIZE 50M;
Thanks you so much.

Thanks Cow Town but it is not my point. I say when the primary is a single instance and I want to have an standby in a RAC compose of two instance. That is:
source database-: single instances
future standby database: two instances RAC
As said I know that if the future standby database will be a single instance too, I need to create one standby group more than the number of online redolog present in the source DB. But in my situation the standby will be two instances RAC and my question is if I need to create the four groups in each instance or just in one of all.
Please tell me if you understand my question, and again thanks so much.

Standby redologs in the standby database

Hi All,
I am preparing the standby database using RMAN creation steps. I am confusing in one area. I have standby redologs in the Primary server. When we issue the duplicate target database for standby dorecover nofilenamecheck command, is it create the standby redologs in the standby database or not ?
please cofirm
Thanks
Shiju

Hi,
no, you must to create standby redo logs manually.
This script may help you
select 'alter database add standby logfile '''||
regexp_substr(MEMBER,'/.+/')||'stdby_'||
regexp_replace(member,regexp_substr(MEMBER,'/.+/'),'')||
''' size '||bytes||';' "Create Standby redo"
from v$logfile lf , v$log l
where l.group# = lf.group#
union all
select 'alter database add standby logfile '''||
regexp_substr(MEMBER,'/.+/')||'stdby_redo0'||(select max(group#)+1 from v$log)||'.rdo'||
''' size '||bytes||';' "Create Standby redo"
from v$logfile lf , v$log l
where l.group# = lf.group#
and rownum <=2
Create Standby redo
alter database add standby logfile '/oracle/redo/prod1/stdby_redo03a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo03b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo02a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo02b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo01a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo01b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo04.rdo' size 52428800;
more
http://www.pythian.com/news/581/oracle-standby-redo-logs
Regards,
Tom
http://asktom.cz

How to create a standby redolog from rac to non rac ??

Hi,
How to create a standby redolog from rac to non rac DR setup..???
in rac we can create with specifying thread number for each instances..... but this will be replicating to standby ....so how this will act/create on single DR??
pls help

854393 wrote:
Thanks Shivanandha,
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database.In maximum performance mode you can keep same number of redo logs but having one more redo log member for each thread is recommended and mandtory for other protection modes.
How to create a standby redolog from rac to non rac DR setup..???
in rac we can create with specifying thread number for each instances..... but this will be replicating to standby ....so how this will act/create on single DR??pls help
Yes, even your DR is RAC or non-RAC, you must have both threads, because each instance information exist on own thread, So to perform redo transition from both the instances, you must have both standby redo log threads even though if it is non an RAC DR.
Hope This helps.

Standby redologs

Hi
I created standby redologs and change lgwr async mode. (max performance)
How can I know wheter the standby redologs are used or not?
I want to make sure that db is using standby redologs rather than archive transfer..

Hi..
How can I know wheter the standby redologs are used or not?You can verify using the below query on the standby database:-
SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
For V$standby_log refer to [http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/dynviews_2115.htm]
HTH
Anand

Redologs in physical standby database

The MRP process is started and the standby database is physical standby, which is running under managed standby. My Question is as below
1. Under managed recovery mode do we require the redo logs created on the physical standby database.
2. How does oracle keep the database in sync when there are no redo logs are created on the standby database.

The output is as below
SQL> select status, pid, sequence# from v$managed_standby where process like 'MRP%';
STATUS PID SEQUENCE#
WAIT_FOR_GAP 29710 88576
SQL>
The contents of alertlog ; i Just restarted the managed recovery to capture the information
RFS[1]: Archived Log: '/u02/archive/1_88817_665420030.dbf'
Sun Apr 18 18:34:26 2010
RFS[2]: No standby redo logfiles created
RFS[2]: Archived Log: '/u02/archive/1_88818_665420030.dbf'
Sun Apr 18 18:44:26 2010
RFS[3]: No standby redo logfiles created
RFS[3]: Archived Log: '/u02/archive/1_88819_665420030.dbf'
Sun Apr 18 18:54:26 2010
RFS[4]: No standby redo logfiles created
RFS[4]: Archived Log: '/u02/archive/1_88820_665420030.dbf'
Sun Apr 18 18:56:32 2010
alter database recover managed standby database cancel
Sun Apr 18 18:56:50 2010
MRP0: Background Media Recovery cancelled with status 16037
Sun Apr 18 18:56:50 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Sun Apr 18 18:56:51 2010
Waiting for MRP0 pid 29710 to terminate
Sun Apr 18 18:56:51 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
ORA-16037: user requested cancel of managed recovery operation
Sun Apr 18 18:56:51 2010
MRP0: Background Media Recovery process shutdown (rmdp3)
Sun Apr 18 18:56:52 2010
Managed Standby Recovery Canceled (rmdp3)
Completed: alter database recover managed standby database cancel
Sun Apr 18 18:57:19 2010
alter database recover managed standby database disconnect
from session
Sun Apr 18 18:57:19 2010
Attempt to start background Managed Standby Recovery process (rmdp3)
MRP0 started with pid=19, OS id=2123
Sun Apr 18 18:57:19 2010
MRP0: Background Managed Standby Recovery process started (rmdp3)
Managed Standby Recovery not using Real Time Apply
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u03/redologs/rmdp3/redo01.log
Clearing online log 1 of thread 1 sequence number 88818
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 88576
Fetching gap sequence in thread 1, gap sequence 88576-88675
FAL[client]: Error fetching gap sequence, no FAL server specified
Sun Apr 18 18:57:25 2010
Completed: alter database recover managed standby database disconnect
from session
Sun Apr 18 18:57:54 2010
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 88576-88675
DBID 440735188 branch 665420030
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Edited by: user11982297 on Apr 18, 2010 10:58 AM

STATUS of STANDBY REDOLOG

Hello, masters
I have configured a replication environment using real-time capture downstream and everything has gone well. As I have in my source database three groups of redologs, before I created the capture process I add four groups of standby redolog in the downstream database. That is, one more than the number of online redolog present in my source database.
But sometime, when I do the following query:
SELECT ARCHIVED, STATUS FROM V$STANDBY_LOG;
It returns the following for all the standby redolog groups
ARCHIVED STATUS
NO ACTIVE
Because of the above, the capture process behaves like an archived-log downstream capture process. In other words, when a redolog group is archived at the source database, the capture process does his work.
When I look in the alert file I found this message
ORA-16014: log 5 sequence# 6980 not archived, no available destinations
And the trace file:
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 5 thread 1: '+BD4/stra/onlinelog/group_5.271.712605279'
ORA-00312: online log 5 thread 1: '+BD3/stra/onlinelog/group_5.261.712605279'
*** 2010-05-09 06:48:24.805 11367 kcrr.c
Impossible archival state:10
Thanks in advance

Yes I do
ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=+BD7/ VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)';

Redolog in standby

Similar Messages

Maybe you are looking for