Dataguard logs not applied

Hi,
We have dataguard on Oracle 10g. The logs are shipped from primary to physical stand by but when I look at "Last Applied Log" under EM on the primary db, I see 0. The logs are shipping but not applied to physical stand by.
I restarted the standby to mount stage.
I can tnsping both the database from other servers
***** on primary *****
SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_1';
NAME
VALUE
log_archive_dest_state_1
enable
SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_2';
NAME
VALUE
log_archive_dest_state_2
ENABLE
SELECT name, value FROM gv$parameter WHERE name = 'standby_archive_dest';
NAME
VALUE
standby_archive_dest
select status, error from v$archive_dest where dest_id=2;
STATUS ERROR
VALID
select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
select protection_mode, protection_level, database_role from v$database;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PRIMARY
SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
MAX(SEQUENCE#) THREAD#
4483 1
SELECT dest_id, valid_type, valid_role, valid_now FROM gv$archive_dest;
DEST_ID VALID_TYPE VALID_ROLE VALID_NOW
1 ONLINE_LOGFILE ALL_ROLES YES
2 ONLINE_LOGFILE PRIMARY_ROLE YES
***** on physical stand by *****
select protection_mode, protection_level, database_role from v$database;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PHYSICAL STANDBY
SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
MAX(SEQUENCE#) THREAD#
4483 1
Can anyone advise what can I check and how can I get the logs to apply on the standy by. The stand by is in mount stage. Thanks

The alert log for primary does not show any errors:
LNS: Standby redo logfile selected for thread 1 sequence 4520 for destination LOG_ARCHIVE_DEST_2
This is in the alert log for standby
Primary database is in MAXIMUM PERFORMANCE mode
RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
On standby I have the MRP process running:
$ ps -ef|grep mrp
oracle 10957 1 0 15:26:48 ? 0:01 ora_mrp0_prd1
SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2 ;
RECOVERY_MODE
MANAGED REAL TIME APPLY
This is from v$dataguard_status
Remote File Server Warning 0 167 0 NO 20-DEC-07
RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
should I try this as first suggested ?
alter database recover managed standby database parallel 2 using current logfile disconnect;

Similar Messages

  • My Active dataguard is not applying archives.

    Dears,
    Following is my setup
    =====================
    Primary:
    prod on RAC with 2 nodes
    Database : Oracle 11.2.0.3
    OS OEL 5.7
    storage : ASM
    +DATADG
    +FLASHDG
    Standby:
    sync on single node
    Database : Oracle 11.2.0.3
    storage : ASM
    +DATADG
    +FLASHDG
    I've configured Active dataguard successfully and was able to apply archivelogs successfully instantly.
    Archive log locations are +FLASHDG/prod/ARCHIVELOG/ AND /u02/arch  --- on primary
    Archive log locations are +FLASHDG/stby/ARCHIVELOG/ AND /u02/arch  --- on standby
    On Standby
    ===========
    SQL> select 'Using Active Data Guard' ADG from v$managed_standby m,v$database d where m.process like 'MRP%' ;
    ADG
    Using Active Data Guard
    SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
    OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
    READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
    SQL>
    Upto now everything is ok, means same data is sync on primary and standby. As my archive location was getting full, i've used this SQL query to clean them
    SELECT 'alter diskgroup '||dg.name||' drop file
    ''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
    FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
    WHERE al.file_number = fi.file_number(+)
    AND al.group_number = dg.group_number
    AND fi.type = 'ARCHIVELOG'
    START WITH alias_index = 0
    CONNECT BY PRIOR al.reference_index = al.parent_index;
    SELECT 'alter diskgroup '||dg.name||' drop file
    ''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
    FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
    WHERE al.file_number = fi.file_number(+)
    AND al.group_number = dg.group_number
    AND fi.type = 'BACKUPSET'
    START WITH alias_index = 0
    CONNECT BY PRIOR al.reference_index = al.parent_index;
    In order to delete ARCHIVE logs which are stored in ASM FLASHDG, which will have a type of "ARCHIVELOG" and "BACKUPSET" i've used this above two queries.
    After performing this steps , my Active dataguard is not applying archives.
    On the primary server, check the latest archived redo log
    SELECT sequence#, first_time, next_time
    FROM v$archived_log
    ORDER BY sequence#;
    2809 16-APR-13 16-APR-13
    2809 16-APR-13 16-APR-13
    2809 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2810 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2811 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2812 16-APR-13 16-APR-13
    2813 16-APR-13 16-APR-13
    2813 16-APR-13 16-APR-13
    2814 16-APR-13 16-APR-13
    2814 16-APR-13 16-APR-13
    2815 16-APR-13 16-APR-13
    2815 16-APR-13 16-APR-13
    2816 16-APR-13 16-APR-13
    2816 16-APR-13 16-APR-13
    2817 16-APR-13 16-APR-13
    2817 16-APR-13 16-APR-13
    2818 16-APR-13 16-APR-13
    2818 16-APR-13 16-APR-13
    2819 16-APR-13 16-APR-13
    2819 16-APR-13 16-APR-13
    2820 16-APR-13 16-APR-13
    2820 16-APR-13 16-APR-13
    2821 16-APR-13 16-APR-13
    2821 16-APR-13 16-APR-13
    2822 16-APR-13 16-APR-13
    2822 16-APR-13 16-APR-13
    2823 16-APR-13 16-APR-13
    2823 16-APR-13 16-APR-13
    2824 16-APR-13 16-APR-13
    2824 16-APR-13 16-APR-13
    2825 16-APR-13 16-APR-13
    2825 16-APR-13 16-APR-13
    2826 16-APR-13 16-APR-13
    2826 16-APR-13 16-APR-13
    2827 16-APR-13 16-APR-13
    2827 16-APR-13 16-APR-13
    2828 16-APR-13 16-APR-13
    2828 16-APR-13 16-APR-13
    2829 16-APR-13 16-APR-13
    2829 16-APR-13 16-APR-13
    2830 16-APR-13 16-APR-13
    2830 16-APR-13 16-APR-13
    2831 16-APR-13 16-APR-13
    2831 16-APR-13 16-APR-13
    2832 16-APR-13 16-APR-13
    2832 16-APR-13 16-APR-13
    2833 16-APR-13 16-APR-13
    2833 16-APR-13 16-APR-13
    2834 16-APR-13 16-APR-13
    2834 16-APR-13 16-APR-13
    2835 16-APR-13 16-APR-13
    2835 16-APR-13 16-APR-13
    2836 16-APR-13 16-APR-13
    2836 16-APR-13 16-APR-13
    2837 16-APR-13 16-APR-13
    2837 16-APR-13 16-APR-13
    2838 16-APR-13 16-APR-13
    2838 16-APR-13 16-APR-13
    2839 16-APR-13 16-APR-13
    2839 16-APR-13 16-APR-13
    2840 16-APR-13 16-APR-13
    2840 16-APR-13 16-APR-13
    2841 16-APR-13 16-APR-13
    2841 16-APR-13 16-APR-13
    2842 16-APR-13 16-APR-13
    2842 16-APR-13 16-APR-13
    2843 16-APR-13 16-APR-13
    2843 16-APR-13 16-APR-13
    2844 16-APR-13 16-APR-13
    2844 16-APR-13 16-APR-13
    2845 16-APR-13 16-APR-13
    2845 16-APR-13 16-APR-13
    2846 16-APR-13 16-APR-13
    2846 16-APR-13 16-APR-13
    Check the new archived redo log has arrived at the standby server and been applied.
    SELECT sequence#, first_time, next_time, applied
    FROM v$archived_log
    ORDER BY sequence#;
    2801 15-APR-13 15-APR-13 YES
    2801 15-APR-13 15-APR-13 YES
    2802 15-APR-13 15-APR-13 YES
    2802 15-APR-13 15-APR-13 YES
    2803 15-APR-13 15-APR-13 YES
    2803 15-APR-13 15-APR-13 YES
    2804 15-APR-13 15-APR-13 YES
    2804 15-APR-13 15-APR-13 YES
    2805 15-APR-13 15-APR-13 YES
    2805 15-APR-13 15-APR-13 YES
    2806 15-APR-13 15-APR-13 YES
    2806 15-APR-13 15-APR-13 YES
    2807 15-APR-13 15-APR-13 YES
    2807 15-APR-13 15-APR-13 YES
    2808 15-APR-13 16-APR-13 YES
    2808 15-APR-13 16-APR-13 YES
    2809 16-APR-13 16-APR-13 YES
    2809 16-APR-13 16-APR-13 YES
    2810 16-APR-13 16-APR-13 YES
    2810 16-APR-13 16-APR-13 YES
    2811 16-APR-13 16-APR-13 YES
    2811 16-APR-13 16-APR-13 YES
    2812 16-APR-13 16-APR-13 IN-MEMORY
    2812 16-APR-13 16-APR-13 YES
    So could anyone help me to resolve this issue. Anticipating your response at the earliest.
    Regards,
    VIKHAR
    Edited by: VIKHARAHMED on Apr 16, 2013 9:38 AM

    Here is the alert log file
    Media Recovery Log +FLASHDG/stby/archivelog/2013_04_16/thread_2_seq_1476.1987.812900733
    Tue Apr 16 18:56:42 2013
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[1]: Assigned to RFS process 16803
    RFS[1]: Selected log 12 for thread 2 sequence 1485 dbid 220323208 branch 808484882
    Tue Apr 16 18:56:42 2013
    RFS[2]: Assigned to RFS process 16807
    RFS[2]: Opened log for thread 2 sequence 1484 dbid 220323208 branch 808484882
    Archived Log entry 6324 added for thread 2 sequence 1484 rlc 808484882 ID 0xd21a288 dest 10:
    Tue Apr 16 19:09:02 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1486 dbid 220323208 branch 808484882
    Tue Apr 16 19:09:02 2013
    Archived Log entry 6325 added for thread 2 sequence 1485 ID 0xd21a288 dest 1:
    Archived Log entry 6326 added for thread 2 sequence 1485 ID 0xd21a288 dest 2:
    Tue Apr 16 19:12:23 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1487 dbid 220323208 branch 808484882
    Tue Apr 16 19:12:23 2013
    Archived Log entry 6327 added for thread 2 sequence 1486 ID 0xd21a288 dest 1:
    Archived Log entry 6328 added for thread 2 sequence 1486 ID 0xd21a288 dest 2:
    Tue Apr 16 19:14:41 2013
    "alert_stby.log" 845L, 33990C 782,1 94%
    Tue Apr 16 19:17:27 2013
    Archived Log entry 6331 added for thread 2 sequence 1488 ID 0xd21a288 dest 1:
    Archived Log entry 6332 added for thread 2 sequence 1488 ID 0xd21a288 dest 2:
    Tue Apr 16 19:25:51 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1490 dbid 220323208 branch 808484882
    Tue Apr 16 19:25:51 2013
    Archived Log entry 6333 added for thread 2 sequence 1489 ID 0xd21a288 dest 1:
    Archived Log entry 6334 added for thread 2 sequence 1489 ID 0xd21a288 dest 2:
    Tue Apr 16 19:51:02 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1491 dbid 220323208 branch 808484882
    Tue Apr 16 19:51:02 2013
    Archived Log entry 6335 added for thread 2 sequence 1490 ID 0xd21a288 dest 1:
    Archived Log entry 6336 added for thread 2 sequence 1490 ID 0xd21a288 dest 2:
    Tue Apr 16 20:37:12 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1492 dbid 220323208 branch 808484882
    Tue Apr 16 20:37:12 2013
    Archived Log entry 6337 added for thread 2 sequence 1491 ID 0xd21a288 dest 1:
    Archived Log entry 6338 added for thread 2 sequence 1491 ID 0xd21a288 dest 2:
    Tue Apr 16 21:08:23 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1493 dbid 220323208 branch 808484882
    Tue Apr 16 21:08:23 2013
    Archived Log entry 6339 added for thread 2 sequence 1492 ID 0xd21a288 dest 1:
    Archived Log entry 6340 added for thread 2 sequence 1492 ID 0xd21a288 dest 2:
    Tue Apr 16 22:16:06 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1494 dbid 220323208 branch 808484882
    Tue Apr 16 22:16:06 2013
    Archived Log entry 6341 added for thread 2 sequence 1493 ID 0xd21a288 dest 1:
    Archived Log entry 6342 added for thread 2 sequence 1493 ID 0xd21a288 dest 2:
    Tue Apr 16 22:31:46 2013
    RFS[1]: Selected log 12 for thread 2 sequence 1495 dbid 220323208 branch 808484882
    Tue Apr 16 22:31:46 2013
    Archived Log entry 6343 added for thread 2 sequence 1494 ID 0xd21a288 dest 1:
    Archived Log entry 6344 added for thread 2 sequence 1494 ID 0xd21a288 dest 2:
    Wed Apr 17 09:31:59 2013
    RFS[1]: Selected log 11 for thread 2 sequence 1496 dbid 220323208 branch 808484882
    Wed Apr 17 09:32:00 2013
    Archived Log entry 6345 added for thread 2 sequence 1495 ID 0xd21a288 dest 1:
    Archived Log entry 6346 added for thread 2 sequence 1495 ID 0xd21a288 dest 2:

  • Dataguard ,redo log not applied

    hi
    i am using oracle dataguard 10g .
    everything was quit fine . but some days later a problem occured . after sequence 128 log is not applied .
    i am using realtime log appled.
    can anybody help me .
    Thanks in advance
    munir .

    Hi,
    Is your standby database a physical or a logical standby ???
    Is the standby database in recover mode?
    What is the current log sequence number on your primary database?
    Place your standby database in recovery mode (if it is not) and restore arhcive logs on the standby database generated after log seq. 128
    Regards
    Asif Momen
    http://momendba.blogspot.com

  • Archive logs not applied on logical database.

    I have 10.2.04 oracle logical dataguard on windows:
    The logs are trasported smoothly from primary to stanby;
    But they are not applied to the logical standby;
    There are no GAPS.
    This is the message i got from DG broker wehn i ran verify configuration
    Initializing
    Connected to instance I-AG1101:tito
    Starting alert log monitor...
    Updating Data Guard link on database homepage...
    Data Protection Settings:
    Protection mode : Maximum Performance
    Redo Transport Mode settings:
    hclistg: ASYNC
    hclidg: ASYNC
    Checking standby redo log files.....OK
    Checking Data Guard status
    hclistg : Normal
    hclidg : Normal
    Checking Inconsistent Properties
    Checking agent status
    hclistg ... OK
    hclidg ... WARNING: No credentials available for target. I-SAG1151
    Attempting agent ping ... OK
    Switching log file 420.Done
    Checking applied log on hclidg.......WARNING:
    Timed out after 60 seconds waiting for log to be applied.
    Processing completed.
    This is the results of query: SELECT SEQUENCE#, FIRST_TIME, APPLIED
    FROM DBA_LOGSTDBY_LOG
    ORDER BY SEQUENCE#;
    SEQUENCE#|FIRST_TIME|APPLIED
    391|3/31/2010 1:08:27 PM|CURRENT
    392|3/31/2010 3:10:19 PM|NO
    393|3/31/2010 3:47:05 PM|NO
    394|3/31/2010 3:47:13 PM|NO
    395|3/31/2010 3:47:40 PM|NO
    396|3/31/2010 3:47:46 PM|NO
    397|3/31/2010 3:50:14 PM|NO
    398|3/31/2010 3:50:20 PM|NO
    399|3/31/2010 3:54:01 PM|NO
    400|3/31/2010 3:54:36 PM|NO
    401|3/31/2010 3:54:43 PM|NO
    402|3/31/2010 3:56:24 PM|NO
    403|3/31/2010 3:56:30 PM|NO
    404|3/31/2010 4:00:46 PM|NO
    405|3/31/2010 4:34:03 PM|NO
    406|3/31/2010 4:35:31 PM|NO
    407|3/31/2010 5:38:57 PM|NO
    408|4/1/2010 7:30:25 AM|NO
    409|4/1/2010 11:45:23 AM|NO
    410|4/1/2010 11:47:06 AM|NO
    411|4/1/2010 2:26:25 PM|NO
    412|4/1/2010 2:26:43 PM|NO
    413|4/1/2010 2:26:44 PM|NO
    414|4/1/2010 2:28:13 PM|NO
    415|4/1/2010 5:08:12 PM|NO
    416|4/1/2010 5:08:19 PM|NO
    417|4/1/2010 5:08:52 PM|NO
    418|4/2/2010 10:31:19 AM|NO
    419|4/2/2010 10:35:06 AM|NO
    420|4/2/2010 11:24:27 AM|NO
    Please help,,,

    i am getting this error when i run alter database mount standby database
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount;
    ORACLE instance started.
    Total System Global Area 1610612736 bytes
    Fixed Size 1299288 bytes
    Variable Size 545262760 bytes
    Database Buffers 1056964608 bytes
    Redo Buffers 7086080 bytes
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01665: control file is not a standby control file
    I configured my logical DG using Grid control

  • Logs not applying on Standby Database

    I am afraid I am back.
    I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
    Fri Jun 29 15:03:40 2012
    alter database recover managed standby database disconnect from session
    Attempt to start background Managed Standby Recovery process (SAPDS)
    Fri Jun 29 15:03:40 2012
    MRP0 started with pid=29, OS id=23272
    MRP0: Background Managed Standby Recovery process started (SAPDS)
    started logmerger process
    Fri Jun 29 15:03:45 2012
    Managed Standby Recovery not using Real Time Apply
    Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
    Rereading datafile 2 header failed with ORA-01206
    MRP0: Background Media Recovery terminated with error 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    Recovery Slave PR00 previously exited with exception 1110
    Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
    ORA-01206: file is not part of this database - wrong database id
    MRP0: Background Media Recovery process shutdown (SAPDS)
    Completed: alter database recover managed standby database disconnect from session
    My question therefore is how can I get out of this and get my logs to apply on standby?

    Hello again;
    Do you think if I tried to repeat the duplicate?
    Yes I think you should do this.
    Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
    I always cleanup the standby before trying another dup
    OVERVIEW
    Step 1 - Password file fro standby - Copy from primary and rename
    Step 2 - Directory Structure on the remote server - Make sure noting is missing
    Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
    Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
    Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
    Step 6 - Initialization Parameter File for the Auxiliary Instance
    Step 7 - Set SID for Auxiliary Instance
    Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
    Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
    Step 10 - Start RMAN and run the DUPLICATE Command
    SID_LIST_LISTENER Example from mine
    SID_LIST_LISTENER =
       (SID_LIST =
           (SID_DESC =
           (SID_NAME = PLSExtProc)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (PROGRAM = extproc)
           (SID_DESC =
           (global_dbname = CLONE.hostname)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
           (sid_name = CLONE)
    Prevent Timeouts
    Add these to both servers
    To listener.ora
    INBOUND_CONNECT_TIMEOUT_ = 120
    To sqlnet.ora
    SQLNET.INBOUND_CONNECT_TIMEOUT = 120
    Then stop and start the listener.
    RMAN
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    Connect should return something like this
    connected to target database: RECOVER9 (DBID=3806912436)
    connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
    INIT Extras
    To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
    Best Regards
    mseberg
    Edited by: mseberg on Jun 29, 2012 11:12 AM

  • Dataguard - Primary not applying logs to Standby

    Having an issue applying logs to the standby, seemingly it's not setup correctly. I am sure I'm missing something simple here, but would love any input or help. Thanks in advance.
    Background:
    Primary: CDPMTSB (Single Stand alone)
    Standby: CDPMT (RAC)
    Error Message on Primary (Alert Log):
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16014: log 3 sequence# 4071 not archived, no available destinations
    ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
    ARCH: Archival error occurred on a closed thread. Archiver continuing
    ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
    Mon Nov 19 19:54:24 2012
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
    ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16401: archivelog rejected by RFS
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16014: log 3 sequence# 4071 not archived, no available destinations
    ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
    ARCH: Archival error occurred on a closed thread. Archiver continuing
    ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
    Mon Nov 19 19:59:24 2012
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
    ARC6: Archive log rejected (thread 2 sequence 4071) at host 'CDPMT'
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16401: archivelog rejected by RFS
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16014: log 3 sequence# 4071 not archived, no available destinations
    ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
    ARCH: Archival error occurred on a closed thread. Archiver continuing
    ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
    Mon Nov 19 20:00:00 2012
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_j001_17473.trc:
    ORA-12012: error on auto execute of job 72620
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    ORA-06512: at "CD_ADMIN.UTDCD_SURVEY_PKG", line 4926
    Standby Alert Log:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:32:15 2012
    RFS[6]: Assigned to RFS process 4248
    RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 9561
    Mon Nov 19 19:32:22 2012
    RFS[1]: Selected log 6 for thread 1 sequence 4073 dbid 1629723947 branch 769881773
    Mon Nov 19 19:32:22 2012
    Archived Log entry 1097 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 1:
    Archived Log entry 1098 added for thread 1 sequence 4072 ID 0x62e7f5cf dest 3:
    Mon Nov 19 19:34:23 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:38:12 2012
    RFS[1]: Selected log 5 for thread 1 sequence 4074 dbid 1629723947 branch 769881773
    Mon Nov 19 19:38:12 2012
    Archived Log entry 1099 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 1:
    Archived Log entry 1100 added for thread 1 sequence 4073 ID 0x62e7f5cf dest 3:
    Mon Nov 19 19:39:23 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:44:24 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:49:24 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:54:24 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Mon Nov 19 19:59:24 2012
    Errors in file /opt/app/oracle/diag/rdbms/cdpmt/CDPMT1/trace/CDPMT1_rfs_24994.trc:
    ORA-16401: archivelog rejected by RFS
    Primary Parameters:
    NAME TYPE VALUE
    log_archive_config string DG_CONFIG=(CDPMT,CDPMTSB)
    log_archive_dest string
    log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_
    DEST VALID_FOR=(ONLINE_LOGFIL
    ES,ALL_ROLES) DB_UNIQUE_NAME=C
    DPMTSB
    log_archive_dest_10 string
    log_archive_dest_2 string SERVICE=CDPMT VALID_FOR=(ONLIN
    E_LOGFILES,PRIMARY_ROLE) DB_UN
    IQUE_NAME=CDPMT
    log_archive_dest_3 string location="+FRA_DG_01/cdpmtsb/s
    tandbylog", valid_for=(STANDB
    Y_LOGFILE,STANDBY_ROLE)
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string ENABLE
    log_archive_dest_state_3 string ENABLE
    log_archive_dest_state_4 string defer
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 7
    log_archive_min_succeed_dest integer 2
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    Standby Parameters:
    NAME TYPE VALUE
    log_archive_config string dg_config=(CDPMT,CD PMTSB)
    log_archive_dest string
    log_archive_dest_1 string location="USE_DB_RE COVERY_FILE
    _DEST", valid_for= (ALL_LOGFIL
    ES,ALL_ROLES)
    log_archive_dest_10 string
    log_archive_dest_2 string SERVICE=cdpmtsb LGW R ASYNC VAL
    ID_FOR=(ONLINE_LOGF ILES,PRIMAR
    Y_ROLE) DB_UNIQUE_N AME=cdpmtsb
    log_archive_dest_3 string LOCATION=+FRA_DG_01 /CDPMT/STAN
    DBYLOG VALID_FOR=( STANDBY_LOG
    NAME TYPE VALUE
    FILES,STANDBY_ROLE) DB_UNIQUE_
    NAME=CDPMT
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string ENABLE
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string ENABLE
    NAME TYPE VALUE
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 30
    NAME TYPE VALUE
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    SQL> show parameter log_ar
    NAME TYPE VALUE
    log_archive_config string dg_config=(CDPMT,CDPMTSB)
    log_archive_dest string
    log_archive_dest_1 string location="USE_DB_RECOVERY_FILE
    _DEST", valid_for=(ALL_LOGFIL
    ES,ALL_ROLES)
    log_archive_dest_10 string
    log_archive_dest_2 string SERVICE=cdpmtsb LGWR ASYNC VAL
    ID_FOR=(ONLINE_LOGFILES,PRIMAR
    Y_ROLE) DB_UNIQUE_NAME=cdpmtsb
    log_archive_dest_3 string LOCATION=+FRA_DG_01/CDPMT/STAN
    DBYLOG VALID_FOR=(STANDBY_LOG
    NAME TYPE VALUE
    FILES,STANDBY_ROLE) DB_UNIQUE_
    NAME=CDPMT
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string ENABLE
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string ENABLE
    NAME TYPE VALUE
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 30
    NAME TYPE VALUE
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    SQL>
    DGMGRL> show configuration verbose;
    Configuration
    Name: cdpmtqa
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    cdpmtsb - Primary database
    cdpmt - Physical standby database
    Fast-Start Failover: DISABLED
    Current status for "cdpmtqa":
    Warning: ORA-16608: one or more databases have warnings
    DGMGRL> show database verbose CDPMT
    Database
    Name: cdpmt
    Role: PHYSICAL STANDBY
    Enabled: YES
    Intended State: APPLY-ON
    Instance(s):
    CDPMT1
    CDPMT2 (apply instance)
    Properties:
    DGConnectIdentifier = 'cdpmt'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '30'
    RedoCompression = 'DISABLE'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '4'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = ''
    LogFileNameConvert = ''
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName(*)
    SidName(*)
    StaticConnectIdentifier(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    LatestLog(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
    Current status for "cdpmt":
    Warning: ORA-16809: multiple warnings detected for the database
    Any help would be really appreciated. Thanks!
    Edited by: 972075 on Nov 19, 2012 3:09 PM

    Thanks MSEBERG,
    Here's what I found. FRA seems to have enough space on ASM and there are other logs there, not sure what the issue is:
    14:31:58 SYS: CDPMTSB> show parameter db_recovery
    NAME TYPE VALUE
    db_recovery_file_dest string +FRA_DG_01
    db_recovery_file_dest_size big integer 60G
    DGMGRL> show database CDPMTSB logxptstatus;
    LOG TRANSPORT STATUS
    PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
    CDPMTSB cdpmt
    DGMGRL> SHOW DATABASE CDPMTSB InconsistentProperties;
    INCONSISTENT PROPERTIES
    INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
    DGMGRL> show database CDPMTSB InconsistentLogXptProps;
    INCONSISTENT LOG TRANSPORT PROPERTIES
    INSTANCE_NAME STANDBY_NAME PROPERTY_NAME MEMORY_VALUE BROKER_VALUE
    DGMGRL> show database CDPMT logxptstatus;
    Error: ORA-16757: unable to get this property's value
    DGMGRL> SHOW DATABASE CDPMT InconsistentProperties;
    INCONSISTENT PROPERTIES
    INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
    CDPMT2 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt
    CDPMT2 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt
    CDPMT1 LogArchiveMaxProcesses 4 30 4
    CDPMT1 DbFileNameConvert DG_01/cdpmtsb, DG_01/cdpmt DG_01/cdpmtsb,DG_01/cdpmt
    CDPMT1 LogFileNameConvert FRA_DG_01/cdpmtsb, FRA_DG_01/cdpmt, DG_01/cdpmtsb, DG_01/cdpmt FRA_DG_01/cdpmtsb,FRA_DG_01/cdpmt,+DG_01/cdpmtsb,+DG_01/cdpmt
    DGMGRL> show database CDPMT InconsistentLogXptProps;
    Error: ORA-16757: unable to get this property's value
    Errors in the Alert (from Primary):
    ARCH: Archival error occurred on a closed thread. Archiver continuing
    ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
    Tue Nov 20 14:34:43 2012
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    Changing destination 4 from remote to local during archival of log#: 3 sequence#: 4071 thread#: 2
    ARC6: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
    ARC6: Archive log rejected (thread 2 sequence 4071) at host 'cdpmt'
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16401: archivelog rejected by RFS
    Errors in file /data/oracle/app/oracle/diag/rdbms/cdpmtsb/CDPMTSB/trace/CDPMTSB_arc6_9571.trc:
    ORA-16014: log 3 sequence# 4071 not archived, no available destinations
    ORA-00312: online log 3 thread 2: '+FRA_DG_01/cdpmtsb/onlinelog/group_3.291.799379949'
    ARCH: Archival error occurred on a closed thread. Archiver continuing
    ORACLE Instance CDPMTSB - Archival Error. Archiver continuing.
    DGMGRL> DGMGRL> show database verbose CDPMT
    Database
    Name: cdpmt
    Role: PHYSICAL STANDBY
    Enabled: YES
    Intended State: APPLY-ON
    Instance(s):
    CDPMT1
    CDPMT2 (apply instance)
    Properties:
    DGConnectIdentifier = 'cdpmt'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '30'
    RedoCompression = 'DISABLE'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '4'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = ''
    LogFileNameConvert = ''
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName(*)
    SidName(*)
    StaticConnectIdentifier(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    LatestLog(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
    Current status for "cdpmt":
    Warning: ORA-16809: multiple warnings detected for the database
    DGMGRL> show database verbose CDPMTSB
    Database
    Name: cdpmtsb
    OEM Name: CDPMTSB_devdb40.utd.com
    Role: PRIMARY
    Enabled: YES
    Intended State: TRANSPORT-ON
    Instance(s):
    CDPMTSB
    Properties:
    DGConnectIdentifier = 'cdpmtsb'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '30'
    RedoCompression = 'DISABLE'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '7'
    LogArchiveMinSucceedDest = '2'
    DbFileNameConvert = '+DG_01/cdpmt, +DG_01/cdpmtsb'
    LogFileNameConvert = '+FRA_DG_01/cdpmt, FRA_DG_01/cdpmtsb, DG_01/cdpmt, +DG_01/cdpmtsb'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName = 'devdb40.utd.com'
    SidName = 'CDPMTSB'
    StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=devdb40.utd.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=CDPMTSB_DGMGRL)(INSTANCE_NAME=CDPMTSB)(SERVER=DEDICATED)))'
    StandbyArchiveLocation = '+FRA_DG_01/cdpmtsb/standbylog'
    AlternateLocation = ''
    LogArchiveTrace = '0'
    LogArchiveFormat = '%t_%s_%r.dbf'
    LatestLog = '(monitor)'
    TopWaitEvents = '(monitor)'
    Current status for "cdpmtsb":
    SUCCESS
    Thanks for your help btw, I'm really at a loss here as to what is going on with this.

  • Archived log not applying

    archived logs are not apllying in DR
    SQL> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    SQL>
    SQL> select process,status,sequence# from v$managed_standby;
    PROCESS   STATUS        SEQUENCE#
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    ARCH      CONNECTED             0
    RFS       IDLE                  0
    RFS       IDLE                  0
    RFS       IDLE              34473
    MRP0      WAIT_FOR_GAP      31753
    RFS       IDLE                  0
    RFS       IDLE                  0
    RFS       IDLE                  0
    11 rows selected.

    Hello,
    As previously posted, you have a GAP. So, you may have to investigate why the Archived logs cannot be applied.
    To do so, you may check for the File System if any Archive destination is FULL. Also, you may have to verify the parameters on the PRIMARY and STANDBY site:
    sqlplus "/ as sysdba"
    show parameter fal
    show parameter dest
    show parameter config
    show parameter broker
    Check also the Alert log on both Primary and Standby.
    If the DATAGUARD BROKER is enabled you may also execute this
    dgmgrl
    show configuration verbose
    Also try to "tnsping" the services used in the Archive Destination from both site.
    When you are sure that everything is correct then, verify if any Archived logs is missing and try to restore it if possible.
    Else if everything is broken, and there's no way to get back the missing Archived logs, you 'll have to "rebuild" the Standby from a new Backup of the PRIMARY.
    Hope this help.
    Best regards,
    Jean-Valentin Lubiez

  • Archive Logs NOT APPLIED but transferred

    Hi Gurus,
    I have configured Primary & Standby databases in same Oracle Home. OS version is OEL 5. Database version is 10.2.0.1. I could get the archive logs in the standby site but they are not getting applied in the standby database. I don't have OLAP installed in my database version. Would this create this issue? However I attached my primary alert log details below for your reference:
    Thu Aug 30 23:55:37 2012
    Starting ORACLE instance (normal)
    Cannot determine all dependent dynamic libraries for /proc/self/exe
    Unable to find dynamic library libocr10.so in search paths
    RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
    LD_LIBRARY_PATH is not set!
    The default library directories are /lib and /usr/lib
    Unable to find dynamic library libocrb10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    sga_target = 289406976
    control_files = /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control01.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control02.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control03.ctl
    db_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim
    log_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWSTAND/onlinelog, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWPRIM/onlinelog
    db_block_size = 8192
    compatible = 10.2.0.1.0
    log_archive_config = DG_CONFIG=(newprim,newstand)
    log_archive_dest_1 = LOCATION=/home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/arch/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=newprim
    log_archive_dest_2 = SERVICE=newstand LGWR ASYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=newstand
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    log_archive_max_processes= 30
    log_archive_format = %t_%s_%r.dbf
    fal_client = newprim
    fal_server = newstand
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=newprimXDB)
    job_queue_processes = 10
    background_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump
    user_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump
    core_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/cdump
    audit_file_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/adump
    db_name = newprim
    db_unique_name = newprim
    open_cursors = 300
    pga_aggregate_target = 95420416
    PMON started with pid=2, OS id=28091
    PSP0 started with pid=3, OS id=28093
    MMAN started with pid=4, OS id=28095
    DBW0 started with pid=5, OS id=28097
    LGWR started with pid=6, OS id=28100
    CKPT started with pid=7, OS id=28102
    SMON started with pid=8, OS id=28104
    RECO started with pid=9, OS id=28106
    CJQ0 started with pid=10, OS id=28108
    MMON started with pid=11, OS id=28110
    MMNL started with pid=12, OS id=28112
    Thu Aug 30 23:55:38 2012
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    Thu Aug 30 23:55:38 2012
    ALTER DATABASE MOUNT
    Thu Aug 30 23:55:42 2012
    Setting recovery target incarnation to 2
    Thu Aug 30 23:55:43 2012
    Successful mount of redo thread 1, with mount id 1090395834
    Thu Aug 30 23:55:43 2012
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Thu Aug 30 23:55:43 2012
    ALTER DATABASE OPEN
    Thu Aug 30 23:55:43 2012
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=16, OS id=28122
    ARC1 started with pid=17, OS id=28124
    ARC2 started with pid=18, OS id=28126
    ARC3 started with pid=19, OS id=28128
    ARC4 started with pid=20, OS id=28133
    ARC5 started with pid=21, OS id=28135
    ARC6 started with pid=22, OS id=28137
    ARC7 started with pid=23, OS id=28139
    ARC8 started with pid=24, OS id=28141
    ARC9 started with pid=25, OS id=28143
    ARCa started with pid=26, OS id=28145
    ARCb started with pid=27, OS id=28147
    ARCc started with pid=28, OS id=28149
    ARCd started with pid=29, OS id=28151
    ARCe started with pid=30, OS id=28153
    ARCf started with pid=31, OS id=28155
    ARCg started with pid=32, OS id=28157
    ARCh started with pid=33, OS id=28159
    ARCi started with pid=34, OS id=28161
    ARCj started with pid=35, OS id=28163
    ARCk started with pid=36, OS id=28165
    ARCl started with pid=37, OS id=28167
    ARCm started with pid=38, OS id=28169
    ARCn started with pid=39, OS id=28171
    ARCo started with pid=40, OS id=28173
    ARCp started with pid=41, OS id=28175
    ARCq started with pid=42, OS id=28177
    ARCr started with pid=43, OS id=28179
    ARCs started with pid=44, OS id=28181
    Thu Aug 30 23:55:44 2012
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARCt started with pid=45, OS id=28183
    LNS1 started with pid=46, OS id=28185
    Thu Aug 30 23:55:48 2012
    Thread 1 advanced to log sequence 68
    Thu Aug 30 23:55:48 2012
    ARCo: Becoming the 'no FAL' ARCH
    ARCo: Becoming the 'no SRL' ARCH
    Thu Aug 30 23:55:48 2012
    ARCp: Becoming the heartbeat ARCH
    Thu Aug 30 23:55:48 2012
    Thread 1 opened at log sequence 68
    Current log# 1 seq# 68 mem# 0: /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/redo01.log
    Successful open of redo thread 1
    Thu Aug 30 23:55:48 2012
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Thu Aug 30 23:55:48 2012
    SMON: enabling cache recovery
    Thu Aug 30 23:55:48 2012
    Successfully onlined Undo Tablespace 1.
    Thu Aug 30 23:55:48 2012
    SMON: enabling tx recovery
    Thu Aug 30 23:55:49 2012
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=47, OS id=28205
    Thu Aug 30 23:55:49 2012
    Error 1034 received logging on to the standby
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-01034: ORACLE not available
    FAL[server, ARC1]: Error 1034 creating remote archivelog file 'newstand'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Thu Aug 30 23:55:49 2012
    ORACLE Instance newprim - Archival Error. Archiver continuing.
    Thu Aug 30 23:55:49 2012
    db_recovery_file_dest_size of 2048 MB is 9.77% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Thu Aug 30 23:55:50 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump/newprim_ora_28120.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15
    Thu Aug 30 23:55:50 2012
    Completed: ALTER DATABASE OPEN
    Thu Aug 30 23:56:33 2012
    FAL[server]: Fail to queue the whole FAL gap
    GAP - thread 1 sequence 1-33
    DBID 1090398314 branch 792689455
    Kindly, guide me please..
    -Vimal.

    CKPT: The trace file details are added below for your reference;
    /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning and Data Mining options
    ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
    System name:     Linux
    Node name:     localhost.localdomain
    Release:     2.6.18-8.el5PAE
    Version:     #1 SMP Tue Jun 5 23:39:57 EDT 2007
    Machine:     i686
    Instance name: newprim
    Redo thread mounted by this instance: 1
    Oracle process number: 17
    Unix process pid: 28124, image: [email protected] (ARC1)
    *** SERVICE NAME:() 2012-08-30 23:55:48.314
    *** SESSION ID:(155.1) 2012-08-30 23:55:48.314
    kcrrwkx: nothing to do (start)
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 60679 kcrr.c
    Error 1034 received logging on to the standby
    Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 58941 kcrr.c
    kcrrfail: dest:2 err:1034 force:0 blast:1
    kcrrwkx: unknown error:1034
    ORA-16055: FAL request rejected
    ARCH: Connecting to console port...
    ARCH: Connecting to console port...
    kcrrwkx: nothing to do (end)
    *** 2012-08-31 00:00:43.417
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:05:43.348
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:10:43.280
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:15:43.217
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:20:43.160
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:25:43.092
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:30:43.031
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:35:42.961
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:40:42.890
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:45:42.820
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:50:42.755
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:55:42.686
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:00:42.631
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:05:42.565
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:10:42.496
    kcrrwkx: nothing to do (start)
    Mahir: Yes I have my 4 standby redo logs!
    I created the standby manually without using RMAN.
    Hemant: if it asks for even first thread, then obviously it shows nothing is applied on Standby. By the way so it is not called a 'GAP', I think..!
    Thanks.

  • Archive logs not applied on standby!!

    Hi Guys,
    I am trying to set up physical standby on windows 2003 server. I am using oracle 10.2.0.4.0. I get the following error in my alert file on standby
    Failed to request gap sequence
    Following is the results of some queries :
    SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MR(fg) WAIT_FOR_GAP 1 10004 0 0
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    MESSAGE
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    MESSAGE
    MRP0: Background Media Recovery cancelled with status 16037
    MRP0: Background Media Recovery process shutdown
    Managed Standby Recovery Canceled
    Media Recovery Start: Managed Standby Recovery
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    FAL[client]: All defined FAL servers have been attempted.
    SQL>SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
    where applied= 'YES'
    no rows selected
    ##Modification to primary##
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.fal_client='STUTEST'
    *.fal_server='STUSTANDBY'
    *.log_archive_config='DG_CONFIG=(STUTEST,STUSTANDBY)'
    ##Modification to standby##
    *.db_unique_name='STANDBY'
    *.log_archive_dest_2='SERVICE=STANDBY'
    *.log_archive_dest_state_2='ENABLE'
    *.Fal_server=STUTEST
    *.Fal_client=STUSTANDBY
    *.db_file_name_convert='H:\ORACLE\ORADATA\STUTEST\','I:\ORACLE\ORADATA\STUTEST\s_'
    *.log_file_name_convert='D:\oracle\oradata\STUTEST\','D:\oracle\oradata\STUTEST\s_'
    Nore: I used RMAN to create the standby database. The following are brief steps
    Below are the steps to accomplish the task :
    Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby
    backup current controlfile for standby;
    Step 2: Move the backups to the standby server and restore control file from backup
    Step 3: Make changes in the parameter files of both primary and standby database
    Step 4: Do the restore and recover on standby database
    Step 5: Put the standby database in recover managed mode
    Thanks for help guys!!!!!

    Hi sb92075
    Alert log on standby
    alter database mount standby database
    Mon Jul 26 14:10:40 2010
    Setting recovery target incarnation to 1
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=21, OS id=6708
    ARC1 started with pid=22, OS id=3892
    ARC2 started with pid=23, OS id=4380
    ARC3 started with pid=24, OS id=4896
    ARC4 started with pid=25, OS id=6348
    ARC5 started with pid=26, OS id=5868
    ARC6 started with pid=27, OS id=6904
    ARC7 started with pid=28, OS id=4428
    ARC8 started with pid=29, OS id=5008
    Mon Jul 26 14:10:40 2010
    ARC0: Archival started
    ARC9 started with pid=30, OS id=5804
    Mon Jul 26 14:10:41 2010
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Mon Jul 26 14:10:41 2010
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC0: Thread not mounted
    Mon Jul 26 14:10:41 2010
    Successful mount of redo thread 1, with mount id 2477113436
    Mon Jul 26 14:10:41 2010
    Physical Standby Database mounted.
    Mon Jul 26 14:10:42 2010
    ARC1: Becoming the heartbeat ARCH
    Completed: alter database mount standby database
    Mon Jul 26 14:10:42 2010
    Errors in file c:\oracle\admin\stustandby\udump\stustandby_ora_6604.trc:
    Mon Jul 26 14:11:41 2010
    alter database recover managed standby database disconnect from session
    MRP0 started with pid=19, OS id=3696
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Mon Jul 26 14:11:46 2010
    Waiting for all non-current ORLs to be archived...
    Media Recovery Waiting for thread 1 sequence 10004
    Fetching gap sequence in thread 1, gap sequence 10004-10017
    Mon Jul 26 14:11:47 2010
    Completed: alter database recover managed standby database disconnect from session
    Mon Jul 26 14:12:16 2010
    *FAL[client]: Failed to request gap sequence*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    *FAL[client]: All defined FAL servers have been attempted.*
    Alert log on primary
    Mon Jul 26 13:50:11 2010
    db_recovery_file_dest_size of 40960 MB is 49.73% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Mon Jul 26 13:50:12 2010
    Successfully onlined Undo Tablespace 19.
    Mon Jul 26 13:50:12 2010
    SMON: enabling tx recovery
    Mon Jul 26 13:50:12 2010
    Database Characterset is WE8ISO8859P1
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=38, OS id=3776
    Mon Jul 26 13:50:14 2010
    Completed: ALTER DATABASE OPEN
    Mon Jul 26 13:51:10 2010
    Shutting down archive processes
    Mon Jul 26 13:51:15 2010
    ARCH shutting down
    ARCa: Archival stopped
    Mon Jul 26 14:11:47 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017
    DBID 2422302575 branch 670594799
    Mon Jul 26 15:04:10 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    *FAL[server]: DGID from FAL client not in Data Guard configuration*
    *FAL[server]: FAL request for destination STUSTANDBY was:*
    GAP - thread 1 sequence 10004-10017 DBID 2422302575 branch 670594799

  • Standby log not applying

    Hi folks,
    Tried creating Data guard for the first time. Was able to successfully create a standby and on every log switch on primary database, a switch is seen on standby too..
    But the issue is, log's are not getting applied on standby db..
    SQL> archive log list;
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            F:\app\product\11.2.0\dbhome_1\RDBMS
    Oldest online log sequence     33
    Next log sequence to archive   0
    Current log sequence           38
    SQL> SELECT sequence#, first_time, next_time, applied
    2 FROM v$archived_log
    3 ORDER BY sequence#;
    SEQUENCE# FIRST_TIM NEXT_TIME APPLIED
    *16 31-MAY-12 31-MAY-12 NO*
    *17 31-MAY-12 31-MAY-12 NO*
    *19 31-MAY-12 31-MAY-12 NO*
    *20 31-MAY-12 31-MAY-12 NO*
    *28 31-MAY-12 31-MAY-12 NO*
    *29 31-MAY-12 31-MAY-12 NO*
    *32 31-MAY-12 31-MAY-12 NO*
    *34 31-MAY-12 31-MAY-12 NO*
    *36 31-MAY-12 31-MAY-12 NO*
    *37 31-MAY-12 31-MAY-12 NO*
    *38 31-MAY-12 31-MAY-12 NO*
    11 rows selected.
    Also the alert log on strandby show's as...
    Alert log on standby:
    Thu May 31 23:30:43 2012
    RFS[18]: Assigned to RFS process 3380
    RFS[18]: Identified database type as 'physical standby': Client is ARCH pid 5780
    RFS[18]: Selected log 4 for thread 1 sequence 36 dbid 196575176 branch 784736843
    Thu May 31 23:30:45 2012
    Archived Log entry 9 added for thread 1 sequence 36 ID 0xbb7cbc8 dest 1:
    Thu May 31 23:30:45 2012
    RFS[19]: Assigned to RFS process 4968
    RFS[19]: Identified database type as 'physical standby': Client is LGWR ASYNC pid 5072
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[19]: Selected log 4 for thread 1 sequence 37 dbid 196575176 branch 784736843
    Thu May 31 23:30:46 2012
    RFS[20]: Assigned to RFS process 4996
    RFS[20]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Thu May 31 23:30:47 2012
    Archived Log entry 10 added for thread 1 sequence 37 ID 0xbb7cbc8 dest 1:
    RFS[19]: Selected log 4 for thread 1 sequence 38 dbid 196575176 branch 784736843
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001 (162 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4996.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4996.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:30:48 2012
    RFS[21]: Assigned to RFS process 4508
    RFS[21]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Thu May 31 23:30:48 2012
    RFS[22]: Assigned to RFS process 1524
    RFS[22]: Identified database type as 'physical standby': Client is ARCH pid 5308
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001 (198 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4508.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4508.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001 (17296 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1524.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1524.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:30:51 2012
    RFS[23]: Assigned to RFS process 460
    RFS[23]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001 (65 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_460.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_460.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:30:52 2012
    RFS[24]: Assigned to RFS process 3456
    RFS[24]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Thu May 31 23:30:52 2012
    RFS[25]: Assigned to RFS process 1936
    RFS[25]: Identified database type as 'physical standby': Client is ARCH pid 5308
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001 (287 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3456.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3456.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001 (10 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1936.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1936.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:30:56 2012
    RFS[26]: Assigned to RFS process 5084
    RFS[26]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001 (193 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_5084.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_5084.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:30:57 2012
    RFS[27]: Assigned to RFS process 2404
    RFS[27]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001 (8 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2404.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2404.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:48 2012
    RFS[28]: Assigned to RFS process 2988
    RFS[28]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001 (162 blocks)
    Thu May 31 23:36:49 2012
    RFS[29]: Assigned to RFS process 4152
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2988.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    RFS[29]: Identified database type as 'physical standby': Client is ARCH pid 5308
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2988.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:49 2012
    RFS[30]: Assigned to RFS process 4128
    RFS[30]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001 (198 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4128.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4128.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001 (17296 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4152.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4152.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:51 2012
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_arc2_5596.trc:
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000038_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    ARC2: Error 19504 Creating archive log file to 'F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000038_0784736843.0001'
    ARCH: Archival stopped, error occurred. Will continue retrying
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_arc2_5596.trc:
    ORA-16038: log 4 sequence# 38 cannot be archived
    ORA-19504: failed to create file ""
    ORA-00312: online log 4 thread 1: 'F:\APP\ORADATA\STAN\SRL01.LOG'
    Thu May 31 23:36:53 2012
    RFS[31]: Assigned to RFS process 4340
    RFS[31]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001 (65 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4340.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4340.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:54 2012
    RFS[32]: Assigned to RFS process 3080
    RFS[32]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Thu May 31 23:36:54 2012
    RFS[33]: Assigned to RFS process 3296
    RFS[33]: Identified database type as 'physical standby': Client is ARCH pid 5308
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001 (287 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3080.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3080.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001 (10 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3296.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3296.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:55 2012
    RFS[34]: Assigned to RFS process 3464
    RFS[34]: Identified database type as 'physical standby': Client is ARCH pid 5192
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001 (193 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3464.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3464.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:36:57 2012
    RFS[35]: Assigned to RFS process 6036
    RFS[35]: Identified database type as 'physical standby': Client is ARCH pid 5780
    Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001 (8 blocks)
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_6036.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_6036.trc:
    ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
    ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
    ORA-27056: could not delete file
    OSD-04024: Unable to delete file.
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Thu May 31 23:37:09 2012
    Archived Log entry 11 added for thread 1 sequence 38 ID 0xbb7cbc8 dest 1:
    Archiver process freed from errors. No longer stopped
    confirmed that there is enough space and proper permission on the folder's..
    someone please suggest what could have gone wrong??
    Regards!

    Hello again;
    So I both servers log_archive_dest_1 is not set?
    The Oracle example is
    Primary
    LOG_ARCHIVE_DEST_1= 'LOCATION=/arch1/chicago/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=chicago'
    Standby
    LOG_ARCHIVE_DEST_1='LOCATION=/arch1/boston/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=boston'
    If a fast recovery area was configured (with the DB_RECOVERY_FILE_ DEST initialization parameter) and you have not explicitly configured a local archiving destination with the LOCATION attribute, Data Guard automatically
    uses the LOG_ARCHIVE_DEST_1 initialization parameter (if it has not already been set) as the default destination for local archiving. Also, see Chapter 15 for complete LOG_ARCHIVE_DEST_n information.
    My take is since you are not using FRA this parameter is not defined by default. I would probably set it on both, but frankly I'm not sure this will solve your issue. If it does I would sure like to know about it so i can add it to my notes.
    Not related to your issue
    Would consider setting standby_file_management to 'Auto' on both.
    Would consider setting log_archive_dest_state_2 to 'DEFER' on the Standby.
    Best Regards
    mseberg
    Would

  • ORA-326/ORA-334 Physical Standby DB - Not applying logs

    Hi, all, I have a Dataguard, the primary db is a RAC with three nodes, the standby db is a physical standby. the dataguard are all oracle 10.2.0.3 on solaris 9 sparc system
    Now, my standby db did not apply the archivelogs,there are some errors in standby alert log :
    Thu Jan 8 15:44:31 2009
    Errors in file /oracle/admin/xxxx/bdump/whut_mrp0_12863.trc:
    ORA-00326:log begins at change 2984028173, need earlier change 2984013192
    ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Thu Jan 8 15:44:34 2009
    Errors in file /export/home/oracle/admin/whut/bdump/whut_mrp0_12863.trc:
    ORA-00326:log begins at change 2984028173, need earlier change 2984013192
    ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
    Thu Jan 8 15:44:34 2009
    MRP0: Background Media Recovery process shutdown (whut)
    and the archivelogs on the standby db like this :
    NAME APP DEL
    +DGARCH/whut/3_22651_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22650_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22649_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  NO
    +DGARCH/whut/3_22648_611942629.dbf                           NO  YES
    +DGARCH/whut/3_22291_611942629.dbf                           YES YES
    +DGARCH/whut/2_62553_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62552_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62551_611942629.dbf                           NO  NO
    +DGARCH/whut/2_62550_611942629.dbf                           NO  NO
    query the first_change# on the standby db like this :
    SEQUENCE# FIRST_CHANGE# APP ARC
    22646 2983721221 NO YES
    22647 2983911304 NO YES
    22648 2984028173 NO YES
    23813 2984013365 NO YES
    23814 2984118027 NO YES
    62546 2984027708 NO YES
    SEQUENCE# FIRST_CHANGE# APP ARC
    62547 2984163823 NO YES
    23815 2984132128 NO YES
    23816 2984312713 NO YES
    62548 2984255538 NO YES
    62549 2984312692 NO YES
    22649 2984028196 NO YES
    23817 2984351070 NO YES
    then ,how to fix the dataguard and apply the archivelog on standby db ?
    why I can found 2984028173 with 22648,but can not found 2984013192 ??
    and why there have three 22648 with different applied status and deleted status on standby db ???
    Thanks all.

    Thank you for your reply.
    the trc file like this:
    /oracle/admin/xxx/bdump/xxx_mrp0_12863.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /oracle/product/10.2.0/database
    System name:     SunOS
    Node name:     stdb
    Release:     5.9
    Version:     Generic_122300-25
    Machine:     sun4u
    Instance name: xxx
    Redo thread mounted by this instance: 1
    Oracle process number: 27
    Unix process pid: 12863, image: oracle@stdb (MRP0)
    *** SERVICE NAME:() 2009-01-08 15:44:24.179
    *** SESSION ID:(197.3) 2009-01-08 15:44:24.179
    ARCH: Connecting to console port...
    *** 2009-01-08 15:44:24.180 61287 kcrr.c
    MRP0: Background Managed Standby Recovery process started
    *** 2009-01-08 15:44:29.191 1103 krsm.c
    Managed Recovery: Initialization posted.
    *** 2009-01-08 15:44:29.192 61287 kcrr.c
    Managed Standby Recovery starting Real Time Apply
    Recovery target incarnation = 5, activation ID = 721050634
    Influx buffer limit = 152383 (50% x 304766)
    Successfully allocated 3 recovery slaves
    Using 367 overflow buffers per recovery slave
    Start recovery at thread 3 ckpt scn 2984013192 logseq 22648 block 2
    *** 2009-01-08 15:44:31.181
    Media Recovery add redo thread 3
    *** 2009-01-08 15:44:31.181
    Media Recovery add redo thread 1
    *** 2009-01-08 15:44:31.182
    Media Recovery add redo thread 2
    *** 2009-01-08 15:44:31.184 1103 krsm.c
    Managed Recovery: Active posted.
    *** 2009-01-08 15:44:31.838
    Media Recovery Log +DGARCH/whut/3_22648_611942629.dbf
    *** 2009-01-08 15:44:31.851 61287 kcrr.c
    MRP0: Background Media Recovery terminated with error 326
    ORA-00326: log begin at 2984028173, need earlier 2984013192
    ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
    *** 2009-01-08 15:44:31.851 61287 kcrr.c
    Managed Standby Recovery not using Real Time Apply
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 3
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 1
    *** 2009-01-08 15:44:31.851
    Media Recovery drop redo thread 2
    *** 2009-01-08 15:44:34.269 1103 krsm.c
    Managed Recovery: Not Active posted.
    ORA-00326: log begin at 2984028173,need earlier 2984013192
    ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
    ARCH: Connecting to console port...
    *** 2009-01-08 15:44:34.359 61287 kcrr.c
    MRP0: Background Media Recovery process shutdown
    *** 2009-01-08 15:44:34.359 1103 krsm.c

  • Standby not applying the online redo logs

    Hi,
    The redo apply process does not seem to apply the current logs to the standby database.
    The output from the query
    Select last_change#, sequence# from v$standby_log;
    LAST_CHANGE# GROUP# SEQUENCE#
    4 0
    10120537 5 8586
    6 0
    7 0
    gives me the current SCN as that of the primary.
    But the CURRENT_SCN from v$database on the standby lags from that of the output above.
    Select CURRENT_SCN from v$database;
    CURRENT_SCN
    10119641
    The STATUS and PROCESS information from the v$managed_standby show the following:
    PROCESS STATUS SEQUENCE#
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    ARCH CONNECTED 0
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 8586
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 0
    RFS IDLE 0
    PROCESS STATUS SEQUENCE#
    MRP0 APPLYING_LOG 8586
    Any thoughts on why the standby has not applied the recived logs from the primary?
    I am currently using version Oracle 11.2.0.2 for Active dataguard setup. I currently have a primary server and one standy server.
    Thanks

    I had sent the output of the queries in the earlier post. Here it is again
    The output for the query
    select thread#, max(sequence#) from v$archived_log group by thread#; (on primary)
    THREAD# MAX(SEQUENCE#)
    1 8585
    The output for
    select thread#, max(sequence#) from v$archived_log where applied = 'YES' group by thread#; (on standby)
    THREAD# MAX(SEQUENCE#)
    1 8585
    Also the query
    select LAST_CHANGE#, STATUS from V$STANDBY_LOG;
    gives me the current scn generated at the primary.
    LAST_CHANGE# STATUS
    10149990 ACTIVE
    10146538 ACTIVE
    10150844 ACTIVE
    But the current_scn from v$database is lagging.
    select current_scn from v$database;
    CURRENT_SCN
    10146535
    Also the query
    select  THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# from v$archive_gap;
    returns no rows. So there are no archive logs missing on the standby either.
    So I beleive that the RFS has recieved the logs from the primary but the logs have not been applied at the standby.
    Thanks

  • Oracle Dataguard - Logs apply issue

    Hi,
    Due to some issue our archives logs are not applying from production to standy. we had our standby at London. i dont see any error messages. not sure what is happening, i had case open with oracle support.
    we need to shutdown all our production and DR last sunday. once it is back up it stopped sending logs. our production server is a 3 node RAC.
    i just need how to apply archive logs from production to standby which is in london.
    appricate your quick response.
    Thanks

    Hello,
    Please post the result:
    SELECT MAX(SEQUENCE#), MAX(COMPLETION_TIME), APPLIED FROM V$ARCHIVED_LOG GROUP BY APPLIED;
    and
    SELECT * FROM V$ARCHIVE_GAP;
    also you can copy them from the primary to the standby and apply them one by one:
    ALTER DATABASE REGISTER LOGFILE 'LOG_FILE_NAME';
    if the gapsequence is so big like 20 or 30 days i will recreate the dataguard using and clone it using rman.
    Kind regards
    Mohamed

  • I have one problem with Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • Redo log files are not applying to standby database

    Hi everyone!!
    I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
    My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database.  I run the following command on the standby database.
                SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
    The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
    1. How to resolve this issue ?
    2.Is it compulsory to have Primary database open ?
    3. I have created standby  control file by using  command
              SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
    So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should  I have different database name for both or existing one is correct ?
    Can anybody help me to come out from this stuck ?
    Thanks & Regards
    Tushar Lapani

    Thank you Girish. It solved  my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
    I did following scenario.
    1.  Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
    2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
    3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
    So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
    Thanks

Maybe you are looking for

  • Linux ignores mms.cfg

    Creating a /etc/adobe/mms.cfg does not appear to work in several versions of Linux that I have tested with several versions of flash 10. Of course, I would not need this if the camera and microphone security dialog issues was fixed. Any help would be

  • No graphics in vista using media live AM2

    I have just built my second media live, based on AMD Athlon 64 X2 4850e 2.5GHz Socket AM2 and 4gb of 667mhz crucial memory - see see http://www.ebuyer.com/product/142387 and 1TB Samsung Green HDD. My first Live, would not play any videos at all, just

  • [CS5 - JS] Random questions...

    Hi. I come form InDesign scripting and I'm sorry to say that illustrator one is really raw... Anyway, my problems are: - Looks like it's not possible to get something like "textStyleRanges" within a paragraph so the only way to get different text sty

  • Directory Integration Platform - DN Mapping Rule

    Hi all, Can anyone help me with setting up the mapping in a directory synchronization profile in DIP? Using the GUI, the three fields required are Source Container, DIP-OID Container and DN Mapping rule. The containers are obvious but what is the syn

  • Why can't I see user /Library directory?

    I wanted to find the filename(s) for the Contacts file on my machine.  I wanted to save off the file, and then start pruning old contacts from it.  I wanted to save the actual file w/out having to rely on TImeMachine. I found from other searches that