Archiving logs apply frequency in Data Guard

Dear all,

How can we verify/set up the frequency archive newspapers should be applied to the Data Guard?

Version: 10 g 2; OS: Windows 2003 R2 (64-bit).

How we can configure the frequency of archive logs must be applied to the DG?

Erase the question once more what you're expecing, as I understand, it's...

It depends on the Redo genearation / Archive primary & network latency between primary databases & Eve.
There is a configuration, you can change in the primary to put options such as delay , net_timeout and so on.

consult this manual too.
http://download.Oracle.com/docs/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm

Tags: Database

Similar Questions

  • Repeat applies without using Data Guard

    Hello everyone,

    I would like to redo apply to a database of pending. Unfortunately, the DB's standard edition for Data Guard is not an option. Is there documentation on how to achieve something like the roll forward apply without using Data Guard?

    Kind regards
    Frank

    There are a lot of threads on this same forum on this specific topic.
    Please use the search (top right of page), and see the list of threads returned:
    https://forums.Oracle.com/forums/search.jspa?threadID=&q=%2Bstandby+%2Bstandard+%2Bedition&objid=F61&DateRange=all&userid=&NumResults=15

    Nicolas.

  • How do to log into oracle 10g data guard

    I get the error message like "oracle initialization or shutdown in progress"

    Appreciate any help...

    MRP is run the recovery process and LNs is write network-server log.

    Yes, they have done...

  • How to move from Data Guard time really apply (restore) to archive the journal

    Hello

    Standby database configured with broker and application really remake in time; However, I want to change it to archive the journal apply mode without losing the broker configuration. Is this possible? If it is not possible to use the broker to make archive log apply, I can remove the broker and use Data Guard to set up the day before to use the archive log apply?

    Concerning

    Hello;

    Broker automatically allows real-time applies to databases on hold if the standby database has standby redo logs configured.

    Stop repeat applies

    DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-OFF';
    

    Repeat restart applies broker

    DGMGRL> EDIT DATABASE 'PRIMARY' SET STATE='APPLY-ON';
    

    In order to get rid of standby redo logs would be a way. I would like to leave myself alone. Real time assistance to prevent the loss of data.

    Best regards

    mseberg

  • DataGuard archiving log not applied

    Hello

    I met archive log apply errors in the physical standby database. Below are the errors.



    SQL > SELECT SEQUENCE #, FIRST_TIME, NEXT_TIME, APPLIED from V$ ARCHIVED_LOG SEQUENCE ORDER #;

    SEQUENCE # FIRST_TIM NEXT_TIME APP
    ---------- --------- --------- ---
    10 24 AUGUST 11 NO. 24 AUG 11
    10 24 AUGUST 11 NO. 24 AUG 11
    11 AUGUST 24, 11 NO. 24 AUG 11
    12 24 AUGUST 11 NO. 25 AUG 11
    13 25 AUGUST 11 NO. 25 AUG 11
    14-25 AUGUST 11 NO. 25 AUG 11

    6 selected lines.

    SQL > select database_role, open_mode from v$ database;

    DATABASE_ROLE OPEN_MODE
    ---------------- ----------
    FIRST READING WRITING

    SQL > select message from v$ dataguard_status;


    ARCs: Started archiving
    CRAT: Started archiving
    CJACBR: become the "no FAL' ARCH
    CJACBR: become the "no SRL" ARCH
    ARCm: Become the heartbeat ARCH

    Message
    --------------------------------------------------------------------------------
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [1]: assigned to the RFS 3389 process
    RFS [1]: do not use real application clusters
    LGWR: Error 16009 creation archivelog file "DBSOURCE.
    LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [2]: assigned to the RFS 3393 process
    RFS [2]: do not use real application clusters
    FAL [server, ARCo]: error 16009 file creation remote archivelog 'DBSOURCE.

    Message
    --------------------------------------------------------------------------------
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [3]: assigned to the RFS 3397 process
    RFS [3]: do not use real application clusters
    Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [4]: assigned to the RFS 3429 process
    RFS [4]: do not use real application clusters
    Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.

    54 selected lines.


    Of the primary alerts on DB log errors
    Using the default value for the parameter STANDBY_ARCHIVE_DEST as/u01/app/oracle/oradata/DBSOURCE
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [1]: assigned to the RFS 3389 process
    RFS [1]: do not use real application clusters
    Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3389.trc file:
    ORA-16009: destination of the journal archive remote must be a database of the EVE
    Game Aug 25 12:17:10 2011
    Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_lns1_3349.trc file:
    ORA-16009: destination of the journal archive remote must be a database of the EVE
    LGWR: Error 16009 creation archivelog file "DBSOURCE.
    LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
    Game Aug 25 12:17:30 2011
    Again shipping customer logged in as PUBLIC
    -User is valid
    RFS [2]: assigned to the RFS 3393 process
    RFS [2]: do not use real application clusters
    Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3393.trc file:
    ORA-16009: destination of the journal archive remote must be a database of the EVE

    initDBSOURCE.ora params
    DB_NAME = DBSOURCE
    DB_UNIQUE_NAME = DBSOURCE
    LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (DBSOURCE, DBTARGET)'
    LOG_ARCHIVE_DEST_1 =
    "LOCATION = / u01/app/oracle/oradata/DBSOURCE"
    VALID_FOR = (ALL_LOGFILES, ALL_ROLES)
    DB_UNIQUE_NAME = DBSOURCE'
    LOG_ARCHIVE_DEST_2 =
    "SERVICE = DBSOURCE LGWR ASYNC
    VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE)
    DB_UNIQUE_NAME = DBTARGET'
    LOG_ARCHIVE_DEST_STATE_1 = ENABLE
    LOG_ARCHIVE_DEST_STATE_2 = ENABLE
    REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE LOCK
    LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    LOG_ARCHIVE_MAX_PROCESSES = 30



    I have 1 more question. I copied all db files, control files, and archived logs of the remote db DBTARGET but with the standby control file I could mount the db in the remote server but the dbname is always DBSOURCE instead of DBTARGET.

    I tried running NEST to change on the site of relief the dbname but it errored out with
    Copyright (c) 1982, 2007, Oracle. All rights reserved.

    Connected to database DBSOURCE (DBID = 977273159)

    NEST-00131: control file is not current


    Change of database name failed during validation - database is intact.

    Could if apply the newspaper ceased due to the DBNAME is the same on the eve of primary and physical please help

    Edited by: 880215 August 25, 2011 10:02
    dbname is still DBSOURCE instead of DBTARGET
    

    The database must be DBSOURCE on both. It's the same data in two different roles, role PRINCIPAL and ROLE of the day BEFORE.

    Oracle, said by the DB_UNIQUE_NAME parameter.

    What I have is copy the control file before on the basis of pending data down and then copy and rename the control file that are there.

    Does make sense?

    I have some notes here if it helps:

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

    Best regards

    mseberg

  • Data Guard archive political deletion log

    Hi all

    I configured the data guard with 2 bases Eve in oracle 11g.

    I want to use rman to delete archives on all servers.

    I have configured no FRA, no recovery catalog.

    My question is:

    If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.

    I say delete until the different sequences # on primary and standby cause problems for synchronization?

    Thank you

    So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

    She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

    Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

    Last Archive generated on primary:

    SYS@oraprim > select max(sequence#) from v$ archived_log;

    MAX(SEQUENCE#)

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

    114

    Last check-in applied in mode ensures:

    SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

    MAX(SEQUENCE#)

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

    109

    Delete policy set to NONE on primary:

    RMAN > show archivelog deletion policy;

    using the control file of the target instead of recovery catalog database

    RMAN settings for database with db_unique_name ORAPRIM are:

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

    RMAN > delete archivelog until 'sysdate;

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 60 type of device = DISK

    List copies of newspapers archived to database with db_unique_name ORAPRIM

    =====================================================================

    Thrd Seq S key low time

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

    110-1-214 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

    216-1-111 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

    217-1-112 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

    113. OF 1 219 A 13 JANUARY 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

    222 1 114 A JANUARY 13, 16

    Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

    You sure you want to delete the items above (enter YES or NO)? NO.

    It is the removal of primary archives that have not yet been applied on the eve.

    Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

    RMAN > show archivelog deletion policy;

    RMAN settings for database with db_unique_name ORAPRIM are:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

    RMAN > delete archivelog until 'sysdate;

    output channel: ORA_DISK_1

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 60 type of device = DISK

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

    RMAN-08120: WARNING: log archived not deleted, not yet applied watch

    Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

    It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

    Hope that gives you a clear picture of how it works.

    -Jonathan Rolland

  • Data Guard - RMAN removing archive log

    Hello

    I ' v DataGuard with physical standby.

    I do a backup only on the primaries. Both sites have ther separate backup systems.

    I ' v FRA and configured archivelog deletion with RMAN configuration:

    on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

    standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

    It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

    1 should I reconfigure RMAN?

    change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

    change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

    2. make full backup

    Hello

    1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

    section: "all archived Redo Log deletion policy."

    Document provides the best algorithm to analysis of work

    You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.


    If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

    The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

    2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

    It will be useful.

    -Thank you

    Pavan Kumar N

  • Purge logs archiving on things primary and Standby and for Data Guard RMAN


    Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

    Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

    Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

    Q1. The above only removes logs archiving to the primary or primary and Standby?

    Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

    I also saw

    CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

    Q3. That what precedes, and once again it is something that you re primary side?

    I saw the following advice in the manual of Concepts of data protection & Admin

    Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

    Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

    Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

    Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

    Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

    Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

    Any idea greatly appreciated,

    Jim

    The above only removes logs archiving to the primary or primary and Standby?

    When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

    including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

    You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

    If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

    Its a configuration, it will not erase by itself.

    If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

    1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

    2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

    If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

    Great example:

    http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

    All Oracle is worth a peek here:

    http://emrebaransel.blogspot.com/

    That what precedes, and once again it is something that you re primary side?

    I would never use it. I always had it put it this way:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

    I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

    Why would I want my primary ro connect to the RMAN Repository?

    Because if you break down, you want to be able to backup there, too.

    Also if it remains idle for awhile you want.

    Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

    Always use a database of catalog RMAN with Data Guard.

    If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

    Same answer as 5, use a catalog database.

    Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

    Same answer as 5, use a catalog database.

    What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

    I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

    Best regards

    mseberg

    Summary

    Always use a database with RMAN catalog.

    Always use CRF with RMAN.

    Always set the deletion «To APPLY ON ALL STANDBY» policy

    DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

    Post edited by: mseberg

  • Can a weird question we use Data Guard to apply the bidirectional log?

    Hi I have a question about Data Guard, can we use Data Guard to apply the bidirectional log? I mean keeping the two of them primary and standby to Active status (read write Mode).

    Maybe my question seems silly, but I just wanted to check on it.

    Thank you

    Laughing out loud

    That Golden Gate or water courses that will work in two ways. One or the other. Puts additional requirements on the hardware is the downside.

    Data Guard does not do that.

  • Reg apply log archiving after the transfer of data files

    Hi all

    That I reinstalled the main server of the D-Drive E-reader data files using the command line.
    C:\>Move <source_path> <destination_path>
    The redo logs for the move operation will apply on the eve of the database?
    In addition, what happens if the data files are moved manually in the primary database (i.e. without using the command prompt)?


    Thank you
    Madhu

    See this doc. Keyword search Rename a data file in the primary database

    http://docs.Oracle.com/CD/B28359_01/server.111/b28294/manage_ps.htm#i1034172

    Also, you need to update primary database controlfile if some moment of the file made...

    And also close this thread

    Reg apply log archiving after the transfer of data files

    As it would help in the forum of maintenance to clean.

  • Archive log list does not sequence of current journal is awaiting data base

    Hi all

    So I tried waiting for database physical installation in my local vm.

    I apparently completed the Setup, but I am facing a problem which I cannot understand.

    OS:-Linux 6.4

    Oracle version: 12.1.0.2.0

    primary data: ORA12C

    backup database: ORASTD

    Primary database: -.

    SYS@ORA12C > list of archive logs;

    Database log mode Archive Mode

    Active AutoArchive

    Archives/u01/app/oracle/fast_recovery_area of destination

    More old sequence of journal online 14

    Log sequence archive 16

    Current log sequence 16

    SYS@ORA12C > select name, database_role, controlfile_type from v$ database;

    NAME DATABASE_ROLE CONTROL

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

    ORA12C CURRENT PRIMARY

    SYS@ORA12C > select the sequence #, first_time, next_time, applied from v$ archived_log;

    FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

    4 15 APRIL 15 APRIL 16 15 NO.

    4 15 APRIL 15 APRIL 16, 15 YES

    5 16 APRIL 15 APRIL 16 15 NO.

    5 16 APRIL 15 APRIL 16, 15 YES

    6 16 APRIL 15 APRIL 16 15 NO.

    6 16 APRIL 15 APRIL 16, 15 YES

    7 16 APRIL 15 APRIL 16 15 NO.

    7 16 APRIL 15 APRIL 16, 15 YES

    8 16 APRIL 15 APRIL 16 15 NO.

    8 16 APRIL 15 APRIL 16, 15 YES

    9 16 APRIL 15 APRIL 16 15 NO.

    FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

    9-16 APRIL 15 APRIL 16, 15 YES

    10 16 APRIL 15 APRIL 16 15 NO.

    10-16 APRIL 15 APRIL 16, 15 YES

    11 16 APRIL 15 APRIL 16 15 NO.

    12 16 APRIL 15 APRIL 16 15 NO.

    13 16 APRIL 15 APRIL 16 15 NO.

    11-16 APRIL 15 APRIL 16, 15 YES

    12-16 APRIL 15 APRIL 16, 15 YES

    13-16 APRIL 15 APRIL 16, 15 YES

    14 16 APRIL 15 APRIL 16 15 NO.

    15 16 APRIL 15 APRIL 16 15 NO.

    FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

    15 16 APRIL 15 APRIL 16 15 NO.

    14-16 APRIL 15 APRIL 16, 15 YES

    Waiting for the database: -.

    Select the sequence #, first_time, next_time, applied from v$ archived_log;

    FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

    4 15 APRIL 15 APRIL 16, 15 YES

    5 16 APRIL 15 APRIL 16, 15 YES

    6 16 APRIL 15 APRIL 16, 15 YES

    7 16 APRIL 15 APRIL 16, 15 YES

    8 16 APRIL 15 APRIL 16, 15 YES

    9-16 APRIL 15 APRIL 16, 15 YES

    10-16 APRIL 15 APRIL 16, 15 YES

    11-16 APRIL 15 APRIL 16, 15 YES

    12-16 APRIL 15 APRIL 16, 15 YES

    13-16 APRIL 15 APRIL 16, 15 YES

    15 16 APRIL 15 16 APRIL 15 IN-MEMORY

    FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

    14-16 APRIL 15 APRIL 16, 15 YES

    SQL > select name, database_role, controlfile_type from v$ database;

    NAME DATABASE_ROLE CONTROL

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

    PHYSICAL STANDBY ORA12C STANDBY

    SQL > archive logs list;

    Database log mode Archive Mode

    Active AutoArchive

    Archives/u01/app/oracle/fast_recovery_area of destination

    More old sequence of journal online 0

    Log sequence to archive 0

    Current log sequence 0

    Now, here's my question is why the sequence of current newspapers shows 0. I tested the datas

    database primary eve happens again. I'm totally out of index.

    I tried to find it on google but nothing could help me until now.

    Any kind of help would be very appreciated.

    Thank you

    Soumya

    Hello

    I am also testing in Data Guard 12.1 configurations.

    Oracle support response is "it seems therefore that this information be removed.

    So is the best way to check on the database pending:

    SQL > select thread #, max(sequence#) ' last day before Seq received. "

    v $ archived_log val, v$ database vdb

    where val.resetlogs_change # = vdb.resetlogs_change #.

    Group thread # order by 1;

    SQL > select thread #, max(sequence#) ' last day before Seq applied.

    v $ archived_log val, v$ database vdb

    where val.resetlogs_change # = vdb.resetlogs_change #.

    and val.applied in ('YES', "IN-MEMORY")

    Group thread # order by 1;

    concerning

  • The archive logs shipped but more old logs do not applied...

    Environment:

    Oracle on Solaris 11.2.0.3 10.5

    The Data Guard environment working fine for 6 months.

    I recently had problems with disk space on the day before and had to copy some files from newspapers of the archives to a mount point different that had been shipped to the waiting, but not yet applied because I had to cancel the paper application process.

    After having cleared the space problem and start log shipping and return application log on (change database recovery managed to sleep...) I have the new logs shipped but my watch is a bunch of log files behind. I can see it in the V$ ARCHIVED_LOG on intelligence, where the last seq # applied is 8083 in my case and the more current seq # is currently more than 8200.

    I have all the archives always connects in 'other' the mount point and can move back the directory the correct archive according to needs.

    Since the next file that the application requires is seq # 8084, I moved this file in the/arch directory awaits the day before 'see' and apply it. No luck.

    By searching in the alert log just before after execution of the 'alter database recover managed standby database disconnect;' I see the following:
    Media Recovery Waiting for thread 1 sequence 8084
    and also:
    Fetching gap sequence in thread 1, gap sequence 8084-8084
    and just below that:
    FAL[client]: Error fetching gap sequence, no FAL server specified
    I thought I read in the docs that the FAL_SERVER and the FAL_CLIENT are no longer needed. (?)

    I also found a CKPT script that lists information about DG Environment. For the primary side to hang on, but the day before one produces this output:
    NAME                           DISPLAY_VALUE
    ------------------------------ ------------------------------
    db_file_name_convert           /u01/oradata/APSMDMP1, /u01/or
                                   adata/APSMDMP1, /u02/oradata/A
                                   PSMDMP1, /u02/oradata/APSMDMP1
                                   , /u03/oradata/APSMDMP1, /u03/
                                   oradata/APSMDMP1, /u04/oradata
                                   /APSMDMP1, /u04/oradata/APSMDM
                                   P1
    
    db_name                        APSMDMP1
    db_unique_name                 APSMDMP1STBY
    dg_broker_config_file1         /u01/app/oracle/product/11203/
                                   db_2/dbs/dr1APSMDMP1STBY.dat
    
    dg_broker_config_file2         /u01/app/oracle/product/11203/
                                   db_2/dbs/dr2APSMDMP1STBY.dat
    
    dg_broker_start                FALSE
    fal_client
    fal_server
    local_listener
    log_archive_config             DG_CONFIG=(APSMDMP1,APSMDMP1ST
                                   BY)
    
    log_archive_dest_2             SERVICE=APSMDMP1 ASYNC VALID_F
                                   OR=(ONLINE_LOGFILES,PRIMARY_RO
                                   LE) DB_UNIQUE_NAME=APSMDMP1 MA
                                   X_CONNECTIONS=2
    
    log_archive_dest_state_2       ENABLE
    log_archive_max_processes      4
    log_file_name_convert          /u01/oradata/APSMDMP1, /u01/or
                                   adata/APSMDMP1
    
    remote_login_passwordfile      EXCLUSIVE
    standby_archive_dest           ?/dbs/arch
    standby_file_management        AUTO
    
    NAME       DB_UNIQUE_NAME                 PROTECTION_MODE DATABASE_R OPEN_MODE
    ---------- ------------------------------ --------------- ---------- --------------------
    APSMDMP1   APSMDMP1STBY                   MAXIMUM PERFORM PHYSICAL S READ ONLY WITH APPLY
                                              ANCE            TANDBY
    
    
       THREAD# MAX(SEQUENCE#)
    ---------- --------------
             1           8083
    
    PROCESS   STATUS          THREAD#  SEQUENCE#
    --------- ------------ ---------- ----------
    ARCH      CLOSING               1       7585
    ARCH      CLOSING               1       7588
    ARCH      CLOSING               1       6726
    ARCH      CLOSING               1       7581
    RFS       RECEIVING             1       8462
    MRP0      WAIT_FOR_GAP          1       8084
    RFS       IDLE                  0          0
    
    NAME                           VALUE      UNIT                           TIME_COMPUTED                  DATUM_TIME
    ------------------------------ ---------- ------------------------------ ------------------------------ ------------------------------
    transport lag                  +00 00:01: day(2) to second(0) interval   08/16/2012 13:24:04            08/16/2012 13:23:35
                                   59
    
    apply lag                      +01 23:08: day(2) to second(0) interval   08/16/2012 13:24:04            08/16/2012 13:23:35
                                   43
    
    apply finish time              +00 00:17: day(2) to second(3) interval   08/16/2012 13:24:04
                                   21.072
    
    estimated startup time         15         second                         08/16/2012 13:24:04
    
    NAME                                                            Size MB    Used MB
    ------------------------------------------------------------ ---------- ----------
                                                                          0          0
    I do not use a fast recovery area.

    What should I do to get the old logs to check-in begins to apply again?

    The alert log says something about "Adding value to the media", but I don't know why I would need that since I have the log files itself.

    Any help is appreciated.

    Also, I spend a significant amount of time to read through this forum and many articles on the web but couldn't find exactly the solution I was looking for.

    Thank you very much!!

    -gary

    Try to save the log file

    alter database register logfile 'full path for the 8074 sequence.

    and check select message from v$ dataguard_status;

  • Removal of RMAN, Data Guard, and Archives journal

    Our DG Environment running Oracle 11 g R2
    We have a 3 node DG Environment with
    A primary being
    B and C being Active Data Guard Standby
    Backups are taken out of B and go directly to tape.
    Standby Redo Logs and fast recovery area are used



    Holding the recommendation of "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
    RMAN primary control ('A')
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING

    RMAN standby ("B") where the backup is performed
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY

    RMAN set the other Standby ("C")
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED PENDING

    How can we know what newspaper Archives are eligible to be removed from 'A' and 'C '?
    When remove it takes place?
    How can say us when archiving logs are deleted from the 'A' and 'C '?

    Dear user10260925,

    The documentation that you read is reliable but not enough.

    The Oracle can handle the archivelog directory and know that you are eligible for deletion. Stuff you posted here was derived from the books online and is supported and can be used when the Oracle knows and manages the archivelogs. This is simply called the flash recovery area. Please read the FRA at this very moment.

    Under the personal component normal circumstances in the industry use a few scripts to achieve on backup archivelog deletion.

    Here's a useful example to you;

    # Remove old archivelogs
    ######################################
    00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    ######################################
    
    vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    export ORACLE_SID=optstby
    export ORACLE_HOME=/oracle/product/10.2.0/db_1
    cd /db/optima/archive/OPTPROD/archivelog
    
    /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
    grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
    chmod 755 delete_applied_redo_logs_1.sh
    sh delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs.lst
    
    vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
    vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
    set echo off
    set heading off
    spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
    select 'rm -f ' || name from v$archived_log where applied = 'YES';
    spool off
    exit
    vals3:/db/optima/archive/OPTPROD/archivelog#
    

    Hope that helps.

    Ogan

  • Archive Data Guard and Flashback

    Hello

    I have a DB 11.2.0.1 with a database of pending.
    If I put a few tables to be in the flashback data archive, (support for FDA tables) will be copied to a db as well sleep?

    concerning

    Hello;

    I hesitate to answer because you don't seem to close your old questions or give points to those who help. But I also believe in giving the benefit of the doubt.

    If the FIU is configured on your watch then the answer is Yes.

    While this is not a requirement to use I would always use FRA with Data Guard.

    db_recovery_file_dest = ' / u01/app/oracle/flash_recovery_area.

    The following are some sample parameter values that might be used to configure a physical standby database to archive its standby redo log to the fast recovery area:
    
    LOG_ARCHIVE_DEST_2 = 'LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILE,STANDBY_ROLE)' LOG_ARCHIVE_DEST_STATE_2=ENABLE
    

    Source

    DataGuard of Concepts and Administration 11g Release 2 (11.2) E10700-02

    With RMAN efficiently in an environment of Dataguard. [848716.1 ID]

    Best regards

    mseberg

    Published by: mseberg on December 1, 2012 13:53

  • Restore the size of the log in Data Guard configurations

    DB version: 11.2
    Platform: Solaris 10

    We have currently a DB production which is not Dataguard.It has a load of joint working: some processing OLTP and batch.
    Its size of redo log is * 100 * MB.

    We will create a database with the requirement very similair but this DB will have primary standby (Data guard) and real time applies.

    To adapt to the requirements of dataguard, we should reduce the size of the recovery online newspapers? That is to say. Transport of small pieces of roll forward is better than carrying more. Right?

    Hello;

    If you use "real-time applies" the key is not the size so that the standby Redo Logs.

    In most cases, 100 MB is fine. Newspapers to sleep again must be the same size that it again.

    With 'real time applies' SRL act as a buffer.

    Unless you have a real problem with the size of do it again I would not change it.

    An excellent source of information on this is 'Restore the Services of Transport' in ' Data Guard Concepts and Administration 11 g Release 2 (11.2) "E10700-02".

    If you believe that your logs are too big departure "Troubleshooting performance problems with the database and base/MFG MRP [ID 100964.1]"

    Best regards

    mseberg

    Published by: mseberg on May 31, 2012 11:33

Maybe you are looking for