waiting for redo log deleted

Oracle 11 g 2 (11.2.0.3) Linux x86_64

A silly mistake was made. While recreate redo standby logfiles, I managed to remove (rm command) waiting for redo log file in progress (before the end of the application) of the BONE. Now I see in the log of alerts:

ORA-00313: open failed for members of log group 7 of thread 1
ORA-00312: online log 7 thread 1: ..../standby_redo7.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

What are my options at this point? I have to any cancelled transaction? The settlement seems to be moving right on the property. Where am I people?

Thanks to you all.

Hello

1 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

2. ALTER LOGFILE GROUP 7 CLEAR DATABASE;

3 ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;

4. ALTER DATABASE ADD STANDBY LOGFILE GROUP 7; OR ALTER DATABASE ADD LOGFILE MEMBER '' HELPS GROUP 7;

5. START AGAIN APPLY: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CURRENT LOGFILE USING DISCONNECT FROM THE SESSION;

HTH

Tobi

Tags: Database

Similar Questions

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

---------- ---------- ---------- ----------

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

---------- ------- ------- ------------------------------ --- ----------

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

Waiting for redo log
Hello
in 10g R2 what are / can be the causes of waiting for redo log?

Thank you.
example of waiting for recovery logs causes may be:
-does not redo groups (remember to add one more, if necessary)
-low rate of I/O
-Redo large log buffer (take a long time for the dump file data) - refers to the slow storage
-application hurt writes, making many validations

Run the Advisor of the ADDM, and see the recommendations. Look at the first 5 albums events. Maybe it's not relevant to DBTime?

I have to create the new group for waiting for redo log files?

I have 10 group of files redo log with 2 members of each group for my primary database, I need to create new group for redo log files for the database of relief pending
Group # members
==============
1              2
2              2
3             2
4             2
5             2
6             2
7             2
8             2
9             2
2 of 10
If so, the following statement is correct? or nto
ALTER DATABASE ADD STANDBY LOGFILE GROUP 1 ('D:\Databases\epprod\StandbyRedoLog\REDO01.) LOG',D:\Databases\epprod\StandbyRedoLog\REDO01_1.log');
Please correct me if am doin wrong
because when I run the statement I have error message saying: the group is already created.

Thanks John

I just found the answer

Yes, it of recomeded to add the new group, for instnace if I have 10 group of 1 to 10, then the wait should be from 11 to 20

Thanks I found the answer.

What is the purpose of waiting for redo log files
Hello

What is the purpose of the log files waiting for redo in the Dr?

What happens if the standby redo log files are created? or else is not created?

Please explain

Thank you
Re: what is the difference between onlinelog and standbylog

I mentioned the goal of the eve of the redo log in RD files in above thread.

Concerning
Girish Sharma

WAITING FOR REDO DICTIONARY: FILE
Hi all

I'm WAITING for REMAKING DICTIONARY: NAME of FILE status

SELECT STATUS FROM V$ STREAMS_CAPTURE;

I tried to solve it and found that some redo log file is missing.
Can you get it someone please let me know what could be the cause of the lack of redo log file?
If the cause for this is that some redo log file is not saved, then how would I record?
I have already questioned the views of data dictionary DBA_REGISTERED_ARCHIVED_LOG and DBA_CAPTURE and I have a few lines.

Thank you all.

Concerning
Nick
It must be reflected in the alerts log.

You can use the following question as well:

SQL > select name from v$ archived_log where between first_change # and next_change #;

recommended OS size for redo log block
Hello

AIX platform
Oracle 10.2.0.4

Is there any system recommended filesystem blocksize where redo log should be placed?
We tested with 512 bytes to 4 096 bytes. We got the best performance over 512 bytes in terms of waiting avg on synchronization of log file.
There's recommendation on the same oracle/AIX?
978881 wrote:
Hello

AIX platform
Oracle 10.2.0.4

Is there any system recommended filesystem blocksize where redo log should be placed?
We tested with 512 bytes to 4 096 bytes. We got the best performance over 512 bytes in terms of waiting avg on synchronization of log file.
There's recommendation on the same oracle/AIX?

The recommendation is to create logs of recovery on a mount with agblk = 512bytes. Please refer following link (page 60) which is an oracle + IBM technical brief:

http://www-03.IBM.com/support/techdocs/atsmastr.nsf/5cb5ed706d254a8186256c71006d2e0a/bae31a51a00fa0018625721f00268dc4/ $FILE/Oracle%20Architecture%20and%20Tuning%20on%20AIX%20 (v%202.30) .pdf

Kind regards
S.K.

Oracle 10g Capture of Source DB process: waiting for redo of the dictionary?
Hi all,

Location: Source DB waiting for dictionary redo first SNA

First SCN = 314353677
Start the SNA = 644568684
Current SNA = 779444676

Do not now how to trouble shoot
Previous error's break to flow control
Now, that's what makes the dictionary again first SNA

How to draw step by step problem
PLeeaasssssssse expertssssss need help
No stop is mandatory, you db is not involved in the restoration.
And please stop thanks, it becomes very annoying.

One group of standby Redo Log is ACTIVE

Hi guys,.
I have successfully configured a custodian of data between a primary database (oradb) and a database ensures Physics (oradb_s8).
However, I have noticed that in V$ STANDBY_LOG only one group of standby Redo Log is ACTIVE, regardless of how many times I go log in the primary database.
' The following was stated in the documentation:
When a switch of newspaper occurs on the database of the source again, redo incoming is then written to the next group of waiting for redo log, and the group used newspaper before again Eve is archived by a foreground ARCn process.
Source.
So, I guess that group of standby Redo Log is turned on when the Redo Log is enabled in the primary database.
Could you please clarify it for me?
It's the Oracle 11 g R2 (11.2.0.1) on Red Hat Server 5.2.
On autonomy in standby:
SQL > SELECT GROUP #, THREAD #, SEQUENCE #, ARCHIVED, STATUS FROM V$ STANDBY_LOG
GROUP # THREAD # SEQUENCE # ARC STATUS
---------- ---------- ---------- --- ----------
4 1 248 YES ACTIVE <-this is the only group that is still ACTIVE
5 1 0 NOT ASSIGNED NO.
6 0 YES 0 UNASSIGNED
7 0 YES 0 UNASSIGNED
SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME
V $ ARCHIVED_LOG
SEQUENCE ORDER #;
SEQUENCE # FIRST_TIM NEXT_TIME APPLIED
---------- --------- --------- ---------
232 06-06-SEPT.-15-15-SEP YES
233 06-06-SEPT.-15-15-SEP YES
234 06-06-SEPT.-15-15-SEP YES
235 06-06-SEPT.-15-15-SEP YES
236 06-06-SEPT.-15-15-SEP YES
237 06-06-SEPT.-15-15-SEP YES
238 06-06-SEPT.-15-15-SEP YES
239 07-06-SEPT.-15-15-SEP YES
240 YES 15-SEP-07 07-SEVEN.-15
241 YES 15-SEP-07 07-SEVEN.-15
242 YES 15-SEP-07 07-SEVEN.-15
YES 243 15-SEP-07 07-SEVEN.-15
244 YES 15-SEP-07 07-SEVEN.-15
245 YES 15-SEP-07 07-SEVEN.-15
246 YES 15-SEP-08 15-SEP-07
247 15 - SEP - 08 IN-MEMORY 15-SEP-08
16 selected lines.
On the primary:
SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME
V $ ARCHIVED_LOG
WHERE NAME = 'ORADB_S8 '.
SEQUENCE ORDER #;
SEQUENCE # FIRST_TIM NEXT_TIME APPLIED
---------- --------- --------- ---------
232 06-06-SEPT.-15-15-SEP YES
233 06-06-SEPT.-15-15-SEP YES
234 06-06-SEPT.-15-15-SEP YES
235 06-06-SEPT.-15-15-SEP YES
236 06-06-SEPT.-15-15-SEP YES
237 06-06-SEPT.-15-15-SEP YES
238 06-06-SEPT.-15-15-SEP YES
239 07-06-SEPT.-15-15-SEP YES
240 YES 15-SEP-07 07-SEVEN.-15
241 YES 15-SEP-07 07-SEVEN.-15
YES 07-SEP-15 242 07-SEP-15
YES 243 15-SEP-07 07-SEVEN.-15
244 YES 15-SEP-07 07-SEVEN.-15
245 YES 15-SEP-07 07-SEVEN.-15
246 YES 15-SEP-08 15-SEP-07
247 NO. 15-SEP-08 08 - SEPT.-15

If you have a large DML activity on primary, you see more than one group # in v$ active standby_log.

RFS will always try to assign the next available standby log, because your group changes # 4 are already applied, it allocates this group again after the switch.

Check metalink doc: bug 2722195 and 219344.1

Standby redo logs must be configured on the primary

Oracle 11.2.0.4, 4 CARS on primary node
Oracle 11.2.0.4, node 4 CARS waiting
Configured with oracle Data Guard using Data Guard Broker
I use the latest version or orachk 12.1.0.2.4
In the orachk report, I see the following error message:
Standby redo logs must be configured on the primary
+RECO/finprd1/onlinelog/group_13.2146.881183157
+RECO/finprd1/onlinelog/group_14.2143.881183159
+RECO/finprd1/onlinelog/group_15.5008.881183161
+Data/finprd1/onlinelog/group_16.1660.881183161
+RECO/finprd1/onlinelog/group_16.5003.881183161
+RECO/finprd1/onlinelog/group_17.4999.881183163
+RECO/finprd1/onlinelog/group_18.2096.881183163
+RECO/finprd1/onlinelog/group_19.2094.881183305
+RECO/finprd1/onlinelog/group_20.1778.881183305
+RECO/finprd1/onlinelog/group_21.4994.881183307
+RECO/finprd1/onlinelog/group_22.4992.881183307
+RECO/finprd1/onlinelog/group_23.2049.881183307
+RECO/finprd1/onlinelog/group_24.1454.881183309
+RECO/finprd1/onlinelog/group_25.4983.881183309
+RECO/finprd1/onlinelog/group_26.1688.881183309
+RECO/finprd1/onlinelog/group_27.4973.881183311
+RECO/finprd1/onlinelog/group_28.4969.881183311
But when I check the primary database, I see that there are waiting for redo logs. So, why the error? Any ideas?
[SYS@FINPRD11] SQL > select
2 lg.group #.
LG.type,
3 4 lg.member
l.bytes/1024/1024 as SIZE_MB
Of
5 6 7 v$ logfile lg,.
v 8 $log l
9 where
10 lg.group #= l.group #.
Union of all the
11 12 select
LG.Group # 13,
LG.type 14,
15 lg.member,
16 st.bytes/1024/1024 as SIZE_MB
17 of
18 v$ logfile lg,.
19 v$ standby_log st
where the 20
21 lg.group #= st.group #;
GROUP # TYPE MEMBER SIZE_MB
---------- ------- -------------------------------------------------- ----------
1 +DATA/finprd1/onlinelog/group_1.286.876507139 on LINE 512
1 +RECO/finprd1/onlinelog/group_1.706.876507139 on LINE 512
+DATA/finprd1/onlinelog/group_2.384.876507141 online 2 512
+RECO/finprd1/onlinelog/group_2.737.876507141 online 2 512
+DATA/finprd1/onlinelog/group_7.451.876507495 online 7 512
+RECO/finprd1/onlinelog/group_7.714.876507497 online 7 512
+DATA/finprd1/onlinelog/group_8.450.876507497 online 8 512
+RECO/finprd1/onlinelog/group_8.1162.876507497 online 8 512
+DATA/finprd1/onlinelog/group_5.449.876507499 online 5 512
+RECO/finprd1/onlinelog/group_5.355.876507499 online 5 512
+DATA/finprd1/onlinelog/group_6.448.876507499 online 6 512
+RECO/finprd1/onlinelog/group_6.818.876507501 online 6 512
+DATA/finprd1/onlinelog/group_3.447.876507501 online 3 512
+RECO/finprd1/onlinelog/group_3.1188.876507501 online 3 512
4 +DATA/finprd1/onlinelog/group_4.446.876507503 on LINE 512
4 +RECO/finprd1/onlinelog/group_4.385.876507503 on LINE 512
+DATA/finprd1/onlinelog/group_9.1653.881182905 online 9 512
+RECO/finprd1/onlinelog/group_9.5058.881182905 online 9 512
+DATA/finprd1/onlinelog/group_10.1654.881182985 online 10 512
+RECO/finprd1/onlinelog/group_10.2206.881182985 online 10 512
+DATA/finprd1/onlinelog/group_11.1655.881182985 online 11 512
+RECO/finprd1/onlinelog/group_11.2205.881182987 online 11 512
+DATA/finprd1/onlinelog/group_12.1656.881182987 online 12 512
+RECO/finprd1/onlinelog/group_12.5045.881182987 online 12 512
+RECO/finprd1/onlinelog/group_13.2146.881183157 EVE 13 512
+RECO/finprd1/onlinelog/group_14.2143.881183159 EVE 14 512
+RECO/finprd1/onlinelog/group_15.5008.881183161 EVE 15 512
+DATA/finprd1/onlinelog/group_16.1660.881183161 EVE 16 512
+RECO/finprd1/onlinelog/group_16.5003.881183161 EVE 16 512
+RECO/finprd1/onlinelog/group_17.4999.881183163 EVE 17 512
+RECO/finprd1/onlinelog/group_18.2096.881183163 EVE 18 512
+RECO/finprd1/onlinelog/group_19.2094.881183305 standby 19 512
+RECO/finprd1/onlinelog/group_20.1778.881183305 EVE 20 512
+RECO/finprd1/onlinelog/group_21.4994.881183307 EVE 21 512
22 +RECO/finprd1/onlinelog/group_22.4992.881183307 ENSURES 512
+RECO/finprd1/onlinelog/group_23.2049.881183307 EVE 23 512
+RECO/finprd1/onlinelog/group_24.1454.881183309 EVE 24 512
+RECO/finprd1/onlinelog/group_25.4983.881183309 EVE 25 512
26 +RECO/finprd1/onlinelog/group_26.1688.881183309 ENSURES 512
+RECO/finprd1/onlinelog/group_27.4973.881183311 EVE 27 512
+RECO/finprd1/onlinelog/group_28.4969.881183311 EVE 28 512
41 selected lines.
[SYS@FINPRD11] SQL > SELECT GROUP #, THREAD #, SEQUENCE #, ARCHIVED, STATUS FROM V$ STANDBY_LOG
2;
GROUP # THREAD # SEQUENCE # ARC STATUS
---------- ---------- ---------- --- ----------
13 1 0 UNASSIGNED YES
14 1 0 UNASSIGNED YES
15 1 0 UNASSIGNED YES
16 1 0 UNASSIGNED YES
17 2 0 UNASSIGNED YES
18 2 0 UNASSIGNED YES
19 2 0 UNASSIGNED YES
20 2 UNASSIGNED YES 0
21 3 0 UNASSIGNED YES
22 3 0 UNASSIGNED YES
23 3 0 UNASSIGNED YES
GROUP # THREAD # SEQUENCE # ARC STATUS
---------- ---------- ---------- --- ----------
24 3 0 UNASSIGNED YES
25 4 0 UNASSIGNED YES
26 4 0 UNASSIGNED YES
27 4 0 UNASSIGNED YES
28 4 0 UNASSIGNED YES

IT would be difficult to debug, better you trigger SR in support to verify the code. Good thing is you know again sleep exists, so why worry.

You can ignore it.

Standby redo logs

Hi all
For the installation of dataguard, supposed to docs create standby redo logs on the standby server.
It does not mention to create logs to redo waiting on the primary server.
So what happens if I pass of the day before?
Then my primary db now becomes the day before db. But there is no waiting for redo logs?
Kindly shed lights...
Thank you very much
JC

Jenna_C wrote:

Hi Sysas and ALL,

the rule is to create a group of newspapers waiting to roll forward pending Eve more than the number of redo log group in the primary.

Do you mean > the rule is to create a group of newspapers waiting to roll forward pending Eve more than the number of the Group of online redo logs in the primary?

So, if I have 3 ONLINE redo log groups and 4 STANDBY redo log at the primary level, 3o + 4 s = 7

I'll create 3 groups of online redo logs and 1 redo log group ENSURES the standby? 3O + 1 s = 4

Why not just create everything as even with the main number? 3O + 4 s = 7 for sleep?

Thank you.

Sorry... If you have 3 groups of newspapers online redo (in primary and standby), and then create 4 STANDBY redo record groups (primary and standby).

Concerning

That redo log files waiting?

Hello Experts,
I read articles on the log redo and undo segment files. I was wondering something very simple. That redo log files waiting in there? It stores the sql statements?
Lets say that my update statement to modify 800 blocks of data. A unique single update statement can modify different data 800 right blocks? Yes, it may be true. I think that these data blocks can not hold buffers to the log to roll forward, right? I mean I know exactly what to do redo log buffer and redo log file. And I know that the task of backgrounding LGWR. But, I wonder if she she holds the data blocks? It is not supposed to hold data like cache buffer blocks, right?
My second question is, rollback isn't effect to restore the newspaper to the right buffer? Because it does not need log buffer for effect do it again. Conversely, the restoration; statement is included in the restore log buffer by progression when someone isse, am I right?
As far as I know, rollback interact directly with UNDO TABLESPACE?
I hope that I have to express myself clearly.
Thanks in advance.

Here's my question:

My second question is, rollback isn't effect to restore the newspaper to the right buffer? Because it does not need log buffer for effect do it again. Conversely, the restoration; statement is included in the restore log buffer by progression when someone isse, am I right?

As far as I know, rollback interact directly with UNDO TABLESPACE?

Yes, where else would the undo data come from? Undo tablespace contains the Undo segments that contain the Undo data required for the restoration of your transaction.

I can say that rollback does not alter the data of the log buffer rede to the past. In other words, change vectors will be remain the same before restoration. Conversely, rollback command is also recorded in the log file of restoration by progression. As the name, all orders are saved in the REDO LOGS.

I hope that I am wrong so far?

Not sure why you even the buffer log roll forward for Rollback? This is the reason why I asked you it was for, where occurs the dose the cancellation? And the answer for this is that it happens in the buffer cache. Before you worry about the drivers of change, you must understand that it is not serious what contains where as long as there is no transaction recorded in the operating of the Undo segment table. If the operating table indicates that the transaction is longer there, there must be a cancellation of the transaction. Vectors of change are saved in the file log roll forward, while the restore happens on blocks of data stored in the file "data" undo blocks stored in the undo file "data".

At the same time I read an article about redo and undo. In this article process transaction is explained. Here is the link http://pavandba.files.wordpress.com/2009/11/undo_redo1.pdf

I found some interesting information in this article as follows.

It is worth noting that during the restore process, recovery logs never participate. The only time where redo logs are read is retrieving and archiving. This is the concept of tuning key: redo logs are written on. Oracle does not read during normal processing. As long as you have sufficient devices so that when the ARC is reading a file, LGWR's writing to a different device, then there no contention for redo logs.

If redo logs are never involved in the restoration process, how is it Oracle will then know the order of the transaction? As far as I know it is only written in redo logs.

I have thoughts very amazed to Aman.

Why you ask?

Now, before giving a response, I say two things. One, I know Pavan and he is a regular contributor to this forum and on several other forums Facebook and two, with all due respect to him, a little advice for you, when you try to understand a concept, to stick to the Oracle documentation and do not read and merge articles/blog-posts from the web. Everone, which publishes on the web, has their own way to express things and many times, the context of the writing makes it more confusing things. Maybe we can erase the doubts that you can get after reading the various search results on the web.

Redo logs used for the restoration, not to restore. The reason is the redo log files are applied in sequential order, and this is not the case when we look for the restoration. A restore is required to do for a few blocks away. Basically, what happens in a restoration, is that the records of cancellation required for a block of data are sought in the reverse order of their creation. The entry of the transaction is in the slot ITL of the block of data that point to the necessary undo bytes Address (UBA) using which oracle also knows what that undo the blocks would be necessary for the restoration of your transaction. As soon as the blocks of data will be cancelled, the ITL slots would be cleared as well.

In addition, you must remember, until the transaction is not qualified as finished, using either a commit or a rollback, the cancellation of this data would remain intact. The reason for this is that oracle would ensure that undo data would be available to make the cancellation of the transaction. The reason why Undo data are also recorded in the journals of recovery is to ensure that in the event of the loss of the cancellation of the data file, retrieving them would be possible. Because it would also require changes that's happened on the blocks cancel, restore the vectors change associated with blocks of cancellation are also saved in the buffer log roll forward and, in the redo log files.

HTH

Aman...

Redo log shipping after a stop pending physical

Hallo,
I just have a question for redo log shipping
in a configuration simple primary/secondary 11g.
In a shutted down an instance physical standby, redoshipping is active? Primary redo file transfer is still ongoing?
Thanks in advance

Hello;

I'm not going to say no. I still SEE on the primary side before I shutdown, maintains false alarms from happening.

Test

Using this query

http://www.mseberg.NET/data_guard/monitor_data_guard_transport.html

DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP

---------- -------------- ------------ ----------- -------------- -------

TDBGIS01B PRIMARY 5558 5557 21-OCT/12:51 1

Stop waiting

SQL > alter database recover managed standby database cancel;

Database altered.

SQL > shutdown

ORA-01109: database is not open

The database is dismounted.

Journal of strength comes on primary side

SQL > alter system switch logfile;

Modified system.

(3)

Journal of before was 5558 check so make sure 5559 or higher

Last log is

o1_mf_1_5558_c2hn5vdf_.arc

Wait a few minutes, no change

Best regards

mseberg

REDO LOG BUFFER DOUBT
Hi EXPERTS,

IM on 11 G R2, RHEL 5 my question that when the data changes in the database buffer cache how immediately it is copied in the redo log buffer. I mean what process the copy. I read it in the oracle documentation only when waiting for event [log file command (private stream flush incomplete)] LGWR waits DBWR again complete flushing of buffers IMU in the recovery log buffer. Completion of DBWR LGWR can then finish writing the log in process and then move the log files.

the stubborn standby redo log
I have a dowstreams that has four groups of log roll forward pending. one of these groups is always in a redo of the day 23/04/2010. This former roll forward is not filed, always there.
This implies that the endorsements of the database are working with three groups of redo log and some oacaciones all that is in the active State and at this time that the view v $ archived_dest returns the error for that destination (natural).

the question is:

How can I eliminate this newspaper waiting for redo which is more archived.

Thank you very much for your attention
You have error messages in the alert log?

See this Metalink Note:
Alert.log watch no. standby redo Logfiles of size 153600 available blocks [405836.1 ID]

waiting for redo log deleted

Similar Questions

Maybe you are looking for