Redo Logs

Running Oracle 11 g r2.

I just want to confirm if Oracle recommends at least 3 redo logs to run the database?

If so, how can I create the third (and fourth) redo logs (I believe the default is 2 recovery logs)?

Thank you.

Scott

Running Oracle 11 g r2.

I just want to confirm if Oracle recommends at least 3 redo logs to run the database?

Post a link to the source of this information.

If so, how can I create the third (and fourth) redo logs (I believe the default is 2 recovery logs)?

You CAN'T do that. Do NOT modify Oracle based on your personal beliefs. You must use FACTS.

What you believe has NOTHING to do with the reality of what can be your real system. You can only change your system.

So first, you must determine how many newspaper groups and members your system log has already.

The detail on the REDO log and groups members that exist on your system. The Oracle documentation at the address provided already has examples on how to do it.

Tags: Database

Similar Questions

  • 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

  • Loss/Corruption of a Redo Log multiplex group member

    Grid infrastructure: 11.2.0.4

    DB version: 11.2.0.4

    OS: RHEL 6.5

    All recovery logs are multiplexed IE once. Copy of a mirror

    I created a document on how to cope with the loss of a member of a group of Redo Log multiplex. It applies to DBs in ASM or Linux Filesystem.

    If a member of a multiplex redo logs group is lost/damaged is in State assets or CURRENT (v$ log.status), will be the following work?

    Assuming that the DB would not crash (well that's the whole point of multiplexing)

    Step 1. Switch redo log group and bring him to the INACTIVE State IE. LGWR is not written for her now


    Step 2. Remove the Member lost/damaged.

    ALTER DATABASE DROP LOGFILE MEMBER "+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203";

    Apparently, this command does not actually remove the log file at the level of the ASM/OS; It updates only the control file

    Step 3. If it is a corrupt then log file physically remove the damaged location ASM/OS file

    Step 4. I hope the below will create a mirror copy of the survivor

    ALTER DATABASE ADD LOGFILE MEMBER '+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203' to GROUP 3.

    The above steps won't work?

    There is no point in writing in the document if you do not actually test what you write

    It seems that you are working with Oracle managed files. In this case:

    You will find that your "apparently" in step 2 is not correct, and that your step 4 will throw an ora-01276.

  • Will be online Redo Logs to sleep never used?

    Version: 11 GR 2

    OS: Oracle Linux 6.5

    Pending a physical DB, newspapers online redo will be ever written because the author of newspaper on the standby site will be inactive. Right?

    In the DB in waiting, only forward Redo logs will be written to by RFS. Right?

    Pending a physical DB, newspapers online redo will be ever written because the author of newspaper on the standby site will be inactive. Right?

    ORL will be used when the database starts to behave like a primary database and LGWR writes the data to the newspaper for the ORL buffer again.

    They are not used while the database behaves like a physical standby.

    In the DB in waiting, only forward Redo logs will be written to by RFS. Right?

    Yes, the process RFS writes that data to the standby redo redo logs on the standby database.

    Just for your reference https://docs.oracle.com/cd/B19306_01/server.102/b14239/log_apply.htm#i1022881

    HTH

    -Jonathan Rolland

  • Redo log size of the defect of EBS

    Hi all

    EBS R12.2.4

    11 GR 2

    Rhel6.5

    I noticed that the installation by dΘfaut of EBS has only two 1 GB size redo log groups.

    Is this acceptable to perform better?

    Your comment is very much appreciated.

    Thank you very much

    JC

    Protection for the primary database in three ways:

    Maximum availability: Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If no location intelligence is available, it in the same way as the maximum performance mode until a standby is available again.
    Maximum performance: Transactions on the validation of primary as soon as redo information has been written for the online redo log. Transfer of information to roll forward to the standby server is asynchronous, so it has no impact on the performance of the primary.
    Maximum protection: the Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If the standby not suitable location is available, the primary database stops.

    By default, a newly created Eve, the primary database is in maximum performance mode.

    I suggest to use the maximum performance with delay mode in the application of 15 minutes. You can drop the idea of delay if you are not comfortable with data loss

    concerning

    Pravin

  • 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

  • Recreate the Member lost/damaged redo log in a group

    DB version: 11.2.0.4

    OS: Oracle Linux 6.5

    In this particular PB we have multiplexes recovery logs (2 members from each group of redo).

    If one member of a group of Redo log is corrupted then, regardless of whether the Member belonged to the Group that is CURRENT, ACTIVE or INACTIVE, can we just let GO and CREATE the file journal lost this group member by following the steps below?

    -Find the corrupted Member

    SELECT GROUP #, STATUS, MEMBER OF V$ LOGFILE WHERE STATUS = 'INVALID ';

    1 back UP the DB

    2. CHANGE THE SYSTEM CHECKPOINT;

    3 ALTER DATABASE CLEAR LOGFILE GROUP 3;  - , This step should not be executed. Right?

    4. ALTER DATABASE DROP LOGFILE MEMBER ' / oracle/oradata/wms/redo02.log';

    (Apparently, this removes not the logfile at the OS level, only the control file is updated in the DB)

    5 ALTER DATABASE ADD LOGFILE MEMBER ' / oracle/oradata/wms/redo02b.log' to GROUP 3.

    When I googled for steps, I found the table below in the official documentation of the Oracle. This table is applicable only if the ENTIRE REDO LOG disappeared.

    http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/osadvsce.htm#CACFJDBG

    I want just the steps if only 1 member of a multiplex group is lost/damaged.

    3. ALTER DATABASE CLEAR LOGFILE GROUP 3;  -This step should not be executed. Right?

    Yes. It's true. You can refer to the section 'Recovery after losing a member of the a multiplex online Redo Log group' under recovery after the loss of online redo log files: scenarios

    HTH

    -Jonathan Rolland

  • 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

  • Will the DB down if INACTIVE redo log group is deleted?

    Platform: Oracle Linux 6.5

    DB version: 11.2

    If I delete one or all members of a Redo Log group online that is IDLE, manually (using the rm command) will be the DB crash?

    Instead of everybody speculating, why not just run a test?

    Oracle 11.2.0.1, Enterprise Edition, 64-bit on OL 5, running in archivelog mode

    SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    1 YES INACTIVE
 2    2 YES INACTIVE
 3    3 NO  CURRENT
3 rows selected.
SQL> --
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> select * from v$logfile;
    GROUP# STATUS  TYPE MEMBER  IS_
---------- ------- ------- ------------------------------ ---
 3 ONLINE /oradata/tulsa/redo03.rdo  NO
 2 ONLINE /oradata/tulsa/redo02.rdo  NO
 1 ONLINE /oradata/tulsa/redo01.rdo  NO
3 rows selected.
SQL>
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 NO  ACTIVE
3 rows selected.

    Group 2 is inactive, so delete the

    SQL> !rm /oradata/tulsa/redo02.rdo
SQL> !ls -l /oradata/tulsa/redo02.rdo
ls: /oradata/tulsa/redo02.rdo: No such file or directory

    And continue the activity of db.  Keep an eye on the #2 group

    SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  ACTIVE
 2    5 NO  CURRENT
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 YES INACTIVE
 2    5 NO  ACTIVE
 3    6 NO  CURRENT
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    7 NO  CURRENT
 2    5 NO  ACTIVE
 3    6 NO  ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;

    At this point, the SWTICH LOGFILE command has been attached, and in the alerts log, we see this:

    CJQ0 started with pid=26, OS id=4817
Sat Sep 19 10:48:11 2015
Thread 1 advanced to log sequence 4 (LGWR switch)
  Current log# 1 seq# 4 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:11 2015
Archived Log entry 1 added for thread 1 sequence 3 ID 0xdaf1e381 dest 1:
Sat Sep 19 10:48:44 2015
Thread 1 advanced to log sequence 5 (LGWR switch)
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Sat Sep 19 10:48:44 2015
Archived Log entry 2 added for thread 1 sequence 4 ID 0xdaf1e381 dest 1:
Thread 1 cannot allocate new log, sequence 6
Checkpoint not complete
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Thread 1 advanced to log sequence 6 (LGWR switch)
  Current log# 3 seq# 6 mem# 0: /oradata/tulsa/redo03.rdo
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Thread 1 advanced to log sequence 7 (LGWR switch)
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance tulsa - Archival Error
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_4864.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Checker run found 2 new persistent data failures
ORACLE Instance tulsa - Can not allocate log, archival required
Thread 1 cannot allocate new log, sequence 8
All online logs needed archiving
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_5163.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

  • How to create Redo Log as a good way to avoid the problem of performance

    Hi Experts,

    I work in the following environment.

    OS - Windows server 2012

    version - 11.2.0.1.0

    Server: production server

    1 to 10 of each month, we have huge process. Like many DML and ddl involve.

    I've implemented the RMAN also.

    My Alerts log entry is as below,

    Kills Sep 08 17:05:34 2015

    Thread 1 cannot allot of new newspapers, 88278 sequence

    Private stream flush is not complete

    Currently journal # 1, seq # 88277 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL

    Thread 1 Advanced to record the sequence 88278 (switch LGWR)

    Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Kills Sep 08 17:05:38 2015

    Archived journal 81073 extra for each sequence 1 88277 0x38b3fdf6 dest ID thread entry 1:

    Kills Sep 08 17:05:52 2015

    Thread 1 cannot allot of new newspapers, sequence 88279

    Checkpoint is not complete

    Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Thread 1 Advanced to record the sequence 88279 (switch LGWR)

    Currently Journal # 3 seq # 88279 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL

    Kills Sep 08 17:05:58 2015

    Archived journal 81074 extra for each sequence 1 88278 0x38b3fdf6 dest ID thread entry 1:

    Kills Sep 08 17:06:16 2015

    Thread 1 cannot allot of new newspapers, sequence 88280

    Checkpoint is not complete

    When I check in the internet I found a few points and need clarity also by the following.

    -It is recommended that this switch Redo log 5 times maximum per hour, but I have this time of maximum peak about 100 redo log changes occur.

    -It is recommended to have the large size of the Redo log. But I have 3 Group of redo and each size is 50 MB by default.

    -My group of Redo log not multiplexed and it by default with each group have only a single Member

    Group 1 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL

    Group 2 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Group 3 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL

    And advised by experts with add that again group will give more performance in the other location. Is it mean that I need to add the Redo log as a different group, player or Redo Log itself I need to replace the other location.

    Say in the end, My Live server works with the location and size of restore default. I'm trying to create a better way and get all confused

    How to do it perfectly.

    Experts, please share your comments to my environment to log redo instance as better through your comment or recommended weblink based on my above needs, or a document.

    Thanks in advance, if you need more information to help me, then ask me, I'll share you.

    Hello

    You can't resize an existing redo log group.

    You will need to create 3 new redo log groups and drop old log redo (with 200 MB size) groups.

    Here you can find a good explanation: DBA for Oracle tips Archives

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

  • in oracle redo-log, QMD means fast Multi delete, but what do I do to generate such redo log?

    to QMI(Quick multi-insert), I can run the following SQL to generate the QMI redo log:

    Insert into t1 select * from t2;

    or use forall sentence to achieve this goal.

    but I do not know how to generate log redo QMD, can someone help me?

    Hello

    When I restore after an insert... Select I get the following type of repeat folder:

    PROGRESS RECORD roll - Threading: 1 RBA: LEN 0x000e78.00005fb5.00cc: 0x00e8 VLD: 0x01 CON_UID: 0

    RCS: 0x0000.0b8cc83a SUBSCN: 1 08/12/2015 23:07:08

    CHANGE CON_ID:0 #1 TYP:0 CLS:1 AFN: 6 x 0000 .0b8cc837 SEQ:4 OP:11.12 ENC:0 SCN:0 OBJ:116277 DBA:0x018264c2 RBL: 0 FLG:0 X 0000

    KTB Redo

    OP: worm 0 x 02: 0 x 01

    compat bit: 4 (post-11) stuffing: 1

    OP: C uba: 0x01001a86.0d68.0c

    Op KDO code: line QMD disabled dependencies

    xType: XR flags: 0 x 00000000 bdba: hdba 0x018264c2: 0 x 01825972

    itli: 1 ispac: 0 maxfr: 4858

    Tabn: 0 lock: nrow equals 0: 16

    location [0]: 54

    location [1]: 55

    slot [2]: 56

    slot [3]: 57

    Housing [4]: 58

    Housing [5]: 59

    Housing [6]: 60

    slot [7]: 61

    slot [8]: 62

    Housing [9]: 63

    slot [10]: 64

    slot [11]: 65

    Housing [12]: 66

    slot [13]: 67

    slot [14]: 68

    slot [15]: 69

    CHANGE CON_ID:0 #2 TYP:0 CLS:24 AFN: 4 x 0000 .0b8cc83a SEQ:13 OP:5.6 ENC:0 SCN:0 OBJ:4294967295 DBA:0x01001a86 RBL: 0 FLG:0 X 0000

    ktubu again: am: rci 0: 12 opc: 11.1 objn: 116277 objd: tsn 116277: 4

    Cancel type: Regular cancel cancel type: user cancellation made last buffer split: No.

    Undo tablespace: No.

    0x00000000

    ktuxvoff: 0x17cc ktuxvflg: 0x0002

    Kind regards

    Franck.

    PS: this is the replication product that I think?

  • 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

  • ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

    Hello

    I am getting below error when executing the activities of flashback. Currently we have backups, so when I tried the command flashback in RMAN my question solved.

    But if I want to do the same thing using SQLPLUS what steps should I take?

    ERROR:

    ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

    ORA-38762: redo logs needed for SNA to SNA 20062842936 20062842926

    ORA-38761: redo log sequence 4 in thread 2, 65 incarnation cannot

    consulted

    DATABASE:11.2.0.3.0 (UAT)

    RMAN will automatically restore logs archived redo required for the operation of blowback when they are not present on the drive, while (as meyssoun said) when using sqlplus required archived redo logs must be available on the disc.

    Concerning

    AJ

  • 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

Maybe you are looking for