Standby DB not applying logs

Hi,
i opened my primary DB using "alter database open resetlogs" after recovering from a power failure crash.
this caused the log sequence number to reset to 1.
when i check the standby DB for maximum log sequence applied, it is showing the last log applied before the crash whereas the primary DB has since the recovery, produced over 200 logs.
how can i get the standby DB to start applying the new log sequence?
regards,
Michael

If you had opened the Primary with a RESETLOGS to a point earlier than the highest log applied on the standby and you cannot flashback the standby, you have to rebuild the standby.
For example, the Standby has applied Sequence#1411 but the Primary was opened with RECOVER upto Sequence#1409 and RESETLOGS. The Primary has diverged from the Standby so the standby has to be rebuilt.
If however, the last redo applied to the Standby was lower than the RECOVER and RESETLOGS point on the primary, the Standby should be automatically able to continue. In your case, you say that the Standby hasn't continued. Therefore, I suspect the former (Primary RECOVER and RESETLOGS to a lower SCN/SEQUENCE#).
See "9.4 Recovering Through the OPEN RESETLOGS Statement" at http://docs.oracle.com/cd/E11882_01/server.112/e25608/manage_ps.htm#i1026480
Hemant K Chitale

Similar Messages

  • 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

  • 10gR2 Logical Standby database not applying logs

    No errors are appearing in the logs and I've started the apply process :ALTER DATABASE START LOGICAL STANDBY APPLY but when I query dba_logstdby_log, none of the logs for the last 4 days shows as applied and the first SCN is still listed as current. Any thoughts on where I should start looking?
    the latest event in DBA_LOGSTDBY_EVENTS is the startup of the log mining and apply.
    I do not have standby redo logs so I cannot do real time apply, though I am looking to implementing this. Obviously, this is pretty new to me.

    Sorry I didn't mention this before, the logs are being transferred, I verified their location on the os and it matches the location in the dba_logstdby_log view.

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

  • Standby database not applying archivelogs, manually apply after registering

    Hi
    I have a small problem with physical standby db.
    Standby db was created and it was working fine, was applying logs with no problem. One day I had to switch it to read only mode, it stayed in this mode for quiet a while. Then there was a problem with space for archive logs. I fixed this, copied missing logs, registered them and these were applied.
    And then database stopped on the sequence which was automatically registered by primary database.
    v$managed_standby:
    PROCESS STATUS CLIENT_P SEQUENCE# DELAY_MINS BLOCK#
    ARCH CLOSING ARCH 19667 0 126977
    ARCH CLOSING ARCH 19668 0 133121
    MRP0 WAIT_FOR_LOG N/A 19600 0 0
    As you can see there is WAIT_FOR_LOG sequence 19600 which should be applied, which is in the directory, to which oracle user has rights to read etc, etc.
    Only way to force database to apply this log is to manually register it, but I have to add "or replace", because file is already registered.
    /path/dbsid1_19600_668777138.log 2 19600 YES NO NO A 28-OCT-09 28-OCT-09
    alter database register or replace physical logfile '/path/dbsid1_19600_668777138.log';
    After this I have:
    /path/dbsid_19600_668777138.log 2 19600 YES NO NO A 28-OCT-09 28-OCT-09
    /path/dbsid_19600_668777138.log 0 19600 YES YES NO A 29-OCT-09 28-OCT-09
    Registering this file causes applying at once.
    In pfile on primary:
    log_archive_dest_2 string SERVICE=DRSTDB2 ARCH DELAY=2880
    Pay attention - destination 2.
    Question is obvious - why logs are not applied automatically?
    Why logs ARE applying manually but the DEST_ID is set to 0?
    There was no major structure change in primary, besides - logs are applied after all. Bouncing the database doesn't give me any good, switching to readonly and back to recovery mode neither.
    Please can you help? I can build this standby again but this is not a solution.
    Any additional info on request.
    Regards
    Jarek Jozwik
    Edited by: user11281267 on 30-Oct-2009 06:15

    You haven't given any usefuly information on your problem.
    show parameter log_archive_dest
    show parameter fal
    show parameter dg
    What errors are in your alert logs ?
    What command are you using to recover ?
    Check the contents of v$archived_log
    # run on primary to detect failures :-
    select destination, status, fail_date, valid_now
    from v$archive_dest
    where status != 'VALID' or VALID_NOW != 'YES';
    # run on standby to get exact position of rollforward :-
    select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
    to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
    to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
    Are you using dataguard broker ?

  • Standby do not applied archives

    Hi,
    Please help me any one,
    am facing the below problem,
    Errors in file /oracle/admin/marvlstd/bdump/marvlstd_mrp0_28273.trc:
    ORA-12801: error signaled in parallel query server P000
    ORA-00600: internal error code, arguments: [3020], [90], [573443], [378060803], [], [], [], []
    ORA-10567: Redo is inconsistent with data block (file# 90, block# 573443)
    ORA-10564: tablespace USERS
    ORA-01110: data file 90: '+DA
    when am started MRP above error  to be occurred how to solve the issue in statdby
    i have restarted asm and DB its fine but archives not applied,
    once i put the below command facing the above problem.
    alter database recover managed standby database disconnect from session;
    Thanks
    Gopi G

    Hi,
    please check following link: ORA-10567: Redo is inconsistent with data block (file# 124, block# 214081) « Hendry's "Oracl…
    Thank you

  • Standy database MRP0 is not applying logs

    Hi all,
    i am using oracle 11.1.0.7.0 database on linux
    standby database is receving archives but not applying to to standby.
    CTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    PROCESS CLIENT_P STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    ARCH ARCH CONNECTED 0 0 0 0
    RFS LGWR RECEIVING 1 66141 33298 2
    RFS UNKNOWN IDLE 0 0 0 0
    MRP0 N/A WAIT_FOR_GAP 1 66003 0 0
    PROCESS CLIENT_P STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    RFS UNKNOWN IDLE 0 0 0 0
    34 rows selected.
    please help to fix this
    thank you

    check whether there is any gap using the V$ARCHIVE_GAP view or using the V$ARCHIVED_log on the primary.. Appears that there is a gap...
    Thanks,
    Vishnu

  • Standby not applying log - DATAGUARD

    Hi pros and gurus,
    I have encountered a problem which is i don't know how to solve it is since every single log working just fine. I already done creating RMAN files and instantiate it later. But after i bring up standy for receiving logs from primary and apply it, nothing is happening. At the end of instantiate standby database, i got this error:
    RMAN 03015 error occurred in stored script Memory Script
    RMAN 06136 ORACLE error from auxiliary database
    ora-01180 cannot create data file 1
    ora-01110 data file 1 '.../system_1.dbf
    is this error affecting my replication? Please help me.

    syns wrote:
    Hi pros and gurus,
    I have encountered a problem which is i don't know how to solve it is since every single log working just fine. I already done creating RMAN files and instantiate it later. But after i bring up standy for receiving logs from primary and apply it, nothing is happening. At the end of instantiate standby database, i got this error:
    RMAN 03015 error occurred in stored script Memory Script
    RMAN 06136 ORACLE error from auxiliary database
    ora-01180 cannot create data file 1
    ora-01110 data file 1 '.../system_1.dbf
    is this error affecting my replication? Please help me.Can u paste the command which you are running on rman prompt with error message?
    Check alert log file ?
    Post the steps u are following ...
    --neeraj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Error in standby db while applying logs

    Hi,
    we have a manual standby db of version 9.2.0.6 on sun solaris
    in alert log file i found error in one og the log i.e Errors with log /arch/log/1_1817.dbf
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:33:03 2008
    Media Recovery Log /arch/log/2_1616.dbf
    Wed Oct 22 18:35:47 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:35:47 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:35:47 2008
    Media Recovery Log /arch/log/2_1617.dbf
    Wed Oct 22 18:36:50 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:36:50 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:36:50 2008
    Media Recovery Log /arch/log/1_1817.dbf
    Errors with log /arch/log/1_1817.dbf
    ORA-308 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:36:50 2008
    ALTER DATABASE RECOVER CANCEL
    Wed Oct 22 18:36:50 2008
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER CANCEL
    Wed Oct 22 18:37:38 2008
    alter database open read only
    Wed Oct 22 18:37:38 2008
    SMON: enabling cache recovery
    Wed Oct 22 18:37:38 2008
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication fo
    nd)
    Completed: alter database open read only
    Wed Oct 22 18:39:33 2008
    Errors in file /arch/dump/udump/icai_ora_25288.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
    003713], [4194306], [], []
    Wed Oct 22 18:39:45 2008
    Errors in file /arch/dump/udump/icai_ora_25288.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [1823949225], [0], [197
    003713], [4194306], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
    003713], [4194306], [], []
    003713], [4194306], [], []i want to konw the whether the system had applied the 1_1817.dbf logs or not if db server generates an error on one of the logs...
    looking for your reply...

    SQL> select * from v$log_history;
         RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
          3421  668092912          2       1613    1821523608 08-OCT-08   1822019922
          3422  668092971          1       1809    1821576072 08-OCT-08   1821777080
          3423  668093151          1       1810    1821777080 10-OCT-08   1822019918
          3424  668093340          1       1811    1822019918 11-OCT-08   1822282436
          3425  668284338          2       1614    1822019922 11-OCT-08   1822677394
          3426  668284525          1       1812    1822282436 13-OCT-08   1822526199
          3427  668284721          1       1813    1822526199 14-OCT-08   1822781536
          3428  668801898          2       1615    1822677394 15-OCT-08   1823381495
          3429  668801993          1       1814    1822781536 15-OCT-08   1823106551
          3430  668802398          1       1815    1823106551 17-OCT-08   1823381490
          3431  668802577          1       1816    1823381490 18-OCT-08   1823923486
         RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
          3432  668802783          2       1616    1823381495 18-OCT-08   1823814529
          3433  668802947          2       1617    1823814529 20-OCT-08   1824079514
    453 rows selected.
    SQL>so here we can see that there is not recid for 1817 sequence that has been corrupted ,so now does it mean that archived have not been applied to the stanby database.....
    SQL> SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT FROM
      2  V$ARCHIVED_LOG R, V$LOG L WHERE
      3  R.DEST_ID=1 AND L.ARCHIVED='YES';
    LAST_SEQ_RECD LAST_SEQ_SENT
    ------------- -------------Edited by: user00726 on Oct 23, 2008 3:21 AM

  • 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

  • Files are not applying in Stand by server.

    Hi All,
    We are getting the bellow error in standby server while applying log files.
    Media Recovery Log /oracle/DB7/saparch/DB7arch1_97211_627008903.dbf
    Errors with log /oracle/DB7/saparch/DB7arch1_97211_627008903.dbf
    ORA-310 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/DB7/saparch/DB7arch1_97211_627008903.dbf'  ...
    Fri Feb 18 13:09:56 2011
    ALTER DATABASE RECOVER CANCEL
    ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
    This error we are facing after sudden reboot/crash of the server.  Upto DB7arch1_97210 files successfully applied.
    Please help on this.
    Regards,
    Venkata.

    Make the all archivelogs available in archive directory and use below command (After mounting your DB in standby mode).
    recover standby database
    Update this message with the result after issuing above command (Paste the last 10 lines of your controlfile)
    Regards,
    Nick Loy

  • Standby  can't  received  logs  from  primary after  upgrade 10.2 to  11.2

    Hi
    I have counter problem on standby after upgrade from 10.2.0.1 to 11.2.0.2.The standby can not received logs from primary when look on dataguard log is shown as follows.it seem log transport service timeout before completion send logs to standby server
    D MON_PROPERTY operation completed
    2012-03-20 15:09:14.522 DMON: Timeout posting message to database 2 after having waited for 0 seconds, killing NSV1 (PID=4672)
    2012-03-20 15:09:15.524 02001000 622551633 DMON: failed to forward op CTL_GET_STATUS to site standby with error ORA-16662
    2012-03-20 15:09:15.524 02001000 622551633 DMON: Database PRIMARY returned ORA-16662
    2012-03-20 15:09:15.524 02001000 622551633 for opcode = CTL_GET_STATUS, phase = NULL, req_id = 1.1.622551633
    2012-03-20 15:09:15.525 02001000 622551633 DMON: CTL_GET_STATUS operation completed
    2012-03-20 15:09:48.676 RSM detected log transport problem: log transport for database 'standby' has the following error.
    2012-03-20 15:09:48.676 ORA-16198: Timeout incurred on internal channel during remote archival
    2012-03-20 15:09:48.677 RSM0: HEALTH CHECK ERROR: ORA-16737: the redo transport service for standby database "standby" has an error
    2012-03-20 15:09:48.789 00000000 622551634 Operation HEALTH_CHECK canceled during phase 2, error = ORA-16778
    2012-03-20 15:09:48.790 00000000 622551634 Operation HEALTH_CHECK canceled during phase 2, error = ORA-16778
    Please anyone have ideas
    thanks
    kind regard
    Salutary(bob)
    Edited by: 826034 on Mar 20, 2012 5:31 AM

    826034 wrote:
    SQL> select severity, error_code,message,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') from v$dataguard_status where dest_id=2;
    Error              16198
    WARN: ARC0: Terminating pid 31868 hung on an I/O operation
    +20-MAR-2012 13:29:32+
    SEVERITY      ERROR_CODE
    MESSAGE
    TO_CHAR(TIMESTAMP,'D
    Error              16198
    WARN: ARC0: Terminating pid 32182 hung on an I/O operation
    +20-MAR-2012 13:34:37+
    Error              16198
    WARN: ARC0: Terminating pid 32393 hung on an I/O operation
    SEVERITY      ERROR_CODE
    MESSAGE
    TO_CHAR(TIMESTAMP,'D
    +20-MAR-2012 13:39:42+
    Error              16198
    WARN: ARC0: Terminating pid 32620 hung on an I/O operation
    +20-MAR-2012 13:44:47+
    Error              16198
    SEVERITY      ERROR_CODE
    MESSAGE
    TO_CHAR(TIMESTAMP,'D
    WARN: ARC0: Terminating pid 474 hung on an I/O operation
    +20-MAR-2012 13:49:52+
    Error              16198
    WARN: ARC0: Terminating pid 696 hung on an I/O operation
    +20-MAR-2012 13:54:57+
    thanks
    regard
    SalutaryCheck this thread, it may helpful.. looks similar issue log shipping problem after upgrade to 11.2.0.2

  • 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

  • Archive log registered,but showing as not applied in standby db + oracle 9i

    Hi all,
    In my standby database some of the archive log files are not applied.found through the following command
    SQL > select sequence#,applied from v$archived_log where applied='NO';
    sequence# APP FIRST_TIME
    18425 NO 05-FEB-10
    but when try to register manually
    SQL > alter database register logfile '/disk12/arch/A00123000018425.arc';
    ERROR at line 1
    ORA-16089:archive log has already been registered.
    "recover standby database" also asking for the new archive file. how will i apply that?
    any solutions?

    user11919409 wrote:
    I have did that so many times from 05-feb-10 onwards.
    even then only one archive gap???
    or only one is not applied? if yes may be archive file which exist at standby may be corrupt try to restore it from backup and recover.
    also check for some clues at logs at standby and primary.. what actually happen. if archive gap is huge and you have all archvies then you may have to do manual recovery then keep it back to auto recovery mode.
    Hope that may help you.
    Anil Malkai

  • 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

Maybe you are looking for

  • Cant install win.8.1 on a older samsung NetBook w. 11" screen

    when going to windows store for a free upgrade it gives error message" screen resolution to low." and I cant take installation further then it stops and I cant change screen resolution  of course then its low.  The netbook its a 11" 

  • HP Officejet Pro 8600, bad size for print from Corel suite product

    When i try to print a work with Corel Photo-Paint, or Corel Draw, I can't print to the same dimension that I see on the print preview of the program. For example if I want to print a photo in A4 format, the printer get out a sheet with a full print o

  • What do you do with a group of random pics + general questions

    I am a potential new user of iPhoto 6 and Mac. I have been reading through the hundreds of threads for iPhoto. I have a collection of over 12000 images (some on a pc, some on cd, and others on floppy). I have yet to get the entire catalog organized t

  • Issue in workbench integration with Dev studio on unix machine

    Hi, I am trying to integrate my workbench on unix machine with dev studio on windows machine. To do so, I did the following: 1. created a new application in dev studio 2. In dev studio - Tools - Workbench settings I gave the host and port of my unix

  • Error message at adobe edge start-up.

    I get an error message when i open or create a new project. I've looked on the internet for a solution but I couldn't find one that has my error in it. I've included the message below, as you can see I've barely done anything in the new file except i