Creating standby Redo Log

Similar Questions

• 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

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

• Create the REDO Logs after restoration of RMAN

  Version 11.2
  Platform: Solaris 10
  
  We restore the cold RMAN backup to a new server. It's a basic restore RMAN where DB name remains the same.
  
  I understand that RMAN backup online redo logs, and for good reason.
  
  We have restored our datafiles successfully. The control file still has the old entries so the query below shows old information about recovery logs
  
  -Display of the configuration of the log file the old control file data

  SYS > select * from v$logfile;         ------------> The below output shows the result of the source server
  
      GROUP# STATUS  TYPE    MEMBER                              IS_
  ---------- ------- ------- ----------------------------------- ---
           1         ONLINE  /DATAM/DB/oradata/slmps/redo1.log      NO
           2         ONLINE  /DATAM/DB/oradata/slmps/redo2.log      NO
           3         ONLINE  /DATAM/DB/oradata/slmps/redo3.log      NO

  I have to use ALTER DATABASE RENAME FILE command as below to update the control file.

  alter database rename file '/DATAM/DB/oradata/slmps/redo1.log' to '/data/oradata/slmps/slmps_log01.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo2.log' to '/data/oradata/slmps/slmps_log02.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo3.log' to '/data/oradata/slmps/slmps_log03.dbf' ;  

  Currently, in the new server, at the level of the BONE there is no physical file above to
  

  /data/oradata/slmps

  I need to create physically redo new logs using the command or the command ALTER DATABASE RENAME above key create a physical file at the level of the BONE?

  Salvation in spiral,

  Surely, RMAN will search for redo logs when RECOVER is issued.

  When you issue the command RECOVER after restore, RMAN does not check online redo logs. During RECOVERY, RMAN will try to apply the archivelogs or incremental L1 if it has been saved on the source server. RMAN Backup restorations online redo logs or never.

  Here OP tries to restore the backup from the cold to a new server. In this case the RECOVER command is not necessary. The example of the Oracle doc you mentioned should do a restore, recovery of a backup hot. In this case, during the RESTORATION, RMAN will try to apply archivelogs or L1 of the incremental backups.

  In both cases (cold backup restore or restore, recover from Hot Backup), it is the

  alter database open resetlogs
  

  command that will create the online redo log, so it is absent in the location specified by the control file. Because it is a restoration to a new server, recovery logs is missing because it has not been restored (because it has not been saved)

• 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]

• DB restore Archives not lost mode redo log file... restore from controlfile tr

  I have a 11g database I had taken an archive backup but has failed to take redo backup of log files...
  so, while I restored the PB... after formatting the machine... the oracle instance does not start.
  
  
  I create controlfile track but when I run it I get errors.
  given that I don't have the old log files... How can I get around this issue
  Thank you
  Here is the example of trace control file... Note that I can't create the redo log file
  given that the db will not climb up, it must be in mode nonmount
  and here's my created controlfile...
  CREATE CONTROLFILE REUSE DATABASE "XE" NORESETLOGS NOARCHIVELOG
  MAXLOGFILES 16
  MAXLOGMEMBERS 3
  MAXDATAFILES 100
  MAXINSTANCES 8
  MAXLOGHISTORY 292
  LOGFILE
  GROUP 1
  ' C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_80L7C259_. JOURNAL"
  SIZE 50 M 512 BLOCKSIZE,
  GROUP 2
  ' C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_80L7C375_. JOURNAL"
  SIZE 50 M BLOCKSIZE 512
  -STANDBY LOGFILE
  DATA FILE
  ' C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSTEM. DBF',.
  ' C:\ORACLEXE\APP\ORACLE\ORADATA\XE\UNDOTBS1. DBF',.
  ' C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSAUX. DBF',.
  ' C:\ORACLEXE\APP\ORACLE\ORADATA\XE\USERS. DBF'
  CHARACTER SET AL32UTF8
  ;
  
  I do not have these 2 files... what should I do to work around this situation
  ' C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_80L7C259_. JOURNAL"
  SIZE 50 M 512 BLOCKSIZE,
  GROUP 2
  ' C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_80L7C375_. JOURNAL"
  SIZE 50 M BLOCKSIZE 512
  -STANDBY LOGFILE
  DATA FILE
  
  Published by: zycoz100 on February 27, 2013 22:57

  If you have a backup to cold (closing correctly database) without the redo logs, change this:

  CREATE CONTROLFILE REUSE DATABASE "XE" NORESETLOGS NOARCHIVELOG
  

  TO

  CREATE CONTROLFILE REUSE DATABASE "XE" RESETLOGS NOARCHIVELOG
  

  You need to change the NORESETLOGS RESETLOGS for Oracle to recreate online redo logs.

  Hemant K Collette

• 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

• 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

• SIZE OF THE REDO LOG FILE

  
  Hello

  I got an error message when I add me new group. log files I searched and found the answer on the form. Ago 4 M minimum size of 11 g R2 log file size.

  My question is why a log file size depends on DB_BLOCK_SIZE? This parameter is set to the component structures of memory that create an instance when a log file is an operating system file that depend on the version of the OS not DB_BLOCK_SIZE.

  Thank you.

  
  SQL > alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m;
  alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m
  *
  ERROR on line 1:
  ORA-00336: 2048 blocks the size of the log file is minimum lower than 8192 blocks

  
  SQL > show parameter db_block_size

  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  Whole DB_BLOCK_SIZE 8192
  SQL >

  You are assuming that the redo log block size is the same as the database block size. This is not correct.

  The error indicates that 8192 is the minimum number of blocks of a redo log file. The documentation states that the minimum size is 4 M. For example, you can deduct your redo log block size is 512 bytes.

  Here's some more information about the size of redo log, the documentation block.

  Unlike the database block size, which can always be between 2 K and 32 K, redo log default files to a block size that is equal to the size of physical sector of the disk. Historically, it is usually 512 bytes (512 b).

  Some new large disks offer 4K sizes byte (4K) to increase sector efficiency improved format and ECC capabilities. Most of the Oracle database platforms are able to detect this bigger sector size. The database then automatically creates files redo log with a block size of 4 K of these discs.

• new with OMF online redo log files

  Hi all
  
  I'm using Oracle 11 g 2, I created my DB using Oracle managed (OMF) files.
  
  I wanted to re size my recovery connects so I went in an old redo logs fall and create a new.
  
  That was how my redo logs resembles. It was created by the creation of the DB with OMF format:

  .../app/oradata/ORCL11/onlinelog/o1_mf_1_6pfncw81_.log
  .../app/flash_recovery_area/ORCL11/onlinelog/o1_mf_1_6pfncx5z_.log
  .../app/oradata/ORCL11/onlinelog/o1_mf_2_6pfncxps_.log
  .../app/flash_recovery_area/ORCL11/onlinelog/o1_mf_2_6pfncz1v_.log
  .../app/oradata/ORCL11/onlinelog/o1_mf_3_6pfnczhd_.log
  .../app/flash_recovery_area/ORCL11/onlinelog/o1_mf_3_6pfnd0vw_.log

  using the script I created new below redo logs

  alter database add logfile group 1 (
  '.../app/oradata/ORCL11/onlinelog/redo1.log',  
  '.../app/flash_recovery_area/ORCL11/onlinelog/redo1.log') size 76m reuse;

  .........
  and I added the new redo log group
  

  alter database add logfile group 4 (
  '.../app/oradata/ORCL11/onlinelog/redo4.log',  
  '.../app/flash_recovery_area/ORCL11/onlinelog/redo4.log') size 76m reuse;

  I was not able to create the recovery logs, where is the name of the redo log file: o1_mf_1_6pfncw81_.log, since this is the format OMF.
  
  My question by creating my recovery connects the way does it have an impact? on the archiving of newspapers of recovery? any impact on the database for now, this isn't OMF?
  
  How can I create my redo logs with OMF format?
  
  Kind regards

  try: -.
  alter database add logfile Group 4;

  for example; -.

  SQL> alter database add logfile group 4;
  
  Database altered.
  
  SQL> select member from v$Logfile;
  
  MEMBER
  --------------------------------------------------------------------------------
  /home/u01/app/oracle/oradata/dbtest/redo03.log
  /home/u01/app/oracle/oradata/dbtest/redo02.log
  /home/u01/app/oracle/oradata/dbtest/redo01.log
  /home/u01/app/oracle/flash_recovery_area/DBTEST/onlinelog/o1_mf_4_75nmw33l_.log
  
  SQL> alter database add logfile group 5 size 100m;
  
  Database altered.
  
  SQL> select member from v$logfile;
  
  MEMBER
  --------------------------------------------------------------------------------
  /home/u01/app/oracle/oradata/dbtest/redo03.log
  /home/u01/app/oracle/oradata/dbtest/redo02.log
  /home/u01/app/oracle/oradata/dbtest/redo01.log
  /home/u01/app/oracle/flash_recovery_area/DBTEST/onlinelog/o1_mf_4_75nmw33l_.log
  /home/u01/app/oracle/flash_recovery_area/DBTEST/onlinelog/o1_mf_5_75nmyvjg_.log
  

  Published by: rajeysh on August 28, 2011 20:00

• 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

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