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]

Tags: Database

Similar Questions

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 and the Directory Structure in the Backup Site

Hi guru
I just want to confirm, I know that if the directory structure is different, I need to talk about these 2 settings in the file pfile
on the main site:
DB_CONVERT_DATAFILE = 'sleep', 'primary '.
LOG_CONVERT_DATAFILE = 'sleep', 'primary '.
On the secondary Site:
DB_CONVERT_DATAFILE = 'primary', 'sleep '.
LOG_CONVERT_DATAFILE = 'primary', 'sleep '.
But I want to confirm this weather I have to deliver the full path of the directory in the two paramtere above:
as:
DB_CONVERT_DATAFILE = ' / u01/oracle/app/oracle/oradata/sleep ', ' / u01/oracle/app/oracle/oradata/primary.
LOG_CONVERT_DATAFILE = ' / u01/oracle/app/oracle/oradata/sleep ', ' / u01/oracle/app/oracle/oradata/primary.
Second Confusion: -.
After that transfer standby Redo logs creates primary and made to sleep on the foregoing, mentioned the directory structure and after restoring the alongwith primary db backup, that ensures the control file will not affect the journal of physics again placed watch on the above mentioned location.
Thanks in advance for your help

vk82 wrote:

In fact, I create the day before by using the RMAN Duplicate command. but where I am confused is the point if I transfer the backup that i taken the pri on the C:\backup_files path. and after that, I transfer the backups to the waiting on C:\backup_files. After that when I restore it will create datafile and other stuff in another directory I mentioned using DB_FILE_NAME_CONVERT as LOG_FILE_NAME_CONVERT. I think Yes but need your advice during the same period.

Hello

Yes, files should be created under the directory mentioned in the path of the parameters 'db_file_name_convert' and 'log_file_name_convert.

Kind regards
Shivananda

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

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

Creating standby Redo Log

DB version: 11.2
OPERATING SYSTEM: AIX 6.1

We have a 2 RAC node. We have a disk group for all files of data, tempfiles, recovery logs... etc.
Currently in our primary database Redo logs look like

SQL> SELECT a.group#, b.thread#, a.member, b.bytes
FROM v$logfile a, v$log b WHERE a.group# = b.group#
order by a.group# , b.thread#  2    3  ;

         GROUP#         THREAD# MEMBER                                BYTES
--------------- --------------- -------------------------------- ---------------
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600

6 rows selected.

1 member per group
3 group per instance

We need to create a physical standby DB for DB above with real time applies. For standby Redo logs, I need a log file additional for each Instance.

So, I'll add
Group # 7 for thread 1
and
Group # 8 for thread 2

Finally, SRls will look like

         GROUP#         THREAD# MEMBER                                BYTES
--------------- --------------- -------------------------------- ---------------
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
              
           7               1 +ORCL_DG/orcl/orcl_log07.dbf         104857600  ------->  Additional

              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
              
           8               2 +ORCL_DG/orcl/orcl_log08.dbf         104857600  ------->  Additional

Something wrong with my creation SRL project?

Super good

1 member by regular group raises a different issue.

Generating all you need is 1.

Best regards

mseberg

Standby redo log query

Hello team,
I have a query:
When I add or delete redo Eve journal/primary group is that ensure redo log group corresponding is added / removed pending?
Kind regards

As already answer, this change will be automatically in standby mode.

This section of the documentation discusses steps to add redo log files to a database of pending. I find that to be a little lack of detail, so you can also visit Metalink Note 740675.1 online Redo Logs in physical availability.

HTH,

Brian

How to replace the members of the Group missing redo log after the failure of a support

Hello
I'm testing a disk failure scenario. I had recovery multiplexes on three sites (Windows drive letters) logs; one of the three locations also contained the data files. I deleted the Windows player that contained data files and saw a restoring with RMAN. All is well except that redo log members who are found on the occult Windows disk are of course still missing; the database opens, etc., but puts messages like this in the ALERT.log:
ORA-00321: log thread 2 1, cannot update log file header
ORA-00312: wire 2 1 online journal: ' F:\APP\NGORA12CR2SRV\ORADATA\ORATEST5\ONLINELOG\O1_MF_2_BW4B5MY0_. JOURNAL"

What is the 'right' way to replace missing limbs? Just get all the new groups of newspapers with new members on all three discs? Carefully copy the LOG files representing missing members of one of the other sites? I add new members at this location and remove existing members (missing)?

Is how important it?

Thank you!

Martin

See 'Recover after losing a member of a group of Redo Logs online multiplexed'

at http://docs.oracle.com/cd/E11882_01/backup.112/e10642/osadvsce.htm#sthref2205

Hemant K Collette

Check the configuration of Redo Log Archives to
DB version: 10 gr 2, 11 2 GR
Version of the operating system: Solaris 5.10, AIX 6.1

While allowing for a DB from Production 2 node RAC, I made a mistake specifying LOG_ARCHIVE_DEST (a typing error).

After I brought the DB to the top (open) after you have enabled archiving, I tested the journal using switching
```
SQL> alter system switch logfile;

System altered
```
and had no error.

Later, I realized, archiving does not work. But I wonder, why I have no error for
```
SQL> alter system switch logfile;
```
Errors may have been recorded in the log of alerts. Since then I have no error from sqlplus to the command above, I thought everything was fine.

But the following command triggered error.
```
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
ALTER SYSTEM ARCHIVE LOG CURRENT
*
ERROR at line 1:
ORA-16038: log 4 sequence# 127 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 4 thread 2: '+LTMPROD_DATA/LTMPROD/redo04.log'
ORA-15173: entry 'ltmprod_arch' does not exist in directory '/'
```
Should what command I use to ensure that activation of Archive was successful?
Hello

Any more ways on how professional to check whether the archive allowing a success?

ALWAYS... After putting data in ARCHIVE MODE, you must force the newspaper archive database.
```
SQL > ARCHIVE LOG LIST; # To check status

SQL > ALTER SYSTEM ARCHIVE LOG CURRENT; # This command must be executed sucessfull.

Query V$ARCHIVE_LOG or use RMAN to check path/location of ARCHIVELOG. 

$ rman target /
RMAN > LIST ARCHIVELOG ALL; 
```
Use ARCHIVE LOG SWITCH LOGFILE command to force again them to archive the disk, because they have a slight difference.

JOURNAL of ARCHIVING is synchronous, this command waits until the online redo log has completed writing the log file again the file system, if again is not archived error is thrown on command prompt.

SWITCH LOGFILE is asynchronous, this command start only switch / archive run in the background if ARCH process cannot finish writing the archivelog directory on file the error not returned not invite since he was released.

You can use this technical note:
* How to enable archiving ON and OFF [ID 69739.1] *.

Hope this helps,
Levi Pereira

Published by: Levi Pereira on September 23, 2011 01:28

error in the extension of redo logs
Dear friends,

I just tried a few measures to extend some redologs and it worked.

Applied to a different database and problems.

Please guide me.

alter database drop logfile Group 1;

change the database
Add logfile group 1 ('F:\DEV\REDO01.) LOG ') SIZE 20 M;

error: ORA-00301: Error adding the log file ' F:\DEV\REDO01. NEWSPAPER "-could not create the file"
ORA-27038: created file already exists
OSD-04010: < create > option specified, the file already exists

But the first line was a success.

Please help me.

Nith
alter database add logfile group 1 ('F:\DEV\REDO01.) LOG ') SIZE 20 M REUSE;

How do I know if there's bottleneck in the redo logs?

Hi all
EBS R12.2
11 GR 2
OL 6.5
We have two groups of log of size 1 GB.
and oyour archiving logs generates 13 newspapers every hour.
-rw - r-. 1 oraprod s/n 956896768 Jan 25 14:00 1_3372_898613761.dbf
-rw - r-. 1 oraprod s/n 1004083200 Jan 25 14:03 1_3373_898613761.dbf
-rw - r-. 1 oraprod s/n 928530432 Jan 25 14:10 1_3374_898613761.dbf
-rw - r-. 1 oraprod s/n 928728576 Jan 25 14:12 1_3375_898613761.dbf
-rw - r-. 1 oraprod s/n 967805952 Jan 25 14:20 1_3376_898613761.dbf
-rw - r-. 1 oraprod s/n 916065792 Jan 25 14:22 1_3377_898613761.dbf
-rw - r-. 1 oraprod s/n 951790592 Jan 25 14:30 1_3378_898613761.dbf
-rw - r-. 1 oraprod s/n 978358272 Jan 25 14:32 1_3379_898613761.dbf
-rw - r-. 1 oraprod s/n 974519808 Jan 25 14:40 1_3380_898613761.dbf
-rw - r-. 1 oraprod s/n 960421376 Jan 25 14:42 1_3381_898613761.dbf
-rw - r-. 1 oraprod s/n 917438976 Jan 25 14:49 1_3382_898613761.dbf
-rw - r-. 1 oraprod s/n 920794624 Jan 25 14:51 1_3383_898613761.dbf
-rw - r-. 1 oraprod s/n 920704000 Jan 25 14:59 1_3384_898613761.dbf
I got this alert saves messages:
Mon Jan 25 15:08:37 2016
Filled checkpoint up to RBA [0xd3b.2.10], RCS: 5978324588151
Mon Jan 25 15:10:57 2016
Thread 1 cannot allot of new newspapers, sequence 3388
Private stream flush is not complete
Currently journal # 1, seq # 3387 mem # 0: /home/oraprod/PROD/data/log01a.dbf
Currently journal # 1, seq # 3387 mem # 1: /home/oraprod/PROD/data/log01b.dbf
Beginning log switch checkpoint up to RBA [0xd3c.2.10], RCS: 5978324634623
Thread 1 Advanced for you connect to sequence 3388 (switch LGWR)
Currently Journal # 2 seq # 3388 mem # 0: /home/oraprod/PROD/data/log02a.dbf
Currently Journal # 2 seq # 3388 mem # 1: /home/oraprod/PROD/data/log02b.dbf
Mon Jan 25 15:11:01 2016
LNS: Standby redo log file selected for thread 1 sequence 3388 for destination LOG_ARCHIVE_DEST_2
Mon Jan 25 15:11:04 2016
Archived journal 6791 extra for each sequence 1 3387 ID thread entry 0 x 12809081 dest 1:
Mon Jan 25 15:11:17 2016
Filled checkpoint up to RBA [0xd3c.2.10], RCS: 5978324634623
Mon Jan 25 15:13 2016
Additional checkpoint up to RBA to RBA [0xd3c.1a8e82.0] [0xd3c.18d210.0], current journal line
Mon Jan 25 15:13:04 2016
Thread 1 cannot allot of new newspapers, sequence 3389
Private stream flush is not complete
Currently Journal # 2 seq # 3388 mem # 0: /home/oraprod/PROD/data/log02a.dbf
Currently Journal # 2 seq # 3388 mem # 1: /home/oraprod/PROD/data/log02b.dbf
Beginning log switch checkpoint up to RBA [0xd3d.2.10], RCS: 5978324673444
Thread 1 Advanced for you connect to 3389 (switch LGWR) sequence
Currently journal # 1, seq # 3389 mem # 0: /home/oraprod/PROD/data/log01a.dbf
Currently journal # 1, seq # 3389 mem # 1: /home/oraprod/PROD/data/log01b.dbf
Mon Jan 25 15:13:07 2016
LNS: Standby redo log file selected for thread 1 sequence 3389 for destination LOG_ARCHIVE_DEST_2
Mon Jan 25 15:13:09 2016
Archived journal 6793 extra for each sequence 1 3388 ID thread entry 0 x 12809081 dest 1:
Mon Jan 25 15:13:11 2016
Filled checkpoint up to RBA [0xd3d.2.10], RCS: 5978324673444
Is it a sign of botteneck? Users complained that each 15:00 they encounter performance degradation.
Kind regards
JC

Jenna_C wrote:

We have two groups of size 1 GB log and our archiving logs generates 13 newspapers every hour.

Is it a sign of botteneck? Users complained that each 15:00 they encounter performance degradation.

If your users are complaining about slow at 15:00 then look at what is happening on the system at this point in time. Use the Active Session history, providing that you have the license, at 3 pm to see if there is a problem. Or take snapshots of the AWR manually around 15:00 in an attempt to capture any anomaly. Or capture instant V$ SESSION yourself manually around 15:00 and see so many sessions is pending or not.

I have seen problems like this on shared physical infrastructure systems where the activity on a system can interfere with each other. Attention to this kind of thing, because if it is caused by another system then you will never find the cause of the problem inside the Oracle. Examples include backups are made at a specific time, causing large amounts of sequential disk i/o and slows down access to the drive for everything else. Such a scenario could cause some writing redo log time to increase significantly. Or the backup could be another system completely who shares the same disks in the same drive bay or the SAN and Bay drives or SAN is inundated by applications e/s backup. But as it's another system, that you will not see what is happening on your Oracle database system.

Or a virtualized with environment sharing CPU and memory where another virtual machine running a CPU intensive job and steals the Oracle system CPU capacity. I saw the same thing with memory so - Vmware has a strange way to virtualize memory, which means it can use all of the memory on the physical hardware and run out, and then he had to intervene to release somehow little memory. What ends up slowing things down.

It could be a network problem - is something that the network of the floods at 15:00? Still, backups can be a common cause of this, during the transfer of data over the network to another system. Is there a work extracted regularly data which runs at 15:00 for example extract given OLTP to feed into a data warehouse, which is copied on the network?

It could be many different things, causing the slowdown. I would definitely recommend watching any expected sessions know and see if this gets worse around 15:00, or if it remains the same, in which case the problem is elsewhere. You must also eliminate everything else - the disks, network, etc.

Good luck

John Brady

Standby database is down and redo logs is not transmitted
Hi all

I have a question about the primary recovery database logs transmition for the standby database.
What happens if the transmition of redo logs was arrested for a period of time (1 month), if I want to re - build the database ensures what measures must be applied?
The papers of recovery will be put on hold? and once the database pending is redo these logs will be sent again? or I have to rebuild my database Eve from scratch?

Kind regards
Hello;

When I rebooted the month so I would change the parameter 'log_archive_dest_state_n' on the primary to postpone next it would stay like that.

I would like to delete the database in waiting, and if the folder structure was not the same I correct it.

When the month has increased I would use RMAN to duplicate a new sleep mode:

http://www.Visi.com/~mseberg/duprman2.html

And then I put "log_archive_dest_state_n" to Activate.

Best regards

mseberg

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

Redo log entries to the online redo log files

Hello
I'm a little confused about the redo log entries.
I learned that LGWR writes redo log entries in the SGA, in redo log files in the following situation:
-3 seconds after the last validation
-redo log buffer has 1 MB
-redo log buffer data 1/3
When I take a transaction and if I change the wrong data, I have to cancel this transaction BUT the right now,
What happens if the LGWR writes redo log disk entries?
Is the bad transaction committed at all times?

2791011 wrote:

Hello

I'm a little confused about the redo log entries.

I learned that LGWR writes redo log entries in the SGA, in redo log files in the following situation:

-3 seconds after the last validation

-redo log buffer has 1 MB

-redo log buffer data 1/3

When I take a transaction and if I change erroneous data, I have to cancel this transaction at this time, BUT

What happens if the LGWR writes redo log disk entries?

Is the bad transaction committed at all times?

DML changes are "permanent" after that VALIDATION is issued.

When any COMMIT is issued, then changes can be undone.

Best location for the archived redo logs

Hello
I am OOF instructions and I want to make life for the DBA, that looks like my job easier.
So, as the title says what is the location of the "standard/Best Practice' for archived redo logs? particularly the dest_1 which is usually local on the same server
Thank you.

Hello

For you, I recommend the use of the Flash/fast recovery area.

Configuration of the archived of Redo Log locations

Oracle recommends that you use fast area recovery to an archive location, because the archived logs are managed automatically by the database. The file names generated for the newspapers archived in the fast recovery area correspond to Oracle managed files and are not determined by the parameter LOG_ARCHIVE_FORMAT . Whatever archiving scheme you choose, it is always advisable to create multiple copies of archived redo logs.

Ref 1:

http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#CHDEHHDH

Ref 2:

http://docs.Oracle.com/CD/E11882_01/server.112/e17157/unplanned.htm#BABEEEFH

REF 3:

http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV89418

Kind regards

Juan M

the stubborn standby redo log

Similar Questions

Configuration of the archived of Redo Log locations

Maybe you are looking for